GitLab

Change-Id: I7dd9b5265c03de48075d0ddb44dc2bab7d75bbe8

If TW_DEVICE_SPECIFIC_VERSION is set in BoardConfig, it will
override the TW_VERSION_STR which is set in recovery/variables.h

Change-Id: I9aaaf27ce0dcd48963dbd663a2864a2fdbcecf72

Add mount_shim.sh to the list of files to copy.

MultiROM support: Add phablet folder

MultiROM-support: Fix mrom-cp_xattrs Android.mk for proper relink

* Revert: Properly build cp_xattrs and ls_xattrs (reverted from commit e1de1455)
* Revert: Re-link bbbootimg when buidling for multirom (reverted from commit 285a4cc1)
* Update multirom/cp_xattrs/Android.mk to build and relink
  cp_xattrs, ls_xatts, and bbootimg

Use restorecon from toolbox

Fix errors when compiling the TWRP android-6.0 branch on aosp 6.0 base

There is no stlport in SDK 23 (Marshmallow).
It links against libc++ instead.

This reverts commit 4ba06182.

Add MultiROM support to standard TWRP tree

Don’t rename umount to umount.bak while in secondary mode
* mount/umount is being handled by multiromedify.cpp
* it breaks CM13 (possibly others), due to variant_script.sh using
  umount, since it doesn’t find the correct one, it uses the one in
  /system/bin which breaks

* some installer-scripts are using "if range_sha1("/dev/block/platform/msm_sdcc.1/by-name/system",...) == "<sha1_hash>" then ..." which obviously breaks multirom rom flashing to secondary since this condition will always be false
* workaround -> remove the check and let it always be true

Squashed commit that allows MultiROM TWRP to be built from
within the standard TWRP environment.

MultiROM build flags and TARGET_RECOVERY_IS_MULTIROM
must be defined in device tree.

-------------------------------------

MultiROM-support:
- Move files to separate folder
  * Move primary multirom files to /recovery/multirom
  * Move multirom prebuilt files to /recovery/multirom/prebuilt
  * Move cp_xattrs folder used by multirom to /recovery/multirom/cp_xattrs
- Add Android.mk for mrom-prebuilt files
- Add Android.mk for mrom-cp_xattrs files
- Fix include paths
  * fix includes in multirom.h/c/hpp/cpp files to go to parent (main recovery folder)
- Add read_data function
  * Add read_data function used by multirom
  * Don't append to minzip, use a seperate file
- Remove deprecated 'flags' variable
  * Remove deprecated 'flags' in function call to mzExtractRecursive
  * Ref: https://github.com/omnirom/android_bootable_recovery/commit/9c0f5d6b348e37533bdcccf1166d6cbf1ca5c50b
- gui: Add multirom functions
  * objects.hpp - Add multirom action definitions
  * action.cpp - Add multirom actions and functions
    Note: TW_ORS_IS_SECONDARY_ROM code moved to openrecoveryscript.cpp
  * Add TARGET_RECOVERY_IS_MULTIROM flag to Android.mk
  * Reorder code changes for easier merging
- twrp-functions
  * Add functions needed by multirom
  * Reorder code changes for easier merging
- partition.cpp and partitionmanager.cpp
  * Add and embed multirom specific code
  * Reorder code changes for easier merging
- twrp.cpp
  * Add and embed multirom specific code
- variables.h
  * Add multirom specific defines
- Android.mk
  * update Android.mk for compartmentalized multirom
- gui: Update fileselector
  * Add <excludes> tag
  * Add support for multiple file extensions
- gui: Update listbox
  * Add support for dynamic <items> tag

Thanks @CaptainThrowback and @z31s1g for your help

set_perm and set_perm_recursive are no longer used. Delete.

(cherry picked from commit 08ef9a95)

Change-Id: I1bcc90ae19af9df4f0705496c5876987159f75ac (reverted from commit 46ab1b61)

For better or worse, here we go...

Change-Id: Ic1150b59e4ebf34f06c689b2a1b10ae691a027bd

Change-Id: I3159a2a0c37589f9472aba83b699840356da33a7

On at least one device I've tested (htc msm8960), setting the
brightness after gr_init() is necessary for the splash to show.

Note that at this point in the boot process, the settings file has
not yet been read, so tw_brightness has its default value of max
brightness. When settings are finally loaded, the correct brightness
is loaded for the GUI.

Change-Id: Ifc58c1dc80ed9e6f6b2a269a9bb6764038626c84

If a device has several LUN but only one storage volume TWRP
recognizes (e.g. lun0 for microsd and lun1 for emulated cdrom), then
avoid mounting the same partition twice by checking the mount point.

Change-Id: Ie23b88acca1818873792e9f65b73b125a15e4a5d

Conditionally run Add_MTP_Storage() after wipe if:
1) is wiped successfully
2) is storage (already implemented)
3) mount succeeds

Previous to this commit, Add_MTP_Storage() was called before mounting
storage, which fails. Mounting storage right after wipe should not be
a problem since Update_System_Details() does it anyways (and doesn't
complain if already mounted).

Change-Id: I8a5a78d5ac9181f3a9464dfe6b77284458f9868b

Change-Id: I05d0e8516686ba2610ea4b437c83323e84eb4595

Change-Id: I949fe4bd99d2a4471fef3e3967980a6163943e71

- PS2: generic xml instead android xml
- PS3: formatting

Change-Id: I4c552e172d670278ab2bad1897ceb89b7ee7fec2

Change-Id: I06ab906ed94b1aaea35c32494880bf85d7564d4d