yashsingh1/xdaforums huggingface dataset:
[Shield Android TV Android Development] nadia p.:
Hello whiteak, I followed these steps to 1st Install recovery.img, then Install boot.img from the 7.1.0 Recovery OS image data, then rebooted the system. This removed TWRP, as expected, and still shows the Orange unlocked bootloader message, then the Nvida logo, then 2x the Red corruption error messages, then a black screen. So nothing really changed accept for the removal of TWRP.

Any other ideas? Should I attempt to install TWRP again? I have full access to the USB drive still and Android Recovery Mode.

---------- Post added at 05:55 AM ---------- Previous post was at 05:38 AM ----------

I'm close to this point as well. One would think that there should be an easy way for Nvidia to offer one package and solution to reinstall the OS cleanly as we can do with computer systems. They install it from hardware with nothing on it at the factory. I'll have to call them and see if the device is sent back how much they would charge to fix it over the cost of a new one. I'm not sure what else to do.
[Shield Android TV Android Development] whiteak:
I take it you never tried my twrp backup or Custom Rom I posted for you in the other thread?

See if you can reboot to Flashboot now, also post the filename of the firmware you have flashed, I've got a feeling you have flashed the 2015 firmware, I may be wrong, but let's rule that out anyway.
[Shield Android TV Android Development] nadia p.:
Hello whiteak, In regards to the recovery.img that TWRP output from

booting

to it, prior to flashing TWRP onto the device, no I wasn't confident as to what it backed up. In regards to "flashboot" I'm not certain what this is or how to do it.

The firmware I downloaded from HERE is per your suggestion

NVIDIA SHIELD TV 2017 Recovery OS Image 7.1.0 (2018-09-26)

nv-recovery-image-shield-atv-2017-7.1.0.zip

boot.img (untouched from 7.1.0)

recovery.img (untouched from 7.1.0)

The version that was installed prior to flashing TWRP was

NVIDIA SHIELD TV 2017 Developer Only OS Image 7.1.0 (2018-09-26)

nv-recovery-image-shield-atv-2017-7.1.0-dev_rooted.zip
[Shield Android TV Android Development] whiteak:
I meant Fastboot not Flashboot, and they are the 2017 Firmwares so we can rule that out.

I posted in the other thread a TWRP backup from one of my 2017 Darcy devices for you to try, I also posted a Custom Rom I made for you try as well. That's why I was saying to keep all this back and forth in another thread instead of multiple threads especially this one as what we are trying to do in getting you backup running is not specific to this thread, anyway, I did post some things for you to try in another thread, but you must not have seen them yet.

I would try to get into Fastboot again, unplug power for 10 seconds, plug controller into Shield into the usb port closest to the hdmi port, while pressing and keeping held down A and B on the controller plug power back in, it should vibrate and then a few seconds later vibrate again, you should be in Fast Boot, if the controller doesn't work you can try the same process with a USB keyboard holding down the A and B keys while plugging power back in.
[Shield Android TV Android Development] nadia p.:
Hello whiteak, I'm able to boot with USB keyboard, press keys A and B and get to that menu, which as I know is the fastboot menu. There I'm able to mount the USB, etc... as normal. I may not have seen that you've created a ROM for me to test, my apologies. If you point me to, or PM me which thread you're referring to I'll gladly read it. In the past week or so has been my crash course on Android. I'm willing to try anything as long as I have access to the device. I really appreciate everyone's help here, it's truly great!
[Shield Android TV Android Development] whiteak:
If you can get to fastboot menu, great, just flash back the 7.1 Firmware, on your pc go to the folder where the firmware is, open the folder so you see all files, go to top of address bar of folder, type cmd, should open a command prompt, just type flash-all, let it do it's thing and hopefully you should be up and running again, don't be too worried if it wants to update to 7.2.1 on setup, if it boots to system fine, should be able to downgrade to 7.1 if that is the firmware you want. If it doesn't prompt you to up date, I would do a Factory Reset anyway with all the issues you have had.

Edit: better yet, you may as well boot to fastboot and do the flash-all with the 7.2.1 2017 Recovery Firmware, then if it boots to system, do a Factory Reset and then downgrade if you wanted to.
[Shield Android TV Android Development] nadia p.:
Hello whiteak, OK. I'll download NVIDIA SHIELD TV 2017 Recovery OS Image 7.2.1 (2018-12-27) package, attempt to install it from the USB drive, perform a factory reset and see if it then boots as if it were a brand new device. From there I'll Sign-In Google Play, etc... . From there what is the best way to (A) down grade to 7.1.0 and (B) prevent automatic updates again?
[Shield Android TV Android Development] Downunder35m:
It seems there is a tiny light for using using TWRP with the 7.2 firmware.

