anonymous/android_bootable_recovery - Team Win Recovery Project (TWRP)

	Commit message (Collapse)	Author	Age	Files	Lines
*	fix adb sideload	that	2015-01-04	1	-1/+1
\| \| \| \| \| \| \| \| \| \|	- "Cancel" button handling requires another thread - simplify handling of child pid - merge duplicated code for reinjecting TWRP after installation - fix error that showed on host PC after sideload finished - fix problem where adbd sometimes does not stop correctly Change-Id: I536877f024b606756c6a3289c6ddfdba423a60d6
*	Update adb sideload feature	Ethan Yonker	2014-11-08	1	-0/+2
\| \| \| \|	Change-Id: Ib503d0e87434e1a28430779302d6565211c26592
*	Move all AOSP code out of recovery binary	Dees_Troy	2013-04-04	1	-2/+2
\| \| \| \| \| \|	Improves license compatibility between GPL and Apache Change-Id: I2b165aa575bb6213af6b07936f99610c113443f0
*	support "sideload over ADB" mode	Doug Zongker	2012-01-10	1	-0/+24
	Rather than depending on the existence of some place to store a file that is accessible to users on an an unbootable device (eg, a physical sdcard, external USB drive, etc.), add support for sideloading packages sent to the device with adb. This change adds a "minimal adbd" which supports nothing but receiving a package over adb (with the "adb sideload" command) and storing it to a fixed filename in the /tmp ramdisk, from where it can be verified and sideloaded in the usual way. This should be leave available even on locked user-build devices. The user can select "apply package from ADB" from the recovery menu, which starts minimal-adb mode (shutting down any real adbd that may be running). Once minimal-adb has received a package it exits (restarting real adbd if appropriate) and then verification and installation of the received package proceeds. Change-Id: I6fe13161ca064a98d06fa32104e1f432826582f5