Cm 11.0 #51
Open
Cm 11.0 #51
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original discussion here: http://review.cyanogenmod.org/45559 Patchset 2: really remove the option Patchset 3: fix options that I broke on ps2 Signed-off-by: Michael Bestas <mikeioannina@gmail.com> Change-Id: I54877a24444c24a296c8c044efd977f30cc66de4
Also: Cleanup leftovers from previous poweroff option Always ensure a clean reboot (Thanks to PhilZ for his implementation) Bootloader option defaults to "bootloader" (fastboot mode), it can be overriden by defining "ro.bootloader.mode=download" prop for samsung download mode We leave reboot to bootloader option always enabled, that way we can override the get_filtered_menu_selection bug that breaks the order of the options when NULLifying menu options. Signed-off-by: Michael Bestas <mikeioannina@gmail.com> Change-Id: I6d674b37ab41ab342b105993719277360b4707e4
Change-Id: Ic5716e5f2c311406bc6384e63fb0f217113e6eeb
the releasetools want this now Change-Id: Ibc3cdbc8f5f8022bf51479a4702d1d0d043f70a9
v1 is the old recovery.fstab format that everybody is still using. Devices using v2 should set RECOVERY_FSTAB_VERSION=2 in their board files Change-Id: Ie7221f110ecc594f6f92973d2c27da10f62b6431
Original discussion here: http://review.cyanogenmod.org/45559 Patchset 2: really remove the option Patchset 3: fix options that I broke on ps2 Signed-off-by: Michael Bestas <mikeioannina@gmail.com> Change-Id: I54877a24444c24a296c8c044efd977f30cc66de4
Also: Cleanup leftovers from previous poweroff option Always ensure a clean reboot (Thanks to PhilZ for his implementation) Bootloader option defaults to "bootloader" (fastboot mode), it can be overriden by defining "ro.bootloader.mode=download" prop for samsung download mode We leave reboot to bootloader option always enabled, that way we can override the get_filtered_menu_selection bug that breaks the order of the options when NULLifying menu options. Signed-off-by: Michael Bestas <mikeioannina@gmail.com> Change-Id: I6d674b37ab41ab342b105993719277360b4707e4
Change-Id: I86a280088ee8767e02ba51b72f4d011cf4658f6f
Change-Id: I86a280088ee8767e02ba51b72f4d011cf4658f6f
Change-Id: Idce9a6d4ca18ddc9b49029024c26bc114f6d3c15
Change-Id: Ibb9be9e764d0ccb842a26a0795a0bb6cb6113b58
Change-Id: Ib5e3df51fa7a383f3699968e899e06d579480564
Change-Id: Ie7e8bfea57bed207c3c2d57bf3cd23daf6cd4c20
See http://review.cyanogenmod.org/#/c/46642/ for why this is necessary. Change-Id: Ib97484755569fcafc062d3c39b2841581987ca72
Change-Id: Ie68daba5e014dff0c4998da85576f35abe8ad270
Add an option to verifier_test to load keys from a file, the way the recovery does. Conflicts: verifier_test.c Change-Id: Icba0e391164f2c1a9fefeab4b0bcb878e91d17b4
Extends the last_log mechanism to save logs from the last six invocations of recovery, so that we're more likely to have useful logs even if the device has repeatedly booted into recovery. Conflicts: recovery.c Change-Id: I08ae7a09553ada45f9e0733fe1e55e5a22efd9f9
This reverts commit 1a6c91f. Change-Id: I5fb1105bfb640f0552ddcc4a99b6f98487a1c946
Voldmanaged volumes use sysfs path instead of device path which is not supported by recovery, so a separate entries for /sdcard and /external_sd are required. We ignore these volume so we don't show the menu for "mount /storage/sdcard0", etc. Change-Id: I6bf26e0ad3fb59579c986cf5537f9e70448891e9
This commit allows the wipe data/factory reset option to recognize the .one_confirm or .no_confirm files in the clockworkmod folder. Signed-off-by: Michael Bestas <mikeioannina@gmail.com> Change-Id: Ib0f82b4448e3b9df95a5e59a49428f3e9da58578
Taken from PhilZ Touch recovery Signed-off-by: Michael Bestas <mikeioannina@gmail.com> Change-Id: I079617fc32f8ad0aea754a60898cd4f9cc482524
…lesystem corruption if some data is not sync when mount sdcard Change-Id: Ib3ad32842fcbf3b058c986df6901c7744bd5cf1f
Change-Id: I762269d696a194889e74c101b9338920e924ebb5
Change-Id: I00556341b746f186f424ebe46c94fd02f10e6536
Useful for command line processes so they can determine whether ui functions are possible. Change-Id: I2e1b8af39806973ae11eaed5bbdb1f3b6ddc7b13
If 'nandroid restore' is run from the command line, prompts are not possible (thanks to Phyto Wardt for pointing this out). Abort with a listing of files that are missing from directory or nandroid.md5. Change-Id: I527ffeafc5da50e7878ddc103f4fb55218632ce1
Currently retains swipe-only touch handling, but all elements are in place to support taps in the future, if desired. Change-Id: I276111f767ade32717c859c62d1d9f046ffa161c
* Adds basic support for capacitive keys (virtual keys) * Only enabled if BOARD_RECOVERY_SWIPE is enabled Change-Id: I13ade22991880e4fb5c5c71639660e1563e95a89
In the mounts and storage menu: * Reduce the complexity of if/elses for /data/media and UMS specific menu entries with a simple struct * Only show UMS mount option if vold managed volumes are available and usb-otg is not in use. Vold does not have any mechanism to determine if a managed volume is usb-otg, so we have to rely on string comparison to the volume label. "usbdisk" is by far the most common label, so this should cover most devices just fine. Change-Id: I8a203a614e1c603c32a06b1afb77834cc4cd51ce
Notable changes since 6.0.4.9: * Segfault fixes for command line nandroid backup/restore * Optimizations to progress thread so it doesn't get overloaded with screen updates (this significantly improves backup/restore speed) * Fixes for command line nandroid backups of vold volumes * Correctly update background image for errors and finished processes * Allow selective restore of more than one partition at a time * New MD5 calculator only verifies checksums of partition(s) selected for restore and warns you when files or checksums are not found * New touch code supports a wider variety of devices for swipe control and virtual (capacative touch) keys are now supported * Only show Mount USB storage option if possible Change-Id: I813dce9d31ce2aa445a512026a210a558cab39e6
When set_bootloader_message_block() is called, it fopens /misc in write binary mode, wiping all contents other than what is being written. The bootloader msg structure is only 1024+32+32 bytes, so some manufacturers store more than just a bootloader msg on /misc. fopen in read+append mode so that only the bootloader msg is written and the rest of the partition is left untouched. Change-Id: I2d2fbdf067282744864a19d404ca7dc12f688a98
Use board define BOARD_RECOVERY_BLDRMSG_OFFSET with a decimal integer to define a custom offset where the bootloader message should be read/written. Change-Id: Id13a23dd41bb7d907b96d657b8e21eb839dfeaa9
Otherwise everything is left running in the kernel domain when booting recovery. Change-Id: Ie3d86547d5be0b68dd1875a97afe1e00fc3e4da1 Signed-off-by: Stephen Smalley <sds@tycho.nsa.gov>
Change-Id: Ia5662f4543e4fbb32b02216b64a2f261e22beb25
When adbd runs as root, it should transition into the su domain. This is needed to run the adbd and shell domains in enforcing on userdebug / eng devices without breaking developer workflows. Use the new device_banner command line option. Change-Id: Ib33c0dd2dd6172035230514ac84fcaed2ecf44d6
Change-Id: Ia1f34a17ae582575f8cd3514ed7bc015b0a5006e
Use intptr_t/uintptr_t to cast between pointer and int to allow building with -Werror=pointer-to-int-cast and Werror=int-to-pointer-cast turned on. Cast to char* instead of unsigned int for pointer arithmetic. Conflicts: minui/graphics.c Change-Id: Ia862306fdcca53866b330e8cf726f3d62f2248a0
The "--shutdown_after" option causes recovery to power down the device on completion rather than rebooting. Removes the last vestiges of the "--previous_runs" argument, which doesn't seem to be used for anything. Conflicts: recovery.c Change-Id: I465eda2ef59d367e2b1c79a8dc69831263c69a4d
Patches with control data tuples with negative numbers in the first and/or second can cause bspatch to write to arbitrary locations in the heap. Change-Id: I8c5d81948be773e6483241131d3d166b6da27cb8
A return here leaves adb sideload in a permanent loop. An exit is more appropriate for this error. Change-Id: I80fb8abae4f6378833aa75f9eaf7ec1acd44b274 Signed-off-by: Ethan Yonker <ethanayonker@gmail.com>
The vold secontext doesn't have enough permissions to allow formatting volumes. CWM uses minivold directly for this purpose, so go ahead and let it run in the recovery domain to give it all the permissions needed. Change-Id: I2ca8e5895bd8cba5ffc9f0758264b3f0fbf38943
Discard type A MT slots if type B MT tracking ID sent: Some devices send an initial ABS_MT_SLOT event before switching to type B events, so discard any type A state related to slot. Track whether ABS_MT_TRACKING_ID was seen in the current sequence to differentiate between vkeys and hardware keys. Change-Id: I7ca3bfa4bd82d05ef7f7a208e954898b88bf3865
These were attempts to write partitions "conservatively" in hopes of fixing the problems with writing the radio partition on Nexus 4. They didn't work (a kernel patch was needed), but got left in. They make writing of partitions unnecessarily slow (ie, we really shouldn't need to sync() after every 4kb). Roll back most of them, but leave the verification read-back in. Change-Id: I94badc0979e88816c5aa0485f6316c02be69173c
If, for whatever reason, a voldmanaged volume had a different filesystem than the one defined in the fstab, then this filesystem was kept when formatting. Change the logic to use the filesystem defined in the fstab when available. Change-Id: Iffbb5dc42838c1585c21f3ffa66b16921a16abd5
Including BOARD_RECOVERY_BLDRMSG_OFFSET in BOARD_RECOVERY_DEFINES turns the define into a string. We need BOARD_RECOVERY_BLDRMSG_OFFSET to be an int. Change-Id: Ib75dec0123e6fb318c4c8192645485683c6a5075
this is QCOM only and there is now already a check for that. Change-Id: I882d013e8e978ca02abceee2b56d0c9a3017814c
In kernel(3.10) USB ADB gadget driver is removed. Using Functionfs for USB adb gadget. Android recovery uses a stripped down version of adb command for sideload only. It's missing the ffs function support, so add the ffs support to allow sideload command to work b/12608946 Change-Id: I4ad024723dfc5bdb544548391f99637c390b171e Signed-off-by: Pierre Couillaud <pierre@broadcom.com>
In kernel 3.10, f_adb has been removed and adbd can use functionfs instead. Mount functionfs on boot for adbd. On older kernels, mount will fail silently and adbd will revert to f_adb. Change-Id: I5db57aaf35b35859ea88c7d0e0661d8c553e5811
Notable changes since 6.0.5.0: * Fix /misc partition erase on recovery start * Set SELinux contexts for init and services * Minor touch updates * Better vold formatting logic * Compatibility updates for adb and 3.10 kernels Change-Id: Ie6035fb706b50be1b78ed09c237644fdd091cce8
Change-Id: Id358db393f4f945b3f5c91419827666f3e70127e
We want to include a suite of tools and symlinks with recovery. This was previously done with a hack in build/core/Makefile. That is rather unorthodox. Instead, use LOCAL_ADDITIONAL_DEPENDENCIES to declare the things we want to include. See also http://review.cyanogenmod.org/74244 Change-Id: Ib054f2bc8aa85cb3df9cbeba3f457ea74dd3ed98
Provide a means to include device-specific recovery modules that need to be built (i.e. not pre-built). A list of recovery modules can be specified by a device with: TARGET_RECOVERY_DEVICE_MODULES := rec_mod_one rec_mod_two Change-Id: Id28a41185b332a074cd15bd5c63e26bf284663d5
bug: 22953624 Change-Id: Ifcc17e39433ac91ca41da5d336fb3006dfbb65a8
Change-Id: I0339664623c8c665f3859175bfdbf94189e592f0
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.