The recovery ID's and checksums need to be matched to the TWRP that is flashed onto the recovery partition.

With that the bootloader would accept TWRP as a "genuine" recovery.

Still no write access for backups and such but a start.

Downside is that we (right now) can ot make these modifiactions without violating the secure boot functions.

A TWRP compiled from sources and using the 7.2 recovery as a base should be able to overcome this by utilising the 7.2 recovery kernel.

Sadly the TWRP builder app won't work on the Shield and trying it from a different device won't work.

I am not good enough with these compilers anymore but if anyone dares, the instructions are available on the TWRP homepage and Wiki.

What I would love however is a modifed TWRP that allows to use just the controller or remote instead of a keyboard and mouse/touchpad.

But we can't have it all, can we? ;)
[Shield Android TV Android Development] darkuni:
But can we get SuperSU/root access this way? :D
[Shield Android TV Android Development] Downunder35m:
I am trying to work on this problem but so far I am stuck with the bootloader and kernel problem.

It might be that Magisk sees an update to cater for these new security features so there is still hope for an easier way out.
[Shield Android TV Android Development] Mogster2K:
I haven't tried grabbing it yet (past my bedtime here) but it seems the source is finally up. Branch rel-30-r3-partner, as expected.

Readme files
[Shield Android TV Android Development] darkuni:
whooo hoooo
[Shield Android TV Android Development] Steel01:
Most of the source release is up. Except... For the pieces I actually need. Still no kernel source or vendor blobs.
[Shield Android TV Android Development] darkuni:
Of course not.
[Shield Android TV Android Development] darkuni:
My NVidia contact said there was a server issue (now fixed) and we should see that upload "soon".
[Shield Android TV Android Development] TheLoonyRebel:
I might finally move over to 7.2.2 once TWRP is working. Thanks for the hard work into bringing TWRP and Lineage to the Shield TV. :D

....now only if HDR would finally be working on YouTube on the Shield TV..... :silly:
[Shield Android TV Android Development] darkuni:
Yeah, my PRO is on 7.2.x but I won't let any of the others update.
[Shield Android TV Android Development] Mogster2K:
Bah, seems no one at Nvidia bothered to check that all the needed repos were marked public. "error: Cannot fetch device/hardware/nvidia/platform/tegra/common". Even cutting the extra devices like stardust and sunstreaker from the manifest doesn't help.
[Shield Android TV Android Development] Steel01:
It's not that the needed repos aren't public, though there are a few that need done so. The entire kernel and vendor blobs branches don't exist yet. linux-4.9, etc are there, but the rel-30-partner branch is not.

[MENTION=2945862]darkuni[/MENTION]: Yeah, I heard that a week or so ago. A couple days later, most of the code got uploaded, but the kernel still isn't there today.
[Shield Android TV Android Development] darkuni:
I'll keep sending my guy this thread info as it comes ...
[Shield Android TV Android Development] Steel01:
So we *finally* got kernel source (but not vendor prebuilts, go figure... ><). Spent a while tonight getting stuff together and have an experimental build working on the newer bootloader. Do note that I've only tested this on foster_e_hdd, but it should work on all variants that actually got the newer bootloader. Namely foster_e, foster_e_hdd, and darcy. I haven't even got the new bootloader to boot on the Jetson TX1, unfortunately. As normal, since this is an experimental build, use at your own risk, report problems, blah blah.

