yashsingh1/xdaforums huggingface dataset:
[Shield Android TV Android Development] Steel01:
There's also the option of running 'fastboot boot twrp.img' (of course replacing twrp.img with whatever I named the experimental release). But yeah, you can always flash back recovery from the official recovery image. If you're not running the dev release, then use the recovery from the real stock recovery image. It is an experimental release in that I haven't fully run it through the paces. Pretty sure standard functionality works, though. Backup, restore, zip flashing, ota flashing, etc. The only thing I've specifically tested is zip flashing, though. I can install my lineage zips (for all of its boot logo hanging glory atm...)

I can't entirely speak to the last part. Not ever done any automated backups. Adb over network is not available in twrp. The openrecoveryscript that's used by ota updates could potentially be used to automate a backup. Again, I'm not extremely familiar with it. But basically, you'd write the script to somewhere in /cache, set a bit in /misc, then reboot to recovery. You might be able to ask about that in #twrp on freenode. They might even have better / simpler solutions than that.
[Shield Android TV Android Development] trohn_javolta:
Yeah, fastboot boot gets a bit annoying as I have to connect my pc every time. I'll try to flash it. I'm realizing now I probably cannot control twrp with my logitech bt keyboard :rolleyes: Maybe works using the unifying receiver..

Oh, I have one last question, it's off topic but since you're also dev of los image maybe you can help: In shield experience system settings I can mount network shares, which is great. But I only have read settings this way :( I know it's intended by nvidia, for security reasons. Currently only 2 apps can get write access to mounted shares, emby and plex...both of which I don't use. Of course apps with built in smb client can write to the share but I'd like it to be possible systemwide for every app. For example, titanium backup app currently backs up to a plugged in usb stick but I'd want it to back up to the network share.

I couldn't find much help over at shield subreddit and nvidia forum.

Do you have any idea how I could archive write permissions on mounted network shares? I'm rooted using magisk.

Only one answer from nvidia made sense, saying I'd have to build my own image with custom fstab file... but idk how to do that+ I don't wanna do that.

I still think there has to be some other, easier way, especially with root.

I'm not fixated on the mount way in the system settings, just any way on the shield to mount smb shares systemwide would be great. So that every app will "see the shares as local hdd's". Hope you know what I mean.
[Shield Android TV Android Development] Adromir:
If the kernel already supports cifs you could mount the shares right after boot using an app like tasker
[Shield Android TV Android Development] Circaflex:
ive been out of the rooting scene for so long, do i need root to install twrp? im looking to install lineageos on my shield
[Shield Android TV Android Development] Circaflex:
maybe someone can help me out here, i flashed twrp and when i try and reboot to recovery i get the little android guy with the red exclamation mark "no command" edit: fixed by using the experimental build steel posted
[Shield Android TV Android Development] I_did_it_just_tmrrow:
Sadly this does not boot on my:

Shield Pro Foster 500GB with 7.2.3 and Magisk-Bootloader.

this is showing by fastboot:

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot twrp-20190201-foster-experimental.img
creating boot image...
creating boot image - 2048 bytes
downloading 'boot.img'...
OKAY [ 0.031s]
booting...
OKAY [ 0.031s]
finished. total time: 0.063s

But then it stucked on the nvidia logo.

Any idea?

Greetings by Idijt

EDIT:

After 1 hour of trying different settings/constelations I came to the idea to unplug the HDMI cable, pluged in only the Micro-usb cable, type in my win10 minimal adb cmd: fastboot boot twrp-20190201-foster-experimental.img

Then fastboot is waiting for a fastboot device. Then I just start the shield pro with the bootloader start. (Holding the power button 2 seconds after plug in the power cable)

So if you also stuck with Steel01's twrp-20190201-foster-experimental.img with the nvidia logo or it always failed and starts the system, you should try:

0. Shutdown your shield

1. plug all cables off

2. Start your fastboot engine and type in: fastboot boot twrp-20190201-foster-experimental.img (in the fastboot cmd is written something like: Waiting for device)

3. Plug your micro-usb cable into your foster/shield pro device and your fastboot host

4. Follow the instructions here to start your foster device derectly into the bootloader

5. You should hear the device plugin sound in Windows 10 and you should see a non-failed process within the fastboot cmd

6. Plug in your HDMI cable and wait about 20 seconds to see the twrp
[Shield Android TV Android Development] trohn_javolta:
[MENTION=1416222]Steel01[/MENTION] Are you in any way involved in the los for nintendo switch development? I read it will get twrp and I wonder if it's a completely different twrp than this and if it can be used for the shield tv.

I still didn't flash this latest twrp version to my shield tv. Tbh experimental has a bad taste for me :/ and as stated imo it's a pita to always connect a pc and only boot the recovery..

I'm still looking for a way to establish automatic twrp/nandroid backups to a storage (preferably to a nas share). I know I can trigger the backups with the help of Tasker and openrecoveryscript but of course for that to work, twrp must be present on the shield tv permanently. I already done many tweaks and changes to my shield so I don't want to risk flashing a recovery that's considered as experimental.

---------- Post added at 06:52 AM ---------- Previous post was at 06:52 AM ----------

[/COLOR [MENTION=1416222]Steel01[/MENTION] Are you in any way involved in the los for nintendo switch development? I read it will get twrp and I wonder if it's a completely different twrp than this and if it can be used for the shield tv.

I still didn't flash this latest twrp version to my shield tv. Tbh experimental has a bad taste for me :/ and as stated imo it's a pita to always connect a pc and only boot the recovery..

I'm still looking for a way to establish automatic twrp/nandroid backups to a storage (preferably to a nas share). I know I can trigger the backups with the help of Tasker and openrecoveryscript but of course for that to work, twrp must be present on the shield tv permanently. I already done many tweaks and changes to my shield so I don't want to risk flashing a recovery that's considered as experimental.
[Shield Android TV Android Development] I_did_it_just_tmrrow:
Sorry, it is quite hard to understand you?

I guess that you had the same problem like me once and that you can now just Boot into your (twrp?) recovery but not into your System. Right?
[Shield Android TV Android Development] TektTheGeek:
so basically it seems as if im having the same issues as a few others but here goes. SO today i decided to finally take the plunge and try the twrp experimental build for my darcy 16gb 2017. I used fastboot boot........instead of fastboot flash because I wanted to make sure that twrp worked in the first place. After seeing twrp boot up, I decided to back up my darcy just incase of anything and now when I try to boot up, it keeps restarting after the nvidia shield logo. Im not sure if i messed something up because i used fastboot boot and then did a nandroid backup instead of doing fastboot flash and then a nandroid backup, but would greatly appreciate if anyone can help me get things working again
[Shield Android TV Android Development] TektTheGeek:
I dont have the controller and Ive been trying this with a usb keyboard. Will I need to purchase a controller or is there another way to complete this process?
[Shield Android TV Android Development] Adromir:
It definitely works with an USB Keyboard. Maybe change the USB port it is plugged in, I think it has to be the one next to the hdmi port
[Shield Android TV Android Development] TektTheGeek:
I will try this later on, BUT just incase, Nvidia is actually sending a replacement! I wanted to know if theres some sort of bug when doing fastboot boot vs fastboot flash? I was skeptical because twrp is still an experimental build, which is why i did fastboot boot in the first place
[Shield Android TV Android Development] meksis:
Please add the ability to backup the Vendor section. Also, twrp unfortunately does not see external memory drives. Especially useful when doing backups of the system.
[Shield Android TV Android Development] BXM500:
Does the 3.2.3.0 support Android Pie?

edit: Already tried and also the experimental version. No luck. Won't boot from fastboot mode.
[Shield Android TV Android Development] Steel01:
Waiting on the source release atm. I do have a twrp build that boots on the 8.0.0 bootloader, but it's still somewhat quirky. Don't want to upload it quite yet. Once things settle a bit more and I get some more testing in, I'll at least upload an experimental version.
[Shield Android TV Android Development] darkuni:
Combined with the latest Magisk do we have a rooting solution?
[Shield Android TV Android Development] Steel01:
I can't speak to that. I'm a Lineage dev, focused on that with TWRP as a side/additional project. I don't like the concept of magisk, so I don't know if it'd work or not. Also fwiw, I've not even booted the new stock image, just grabbed the bootloader and started on twrp and lineage. Once I get a build up, someone should be able to verify pretty quickly, though. Gonna be a few days, though. I'm pretty busy through the weekend.
[Shield Android TV Android Development] trohn_javolta:
So what about shield experience 7.2.3 twrp? Is it save now to flash that latest experimental twrp image? I still didn't flash it because of lacking info wheather it's considered stable now maybe? If not, do we get a stable twrp version for 7.2.3? As long as there's no way to root shield experience 8 I won't update to it and also don't need a twrp version for it.
[Shield Android TV Android Development] Steel01:
I'll have to do a test or two, but I think a twrp built for the stock 8.0.0 bootloader should work on 7.2.3's.
[Shield Android TV Android Development] trohn_javolta:
Great. Once pie on the shield is rootable via magisk I'll update anyways.

Are you involved in the android development on the nintendo switch in any way? Is it your twrp build running on there or weren't you involved at all?
[Shield Android TV Android Development] protechtedd:
TWRP 8.0

[MENTION=1416222]Steel01[/MENTION] Hi there. I'm stuck on 8.0 Pie but cannot install the TWRP from their main website. Would you be willing to post your TWRP version or PM me a link please? Glad to help you test it if you want me to give you feedback on it. TIA
[Shield Android TV Android Development] Steel01:
I've currently got some time tonight. I'll see about running another build and see what it does. Fair warning up front, though. I'm gonna do little more than make sure it boots and displays. Anything past that will be up to y'all to test. I don't even have a stock install, it's all lineage works in progress right now. If it boots, I'll post it to my afh account.
[Shield Android TV Android Development] Steel01:
Well, it does technically boot. HOWEVER. You have to flash it to recovery and either use 'reboot recovery' or boot recovery from the fastboot menu. A 'fastboot boot' WILL NOT WORK. This is due to how system as root is handled. I'll look into making it more flexible later, but this is how it is for now.

Insert standard disclaimer here, beware of dragons, abandon hope, etc, etc. I know it boots and adb works, that's about it. If you haven't done much tinkering with custom roms or modding or whatnot, I'd highly recommend letting some of the other users try first.

twrp-20190201-foster-experimental.img
[Shield Android TV Android Development] protechtedd:
Thanks, so I gave it a try by flashing it via fastboot, rebooted into recovery, and I got the TWRP logo. It then sat there for a couple minutes unchanging, then rebooted itself into System again. Have you experienced this? Anything you want me to try
[Shield Android TV Android Development] Steel01:
That's... weird. Just adb'ed back into my foster_e_hdd and the build I posted has an uptime of 45 minutes. So no, no random reboots here.
[Shield Android TV Android Development] JamesKinds:
Hi,

I am battling to get TWRP loaded on my Shield TV 2017 (Darcey).

I've tried to load TWRP onto version 8.0 and 7.2.3. I've tried standard TWRP (foster) and experimental TWRP mentioned in this thread.

I have no problem unlocking boot loader, down grading or upgrading images, but I can't get TWRP installed.

Can anyone offer any suggestions. Do I need to be on a specific version of the main ROM i.e. less than 7.2.3?

Any help would be appreciated. I want to install LineageOS on my 2017 Shield, but so far I'm stumped by my inability to install TWRP.

Any help or suggestions will be greatly appreciated.
[Shield Android TV Android Development] JamesKinds:
Update.

I managed to get the experimental TWRP to boot on the Shield 2017. However when I try and sideload the ZIP for LineageOS I get an error about unsupported boot versions (see attached picture).

Does anyone have any ideas?
[Shield Android TV Android Development] whiteak:
You may want to try this. http://www.videomap.it/forum/viewtopic.php?f=25&t=2387&sid=3cd69fbb4f9ac0d63d57844080159221
[Shield Android TV Android Development] JamesKinds:
Thanks, I'll definitely give it a look. The only issue for me is that it looks like it has Google Play Services baked into the ROM. I was keen to get LineageOS up and running without Play Services just to see what it was like.

None the less, thank you for the link. It certainly is worth trying out.

Kind regards

Jk
[Shield Android TV Android Development] oldpoem:
rootfan kindly provided working twrp for shieldtv pie. I tested and flash his prerooted kernel. It works on Shield TV 2015 (Foster). Not sure if it works on 2017 or not.

https://xdaforums.com/shield-tv/development/kernel-overclock-kernel-2-22-ghz-t3943079
[Shield Android TV Android Development] dk1keith:
will this TWRP work to make backup/restore? I was able to boot the recovery using fastboot but the micro sd nor the usb thumb drive were recognized as storage.

thanks
[Shield Android TV Android Development] JSMdu974:
Hello,

I want to install lineage os on my shield 2017 16g (darcy).

I success to boot in fastboot, to unlock the bootloader but i can't boot on the twrp : the shield stay blocked on the nvidia logo.

I tried many twrp but it's the same... :c

Someone have a solution for this ?
[Shield Android TV Android Development] lingarajug:
Once you unlock bootloader it should restart to wipe data and cache, then reboot back to fastboot and boot to twrp and install the mods and at the end dont select option to install permanently as it is causing boot loop, use twrp temporarily to flash the kernel, hope it helps.
[Shield Android TV Android Development] JSMdu974:
So, i should use adb/fastboot to wipe partitions data and cache ?

Then, i will just boot (not flashing) on twrp ?

_________

Since the twrp didn't boot, i thought i can flash it by using the twrp apk. But it needs root privilege, so i tried to flash a patched boot file (with magisk) and... boot loop on nvidia logo.

I think that's a brick because i can't use other method than adb to access on the bootloader. I tried to manually boot with keyboards, with the pad controller but didn't work.

Game over ?
[Shield Android TV Android Development] Steel01:
[MENTION=10274963]JSMdu974[/MENTION]: The current official twrp releases are for older satv bootloaders. Namely Shield Experience 7.1.x and earlier, also used by lineage 15.1. See below.

I was hoping to get some testing in on newer devices before I released another experimental build. But someone pointed me at a method to make it more stable in general for the system as root bootloaders. So, I'm going to go ahead and upload it anyways. This is built to work with Shield Experience 8.x releases and the wip lineage 16.0 builds. This *should* work on both mdarcy and sif, but I don't have an mdarcy yet and I haven't figured out how to flash stuff to sif. So as always with experimental builds, ymmv. If someone does try this on an mdarcy, please report back how it works.

twrp-20191102-foster-experimental.img
[Shield Android TV Android Development] lingarajug:
I am not sure, try downloading the dev version of the rom from nvidia website and flash it and dev version is prerooted rom, then try twrp again.
[Shield Android TV Android Development] SkOrPn:
What are the new code names for the 2019 Shield TV's just released? And will this work on those possibly? I have a buddy with the new 2019 Pro (he's in the UK), but after seeing all of the headaches and wiping that this does he decided its not worth it. Plus when he unlocked it it removed his Dolby Vision license from the unit (and who knows what other features were missing), and Dolby Vision was the only reason he wanted this gen Shield and the AI upscaling which we have since determined to be a worthless feature.

If we can keep the device from losing the Dolby Vision license he would be willing to try again, but for now he told me it will stay locked down. Thanks for your hard work on these TWRP builds, its much appreciated. And oh crap I forgot to mention, the only TWRP I had for him to try was the one that was posted in the Performance Enhanced Overclock Kernel by [MENTION=4180946]rootfan[/MENTION]. By the time I thought about trying the official TWRP builds it was too late and he was already put off by the process and loss of Dolby Vision. Lol
[Shield Android TV Android Development] Steel01:
[MENTION=500006]SkOrPn[/MENTION] The two new devices are named sif (non-pro) and mdarcy (pro). I'm not certain that mdarcy actually reports such via ro.hardware, though. Some of the older kernel code looked like it would report darcy. But yeah, that build should work on any known nvidia x1 device. From The original foster to mdarcy to the Jetson tx1.

Need to find someome willing to do some experimentation with an mdarcy. I ordered a sif and am waiting to hear whether nvidia will be sourcing mdarcy's to devs. So far, neither have had recovery images uploaded. And the word from customer service is that there is no way to access fastboot on sif from a desktop. Still waiting to hear back from an engineering contact on whether that's entirely true. Sif has a usb port, it just doesn't have a header soldered down. If it really comes down to it, I'll cut a hole in my case and populate that header.
[Shield Android TV Android Development] SkOrPn:
Yeah he tried that build and it gave him fl;ashing rainbow colours or something. Maybe I can get him to report here exactly what he saw.
[Shield Android TV Android Development] Steel01:
Partial status update: So, I did get my twrp builds to boot on sif. After taking it apart and soldering a usb port to it. But, said usb port only works in fastboot, it doesn't come up in recovery or normal android. Looks like the dts disables it. Problem next: the dtb is wrapped in something. Uncertain if it's signed or just an avb or dtimage format. More research will be needed over time. If someone has an mdarcy, I'd really like to see my last experimental build tried on one.
[Shield Android TV Android Development] zecabra:
any news about twrp to foster_e that can install lineage in the new bootloader's?
[Shield Android TV Android Development] elliwigy:
Man, hope I don't need to resort to that lmao.. I been going the route of fastboot over ethernet using udp/TCP but don't have all the cables I need yet. In theory it should work, i just don't know much about it yet
[Shield Android TV Android Development] Steel01:
[MENTION=1365509]zecabra[/MENTION] The experimental builds I've posted do boot. But if you install current official Lineage, it'll downgrade the bootloader.

[MENTION=3812611]elliwigy[/MENTION] One would think a device without an exposed usb port would support the fastboot ethernet protocol. I've not found it, though. And a ticket with Nvidia customer care claimed that there is no way access fastboot on sif. Upgrade to mdarcy if you want that. :rolleyes:
[Shield Android TV Android Development] elliwigy:
do you have any diagrams for the soldering?
[Shield Android TV Android Development] Steel01:
[MENTION=3812611]elliwigy[/MENTION] I don't have a diagram, no. If you find a tear down video, you can see the five points next to the HDMI point. They are through hole solder points that need convection soldering. The part is available from a few different places, but as far as I can tell, this is the only part that has the right pinout.

https://www.mouser.com/ProductDetai...8LPOQ%2Byk2Wnkghg7F8r0AqLEhMERMJ5mGr/LLn0SA==
[Shield Android TV Android Development] elliwigy:
So a micro usb port?
[Shield Android TV Android Development] elliwigy:
fyi i ended up taking it back and got the pro.. i also got a full backup of all the partitions.. if you can use it let me know and I will upload it..

Currently trying to figure out roo tlol.. i can modify system and everything else but it never fully boots, it sits at the google logo and i have adb access.. i can gain root access using boot to twrp.. it works for the most part.. there are some slight issues with it.. like for example it thinks system is not mounted and can't detect it sometimes but this is because it is at /system_root/system.. this also means i can't flash zips that need to access system...

i suck at making or modifying kernels lmao.. system root also doesn't seem like a very reliable way to go either since most the security will need to be disabled and will likely break things..
[Shield Android TV Android Development] elliwigy:
in about device/settings it reports for the most part as mdarcy, X1+ etc. but of course in props and here and there i see reference to foster.. comparing to my regular 2017 shield it is a bit faster and i can actually notice on some content the AI upscaling really does make things look better that are in 1080 normally.. the downside is a lot of content isn't supported yet for the upscaling.. the mainstream services like disney+ and netflix and youtube etc. all work tho.. I must say it is nice having twice the internal storage and an extra gb of ram and of course usb ports lol.. Sif was not bad tho!
[Shield Android TV Android Development] elliwigy:
anddd im sorta bricked already lmao.. i have no idea which of these partitions are which except for a few.. i was trying to root n was messing with your experimental twrp (this still works) and some magisk.zips and modifying boot and recovery partitions.. also modifying prop.default etc... i was able to test n reboot fine until i was in twrp root shell then manually executed the boot_patch.sh on boot and recovery.. it keps saying something about proc/something not found.. i only tried to fastboot boot with it and it hangs on nvidia logo.. tried reflashing my backups trom before testing but still hangs on nvidia logo..

ive also wiped multiple ways and browsing around in twrp root shell the propsn stuff i edited is back to stock but still no boot lol.

im open to any suggestions anyone might have before i take it back and swap it out lol..

also for anyone curious or waiting for these before I did anything I booted to twrp and pulled each partition off /dev/block/by-name individually and zipped em up and uploaded :)

https://mega.nz/#!1FEn0CCQ
[Shield Android TV Android Development] elliwigy:
ro add theres 32 partitions in the zip.. im used to sammy devices and their naming conventions but so far i know the following:

APP=System or root mounted at /

LNX=boot.img

SOS=recovery.img

UDA=userdata

CAC=cache

vbmeta=vbmeta

vendor=vendor

the rest im still tryna figure out lmao.. hopefully will come in handy at least until nvidia decides to release some firmware or source.