This is needed for device encryption to work properly (there must
be space for a 16 KB footer at the end of the partition, which is
usually specified by the length option).
And yes, the old signature of make_ext4fs was wrong, but worked
anyway because the related header was not included and the compiler
let it pass an as implicit delcaration.
Change-Id: Ied7ec70bebc120cc2917771f59eeaeb7ea76bf8d
-force /data as backup_path if volume for /sdcard is null and the same is true
Change-Id: I927b723cde5b519d81402c6d841f2424627253e8
Conflicts:
nandroid.c
Could also be used to report last lines from log on error.
Signed-off-by: Tanguy Pruvot <tanguy.pruvot@gmail.com>
Change-Id: I3d9e51f4e81e48f20120e2449ccde651efae8d07
There is a max length for system property names at 32 characters. The
old recovery property name was over this length.
Renamed the property to one much shorter so it is read properly.
Change-Id: Iecadd1218a64cab0c4fb94c5e910b920217580f1
The change switches is_safe_to_format() from a hard coded list
to a list that can be overwritten by system property.
Change-Id: Ie536044a912c3e88462831851d288a60fdc30e2b
For the Power menu,
frameworks/base/core/jni/android_os_Power.cpp#L180
already uses TARGET_RECOVERY_PRE_COMMAND if
TARGET_RECOVERY_PRE_COMMAND is defined in the
BoardConfig.mk for a device to make a system() call before
calling __reboot() for recovery. This commit adds
the same thing to the other places that we know we are
getting into recovery using __reboot().
Change-Id: Ifd0394fed1e87b63d80d95e0e2a049004518e27e
Stock sd-card that ships with LG-P500 formatted with no partitions.
This issue can be handled with device2 in recovery.fstab.
But UMS didn't.
We will try to mount second device (if it was defined) if first failed.
Change-Id: Ia8b58b9fdfa3e63f703a1dd5870cb76936cec88e
Don't allow formatting of special partitions like radio, bootloader,
or misc. No sense in formatting recovery from recovery either dawg.
Change-Id: I0f935aad103574b17be237993730afaeae623871
This is checked at runtime to see if /boot is a mountable parition (i.e not mtd), if so it adds an entry into /etc/fstab.
This will allow us to mount /boot from an edify script and push certain files without completely imaging the parition which can contain other files such as the bootloader (u-boot), and recovery kernel and ramdisks as is the case with the encore (NookColor)
Test on NookColor and passion. Correct entry was added to the NC and not added to the passion as expected.
Change-Id: I9850dee866b77653bf400bb5193905e55da3f25f