twrp-20190201-foster-experimental.img
[Shield Android TV Android Development] darkuni:
Trying this out on the Shield TV Pro (500GB) ... it does indeed boot, but SuperSU (2.82 SR3 fails to install. Exact error is:

https://i.imgur.com/pI7ql7y.jpg

Thoughts?

BTW, this was on Update 7.2.0.

Oh, and I decided to update to 7.2.2 (figured at this point - why wait ...) Didn't work there either.
[Shield Android TV Android Development] vivek5050:
darcy update

Novice user here. Booted in 16GB darcy with this image. Didn't flash, used fastboot boot. With the previous TWRP images, it used to stay on the Nvidia logo. TWRP booted with this image. Couldn't sideload SU. It said failed. It looks like it corrupted something in the process. After reboot, was having a boot loop. I had to flash all other images to restore android. Now I am getting corrupted warning during boot. Never had this before.
[Shield Android TV Android Development] Steel01:
Hmmm... I may have broken something in the symlinks. I'll try to take a look in the next couple days, but no guarantee I'll have the time. If I don't, it'll be a bit longer before I can fix it. Going to be off the grid from the 8th to the 16th.

But... corrupted something? If it's like the log in the post before yours, it shouldn't have actually touched anything. That's... odd.
[Shield Android TV Android Development] darkuni:
We appreciate the efforts!
[Shield Android TV Android Development] Steel01:
So, I don't have an install to test something like supersu against. But I did successfully flash a Lineage test build (which doesn't boot, but that's besides the point...). At some point, I'll have to flash stock from a recovery image and see what's up with that. Not going to happen before my trip, though. Sorry.
[Shield Android TV Android Development] ldeveraux:
Hey all, so I also tried booting (not flashing) into TWRP today with no luck. Is this no longer possible for some reason? After 7.2.2 screwed me up, I went to reroot but couldn't boot TWRP. I was able to root with Magisk, but is recovery currently not booting?

edit: I should have searched first! I guess it's not working on 7.2.
[Shield Android TV Android Development] lvbaal:
So, if I understand correctly, at present there is no twrp image available to (fast)boot into i.c.w. Shield Android TV SW Version 7.2.2?
[Shield Android TV Android Development] darkuni:
You can boot to TWRP. But SuperSU (at least) fails. I have no idea what else doesn't work - because that's all I personally use it for.
[Shield Android TV Android Development] lvbaal:
I downloaded twrp-3.2.3-0-foster.img from the link under this YouTube video. Then when I fastboot boot twrp-3.2.3-0-foster.img, the device hangs on the Nvidia logo. Then I began to read on XDA and read that there is no TWRP for 7.2.2 fw. Do you have any further comments on this maybe?
[Shield Android TV Android Development] darkuni:
You have to use the one from this thread a page or two back. AND I used it on the Shield TV Pro 500GB unit.
[Shield Android TV Android Development] lvbaal:
Do you mean twrp-20190201-foster-experimental.img from this post?

And then, while SU install will fail with this TWRP it's maybe an idea to install Magisk instead? Or what do you think?
[Shield Android TV Android Development] darkuni:
Yeah, that's the one. Apparently someone got Magisk installed already. Not my thing .. I'm holding out for SuperSU.
[Shield Android TV Android Development] lvbaal:
So, I booted with fastboot boot twrp-20190201-foster-experimental.img, which went through

Then I made a TWRP backup before fidlding with the device, this went through also

Then I booted to system and got bootloop, although I had not changed / flashed anything. Can't explain

Then I did flash-all.bat from nv-recovery-image-shield-atv-7.2.2-dev_rooted downloaded from NVDIA

and finally installed the latest Magisk Manager, patched the boot image in MM, being aware of AVB 2.0/dm-verity switch, and flashed patched_boot.img.

Now I'm up&running again (Pfff)

edit: and eagerly awaiting Steel01's TWRP for this device running 7.2.2 fw
[Shield Android TV Android Development] darkuni:
Someone else reported a bootloop issue - that didn't happen here. It just FAILED on the SuperSU, I restarted the system and everything was fine.
[Shield Android TV Android Development] BXM500:
Booted into TWRP nicely. Was able to flash the latest stable Magisk no problem. Thank you.
[Shield Android TV Android Development] trohn_javolta:
Nice, so with latest twrp from here, nandroid backups and flashing Magisk works?

Did anyone try to restore a nandroid backup yet?

These are all the things I need twrp for, if that all works I'm gonna flash it too :)
[Shield Android TV Android Development] BXM500:
Yes. Got the experimental twrp image a few pages back. Booted into it and flashed the latest stable Magisk. Root working. No problem.

I have Shield TV 2015 16GB running 7.2.2

I didn't try nandroid backup and I just booted into that experimental TWRP. Didn't flash it.

I'll wait for an official TWRP version that works until I flash it. No rush if the booting works.
[Shield Android TV Android Development] trohn_javolta:
How do you just boot it? Place the .img somewhere on shield, get into fastboot, hook up to pc and run some command like fastboot.boot twrp.img?
[Shield Android TV Android Development] BXM500:
Yea, connect to your compuer and: fastboot boot twrp_filename.img
[Shield Android TV Android Development] trohn_javolta:
Well I tried it yesterday aaand ... I'm in a bootloop now. meh :rolleyes:

What version are you on? 7.2.2? And 2017 or 2015 model? I have 2017 model.

I'm pissed at myself now. I saw the other tutorial of how to get root here: https://xdaforums.com/shield-tv/general/guide-root-nvidia-shield-experience-t3882254

but I thought this is way easier and more convinient + you confirmed it worked for your shield.

Now I wonder if maybe you have an idea how I could fix this?

What I did:

Get into fastboot mode, run fastboot boot twrp.img, in twrp flash magisk.zip and reboot. Voila you have your nice bootloop.

What I already tried:

wait (after some failed boots shield goes to bootloader) and boot twrp again. In twrp I wiped cache and dalvik (which I didn't after flashing magisk) - no success.

Again in twrp I started adb sideload feature and sideloaded the magisk uninstaller. Went through without errors but still bootloop.

In fastboot mode there's the option "boot safe mode" - no success.

I have "boot recovery kernel" and "factory data reset" left. Both of them seem to wipe all data and apps.

If there's no option to boot my shield again without factory reset, can I somehow backup my apps + data? I don't want to set up everything again

I should have backed up before...but didn't know how. On my phone I always use titanium backup...but it needs root. Quick search on how to backup didn't get me much info so I just went for the root.. the wrong way.

Well, I still can get into bootloader and also boot twrp. But idk how I could aquire a backup. I tried plugging in a usb stick but I cannot mount it. One usb port seems to not work, I think reserved vor adb. in the other one I need to plug in a mouse to control twrp. Using a usb hub also does not work..mouse does but stick can't be mounted...I guess that currently just doesn't work with the twrp image.

So I could do a nandroid backup on internal storage but if I do a factory reset (which I fear will be the only option to get it booting again) I guess internal storage thus also the nandroid backup will be wiped :(
[Shield Android TV Android Development] Adromir:
You can make Backups via ADB if you set up a Desktop Password in the Developer Settings prior to that
[Shield Android TV Android Development] BXM500:
Not sure why it didn't work for you to be honest.

My Shield is 2015 16GB version running 7.2.2 as stated earlier.

I presume you mounted the System partition in TWRP before flashing Magisk? At least I did. Or maybe the Magisk script does it already anyway, not sure. Nothing else I can think of at this point.
[Shield Android TV Android Development] trohn_javolta:
Ok, no I didn't mount system partition before. But I think it has sth. to do with dm-verity. I hope I can fix this somehow without loosing all data.
[Shield Android TV Android Development] BXM500:
Here's my sw versions.
[Shield Android TV Android Development] lvbaal:
Please refer to my post of a werk ago and look into this:

https://android.stackexchange.com/q...sk-in-twrp-with-keep-dm-verity-avb-2-0-option

Perhaps this will get to back on track
[Shield Android TV Android Development] trohn_javolta:
Thx I have it working again with this:

https://xdaforums.com/showpost.php?p=78859186&postcount=138
[Shield Android TV Android Development] darkuni:
Are we dead in the water with SuperSU, TWRP and the latest Shield TV? If we have no choice but to move to Magisk, I'll need to move my tutorials as such. [MENTION=1416222]Steel01[/MENTION] ?
[Shield Android TV Android Development] darkuni:
Just for fun, I used my own tutorials and just used Magisk instead of SuperSU and it mostly worked. The Manager doesn't get installed (Shield TV Pro) so that had to be done manually.

Sigh ... I guess I update using Magisk.
[Shield Android TV Android Development] DN38416:
I find Magisk just as easy to install. Is there any disadvantage to using Magisk?
[Shield Android TV Android Development] darkuni:
I don't know. That's part of the problem. I've been using SuperSU forever. I know it, understand it and have so many tutorials written on how to use it. To change will be a considerable investment of time and effort.

I went ahead and updated my Pro tutorial. The sideload didn't auto-install Magisk Manager either - so I had to add more steps. Again, probably a way to make that happen - probably can't use ADB SIDELOAD - but in the end, I got it all working.

https://nvidiashieldzone.com/shield-android-tv/android-8-oreo/shield-tv-pro-root/

Once I do my 2015 and 2017 16GB units, I'll update those tutorials too.
[Shield Android TV Android Development] mikty:
Hi tank you so much to find this solution for pro 2015. Can t wait to test. Hope it will be compatible with the upcoming 7.2.3 firmware thanks again
[Shield Android TV Android Development] darkuni:
No worries. It should. This breakage came as a surprise to everyone. I'm sure it wasn't intentional on NVidia/Google's part.

I gotta get off my fat lazy ass and get those other tutorials done.

I was able to get through 16GB 2017 after some dicking around - it wasn't (nor is it ever) as simple as the 2015 models. I just want to run through it a couple more times before I update the tutorial.
[Shield Android TV Android Development] mikty:
Ok thanks again
[Shield Android TV Android Development] darkuni:
https://nvidiashieldzone.com/shield-android-tv/android-8-oreo/shield-tv-2017-root/

Updated. This is an "easy" version of what [MENTION=3373302]ACiDxCHRiST[/MENTION] posted in another thread. The tutorial doesn't teach you how to patch your bootloader - just provides you with a pre-patched one to get the job done.
[Shield Android TV Android Development] sash11:
I've copied full OTA from latest ingeenering build 7.2.3 30.6.131.70 for 2017 16gb version. Also patched boot.img from it with Magisk 18.1. My shield is now rooted.

PUBLICe8f469c5f07f62ef251dc997871e963b.zip

patched_boot_7.2.3.img
[Shield Android TV Android Development] darkuni:
I feel like we're starting to hijack this thread with non-TWRP related stuff.

That 7.2.3 build .. have you attempted to use a 7.2.2 patched boot image with it?
[Shield Android TV Android Development] sash11:
Just wanted to post it here. Feel free to remove)

I meant 7.2.3. This is engineering latest build for those who signed up for an early program.

https://forums.geforce.com/default/...ld-experience-7-2-2-test-images/post/5957122/

I used 7.2.3 patched boot with it of course.
[Shield Android TV Android Development] darkuni:
Thanks for sharing man. I guess we can take this discussion elsewhere.
[Shield Android TV Android Development] sash11:
If one only needs to root his/her shield, TWRP is no longer necessary. I've rooted mine with simply flashing patched boot.img in fastboot. Not sure if this has been shared here, but here is patched boot.img for Shield 2017 16gb that I patched and flashed myself for latest official build 7.2.2. Patched with Magisk 18.1

patched_boot_7.2.2.img
[Shield Android TV Android Development] mikty:
I have the 2015 pro model so your first tutorial will be ok thanks for continuing to share working solutions

Regards
[Shield Android TV Android Development] mLgz0rn:
https://xdaforums.com/shield-tv/general/guide-root-nvidia-shield-experience-t3882254
[Shield Android TV Android Development] sash11:
That's my post about a different build. Why would you point me to my own post?
[Shield Android TV Android Development] mLgz0rn:
It's not though.

It's to a huge thread on how to root using magisk and patch the boot.img
[Shield Android TV Android Development] sash11:
Ok. I have no problems with rooting through Magisk. Having somebody create detailed instructions is always good though.
[Shield Android TV Android Development] mLgz0rn:
Yeah, I'm also sorry I didn't really do it in a nice way.

But I just wanted to point out that there indeed was a post on how to get magisk working without using twrp.
[Shield Android TV Android Development] mikty:
Hi, thanks again darkuni, I just test with success to re root my device pro 2015 with your cleary tutorial and it work like a charm great job.
[Shield Android TV Android Development] Samuel Holland:
I know I had this problem in the past but a no verity universal zip fixed the bootloop. Just wanted to add in case it could help someone.
[Shield Android TV Android Development] trohn_javolta:
[MENTION=1416222]Steel01[/MENTION] Any news on twrp for latest Shield experience 7.2.3?

Is it gonna happen or discontinued?
[Shield Android TV Android Development] Steel01:
It's still a work in progress. I'm doing twrp and lineage work in tandem. And there's a pretty big blocker on lineage right now that I'm having to wait on Nvidia to fix upstream in their public source release. But what doesn't work on my last unofficial twrp upload? The one issue I've heard is SuperSU repeated and afaict, that's a SuperSU issue, something incompatible with the newer stock image.
[Shield Android TV Android Development] trohn_javolta:
Thx for the feedback! What I just grasped from this thread was that the version is experimental and shouldn't be flashed on the shield...

Back then I didn't really know how I could revert. I'll just flash it and try.... would be just interesting if backup and especially restore would work..

Could you just confirm that I could revert back by grabbing the recovery.img from latest dev os and in fastboot do: fastboot flash recovery recovery.img

And for flashing I would enter: fastboot flash recovery twrp......img right?

I'd like to have automatic nandroid backups set up, do you have an idea how I could do that? I noticed that adb over network works on my debian nas. But I guess backing up while the shield is running won't back up everything right?

Do you know if adb over network even works in twrp? If so, I'd need some way for twrp to trigger the update on my nas.

I guess easiest way would be to have the backup on a usb stick... But I'd like to get auto full nandroid backups on my nas somehow..would be nice.