View Single Post
Old 08-12-2021, 12:18 AM   #29
mergen3107
Wizard
mergen3107 ought to be getting tired of karma fortunes by now.mergen3107 ought to be getting tired of karma fortunes by now.mergen3107 ought to be getting tired of karma fortunes by now.mergen3107 ought to be getting tired of karma fortunes by now.mergen3107 ought to be getting tired of karma fortunes by now.mergen3107 ought to be getting tired of karma fortunes by now.mergen3107 ought to be getting tired of karma fortunes by now.mergen3107 ought to be getting tired of karma fortunes by now.mergen3107 ought to be getting tired of karma fortunes by now.mergen3107 ought to be getting tired of karma fortunes by now.mergen3107 ought to be getting tired of karma fortunes by now.
 
mergen3107's Avatar
 
Posts: 1,514
Karma: 5000046
Join Date: Feb 2012
Location: Cape Canaveral
Device: Kindle Scribe
As for modding the recovery image to include adb in recovery mode, I am stuck. Instructions I found refer to ramdisk contents, and as reported by Magisk this platform is ramdisk-less.

So currently I am not sure how to continue. After all, it is just a convenience of having adb enabled at boot and in recovery mode. Otherwise I will need to boot into fastboot.

Meanwhile, I use TotalCMD's handy shortcut-button to invoke the command su with the parameter:
Code:
settings put global development_settings_enabled 1; settings put global adb_enabled 1; echo "mtp,adb" > /data/property/persist.sys.usb.config
Which is equivalent to going to Dev Settings and toggling the USB Debugging.
mergen3107 is offline   Reply With Quote