yashsingh1/xdaforums huggingface dataset:
[Shield Android TV Android Development] Swagneto:
So, I'm trying to install magisk_shieldtv_pie_r2.zip on my Shield 2015 running the latest dev build of 8.0. I go to install the zip via TWRP and it tells me there was an error with the zip file and it refuses to install. Any ideas on what I'm doing wrong?
[Shield Android TV Android Development] dfl:
Try using a different USB cable and or USB port if flashing via adb sideload xxxx. I believe I flashed from /data via TWRP and not using adb.
[Shield Android TV Android Development] sash11:
In case anyone needs, here is full OTA of the latest hotfix for Shield 2017 32.5.205.74

PUBLIC8dc0a8b4129ba39cfcacf3c7f89d8106.zip
[Shield Android TV Android Development] mLgz0rn:
[MENTION=4180946]rootfan[/MENTION] is it the intention of the shield tools to not keep the clocks you have set after a reboot?

I installed the new kernel for pie and the new shield tools, but every time my stv 2017 is rebooted the clocks are back at stock speeds.
[Shield Android TV Android Development] tstack77:
Thank you for your time making this kernel package for 8.0, it made quick work getting my replacement shield up and running. Only hiccup I've found is that in R1.3 on 16gb-2017, USB issue still present. I noticed a fix for 7.2.3 from Aug 21st, is there another fix for 8.0?
[Shield Android TV Android Development] Ghisy:
Hi,

