I sent you a copy of mine through PM.Thanks. If you have ADB you don't need to be rooted to grab build.prop
ADB pull /system/build.prop
I sent you a copy of mine through PM.Thanks. If you have ADB you don't need to be rooted to grab build.prop
ADB pull /system/build.prop
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...
Got it. Thanks!I sent you a copy of mine through PM.
Hey I had the same issue, I was using a USB male to male cable I made myself but nothing was working. Computer not seeing anything. I didn't realize the 2017 Pro has a micro usb port, that is the port you need to use. I'm embarrassed to say how long it took me to realize that, but as soon as you swap cables you're computer will see it!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
*face palm*...thank you!... managed to root thanks to your post....Hey I had the same issue, I was using a USB male to male cable I made myself but nothing was working. Computer not seeing anything. I didn't realize the 2017 Pro has a micro usb port, that is the port you need to use. I'm embarrassed to say how long it took me to realize that, but as soon as you swap cables you're computer will see it!
Just FYI, the cable it came with does not work well at all for fastboot. You might want to find another one.
Also I think I enabled both network and usb storage by quickly enabling the settings before they vanished. You just have to be very fast.
Got the build.prop for 2017 Pro. Looks like 2017 Pro is exactly the same as the 2015 Pro.success!!! I confirm this works on the shield tv 2017 Pro, no memory loss after rooting and used a micro usb to usb A cable (thanks again harmfulmushroom) thank you for all the time put into this, adroid user you still need the build.prop?
yeah, updated immediately no ifs, no buts, no coconuts....Got the build.prop for 2017 Pro. Looks like 2017 Pro is exactly the same as the 2015 Pro.
When you got your 2017 Pro did it ask to upgrade as soon as you booted? If so then someone can grab the update URL for the 2017 Pro and should be able to flash it on the Pro since so far it looks like there are no changes between the 2015 and 2017 models.
Same for me unfortunately. I thought you could still grab the url by clicking on check for update but I guess not... Next time an update goes live I'll sniff out the url. Or logcat it, whichevers easiest.Got the build.prop for 2017 Pro. Looks like 2017 Pro is exactly the same as the 2015 Pro.
When you got your 2017 Pro did it ask to upgrade as soon as you booted? If so then someone can grab the update URL for the 2017 Pro and should be able to flash it on the Pro since so far it looks like there are no changes between the 2015 and 2017 models.
Not sure if it is a TWRP theme issue or something different in TWRP code. Trying to figure it out but I have no 4K screen to test with. A separate TWRP for 4K screens may need to be built.will twrp ever get support for 4k tvs, unofficial and official? i'm getting closer to getting a 4k tv so i'm sol if i do.
With the Nvidia Shield TV when attached to 4k TV/monitor TWRP is not displayed on monitor. Is it just a theme thing or is there more to it?
If anyone wants to pull the log...I see no reason why it should be a theme thing at all, it should simply be scaled. Does it work with a 2K monitor? adb pull /tmp/recovery.log and dmesg, maybe something is wrong with the framebuffer.
I may be saying something completely stupid but....a while back i was looking into why my genisis emulator console would not play game gear games and as it turns out its not a question of "scaling" or program writing but rather an issue related to the amount of color used by the two systems.... could this be the case for 4K tvs too?
I just finished unlocking the bootloader on a 2017 500GB Shield using the guide here:Anyone with 4K monitor want to test this to see if TWRP is displayed?
The UI will be off...just wondering if anything will be displayed now. If so then I can fix up the UI layout.
I just finished unlocking the bootloader on a 2017 500GB Shield using the guide here:
http://nvidiashieldzone.com/shield-...t/tutorial-root-shield-android-tv-pro-nougat/
I've got an LG 55" OLED w/HDR and Dolby Vision. Unless I'm mixing my concerns, I believe I got around the 4K limitation when unlocking the bootloader by setting my Shield Video Video output setting down to 1080p. When unlocking, the stock bootloader displayed fine.
The TWRP available on the 'nvidiashieldzone' site is "TWRP (Hacked; Darcy), v 3.0.2h", and now that I'm ready for that step, I'm not sure which to install, so opinions are welcomed.
Thanks,
Janx
Flash at your own risk!
Not responsible for any damage you may do by attempting to modify stock software!
Recovery will work on all Shield 16GB 2015, Shield Pro 2015 & Shield 2017 16GB. All models...
You need ADB and FASTBOOT to get this installed.
You can follow this guide HERE or HERE
See attachments below for download.
Update 02/01/17
Added proper device info for 2017 Shield 16GB to allow OTA updates. Should work but not 100% sure if it will.
Extract img file from within zip folder
Reboot to bootloader
Use one of the two following commands
To flash recovery
fastboot flash recovery recovery.img
To boot into recovery without flashing
fastboot boot recovery.img
---
Thanks to TWRP for making the sources available and to @Steel01 for his work on TWRP for original shield which this was ported from.
I didnt even know about the new twrp I used the darcy hack version on my 2017 pro and it worked fineI doubt it since 2015 TWRP did not work on 2017.