android_device_oneplus_dre/rootdir/etc/init.recovery.qcom.rc

import /init.recovery.target.rc

on fs
    wait /dev/block/platform/soc/${ro.boot.bootdevice}
    symlink /dev/block/platform/soc/${ro.boot.bootdevice} /dev/block/bootdevice

on init
    setprop sys.usb.configfs 1

on property:ro.boot.usbcontroller=*
    write /sys/class/udc/${ro.boot.usbcontroller}/device/../mode peripheral
sm8250-common: Include device specific init recovery rc script Change-Id: I7750ff22585a7b760d8b4d6f771fd7fe22db1e2e 2021-01-09 08:00:52 -05:00			`import /init.recovery.target.rc`

sdm845-common: Add recovery support Change-Id: Id44d9793e0ea5fd1359f661ec6a9a1784514dbd2 2018-07-02 08:15:39 -04:00			`on fs`
			`wait /dev/block/platform/soc/${ro.boot.bootdevice}`
			`symlink /dev/block/platform/soc/${ro.boot.bootdevice} /dev/block/bootdevice`

			`on init`
			`setprop sys.usb.configfs 1`
sm8350-common: init.recovery.qcom.rc: Force USB to peripheral mode On some newer platforms USB relies on PMIC to notify it of cable connection status, but the PMIC driver has relocated to ADSP FW. Since ADSP is not expected to be loaded in recovery or fastbootd mode, USB may not get notified and hence won't start up. Force the USB to start in peripheral mode since the whole purpose of recovery/fastbootd is to interact with a USB connection anyhow. Currently the command assumes that there is a sysfs "mode" param located at /sys/class/udc/${ro.boot.usbcontroller}/device/.. which is true for dwc3-msm based driver on most QC SoCs. Change-Id: I5f7a01defdf987dbf4bd48f77bc70344c212a623 2020-04-02 15:17:07 -04:00
			`on property:ro.boot.usbcontroller=*`
			`write /sys/class/udc/${ro.boot.usbcontroller}/device/../mode peripheral`