Can we flash this through TWRP and keep root and apps? [MENTION=4180946]rootfan[/MENTION]
[Shield Android TV Android Development] sash11:
That is not going to work. You have to take the OTA, reboot and re-root again.
[Shield Android TV Android Development] Ghisy:
I wasn't sure. OK, thanks. Although my Shield tells me it's up to date (I flashed the dev image from NVidia's website). I guess I'll have to wait.
[Shield Android TV Android Development] sash11:
You have to sign up in order to get hotfixes:

https://docs.google.com/forms/d/e/1...1qdATbg/viewform?entry.1352533101=DONTDELETE-
[Shield Android TV Android Development] Ghisy:
Oh, thanks! I didn't know about that!
[Shield Android TV Android Development] dermuggi:
Hi.

There was an News update.: 8.0.1

Will method still Work?

Do you have a Short Guide with commands to flash IT?

Adb...all the Stuff ist ready to use.

Just the Commands to flash IT.

Thx
[Shield Android TV Android Development] sash11:
Same process of rooting applies. I've already rooted the latest hotfix build 32.5.205.75
[Shield Android TV Android Development] Largewoodenspoon:
So I can do the 8.01 update on the shield. Then simply flash the magisk zip I used for 8.00 via twrp?
[Shield Android TV Android Development] rootfan:
[MENTION=7186920]mLgz0rn[/MENTION] , the clocks resetting to stock after reboots is the expected behavior. I'll add an option though in the next release to preserve settings across reboots. [MENTION=683752]tstack77[/MENTION] , flash the attached zip and let me know if it fixes the issue.
[Shield Android TV Android Development] mLgz0rn:
Great! Thanks for your awesome work!
[Shield Android TV Android Development] dfl:
[MENTION=4180946]rootfan[/MENTION] I can confirm that pieOC_Test.zip works with USB on 8.0.0 2017 (16Gb).
[Shield Android TV Android Development] dalogan72:
First thanks then help please.

I got the shield 500 2017,

I got your 1.31 with tools 1.1. They both worked fine, I just got an issue with su, I got su working because programs got access to it, I just got su binary occupied error, I just would like to know if this is normal with this realease or I most likely did something wrong. There is a hot to solve under su app, but I didn’t try mainly beacause I don’t know much about this, so if you can help me saying it is normal or re flashing will fix it or any other magic you guys have excellent. Thanks and regards.
[Shield Android TV Android Development] mLgz0rn:
I got no idea what you are saying.

But if you are using the supersu app, you shouldn't.

You should be using magisk manager to manage.
[Shield Android TV Android Development] dalogan72:
Thanks

I will use Magisk, thanks for your fast reply.
[Shield Android TV Android Development] sash11:
Yes
[Shield Android TV Android Development] Largewoodenspoon:
Our just flash this kernel v1. 3.1. Via twrp. Once I've upgraded to 8.0.1 from rooted 8?

It contains magisk (root)?
[Shield Android TV Android Development] Largewoodenspoon:
This is very odd. My 2017 16gb box won't upgrade to 8.0.1. It gets to 20% then reboots!

Not sure what's going on there....
[Shield Android TV Android Development] Largewoodenspoon:
Think I've sorted it. For some reason it was running Foster software not darcy. So the update downloaded as darcy but thought the shield was a Foster.

Oh well......

---------- Post added at 04:02 PM ---------- Previous post was at 03:17 PM ----------

Flashing kernel sends me into a bootloop though...........

Aaaarrrrggghhhh......
[Shield Android TV Android Development] dermuggi:
Great....Same Here...comes to the Nvidia-Logo..last about 1 Minute..then reboot..endless...Help pls :(

I was on the newest Update from nvidia ota.

Followed the given instructions..one by one...Fastboot...Fastboot boot twrp.img.....install zip..No Errors...reboot......BOOTLOOP :(
[Shield Android TV Android Development] dermuggi:
Ive now flashed the whole dev Image 8.0.0

After that the Kernel zip

Bootloop again -_-

After flashed Dev Image everThing was finde...right after Kernel...bootloop
[Shield Android TV Android Development] Largewoodenspoon:
You manage to flash the kernel?

Mine is just not having it!
[Shield Android TV Android Development] dermuggi:
OK...its working...

- Full factory data reset

- flash Dev 8.0.0

- flash pie r2 (Kernel Not working)
[Shield Android TV Android Development] Largewoodenspoon:
So for now I'm on 8.0.1 with magisk and root.

Would love to get this kernel going though......
[Shield Android TV Android Development] frriction:
[MENTION=4180946]rootfan[/MENTION]

I am on 8.0.1 when I boot twrp my TV shows nvidia logo, twrp logo for split second and blank screen.

Is 4k TV a problem for this?

Any solution?
[Shield Android TV Android Development] Largewoodenspoon:
No, I'm on 4k and it's displaying just fine on 8.0.1.

But, any help in getting this kernel going would be greatly appreciated....

Should I try it again from its magisk rooted state?
[Shield Android TV Android Development] frriction:
Thank you for confirming that there no problem with kernel image.

so I tied with another older hdmi cable and it worked.

thank you.
[Shield Android TV Android Development] Largewoodenspoon:
Did you get the kernel to work?
[Shield Android TV Android Development] TektTheGeek:
Works on 8.0.1! No issues whatsoever installing... Thanks a ton!
[Shield Android TV Android Development] frriction:
Yes, without any issue
[Shield Android TV Android Development] Largewoodenspoon:
This is totally fog my head in!

I can't get the kernel to work. It installs via twrp without error, but then won't boot up. Goes to the nvidia logo and then loops....

I've tried everything. Coming at it unrooted 8.0.1. Coming at it rooted 8.0.1 etc......

I can't think what I'm doing wrong!
[Shield Android TV Android Development] MrHomebrew:
Does anyone have stock build.prop from system and vendor folders
[Shield Android TV Android Development] Largewoodenspoon:
You on 8.0.1? You flash the kernel rooted or non rooted?

I'm really stuck!!!
[Shield Android TV Android Development] mLgz0rn:
You must be doing something wrong.
[Shield Android TV Android Development] Largewoodenspoon:
I've followed it to the letter!

I flash devices all the time.

Been rooting and flashing shields since 2015. Never had an issue before.

Just can't get it to go past boot loop.

Very very odd.

It seems I'm not the only one though.......
[Shield Android TV Android Development] mLgz0rn:
It does seem you are the only one, everyone else has sorted it.

What you might want to try is flashing the 8.0.0 recovery image, then let it update again, and then try again.

Something seems wrong with your shield, the fact that you are saying it was running foster and not darcy make no sense, then your device would have been bricked.

You can't run the 2015 firmware on a 2017 device, and vice versa
[Shield Android TV Android Development] Largewoodenspoon:
I flashed the 8 recovery image. Then let it update.

When I was in twrp, I tried to flash the update zip for 8.0.1. But got that weird darcy Foster message..
[Shield Android TV Android Development] mLgz0rn:
What? you are not suppose to flash the update in twrp.
[Shield Android TV Android Development] CHouKar:
I have the same problem with my Shield 2015 (foster) 16GB.

No errors in TWRP, but it won't get past the NVIDIA Logo and the shield reboot by itself after 1-2mn.

I tried a clean install of the 8.0 image, and the 8.0 developer image as well, and no, the kernel won't boot on my Shield.

(Also tried to flash 8.0 image, let it update to 8.0.1 and then flash the kernel, result in a bootloop).

Previously I was on 7.2.3 with your R1.1 kernel, and everything was ok.
[Shield Android TV Android Development] Largewoodenspoon:
I knew it wasn't just me!!!

Let me know if you sort it out. I'll do the same!

I'm on 8.0.1. I can flash magisk r2 just fine.
[Shield Android TV Android Development] frriction:
I followed this instructions.

https://xdaforums.com/showpost.php?p=80198546&postcount=317

get magisk_shieldtv_pie_r2.zip from first post of this thread.
[Shield Android TV Android Development] CHouKar:
magisk r2 zip work fine here too, but kernel zip won't boot since the 8.0 update, no matter what I try.

(latest magisk canary = stuck at nvidia logo, no bootloop just stuck forever)
[Shield Android TV Android Development] Largewoodenspoon:
Me too. It's very strange isn't it!
[Shield Android TV Android Development] frriction:
[MENTION=4180946]rootfan[/MENTION] if I have flashed magisk_shieldtv_pie_r2.zip, is it safe to downgrade Magisk to 19.3?
[Shield Android TV Android Development] Adromir:
As far as I know only magisk 19.4 and upwards has the required changes needed for the 8.0.x upgrade of the shield
[Shield Android TV Android Development] Largewoodenspoon:
Did you manage to sort this and get it working?
[Shield Android TV Android Development] lingarajug:
Thank you for the kernel, much appreciated, I was able to flash this and all is well on 2017 16gb version, i have 2 doubts, first the settings through the app for kernel dont stick after a reboot and i am used to turning off the device as it gets warm even in sleep, second the fan percent values are confusing, is 100 the highest as i see a value of 24562 or something similar and is 100 going to keep fan at full speed or should i set like 130 or 140.
[Shield Android TV Android Development] mLgz0rn:
I asked this a few pages ago
[Shield Android TV Android Development] lenana:
Hello everyone. I am on Full android oreo 7.2.2 by zulu99. I wanted to flash the 7.2.3 kernel but I'm afraid of incompatibility esp that the dev has underlined

7.2.3

in the OP section. Are there any modifications I can do incase it fails? As far as I know twrp doesn't work with oreo 7.2.2, I have never been able to flash twrp or boot in to twrp without flashing...so making nand backups is almost impossible now. Has anyone tried 7.2.3 version on 7.2.2?
[Shield Android TV Android Development] mLgz0rn:
Great work [MENTION=4180946]rootfan[/MENTION] gonna try out the new kernel and shieldtools!

Does the new shieldtools update define better how the fan speed works?

Because I got no idea what the different stuff means.

Talking about temperatures/fan speed
[Shield Android TV Android Development] rootfan:
[MENTION=7186920]mLgz0rn[/MENTION] I hope everything is working out alright with the new release. As for the fan speed settings, this is how they work. Each temperature matches up with the fan speed next to it. So for stock settings as shown in the attached picture, when the device temperature reaches 45°C the fan will run at 31%, when the temperature reaches 56°C the fan will run at 47%, etc... You'll notice after 78% the temperatures become 140,150,etc... That is way outside the Shield's operating range so with stock settings the fan speed never runs above 78%. The max temperature setting likely to do anything is 75°C-80°C.
[Shield Android TV Android Development] mLgz0rn:
Hmm, that's also how I understood it, but for me it looks like this by default
[Shield Android TV Android Development] rootfan:
[MENTION=7186920]mLgz0rn[/MENTION] I can certainly understand your confusion now :) Give this Shield Tools a try and let me know if the problem is fixed.
[Shield Android TV Android Development] mLgz0rn:
I actually think it was an issue with the previous version that transferred over to the new one (1.2). Clicking reset made the numbers go to like the ones in your image.
[Shield Android TV Android Development] rootfan:
The 2017 Shield uses different values than the 2015 model. Clicking reset on Shield Tools 1.2 will make the values appear correct, but what it shows as 100% will actually be less than 1%. I think I fixed this with the Shield Tools I posted above.
[Shield Android TV Android Development] DumbKing@letthemeatspam:
I don't have a mouse how do I root shield without mouse why is this required :( :(
[Shield Android TV Android Development] mLgz0rn:
Aaaah that makes sense now.

Guess that's why it was struggling when I tried to play 4k ?
[Shield Android TV Android Development] Largewoodenspoon:
Am going to try this latest realese.

Couldn't get the last one to work at all.

Just sent into a nvidia screen loop.

I tried everything. Am used to flashing stuff so I'm pretty sure I didn't do anything wrong.

If anybody who was in the same boat as me gets this to work, please let me know!
[Shield Android TV Android Development] mLgz0rn:
Yeah it seems to be working great now with this version!

thank you!
[Shield Android TV Android Development] cubandanger05:
For the values to be applied on boot, did you set up a timer so that it gives us 10 secs or so to go in the app and change things back in case something isn't right? Haven't flashed it yet. Just curious.
[Shield Android TV Android Development] Largewoodenspoon:
I flashed latest version on 2017 16gb shield and I'm still getting the stuck on nvidia logo.

I have literally no idea as to what I could possibly be doing wrong....

I could cry......
[Shield Android TV Android Development] xdakid:
Getting ready to flash my Nvidia shield tv 2017 when I saw this statement..."Shield Tools 1.2.1 fixes fan settings for 2017 shields. Make sure to upgrade from 1.2 if you're using a 2017 shield...." cannot find Shield Tools 1.2 to download....Does this mean I need to have Shield Tools 1.2 installed before flashing or it can be installed after flashing and then reinstall with 1.2.1?

Thanx!
[Shield Android TV Android Development] mLgz0rn:
Just flash and install the app
[Shield Android TV Android Development] urkelz:
Thanks for this useful app. Max CPU and GPU overclocks are stable on mine testing on 3dmark however RAM @ 1866 MHZ causes serious stability issues.
[Shield Android TV Android Development] SkOrPn:
EDIT: Never mind me, it was just a frackin bad cable... LOL

OK, everything seemed to go great with this process. I flashed the kernel, installed the latest magisk manager, then I updated Magisk to 20.0. So far so good and everything worked within the OS per usual. However, the Shield Tools app wasn't setting the speeds I wanted and both the RAM and FAN tabs simply crashed the app back to the shield desktop. So, I figured this was because I updated Magisk. Simple cure then is to downgrade Magisk back to the one provided. Only problem is I flashed "magisk_shieldtv_pie_r2.zip" instead of the kernel again. This gave me a NVIDIA logo that never went away. Hmm, so now I figured I would just "Factory Reset". Well that process seemed to work flawlessly from within the bootloader, however it was still stuck at the NVIDIA logo. So, then I decided to download the stock nvidia image 8.0 and flash each file per normal. But now much of these files I get an error like like below.

So now the ONLY thing I can think of is to flash a complete ROM image from within TWRP. Does anyone know of a twrp flashable ROM.zip for the SHIELD TV 2015 16GB? Or anything else I can do from here please?

PS C:\adb> fastboot flash recovery recovery.img
Sending 'recovery' (17334 KB) OKAY [ 0.477s]
Writing 'recovery' OKAY [ 0.763s]
Finished. Total time: 1.285s
PS C:\adb> fastboot flash system system.img
Sending sparse 'system' 1/50 (32764 KB) FAILED (Error reading sparse file)
fastboot: error: Command failed
PS C:\adb> fastboot flash system system.img
Sending 'system' (1607048 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
PS C:\adb> fastboot flash system system.img
Sending sparse 'system' 1/50 (32764 KB) FAILED (Error reading sparse file)
fastboot: error: Command failed
PS C:\adb> fastboot flash system system.img
Sending sparse 'system' 1/50 (32764 KB) OKAY [ 0.968s]
Writing 'system' OKAY [ 1.437s]
Sending sparse 'system' 2/50 (32764 KB) OKAY [ 1.001s]
Writing 'system' OKAY [ 1.353s]
Sending sparse 'system' 3/50 (32764 KB) FAILED (Error reading sparse file)
fastboot: error: Command failed
PS C:\adb> fastboot flash system system.img
Sending sparse 'system' 1/50 (32764 KB) FAILED (Error reading sparse file)
fastboot: error: Command failed
PS C:\adb> fastboot flash vendor vendor.img
Sending sparse 'vendor' 1/14 (32764 KB) OKAY [ 0.923s]
Writing 'vendor' OKAY [ 1.417s]
Sending sparse 'vendor' 2/14 (32764 KB) OKAY [ 0.908s]
Writing 'vendor' OKAY [ 1.334s]
Sending sparse 'vendor' 3/14 (32764 KB) OKAY [ 0.910s]
Writing 'vendor' OKAY [ 1.334s]
Sending sparse 'vendor' 4/14 (32764 KB) OKAY [ 0.913s]
Writing 'vendor' OKAY [ 1.321s]
Sending sparse 'vendor' 5/14 (32764 KB) FAILED (Error reading sparse file)
fastboot: error: Command failed
PS C:\adb>
[Shield Android TV Android Development] Adromir:
Have you tried to redownload the image ? The Error sounds like the file is corrupt. You can also try updating your ADB, maybe the problem is caused by an outdated version
[Shield Android TV Android Development] SkOrPn:
I am on the latest ADB using the latest 1909 Win10 and PowerShell, and no I didn't re-download the kernel image (which would have been a good idea). However, the device was running good after flashing the kernel so I didn't expect anything was wrong with it. The issue is, after flashing the kernel the Shield Tools 1.2.1 didn't work as expected. So I thought that maybe that was because of me upgrading Magisk to v20. My shield is the 2015 16GB model and it was fully updated to 8.0.1 before I started the process. Shield Tools 1.2.1 didn't set the cpu or gpu, and the fan and ram tabs would force close the app.

On a side note I was using a far too long cable, a 16 foot cable that is at least as old as micrusb spec is. So I found a newer logitech cable that worked perfectly to flash the stock image. I am now wondering if the kernel had issues because of that too long of a cable?

What did I do wrong you think?

EDIT: I'm trying again within the next few minutes, so if I am doing something wrong please let me know now. Am I right in flashing this kernel on my 2015 16gb model and using Shield Tools 1.2.1, and is it OK to update Magisk or NOT?
[Shield Android TV Android Development] SkOrPn:
A few ideas I have since no one else seems to be helping you. Double chack that you are 100% certain of your model. Also flash stock maybe before trying this. Also definitely try a different usb cable because I have an expensive cable that this does not work on and a free cable that came with my Logitech keyboard that definitely flashes perfectly with. Point being it may not seem like it but cables matter. Lol

I'm on the 2015 16GB model P2571 and after reading through this thread twice carefully, it still isn't clear what files/images we are supposed to be flashing. I'm guessing there is no Overclock kernel for my shield. The OP should have put next to every version exactly what device/OS it is meant for, but there is nothing written to make it clearer.

[MENTION=4180946]rootfan[/MENTION] what files are for the 16GB 2015 model foster please? Do I only need the magisk_shieldtv_pie_r2.zip file? Or do I flash the rootfan_kernel_r1,4.zip file? And, what version of shield tools is for foster? And are we allowed to update magisk via latest Magisk Manager, and if so what update method is OK (magisk recommended?)? Non of this is explained in the OP clearly.

Thanks for your hard work it is really appreciated.
[Shield Android TV Android Development] mLgz0rn:
I bet [MENTION=4180946]rootfan[/MENTION] would have specified if the kernels/boots were not for your device.

They should work on every device.

magisk_shieldtv_pie_r2 is just magisk prerooted.

rootfan_kernel_r1,4 is a modified kernel that includes magisk and overclocks.

This is also stated in the first post.

There's also nothing wrong with trying abit yourself.

If something goes wrong you just flash the kernel/boot again.

I was able to update magisk both by using the direct install method but also by flashing in twrp.
[Shield Android TV Android Development] SkOrPn:
Thanks for the info. But quite a few posts in this thread make it seem like each file is for specific setups/devices. One post says exactly that. What are you to think if the Shield Tools doesn't work as expected? Well you are to think that you did something wrong. The ONLY thing I did that was not directed to do was update Magisk, so I was thinking that must have been the issue. If not, then it must be something else, wrong device or wrong files, or something. So now I am left with trying the exact same thing over again, which is what got me in trouble in the first place. Lol

Be right back, going to do exactly what I did before. Boot into twrp, then flash the kernel, then boot into Android and install Shield Tools 1.2.1. This will be the second time doing the same thing, lol. Going to make a twrp backup first though, haha.

EDIT: OK, w00t, it worked this time around. The only thing I did differently this time was that I did NOT update Magisk to 20.0. The Shield Tools 1.2.1 finally works now. I see no reason to update Magisk. Thanks for pushing me to try it again.
[Shield Android TV Android Development] mLgz0rn:
There was an issue in the beginning of pie where the magisk kernels only worked for the pro model, since thats the version [MENTION=4180946]rootfan[/MENTION] has.

He soon got it fixed to work on the other devices :p that's why it was posted.

Was fixed here https://xdaforums.com/showpost.php?p=80190678&postcount=307

Glad you got it working! :)
[Shield Android TV Android Development] SkOrPn:
Thanks. Yeah, I won't be updating Magisk until rootfan himself says its OK to do so. Never needed root on this device, not since trying full roms years ago, but I only use it for 4K Youtube and Movies/Shows. Ever since the new Shield pro was discovered I have been thinking about trying to make this device more powerful, so I modded the cooling pathway completely free of plastic obstructions (pics if wanted) and I plan to add some liquid metal to the X1 chip soon. The new Pro is exactly 25% more powerful, which this mod almost seems to give us 20%. Using the default kernel my Sling Shot Extreme score was about 4000, but now at max everything its 4580. Not bad at all I must say.

Now lets just hope some very smart developers such as [MENTION=4180946]rootfan[/MENTION] figures out how to bring that OS or its features to our older Shields, lol. That AI Enhanced up conversion would be EXTREMELY nice to have on the original Shields, especially for people like myself who have great screen TV's with built-in piss poor native up conversion.
[Shield Android TV Android Development] SkOrPn:
Can someone shed some light on how to set cpu, gpu and ram settings in shield tools please? Lol

EDIT: OK, I was on the assumption that shield tools would default back to stock settings every time you rebooted, but it has kept the settings for me. So I figured out that I was benching with the same settings multiple times after each reboot. Got er sorted though. Thanks
[Shield Android TV Android Development] BXM500:
Just out of curiosity...

If you use your Shield for video playback only why would you want to overclock it? There's no benefits. Or what am I missing.