[Tool][Windows] Control a device with a broken screen. Now with touchscreen support!!

Adb shell
echo "persist.service.adb.enable=1" >>/system/build.prop
echo "persist.service.debuggable=1" >>/system/build.prop
echo "persist.sys.usb.config=mass_storage,adb" >>/system/build.prop"
reboot

Ricky Divjakovski said:

for people who dont have adb enabled, i suggest you contact a kernel developer to automatically enable it in the default.prop and sideload the kernel in recovery!
i broke my S3 on stock so nothing was enabled.
i enabled adb via the default.prop and compiled the kernel and flashed in recovery(sideload).
now i have full control over the device.

Click to expand...

Click to collapse

Msmtx said:

To activate USB debugging AND workaround Secure ADB on Android versions 4.2+:

1. Boot to recovery through hardware buttons
2. Run adb shell
3. Mount system and data partitions (in my case, on TWRP: twrp mount system && twrp mount data)
4. Input into adb shell:
   
   Code:

   echo "persist.service.adb.enable=1" >> default.prop 
   echo "persist.service.debuggable=1" >> default.prop
   echo "persist.sys.usb.config=mtp,adb" >> default.prop
   echo "persist.service.adb.enable=1" >> /system/build.prop 
   echo "persist.service.debuggable=1" >> /system/build.prop
   echo "persist.sys.usb.config=mtp,adb" >> /system/build.prop

5. On Windows, go to "%USERPROFILE%/.android", open adbkey.pub with Notepad or your text editor of preference and copy all of the file's content (CTRL+A and CTRL+C from Notepad and standard editors)
6. Back to adb shell:
   Code:

   echo "<paste key here>" >> /data/misc/adb/adb_keys
   reboot

   -- on standard CMD you can paste by right-clicking the title bar> Edit> Paste, or just right-clicking if you have "Quick Edit mode" enabled in CMD's properties.

Click to expand...

Click to collapse