android/android_bootable_recovery
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
1c50ff29e6
android_bootable_recovery/etc/init.rc

57 lines
1.4 KiB
Plaintext
Raw Normal View History

recovery: Add ueventd service Change-Id: Iad448bc1608f88c5db2108475f35b88ea2877b07
2010-05-14 20:42:20 +00:00
on early-init
start ueventd
auto import from //depot/cupcake/@135843
2009-03-04 03:28:42 +00:00
on init
export PATH /sbin
export ANDROID_ROOT /system
export ANDROID_DATA /data
export EXTERNAL_STORAGE /sdcard
symlink /system/etc /etc
Add support to mount /boot for systems that have a mountable /boot. 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
2011-01-28 20:39:10 +00:00
mkdir /boot
auto import from //depot/cupcake/@135843
2009-03-04 03:28:42 +00:00
mkdir /sdcard
fix sd-ext backup and restore. Change-Id: I346724f231bb29df2c0fa833df420620ab1be1b4
2011-01-16 10:33:04 +00:00
mkdir /sd-ext
mkdir /datadata
Added options for an internal SD card to be handled by recovery. Exable uses in BoardConfig.mk: BOARD_HAS_SDCARD_INTERNAL := true BOARD_SDCARD_DEVICE_INTERNAL := /dev/block/mmcblk3p1 Setting BOARD_SDCARD_DEVICE_SECONDARY to the same value as BOARD_SDCARD_DEVICE_INTERNAL will allow the device to "fall back" to the internal SD card for other actions. Change-Id: I2cf8ab4b1d385ac714f5b7416b915d059033d94b
2010-12-12 03:52:06 +00:00
mkdir /emmc
auto import from //depot/cupcake/@135843
2009-03-04 03:28:42 +00:00
mkdir /system
mkdir /data
mkdir /cache
mount /tmp /tmp tmpfs
on boot
ifup lo
hostname localhost
domainname localdomain
class_start default
recovery: Add ueventd service Change-Id: Iad448bc1608f88c5db2108475f35b88ea2877b07
2010-05-14 20:42:20 +00:00
service ueventd /sbin/ueventd
critical
auto import from //depot/cupcake/@135843
2009-03-04 03:28:42 +00:00
service recovery /sbin/recovery
service adbd /sbin/adbd recovery
Set adbd to be disabled by default in recovery Change-Id: I74fa6edc4b001247b20be52e8301d18407fede2c
2010-06-28 16:01:22 +00:00
disabled
auto import from //depot/cupcake/@135843
2009-03-04 03:28:42 +00:00
init.rc: Simplify logic for starting adbd in recovery Always start adbd if ro.debuggable=1 rather than basing it on user preference in persistent system properties. Use new D001 product ID, which I just allocated for "android recovery mode" Change-Id: I6f1eac5257eaad2e538c0a8dd549ad89219efa3e Signed-off-by: Mike Lockwood <lockwood@android.com>
2011-06-29 14:22:04 +00:00
# Always start adbd on userdebug and eng builds
Always run adbd as root in recovery. At present, invoking "adb shell" while in recovery results in: - exec '/system/bin/sh' failed: No such file or directory (2) - "adb shell" should invoke /sbin/sh, but cannot as /sbin and /sbin/recovery lack other-user execute permission. Invoking "adb root" to restart adbd as root _does_ work, however this behavior may not be intuitive to users who encounter the above error. The solution implemented here is to always run adbd as root in recovery, so it has permission to run /sbin/sh. Furthemore, user shells in recovery are not particularly useful and "su" doesn't exist, thus "adb root" is likely to be invoked anyways. Change-Id: Iaaa25090e85d970e9a076fef068f5fae8202ab0b
2012-01-26 21:05:56 +00:00
# In recovery, always run adbd as root.
init.rc: Simplify logic for starting adbd in recovery Always start adbd if ro.debuggable=1 rather than basing it on user preference in persistent system properties. Use new D001 product ID, which I just allocated for "android recovery mode" Change-Id: I6f1eac5257eaad2e538c0a8dd549ad89219efa3e Signed-off-by: Mike Lockwood <lockwood@android.com>
2011-06-29 14:22:04 +00:00
on property:ro.debuggable=1
Fix starting adb in recovery mode Change-Id: I8444f44d3194ff16ce54121633d5b255231393f5 Signed-off-by: Mike Lockwood <lockwood@android.com>
2011-06-19 06:52:01 +00:00
write /sys/class/android_usb/android0/enable 0
init.rc: Simplify logic for starting adbd in recovery Always start adbd if ro.debuggable=1 rather than basing it on user preference in persistent system properties. Use new D001 product ID, which I just allocated for "android recovery mode" Change-Id: I6f1eac5257eaad2e538c0a8dd549ad89219efa3e Signed-off-by: Mike Lockwood <lockwood@android.com>
2011-06-29 14:22:04 +00:00
write /sys/class/android_usb/android0/idVendor 18D1
write /sys/class/android_usb/android0/idProduct D001
write /sys/class/android_usb/android0/functions adb
Always run adbd as root in recovery. At present, invoking "adb shell" while in recovery results in: - exec '/system/bin/sh' failed: No such file or directory (2) - "adb shell" should invoke /sbin/sh, but cannot as /sbin and /sbin/recovery lack other-user execute permission. Invoking "adb root" to restart adbd as root _does_ work, however this behavior may not be intuitive to users who encounter the above error. The solution implemented here is to always run adbd as root in recovery, so it has permission to run /sbin/sh. Furthemore, user shells in recovery are not particularly useful and "su" doesn't exist, thus "adb root" is likely to be invoked anyways. Change-Id: Iaaa25090e85d970e9a076fef068f5fae8202ab0b
2012-01-26 21:05:56 +00:00
#write /sys/class/android_usb/android0/enable 1
Add missing commands to recovery init.rc Wrote some missing items in recovery, most notably the serial number so that it shows up correctly on adb. Change-Id: If430c0b78191c8d77f781aa605b5081571451775
2011-07-07 20:21:24 +00:00
write /sys/class/android_usb/android0/iManufacturer $ro.product.manufacturer
write /sys/class/android_usb/android0/iProduct $ro.product.model
write /sys/class/android_usb/android0/iSerial $ro.serialno
Always run adbd as root in recovery. At present, invoking "adb shell" while in recovery results in: - exec '/system/bin/sh' failed: No such file or directory (2) - "adb shell" should invoke /sbin/sh, but cannot as /sbin and /sbin/recovery lack other-user execute permission. Invoking "adb root" to restart adbd as root _does_ work, however this behavior may not be intuitive to users who encounter the above error. The solution implemented here is to always run adbd as root in recovery, so it has permission to run /sbin/sh. Furthemore, user shells in recovery are not particularly useful and "su" doesn't exist, thus "adb root" is likely to be invoked anyways. Change-Id: Iaaa25090e85d970e9a076fef068f5fae8202ab0b
2012-01-26 21:05:56 +00:00
#start adbd
setprop service.adb.root 1
auto import from //depot/cupcake/@135843
2009-03-04 03:28:42 +00:00
init.rc: Simplify logic for starting adbd in recovery Always start adbd if ro.debuggable=1 rather than basing it on user preference in persistent system properties. Use new D001 product ID, which I just allocated for "android recovery mode" Change-Id: I6f1eac5257eaad2e538c0a8dd549ad89219efa3e Signed-off-by: Mike Lockwood <lockwood@android.com>
2011-06-29 14:22:04 +00:00
# Restart adbd so it can run as root
fix adb root in recovery recovery's init.rc was missing lines that made adb root work. Change-Id: I300e6997e3b5cb9c7b542b2012eed61deb2550f1
2011-06-23 22:30:34 +00:00
on property:service.adb.root=1
write /sys/class/android_usb/android0/enable 0
restart adbd
write /sys/class/android_usb/android0/enable 1
Reference in New Issue Copy Permalink