|
|
Gathering information to produce a partition layout file is trivial. It is sometimes revealed somewhere under the `/sys/devices` by linux kernel. But this is not always the case. ROM and kernel developers, would, most of the time, figure this out and share this information in development threads on forums like XDA. Other times, it is easiest to obtain a copy of recovery.fstab used by stock, CWM, TWRP and other recoveries. This file is present in the recovery ramdisk and thus can be obtained from someone who has physical access to the device. Alternatively, this file is available at device repositories on Github and other places. A simple search on Google for `android_device_oem_device`, where `oem` is the name of device manufacturer such as `samsung`, `sony`, `motorola`, `lge`..., and `device` is the code name / technical name of the device such as `mako` for `Google Nexus 4` and `m0` for `Samsung Galaxy S III`.
|
|
Gathering information to produce a partition layout file is trivial. It is sometimes revealed somewhere under the `/sys/devices` by linux kernel. But this is not always the case. ROM and kernel developers, would, most of the time, figure this out and share this information in development threads on forums like XDA. Other times, it is easiest to obtain a copy of recovery.fstab used by stock, CWM, TWRP and other recoveries. This file is present in the recovery ramdisk and thus can be obtained from someone who has physical access to the device. Alternatively, this file is available at device repositories on Github and other places. A simple search on Google for `android_device_oem_device`, where `oem` is the name of device manufacturer such as `samsung`, `sony`, `motorola`, `lge`..., and `device` is the code name / technical name of the device such as `mako` for `Google Nexus 4` and `m0` for `Samsung Galaxy S III`.
|
