[RECOVERY] [UNOFFICIAL] TWRP - Shield Android TV 2017 & 2015 - All Models
- Thread starter AndroidUser00110001
- Start date
Enable MTP in TWRP, plug USB cable in and then transfer SU to the internal drive?
Alright guys ... After everyone started talking about having to unplug the cable, I restored to stock and tried to root again.
And - as people have said - TWRP won't boot with the cable in. VERY ODD.
When I enable MTP and insert the cable again - it beeps a few times and reboots. So can't get SuperSU on that way.
My solution? I used a cheap USB 3.0 4 port hub. Put the mouse and flash drive with SuperSU on it into the other USB port.
Poof - mouse with TWRP and USB Storage mounted.
While that is all fine and well - I'd prefer a method without the hub.
Anyone have any other ideas? NOTHING USB works in the outer USB port other than the USBtoPC cable.
I can't find another reliable way.
And - as people have said - TWRP won't boot with the cable in. VERY ODD.
When I enable MTP and insert the cable again - it beeps a few times and reboots. So can't get SuperSU on that way.
My solution? I used a cheap USB 3.0 4 port hub. Put the mouse and flash drive with SuperSU on it into the other USB port.
Poof - mouse with TWRP and USB Storage mounted.
While that is all fine and well - I'd prefer a method without the hub.
Anyone have any other ideas? NOTHING USB works in the outer USB port other than the USBtoPC cable.
I can't find another reliable way.
Strange. I can't mount USB and never had to pull the cable out. I can mount MTP.
Not sure if this could be it but do you have the latest ADB/Fastboot files?
Not sure if this could be it but do you have the latest ADB/Fastboot files?
Yeah, I got the latest and greatest.
What's funny is ... the FIRST time I did it? It was fine! ADB sideload - no problem.
Since then? No TWRP without jerking the cable out.
Did we make any headway in avoiding the Google corruption screen with TWRP?
I actually managed to get a RED screen telling my device was corrupted and could not be trusted
No not yet.Did we make any headway in avoiding the Google corruption screen with TWRP?
I actually managed to get a RED screen telling my device was corrupted and could not be trusted
hey android user,
first off...great work and thank you for this... it is to my understanding this will not work for the 2017 pro version correct?....I believe I read somewhere that trying to root your 500gb shield will effectively give you 11gb of usable space afterwards is this true?
regards
Jeff
first off...great work and thank you for this... it is to my understanding this will not work for the 2017 pro version correct?....I believe I read somewhere that trying to root your 500gb shield will effectively give you 11gb of usable space afterwards is this true?
regards
Jeff
Posted a new build which should allow TWRP to handle OTA updates for 2017 Shield 16GB models.
If someone can post the build.prop file for 2017 Shield Pro then I should be able to add that to the list too for OTA updates
If someone can post the build.prop file for 2017 Shield Pro then I should be able to add that to the list too for OTA updates
ill try rooting my shield later tonight or tomorrow and if I succeed ill try to get you what you seek....
Thanks. If you have ADB you don't need to be rooted to grab build.prop
ADB pull /system/build.prop
ADB pull /system/build.prop
so I tried using an old usb A- A cable I had lying around (one i got eons ago to connect a printer) and it doesn't seem to work. there is no communication between my laptop and the shield pro despite usb debugging, so im guessing only usb 3.0 cables do the trick.... your going to have to be a little more patient for the prop build :s.... iv ordered the cable and Ill hopefully get it tomorrow if not then after the weekend...
Trying to re-root my 2015 after updating to 5.02 however when I type "Fastboot boot twrp.img" I am getting "data transfer failure" error and the shield reboots. I have tried pulling the USB after issuing the command but cant get it to boot into TWRP to install SuperSU.
Did you update your fastboot/adb files? May need the latest version.
I cant seem to get my laptop and shield to interact...according the tutorial on this site im suppose to "enable USB" in storage (im not talking about usb debugging thats not a problem) however the "enable USB" appears for like a second then vanishes... I was able to turn it one just before it disappeared but didnt solve anything.... this leads me to think its either a wrong USB cable again, despite it being a 3.0 this time....
or my laptop security programs are blocking it some how... the only way iv been able to get the two to communicate is via bluetooth.... if i turn bluetooth off on my laptop it wont show in devices and printers or device manager despite being connected to usb..... any insights?
i feel the solution is in plain sight but its zooming over my head
or my laptop security programs are blocking it some how... the only way iv been able to get the two to communicate is via bluetooth.... if i turn bluetooth off on my laptop it wont show in devices and printers or device manager despite being connected to usb..... any insights?
i feel the solution is in plain sight but its zooming over my head
Do you have the USB storage device plugged into the correct port on Shield? If you do not have USB storage device then you do not need to turn it on...
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone