This tutorial – especially Step 3 – has changed considerably. Please work through it carefully and report any issues to me immediately so I can help others.

We are rooting the Shield Android TV (2017; 16GB SKU) running Android 8.0 (aka Oreo) on v7.2.2. Note: This uses a special patched bootloader and will not work in future updates. You’ll need to apply FULL OTA upgrades to restore the bootloader, then repeat this tutorial with the proper version bootloader.  Looking for the Shield TV (2015; 16GB SKU) tutorial?  Click here.  Looking for the 500GB SKU tutorial?  Click here.

Step 1: Pre-Requisites and Warnings

Download the following items – Make sure you get the RIGHT patched bootloader for your Shield TV version:

Ensure you have the following items:

  • USB Mouse – optional
  • Shield Controller with USB Cable
  • Male to Male USB 3.0 Cable (Amazon; verified working) or possibly this gender change from Monoprice (if anyone tries it, please let us know success or failure)  Note: Many users have reported a USB 2.0 cable may work.  It probably depends on the cable quality, etc.

There is a chance you may need a USB hub to complete this tutorial. If you do not have one on hand, here is one from Amazon that is one day Prime shipping and should do the trick. Probably should have this on-hand before starting – just in case.  Take a look around your desk; many monitors have USB hubs built in.  Many keyboards act as a USB hub.If for some reason you have to pull the Male to Male Cable during the Fastboot process, you may avoid using a USB hub IF you haven’t used Adoptive Storage.

Data Destruction Notice

Unlocking the bootloader will ERASE EVERYTHING internally (not on your external SD card if present; adopted storage users may want to make a backup of their SD card contents).  Make sure you have everything saved off and backed up.  You’ll have to resign into Google – so if you use two-step authentication, be sure to have your Google Authenticator app ready.

The process of rooting will not destroy any data.You will need to be able to see your PC AND the Shield TV’s HDMI out in order to perform this.  I used one monitor with two inputs and flipped back and forth as needed.TWRP doesn’t currently work on 4k displays!  Use a 1080p display to complete this tutorial.

Step 2: Preparation

  1. Install Minimal ADB and Fastboot (if you do not already have it installed).
  2. Ensure the Shield Family drivers are extracted somewhere on your system and you know where they are.
  3. Make sure you know how to get to Device Manager on your PC.
  4. Extract TWRP Recovery image from the ZIP file (and do yourself a favor and rename it to something easy like twrprecovery.img). Put this in your Minimal ADB and Fastboot folder (usually c:program files(x86)Minimal ADB and Fastboot).
  5. Copy supersu.zip (it may be named differently; you downloaded it above) into your Minimal ADB and Fastboot folder. Do not extract it.
  6. Plug your Shield TV into the PC with a Male to Male USB 3.0 Cable (Amazon; verified working).Note: Not all USB cables are created equally!  The linked cable above we have verified works.  Not all USB ports are the same.  Some on the back of the PC may work better than those on the front.  Use a USB 3.0 port (you can tell if it is blue inside) – that is what we used.  USB 2.0 may work but that is untested.
  7. Plug your Shield Controller into the USB port right next to the HDMI cable.  The other port will NOT work.  Note: If your bootloader is unlocked already, you don’t need to do this.
  8. Confirm drivers for ADB are installed:
    1. On your PC, go to Device Manager.  Find the yellow (!) ADB device (depending on your version of Windows, it may read differently).  If none exist, you probably already have drivers.  Skip to step 9.
    2. Right click the device and select Update Driver.
    3. When offered, browse your computer for the driver and point it to the Shield Family Drivers folder you extracted in Preparation Step 2 above.
    4. When finished with the driver install, the (!) yellow device should be gone.
  9. Enable Developer mode on Shield TV
    1. On the Shield TV, go to Settings->About->Build (click 7 times on BUILD to unlock developer mode)
  10. Enable USB Debugging on Shield TV
    1. Settings -> Developer -> Debugging; set to On
    2. A popup should appear asking for this PC’s authorization.  Check the Don’t ask again for this PC box and select Allow.  If it doesn’t show up now, it will later.
  11. Enable PC connection to Shield TV
    1. Go to Settings -> Storage & reset
    2. Under SHIELD storage access, turn on Using USB

Step 3: Root Procedure

  1. Install Magisk Manager and Sideload Launcher
    1. Make sure you have the Magisk Manager apk (Magisk-Manager700.apk or whatever you named it when you downloaded it above) in your Minimal ADB and Fastboot folder.
    2. Make sure you have the Sideload Launcher apk (sideload-launcher-android-tv.apk or whatever you named it when you downloaded it above) in your Minimal ADB and Fastboot folder.
    3. Launch Minimal ADB and Fastboot from the Start Menu or icon.  This puts you in a black DOS box.
    4. Type “adb devices” and make sure your Shield TV appears.  Note: If you didn’t have a popup on your screen in Step 10.2 above, it probably will appear now.  You’ll have to authorize the PC before it will show up under adb devices.
    5. Type “adb install magisk-manager700.apk” (or whatever you named it) and hit enter. You will get a success message in the DOS box window.
    6. Type “adb install sideload-launcher-android-tv.apk” (or whatever you named it) and hit enter. You will get a success message in the DOS box window. If you already have Sideload Launcher previously installed, this won’t work – nor is this step necessary.
  2. Reboot into Bootloader on Shield TV
    1. Type “adb reboot bootloader” and hit enter.  The Shield TV should reboot into the bootloader screen.   Note: This can take several seconds on a black screen.  Bootloader won’t show on a 4K display.  Use a 1080p display.
    2. If you are sure Fastboot drivers work and you do not need to unlock the bootloader, jump to Step 9.
  3. Verify Fastboot Drivers are installedNote: If Windows complains about the USB port (Driver Descriptor, etc.) under Universal Serial Bus Controllers and your device doesn’t show up with “fastboot devices” – change ports.  I’ve NEVER seen this happen before now.  Switching USB ports solved the issue.
    1. On your PC, go to Device Manager.
    2. See if a yellow (!) exists that mentions FASTBOOT.  If not, continue to Step 4 to unlock bootloader.
    3. Right click the device and select Update Driver.
    4. When offered, browse your computer for the driver and point it to the Shield Family Drivers folder you extracted in Preparation Step 2 above.
    5. When finished with the driver install, the (!) yellow device should be gone.
    6. Type “fastboot devices” and make sure your Shield TV is visible.
  4. Unlock Bootloader (skip if you already unlocked your bootloader)
    1. Type in “fastboot oem unlock” and hit enter.  EVERYTHING ON THE SHIELD TV WILL BE LOST (other than portable storage)
    2. You will see a prompt on the screen.
    3. Confirm to unlock the bootloader by pressing A on the Shield Controller. Do not be impatient!  Let it finish.
  5. Reboot to Shield TV Interface
    1. Once the bootloader is unlocked, reboot the Shield TV (unplug/plug in) and return to the Shield TV main interface (you will have to go through setup again).
  6. Repeat Preparation: Steps 9 and 10 above to re-enable Developer/USB Debugging.  Note: at some point you will have to re-authorize your PC again; if an ADB command fails, be sure to look at your screen for the authorization prompt.
  7. Unplug the Shield Controller and plug your mouse into the same port.From this point forward you will receive a warning screen on boot, saying that the software cannot be checked for corruption.  You can ignore this; it will boot the system in 5-10 seconds.
  8. Reboot to Bootloader
    1. Type “adb reboot bootloader” and hit enter. The Shield TV should reboot into the bootloader screen.
  9. Install the Magisk Patched Bootloader
    1. Type “fastboot devices” and make sure your Shield TV is visible.
    2. If your Shield TV is listed, type “fastboot flash boot patched_boot_722.img” (or whatever you named it) and hit enter.
    3. Type: “fastboot reboot” and hit enter. Your Shield TV will reboot into the operating system.
  10. Run and update Magisk
    1. Navigate to your Apps on the Shield TV and run Sideload Launcher.
    2. Look for the Magisk Manger app (looks like an Anonymous mask of multi-colors) and run it.
    3. If all is well, you should see that Magisk and Magisk Manager are both installed and up to date. If Magisk doesn’t show installed, you may need to repeat this block of instructions.
    4. Update Magisk and the Manager if prompted to do so.
    5. Exit Magisk Manager
  11. You are now rooted!  Test your root apps now.
  12. Optional: If you want to be able to take OTA versions in the future (you’ll lose root), then go to Settings, Developer options, scroll to the very bottom and turn on Provide full system upgrades.

If Something Goes Wrong

First, don’t panic.  It is pretty hard to permanently “brick” the Shield Android TV just by trying to root it.

No matter what may go wrong, flashing a stock image should put you back in working order.

Follow our tutorial: Tutorial: Restore to Stock Image (Shield TV)

Obviously if your Shield Android TV is stuck in an infinite boot – you cannot reboot to Fastboot from your PC.  You have to do it the “hardware way”.

  1. Unplug your power cable
  2. Plug in your New Shield game controller with the included USB cable into the USB port closest to the HDMI cable
  3. Hold down buttons A & B.
  4. While holding down the two buttons, plug in your power cable (Keep holding down the buttons)
  5. If all went well, the Fastboot menu will show up.

Changelog and Credits

This process originally comes from this XDA thread.  I take no credit for the act; all I’m doing is documenting an easy way to do it.  This tutorial assumes you are running a Shield TV (2017; 16GB) and you have the OTA installed that upgrades you to Oreo.

  • 2019-03-13: Added a patched 7.2.3 bootloader. Make some changes to reflect turning on FULL OTA updates.
  • 2019-03-09: The root process now uses Magisk instead of SuperSU. Tutorial updated to reflect changes.

How to invoke the Android “Fastboot” Menu on SHIELD TV

Answer ID 4359 Updated 03/23/2018 03:10 PM

HOW TO INVOKE THE ANDROID “FASTBOOT” MENU ON SHIELD TV


The new SHIELD TV (16GB):

If you own a SHIELD Controller

  • Unplug SHIELD TV.
  • Connect SHIELD controller to SHIELD TV with a USB cable (use port closest to HDMI).
  • While holding the A and B buttons at the same time, connect power to SHIELD TV.  

If you do not own a SHIELD controller 

  • Unplug SHIELD TV.
  • Connect a USB keyboard directly to SHIELD TV (use port closest to HDMI)
  • While holding the “A” and “B” keys down at the same time, connect power to SHIELD TV.
  • Once you enter Fast Boot mode, on the keyboard use the “X” and “Y” keys to navigate the menu and “A” to select 
     

SHIELD TV Pro or SHIELD TV (2015)

  • Unplug SHIELD TV.
  • Connect a Micro USB cable from the Micro USB port on SATV to a PC.
  • Connect power back to SHIELD TV.
  • Wait 2 seconds, and then hold the NVIDIA power button on SHIELD TV for 5-6s until you see the fastboot menu on the display.

If your computer’s waking up from sleep without any intervention from you, it’s likely another program or device is waking it up. Here’s how to find out what woke it up last.

We’ve shown you how to find out what’s keeping your computer from going to sleep, but if your computer keeps waking up after you put it to sleep, there’s a similar solution.

For Windows: If your computer is waking up regularly, finding the culprit can be tough—but finding the most recent wake cause is a good place to start. To do that, go to Start > Programs > Accessories, right-click on Command Prompt, and open it as an administrator. Then type:

The output will tell you what woke up your computer last, which—if you didn’t initiate it yourself—is probably your culprit.

Sometimes, unfortunately, it doesn’t give you quite enough information to deduce the problem, so you have to look elsewhere. Often, it’s a result of a “wake timer,” which can be a program, scheduled task, or other item that’s set to wake up your computer when it runs. You can disable wake timers in Windows’ Power Options. You may also find that your mouse or keyboard is waking up your computer even when you don’t touch them. For full instructions on how to dig deeper and fix these problems, check out this article at the How-To Geek.

For Mac: If you want to find out what woke up your Mac at a specific time, you can usually find it logged int he Console app. Just head to /Applications/Utilities, open up Console, and search for:

You should get a list of the last few wakes, and the reasons they were triggered.

Windows Setup, the Windows installation tool, unfortunately doesn’t provide any graphical tools for shrinking or expanding an UEFI System Partition (ESP; sometimes EFISYS). You can still create a custom-sized ESP by side-stepping out of Windows Setup and into the Command Line for a minute to partition the disk to your liking. I’ll walk you through the process in this tutorial.

This tutorial assumes you’re working with an empty disk, and that your computer is UEFI compliant. You may need to delete any existing partitions on the drive before proceeding. You can’t rely on this tutorial to grow the UEFI System Partition (ESP) on an existing installation as any attempt would be blocked by your existing partition boundaries. Windows won’t let you recreate an UEFI system outside the Windows Setup installation program. You should follow this tutorial during the initial Windows installation process with Windows Setup.

You are responsible for any data loss and to ensure that you have adequate backups of your own data. Unplug disks you don’t intend to use during the installation to avoid data loss. This is your only warning.

