[Q] Help with TWRP and sideloading SuperSU

Search This thread

Kipper667

Member
Oct 13, 2012
22
2
I've run into the problem of replacing the 5158n glass with the G01 and not having touch for TWRP. I've unlocked, installed TWRP but since I don't have touch and the USB mouse adapter doesn't work with TWRP I have no ability to install SuperSU. I came across a thread http://xdaforums.com/showthread.php?t=2511924 and the OP stated that he bypassed the problem by sideloading TWRP by:

* adb: # echo "sideload" > /cache/recovery/openrecoveryscript && killall recovery
* adb sideload SuperSU.zip
* reboot
* then in terminal emulator I flashed the touchscreen firmware: # touch_fw_update -u /data/local/tmp/02-3011-4820.ekt
* reboot

This is where my problem lies. I don't know how to do this. I tried opening the console and typing the first line but I get "The system cannot find the path specified."

Can anyone give me a step-by-step or fill me in on what I'm doing wrong? Do I need to have TWRP running when I do this? Thanks in advance.
 

cmendonc2

Senior Member
Aug 29, 2011
1,628
896
I've run into the problem of replacing the 5158n glass with the G01 and not having touch for TWRP. I've unlocked, installed TWRP but since I don't have touch and the USB mouse adapter doesn't work with TWRP I have no ability to install SuperSU. I came across a thread http://xdaforums.com/showthread.php?t=2511924 and the OP stated that he bypassed the problem by sideloading TWRP by:

* adb: # echo "sideload" > /cache/recovery/openrecoveryscript && killall recovery
* adb sideload SuperSU.zip
* reboot
* then in terminal emulator I flashed the touchscreen firmware: # touch_fw_update -u /data/local/tmp/02-3011-4820.ekt
* reboot

This is where my problem lies. I don't know how to do this. I tried opening the console and typing the first line but I get "The system cannot find the path specified."

Can anyone give me a step-by-step or fill me in on what I'm doing wrong? Do I need to have TWRP running when I do this? Thanks in advance.

Why don't you use a non touch recovery, like CWM for KitKat ROMs. That should solve some problems:

http://xdaforums.com/showthread.php?t=2632095