| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | recovery: deprecate check for ro.build.system_root_image | Mark Salyzyn | 2018-10-11 | 1 | -3/+4 |
| | | | | | | | | | | If there is a "/system" in the fstab, then can not be a system as root image. Test: compile Bug: 109821005 Change-Id: I2c852dcbdcf6de437d39039937799feeef949516 | ||||
| * | Recovery image is self-contained | Jiyong Park | 2018-06-07 | 1 | -11/+3 |
| | | | | | | | | | | | | | | | | | | | | | | | | Now recovery mode is self-contained, which means we don't need to mount system.img to run shell, etc. What is needed in recovery mode is all in the recovery ramdisk image. Since we no longer use /system as the mount point for the system.img, this allows us to have identical filesystem layout as the system.img. Executables and libs are installed to /system/bin and /system/lib. Right now, we only have adbd, sh, toybox in /system/bin but will move static executables from /sbin to /system/bin as soon as they are converted to dynamic executables. system.img is mounted to /mnt/system instead. Bug: 63673171 Test: `adb reboot recovery; adb devices` shows the device ID Test: `adb root && adb shell` and then $ lsof -p `pidof adbd` shows that libm.so, libc.so, etc. are loaded from the /lib directory. Change-Id: I801ebd18f3e0a112db3d9a11e4fbb4e49181652a | ||||
| * | recovery: add --fsck_unshare_blocks option for adb remount | David Anderson | 2018-05-30 | 1 | -0/+163 |
| Allow "adb remount" on deduplicated filesystems to reboot into recovery and run e2fsck to undo deduplication. The e2fsck binary is copied from the system partition into tmpfs, and the system partition is unmounted so e2fsck can run safely. Bug: 64109868 Test: recovery with --fsck_unshare_blocks; adb remount Change-Id: I7558749b018b58f3c4339e51a95831dbd5be1ae3 | |||||
 |
index : anonymous/android_bootable_recovery | |
| Team Win Recovery Project (TWRP) | mirror |
| summaryrefslogtreecommitdiffstats |