So you’ve booted up into Windows Setup from your installation media, and you’ve selected to perform a Custom installation. Whether you’re planning to and preparing to dual-boot with Linuxor just want to provide a larger margin of error; you may have noticed that the default 105-or-273 MB (100-or-260 MiB) partition for the UEFI System Partition is a tad small. (The default ESP size depends on your disks physical sector size.)

You need to decide what size you want your UEFI System Partition to be before you begin. You can take a pause here to read How large should you make your UEFI System Partition? before your proceed as it will be quite challenging to attempt to change the size you allocate to your ESP after you’ve installed the system without reinstalling.advertisement

Once you’ve decided on the approperiate size for your computer and needs, then you can follow the these steps to proceed. The tutorial begins from the first step of the Custom installation screen in Windows Setup (screenshot of this screen at the end of the article):

  1. Select your installation target and make sure it has no partitions (except unallocated space)
  2. Click the New and then the Apply button.

You should now have four partitions: Recovery, System (ESP), MSR, and Primary.

  1. Select each of the System, MSR, and Primary partitions in turn and click the Delete button to delete these partitions. Leave the Recovery partition in place.
  2. Press Shift+F10 to open the Command Prompt
  3. Type diskpart.exe and press Enter to open the disk partitioning tool
  4. Type list disk and press Enter to list out your disks
  5. Type select disk n where n is the number for the disk you want to install to as identified by the above command and press Enter
  6. Type create partition efi size=550 where 550 is the desired size of the ESP in Mebibytes (MiB), and press Enter
  7. Type format quick fs=fat32 label=System and press Enter to format the ESP
  8. Type exit and press Enter to exit the disk partitioning tool
  9. Type exit and press Enter again to exit the Command Prompt

You should now be back in the graphical Windows Setup partitioning tool where nothing has changed since the last time you looked at it.

  1. Click the Refresh button to detect your partition changes

You should now have a disk with a default Windows Recovery tools partition, a 500 MiB UEFI System Partition, and some unallocated space for your Windows installation.

  1. Select the unallocated space from the disk list and click the New button to automatically recreate the MSR and System partition in the remaining space

The final result should look something like this:

Screenshot of a 550 MiB ESP in Windows Setup

That should be all. From here, you can continue with your Windows installation as normal. If you should run into problems with the system not booting after completing this tutorial, then please refer to your systems manufacturer documentation for any special hardware requirements regarding UEFI boot and the UEFI System Partition in particular. Some older hardware models required non-standard FAT16-formatted ESPs, or had special partitioning size requirements. You should be able to adjust the steps in the tutorial to accommodate such requirements.

Although, having migrated to .net Core for the most part,we all have to support our older applications using .net Framework. As a part of routine, you may tend to update the .net framework in your application only to find out that your test or even prod (yikes!) do not have the latest framework installed. 

One way to find the version is using microsoft’s documentation here:

https://docs.microsoft.com/en-us/dotnet/framework/migration-guide/how-to-determine-which-versions-are-installed

You, look at the complexity, and may just give up. I’ve found an easier place to check the same. And it positively has worked for me every time.

All you need is to browse to a folder path:

C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework.NETFramework

Here’s the structure:

And That’s it. You will see all the framework’s installed on this machine, even a minor version has a different folder as well. Easy on the eye indeed.

How to get multiple TeamCity build agents running on one server.

Found this the hard way, that there is an key thing that needs to be changed before finishing the setup as per teamcity’s official instruction.

First log in to the server where you want the agents to run then open TeamCity from a browser on that box.

Go to the Agents tab.

From the top right of the page choose Install Build Agents then MS Windows Installer.

When prompted choose to run the agent installer. You may have to be an administrator since this will be installing windows services.

Choose the directory where you want the agent configuration and working directories to live. I put them under the TeamCity home directory.

Take the defaults as you work your way through the installer.

The agent directory is being configured.

Here it is important that you choose a unique name and port. The directories should be consistent with your previous choices. You may need to change the server URL and port.

When this popup appears do not click OK yet.

Open an Explorer window and navigate the the launcher/conf directory under the build agent directory you configured above.

Edit wrapper.conf and change the name of the ntservice to match your agent name as appropriate. This is important because each agent runs under a different service and they must have unique names, otherwise only one will connect at a time.

Now you can click OK on the popup.

And choose the defaults the rest of the way through the installer.

If you open Services

You should see the service you named.

The new agent should connect and be visible from the TeamCity Agents page within a few moments.

Repeat the steps to add additional agents.