BOOTMOD - Root your Shield In 1 minute (2015, 2017, & 2019)

Search This thread

jenneh

Senior Member
Every other time I've rooted a device I was installing a new image, a clean slate each time, but for this the whole purpose is to recover some system files from a removable usb that I formatted as external so I can replace the drive -- will this process erase the current system?
Hi there! Yes, the step where we have to unlock the bootloader will unfortunately erase the system.
 
  • Like
Reactions: madmaximux

Cestults

Member
Jun 5, 2016
13
14
Hi, does anyone have the 9.1.1 firmware & bootmod for the 2015 shield 16GB? I’d like to give this a shot. My shield is basically bare bones I’ve deleted virtually every app and done everything I can do to gain additional space on the internal storage. Even with that it’s to the point that I can’t even update apps because there isn’t enough space to download the updates lol. I’ve read about a rogue log file taking up tons of space but need root access to be able to delete it. SHIELDS STORAGE SPACE IS TOO LOW lol
 
Last edited:

Starz04

New member
May 31, 2023
3
2
Thanks for your reply!


I don't like all the launcher apps. So, i hope that it is possible to disable the discover tab and/or disable the ads in the future.

PS:
I have the 2019 version.
Hello mate. it is actually possible to downgrade Shield 2019 to OS 8.2.3. I used this guide and it worked flawlessly: https://florisse.nl/shield/

Obviously huge thanks to the guy who created it as it saves people so much research and trial + error. Basically alot of time saved.

Using this tweak guide, I've deleted close to everything from google and Nvidia (bloatware + data collecting) on the 2019 Shield TV: https://florisse.nl/shield-tweaks/

I've removed the Play Store and Google Play Services, ATV Core Services, ATV Remote Service, Backdrop, Basic Daydreams, Chromecast and many other things.

I don't use Netflix, Amazon Prime Video, Plex etc. So everything was removed from the Shield.

This is my ADB batch file to uninstall pretty much everything unneeded:

Code:
adb shell pm uninstall -k --user 0 com.google.android.speech.pumpkin & adb shell pm uninstall -k --user 0 com.google.android.tts & adb shell pm uninstall -k --user 0 com.google.android.videos & adb shell pm uninstall -k --user 0 com.google.android.tvrecommendations & adb shell pm uninstall -k --user 0 com.google.android.syncadapters.calendar & adb shell pm uninstall -k --user 0 com.google.android.backuptransport & adb shell pm uninstall -k --user 0 com.google.android.partnersetup & adb shell pm uninstall -k --user 0 com.google.android.inputmethod.korean & adb shell pm uninstall -k --user 0 com.google.android.inputmethod.pinyin & adb shell pm uninstall -k --user 0 com.google.android.apps.inputmethod.zhuyin & adb shell pm uninstall -k --user 0 com.google.android.tv & adb shell pm uninstall -k --user 0 com.google.android.tv.frameworkpackagestubs & adb shell pm uninstall -k --user 0 com.google.android.tv.bugreportsender & adb shell pm uninstall -k --user 0 com.google.android.backdrop & adb shell pm uninstall -k --user 0 com.google.android.leanbacklauncher.recommendations & adb shell pm uninstall -k --user 0 com.google.android.feedback & adb shell pm uninstall -k --user 0 com.google.android.leanbacklauncher & adb shell pm uninstall -k --user 0 com.google.android.apps.mediashell & adb shell pm uninstall -k --user 0 com.plexapp.android & adb shell pm uninstall -k --user 0 com.zattoo.player & adb shell pm uninstall -k --user 0 com.nvidia.tegrazone3 & adb shell pm uninstall -k --user 0 com.plexapp.mediaserver.smb & adb shell pm uninstall -k --user 0 com.google.android.play.games & adb shell pm uninstall -k --user 0 com.netflix.ninja & adb shell pm uninstall -k --user 0 com.amazon.amazonvideo.livingroom & adb shell pm uninstall -k --user 0 com.amazon.amazonvideo.livingroom.nvidia & adb shell pm uninstall -k --user 0 com.google.android.youtube.tvmusic & adb shell pm uninstall -k --user 0 com.android.vending & adb shell pm uninstall -k --user 0 com.google.android.gms

Keep in mind this is an extensive removal of pretty much everything. Payed apps etc. wont work with such cleanup. Most apps however do work- Kodi, Firefox, SmartTube, Speedtest, Fdroid, AdAware, Aurora Store (with private login, if you want to update some apps), Aptoide, Twitch, all sorts of Emulators etc.

The thing is that Google Play Store automaticall updates itself in the background, even if you disable it (it gets reenabled automatically) and I dont need that. If I want to update something, I will go to Aurora Store or Aptoide and update manually, but I dont want some sheety apps to be doing whatever they want in the background without asking.

And I didnt install a 3rd party Android Launcher, I use the default one, there are no more ads though after removing like 80% of trash bloatware and adware. The Android TV Home version is 2.1.3-320113730-f and I'm on ShieldOS 8.2.3. No ads to be seen and since even the Nvidia-OTA service was removed, it will never update the Shield by itself or even show a notification that there are updates available- which is exactly how I want it. Everything I need works fine in 8.2.3 and if I ever need an update, I will do it manually.

Also, while we're at it- it is possible to skip the initial login after factory restore, as seen on the picture attached. Source of it is: https://www.reddit.com/r/ShieldAndroidTV/comments/o8tpkx
However it is actually not required to downgrade Android TV Home app to version 2.0.10 to remove ads from the home screen. By simply downgrading to ShieldOS 8.2.3 (down from 9.1.1), the ads were removed from the main screen automatically. Then if you do some additional cleanup (like removing ATV Core Services and disabling autoupdate for Apps in Google Play Store), the ads will never show up.
 

Attachments

  • skip.initial.login.on.clean.os.png
    skip.initial.login.on.clean.os.png
    215.8 KB · Views: 48
Last edited:
  • Like
Reactions: legend0s

legend0s

Member
Apr 3, 2023
5
2
Hello mate. it is actually possible to downgrade Shield 2019 to OS 8.2.3. I used this guide and it worked flawlessly: https://florisse.nl/shield/

Obviously huge thanks to the guy who created it as it saves people so much research and trial + error. Basically alot of time saved.

Using this tweak guide, I've deleted close to everything from google and Nvidia (bloatware + data collecting) on the 2019 Shield TV: https://florisse.nl/shield-tweaks/

I've removed the Play Store and Google Play Services, ATV Core Services, ATV Remote Service, Backdrop, Basic Daydreams, Chromecast and many other things.

I don't use Netflix, Amazon Prime Video, Plex etc. So everything was removed from the Shield.

This is my ADB batch file to uninstall pretty much everything unneeded:

Code:
adb shell pm uninstall -k --user 0 com.google.android.speech.pumpkin & adb shell pm uninstall -k --user 0 com.google.android.tts & adb shell pm uninstall -k --user 0 com.google.android.videos & adb shell pm uninstall -k --user 0 com.google.android.tvrecommendations & adb shell pm uninstall -k --user 0 com.google.android.syncadapters.calendar & adb shell pm uninstall -k --user 0 com.google.android.backuptransport & adb shell pm uninstall -k --user 0 com.google.android.partnersetup & adb shell pm uninstall -k --user 0 com.google.android.inputmethod.korean & adb shell pm uninstall -k --user 0 com.google.android.inputmethod.pinyin & adb shell pm uninstall -k --user 0 com.google.android.apps.inputmethod.zhuyin & adb shell pm uninstall -k --user 0 com.google.android.tv & adb shell pm uninstall -k --user 0 com.google.android.tv.frameworkpackagestubs & adb shell pm uninstall -k --user 0 com.google.android.tv.bugreportsender & adb shell pm uninstall -k --user 0 com.google.android.backdrop & adb shell pm uninstall -k --user 0 com.google.android.leanbacklauncher.recommendations & adb shell pm uninstall -k --user 0 com.google.android.feedback & adb shell pm uninstall -k --user 0 com.google.android.leanbacklauncher & adb shell pm uninstall -k --user 0 com.google.android.apps.mediashell & adb shell pm uninstall -k --user 0 com.plexapp.android & adb shell pm uninstall -k --user 0 com.zattoo.player & adb shell pm uninstall -k --user 0 com.nvidia.tegrazone3 & adb shell pm uninstall -k --user 0 com.plexapp.mediaserver.smb & adb shell pm uninstall -k --user 0 com.google.android.play.games & adb shell pm uninstall -k --user 0 com.netflix.ninja & adb shell pm uninstall -k --user 0 com.amazon.amazonvideo.livingroom & adb shell pm uninstall -k --user 0 com.amazon.amazonvideo.livingroom.nvidia & adb shell pm uninstall -k --user 0 com.google.android.youtube.tvmusic & adb shell pm uninstall -k --user 0 com.android.vending & adb shell pm uninstall -k --user 0 com.google.android.gms

Keep in mind this is an extensive removal of pretty much everything. Payed apps etc. wont work with such cleanup. Most apps however do work- Kodi, Firefox, SmartTube, Speedtest, Fdroid, AdAware, Aurora Store (with private login, if you want to update some apps), Aptoide, Twitch, all sorts of Emulators etc.

The thing is that Google Play Store automaticall updates itself in the background, even if you disable it (it gets reenabled automatically) and I dont need that. If I want to update something, I will go to Aurora Store or Aptoide and update manually, but I dont want some sheety apps to be doing whatever they want in the background without asking.

And I didnt install a 3rd party Android Launcher, I use the default one, there are no more ads though after removing like 80% of trash bloatware and adware. The Android TV Home version is 2.1.3-320113730-f and I'm on ShieldOS 8.2.3. No ads to be seen and since even the Nvidia-OTA service was removed, it will never update the Shield by itself or even show a notification that there are updates available- which is exactly how I want it. Everything I need works fine in 8.2.3 and if I ever need an update, I will do it manually.

Also, while we're at it- it is possible to skip the initial login after factory restore, as seen on the picture attached. Source of it is: https://www.reddit.com/r/ShieldAndroidTV/comments/o8tpkx
However it is actually not required to downgrade Android TV Home app to version 2.0.10 to remove ads from the home screen. By simply downgrading to ShieldOS 8.2.3 (down from 9.1.1), the ads were removed from the main screen automatically. Then if you do some additional cleanup (like removing ATV Core Services and disabling autoupdate for Apps in Google Play Store), the ads will never show up.
Wow!

Amazing news!!

I will give it a try in the next few days.

Can't wait to downgrade to 8.2.3!

Thanks for the info! (-;

Best regards from germany
 

delfz

New member
Mar 13, 2019
1
0
Hello everyone! Can anyone help me please? My developer options is not opening, it's showing in my settings but once you clicked it it will not open. Thank you in advance for any help.
 

RedEyeMagpie

New member
Jun 10, 2023
4
1
Hello Friends~!

We now have a working method to achieve ROOT on STOCK Firmware!

A script has been made that can boot your shield into the bootloader, erase the old boot, flash the new boot, and install your choice of Magisk apk for you. The script is also able to revert you back to the stock boot image if needed.

Takes only a minute or two depending if you already have adb installed, fastboot drivers setup, and bootloader unlocked. (The guide will walk you through this if you are new)

Rooting Your Shield Will Break AI Upscaling and Dolby Vision. You /Cannot/ Lock the bootloader while rooted, you can only Lock the bootloader when you have the stock boot Image installed. This tool simply makes it easier to "Root" and to Revert back to Stock when done, so you can use your AI Enhanced Features again.

HOW TO ROOT:

If you are already running the STOCK firmware version you want to ROOT, Skip to step 2.
You can check your currently installed firmware on the shield by going into Settings, selecting About, then scroll to the bottom.
View attachment 5856143
You will see a section called SHIELD Android TV SW Version, this will show your installed FW

STEP 1:
Select a STOCK firmware from this THREAD, and fully install it.

STEP 2:
Download the BOOT MOD that correlates to your installed STOCK firmware.
If you want to build your own "Boot Mod" the instructions are HERE
Special Thanks to @Manzing for obtaining the 9.1 and 9.1.1 images for us!
Special thanks to @I_did_it_just_tmrrow for taking the time to download from gameworks, patch with magisk, and install the 2015 version, and verified it works HERE as well as they verified the hashes were the same for the boot.img of the 500gb and 16gb boot.img
If you want me to add more, let me know.

STEP 3:
Make sure you have usb debugging enabled in settings and your shield is ON.
This adds an additional Minute to setup time 😊😊😊

Attach a USB-C cable to your shield and plug it into your PC.
(Use the USB port furthest away from the HDMI Cable)
View attachment 5856139
Go into settings, select device preferences

View attachment 5856141

Select About, then hit the build number 7 times
View attachment 5856143

Back out to device preferences and now select developer options
View attachment 5856145

Then enable USB debugging and Network debugging.
View attachment 5856147

Here's a way to install adb quickly using powershell and chocolatey.

Open powershell as admin and copy and paste these two lines, one line at a time:
Code:
Set-ExecutionPolicy Bypass -Scope Process -Force; [System.Net.ServicePointManager]::SecurityProtocol = [System.Net.ServicePointManager]::SecurityProtocol -bor 3072; iex ((New-Object System.Net.WebClient).DownloadString('https://community.chocolatey.org/install.ps1'))

choco install adb

That's it!

Note the ip address and in a terminal on your computer, connect to this ip address.

Example: adb connect 192.168.0.10:5555
View attachment 5856149
This will prompt the shield to allow for a connection, say yes.

STEP 4:
Run your choice of .bootmod, .deltamodonly, or .magiskmodonly. MORE INFO
Simple 1 min demo:

How to use the new .bootmod script:

After Enabling USB Debugging and Wireless debugging, then adb connecting to your device, run the .bootmod script

View attachment 5857915
If you did everything correctly, your device should be listed, and you may proceed by pressing 1 and enter.

If you forgot to adb connect you may now do so with option 3, just type in your Shield's IP address.
View attachment 5857917

After you select 1 on the main menu, the script will then reboot your device into the bootloader and will wait for you to press a key so the script can run fastboot devices to verify that your device has posted.

View attachment 5857919
Wait to press any key until you see your shield's lights come on and then you hear the window's chime on your computer. (see 0:16 in the video) Then Press 1 if your device is listed like above.
Run option 2 again, in case the script went too fast or you hit a key too quickly.

If your device is still not showing, make sure you have unlocked the bootloader and installed the fastboot drivers for your device.

NOTE THAT UNLOCKING YOUR BOOTLOADER WILL ERASE ALL DATA ON THE DEVICE!

The shield should now be at the bootloader menu, simply select unlock bootloader
View attachment 5857743

View attachment 5857923
Now you can select which boot mod you would prefer. The script will erase the old boot image, flash the new one, reset, then the script will pause for us.

View attachment 5856163
When your shield has fully rebooted and is on the main menu, you can press any key in the terminal and the script will finish the magisk installation for us by installing the apk to the device.

View attachment 5858021
If you accidentally pressed a button too quickly, you can always access the apk menu to adb install the Magisk apk.

FULL RUNDOWN OF V2 CHANGES

Remember that you can always revert back to the Stock Boot Image and Lock your bootloader (again you can only lock it with a Stock boot flashed) to get your AI Upscaler and Dolby Vision working again when you are done with Root.

STEP 5:
Now Opening Magisk will trigger this alert:
View attachment 5773711

Select OK and after the reboot, your Magisk of Choice will be fully installed!

View attachment 5774415

You will now have Root and still be able to use apps and features that you shouldn't be able to. Normally with root (or at least on the Dev Rooted Images) we cannot install Disney +, but as you see, we Sure Can Now~! ;-)

IF YOUR PLAYSTORE IS MISSING APPS, SEE THIS POST. REQUIRES MAGISK DELTA
SOURCE CODE --- You may repurpose / share this as you see fit.

DELTAMODONLY.BAT
Code:
fastboot erase boot
fastboot flash boot bootmod2.img
fastboot reboot

MAGISKMODONLY.BAT
Code:
fastboot erase boot
fastboot flash boot bootmod1.img
fastboot reboot

BOOTMOD.BAT ---- There is unused code, the :UNLOCK code will be removed later, it didn't work how I would have liked in testing and I forgot to remove it. It isn't harming anything right now so will remove it with the next update.
Code:
@echo off
title [BOOTMOD]
color 0A
if "%1" neq "" ( goto %1)

:MENU
cls
echo BOOTMOD -- Version 2
echo =========================================
adb devices
echo =========================================
echo 1. Enter Bootloader Menu for Mod Flashing
echo 2. Enter APK Menu
echo 3. ADB Connect
echo 4. Reboot to System
echo 5. HELP
echo 6. EXIT BOOTMOD
echo =========================================
set /p answer= Please Enter your Selection:
if %answer%==1 goto BOOTLOADER
if %answer%==2 goto APK
if %answer%==3 goto ADB
if %answer%==4 goto REBOOT
if %answer%==5 goto HELP
if %answer%==6 goto EXIT
:ADB
cls
set /p answer= Type in SHIELD IP Address:
adb connect %answer%
goto MENU
 
:APK
cls
echo ===========
echo APK MENU
echo ===========
echo 1. Magisk by TopJohnWu
echo 2. Magisk Delta fork by HuskyDG
echo 3. Return to Main Menu
echo ================================
set /p answer= Please Enter your Selection:
if %answer%==1 goto MAGISKAPK
if %answer%==2 goto DELTAAPK
if %answer%==3 goto MENU

:MAGISKAPK
adb install magisk.apk
goto MENU

:DELTAAPK
adb install delta.apk
goto MENU

:HELP
cls
echo Adb must be installed on the computer and USB debugging must be enabled on the Shield.
echo You will need the Fastboot USB drivers installed on your PC.
echo Check the GUIDE on XDA for more help.
echo LINK: https://forum.xda-developers.com/t/bootmod-root-your-shield-in-1-minute-2015-2017-2019.4524873/
echo =====================================================================================
set /p answer=Press 1 to return to Main Menu:
if %answer%==1 goto MENU

:UNLOCK
cls
fastboot oem unlock
echo ==============================================================
echo Use your shield to select yes. Then press any key to continue
echo ==============================================================
pause
set /p answer=Press 1 to Enter Flash Menu or 2 to return to Main Menu:
if %answer%==1 goto FLASH
if %answer%==2 goto MENU

:BOOTLOADER
cls
adb reboot bootloader
pause
cls
echo =====================================================
fastboot devices
echo =====================================================
echo Is your device listed above?
echo =====================================================
set /p answer=Press 1 for yes or 2 for no or 3 for Help:
if %answer%==1 goto FLASH
if %answer%==2 goto BOOTLOADER
if %answer%==3 goto HELP

:FLASH
cls
echo How would you like to flash your boot today? Do you want to include:
echo ====================================================================
echo 1. TopJohnWu's Magisk
echo 2. HuskyDG's Magisk Delta
echo 3. Revert Back To Stock Boot Image
echo 4. Reboot Shield to System
echo 5. Return to Main Menu
echo ====================================
set /p answer=Select a number and press enter:
if %answer%==1 goto MAGISK
if %answer%==2 goto DELTA
if %answer%==3 goto STOCK
if %answer%==4 goto REBOOT
if %answer%==5 goto MENU                                                                                

:MAGISK
cls
fastboot erase boot
fastboot flash boot bootmod1.img
fastboot reboot
echo =====================================
echo Wait for your Shield to fully Reboot.
echo =====================================
pause
adb install magisk.apk
goto MENU

:DELTA
cls
fastboot erase boot
fastboot flash boot bootmod2.img
fastboot reboot
echo =====================================
echo Wait for your Shield to fully Reboot.
echo =====================================
pause
adb install delta.apk
goto MENU

:STOCK
cls
fastboot erase boot
fastboot flash boot boot.img
echo ================================================================================
echo REMEMBER TO LOCK YOUR BOOTLOADER FOR AI UPSCALING AND DOLBY VISION FUNCTIONALITY
echo ================================================================================
echo 1. Reboot Shield to the System
echo 2. Return to Main Menu
echo =========================
set /p answer=Enter your selection:
if %answer%==1 goto REBOOT
if %answer%==2 goto MENU

:REBOOT
fastboot reboot
goto MENU

:EXIT
exit /b
Here are the sources for the Magisk apk's and their respective projects, used in making the boot mods.

Topjohnwu's Magisk APK Direct Download Link (v25.2):

Github Project Page:

HuskyDG's Forked version of Magisk "Delta" Direct Download Link:

Github Project Page:

All original boot images come from NVIDIA's Gameworks:
SPECIAL THANKS TO OUR FRIENDS IN THE XDA COMMUNITY <333
Thank you to @topjohnwu for making Magisk
@huskydg For making the forked magisk with magiskhide enabled and other features
@nooted1 for teaching us about the magisk variant "delta" that has magiskhide still configured inside the apk
@ajolly for their efforts in educating us about safetynet modules that can be used within magisk
@louforgiveno for their efforts in reverse engineering apks, determining that it would be better to clear data in the google playstore instead of cache, and providing excellent feedback on pretty much every step of the way.
@abc1054 for testing the ai upscaler and teaching me how to even use the silly thing.
@Zer0_rulz for testing the upscaler and teaching us about link2sd and providing a useful idea for studies, to "freeze apps" as opposed to straight deletion in tests. I will use both methods in the future!
@pinvok3 for their script they made to teach us how to more efficiently locate the apps tied to the ai upscaler and determining the "tvsettings.apk" to potentially be culpable in jailing our upscaler. They also taught me about the dolby vision feature on the shield
@Renate for allowing me to bother her in the AVB thread while I try to learn how to talk to people like her. haha
@Manzing for stepping up and being the hero we needed for the 2017 shield community! They were able to locate the correct pathing for the OTA Firmware as well as provide us the stock 9.1 boot and complete OTA!!
@I_did_it_just_tmrrow For taking the time to verify magisk is able to indeed patch the 2015 version of the Shield HERE and more so they explained the boot images provided on gameworks for the 2015 version have the same hash, therefore a patched boot will work on both the 16gb and 500gb models. Thank you!

AI UPSCALER FIX:
THERE'S SOME TROUBLE WITH THE UPSCALER STILL, THE COMMUNITY IS WORKING TOGETHER IN THE COMMENTS BELOW
Please note that patching the boot with Magisk causes problems like the AI upscaler and Dolby vision being unavailable. You may want to wait for updates unless you have a reason to root with stock but otherwise feel free to join us in troubleshooting!

NOTE THAT THIS METHOD REQUIRES A FIX SO ONE COULD RUN ADB AS ROOT OUTSIDE OF THE SHELL. (adb shell su works, but not adb root outside of shell) Trying to mod this binary. Bare with me

Verified Working on the Shield:


So just dug out my old ShieldTV and updated to the latest 9.1.1 only to regret it right away. Have a ton of spare time lately due to some medical things. Any chance of one for 9.1.1 for the 2015 500gb model? Know it's kinda an oddball system but the ads are just AWFUL even turning them off and AdGuard didn't do much. So I went to look and see if there was root only to see I just updated right past where I needed to be.

However regardless was an interesting read. Thanks for the work already done I know it has helped many. I haven't rooted my phone in years so kinda forgot the old lower firmware is usually easier to exploit.
 

Starz04

New member
May 31, 2023
3
2
So just dug out my old ShieldTV and updated to the latest 9.1.1 only to regret it right away. Have a ton of spare time lately due to some medical things. Any chance of one for 9.1.1 for the 2015 500gb model? Know it's kinda an oddball system but the ads are just AWFUL even turning them off and AdGuard didn't do much. So I went to look and see if there was root only to see I just updated right past where I needed to be.

However regardless was an interesting read. Thanks for the work already done I know it has helped many. I haven't rooted my phone in years so kinda forgot the old lower firmware is usually easier to exploit.
it is possible to downgrade back to 8.2.3. In my post above Ive linked a tutorial for 2019 STV Pro, maybe it works in the same way for the 2015 model.

Yeah the ads are super annoying, also the fact that the device is less snappy on 9xx OS compared to a very smooth and snappy 8.2.3 os. I dont even plan to update it any time in the future, since everything I use works perfectly on 8.2.3 already.
 

mervetp

New member
Dec 20, 2016
3
1
Hello, I am having some trouble and was wondering if someone could help.

I can't connect via ADB (see pics) - only if WIFI is enabled on shield and my CPU will ADB connect. But that isn't helpful is it?
I have usb debugging enabled and have allowed the security pc fingerprint confirmation popup on the shield when i plug in the usb cable.
I can also run the bootmod and have my shield boot into the flash screen and see my device connected (see pic)
When I try the flash script it says boot loader locked (see pic).
Probably becuase I never got the ADB connection in the first place
I have the latest nvidia shield drivers and it is registering as a connected device when i plug it into windows...
I have tried different usb ports on my PC...
Any ideas???
 

Attachments

  • 3.JPG
    3.JPG
    42.9 KB · Views: 41
  • 2.JPG
    2.JPG
    24.8 KB · Views: 41
  • 1.JPG
    1.JPG
    72.1 KB · Views: 41

pinvok3

Member
Sep 15, 2017
9
12
NOTE THAT THIS METHOD REQUIRES A FIX SO ONE COULD RUN ADB AS ROOT OUTSIDE OF THE SHELL. (adb shell su works, but not adb root outside of shell) Trying to mod this binary. Bare with me

Do I understand correctly, that the only problem to enable AI and Dolby Audio features is making `adb root` from the outside possible?

If thats the case, I will take a look into the binary and check if a simple patch could make it work. Is there a separate thread to discuss the progress, or is it this one here?
 

ravage007

Member
Sep 21, 2010
13
0
So now I'm having a different problem I'm trying to install a driver I don't know how it got fixed but following the instructions do not match I get to this part picture below
1687132520572.png


and click on the let me pick from a list and it gives me
1687132556070.png

I am at a loss of what to do I really want to be able to root my Nvidia Shield

help pleeeeeeeeees
 

Attachments

  • 1687132396869.png
    1687132396869.png
    15 KB · Views: 15

louforgiveno

Senior Member
Jun 24, 2010
3,964
2,500
So now I'm having a different problem I'm trying to install a driver I don't know how it got fixed but following the instructions do not match I get to this part picture below
View attachment 5935567

and click on the let me pick from a list and it gives me
View attachment 5935569
I am at a loss of what to do I really want to be able to root my Nvidia Shield

help pleeeeeeeeees
I think a few of the screenshots on OP are slightly out of order.....
Overall i think your error is you need to manually point to the driver as the pics indicate
 

Attachments

  • 20230618_210236.jpg
    20230618_210236.jpg
    286.9 KB · Views: 23
  • 20230618_210258.jpg
    20230618_210258.jpg
    212.1 KB · Views: 23
  • 20230618_210326.jpg
    20230618_210326.jpg
    260.8 KB · Views: 23
  • 20230618_210350.jpg
    20230618_210350.jpg
    333.4 KB · Views: 24
  • 20230618_210412.jpg
    20230618_210412.jpg
    278.9 KB · Views: 25

ravage007

Member
Sep 21, 2010
13
0
I keep getting an error message about fastboot failing I have redone the steps several times even gone back to stock firmware I manually installed the drivers for fastboot if it would be better I could post a little video of the whole process






Never mind about that last topic now I realize what the problem is the air is not the problem but it is not installing the application

1687204484296.png
 
Last edited:

RM-808

New member
Mar 20, 2013
2
0
Hello mate. it is actually possible to downgrade Shield 2019 to OS 8.2.3. I used this guide and it worked flawlessly: https://florisse.nl/shield/

Obviously huge thanks to the guy who created it as it saves people so much research and trial + error. Basically alot of time saved.

Using this tweak guide, I've deleted close to everything from google and Nvidia (bloatware + data collecting) on the 2019 Shield TV: https://florisse.nl/shield-tweaks/

I've removed the Play Store and Google Play Services, ATV Core Services, ATV Remote Service, Backdrop, Basic Daydreams, Chromecast and many other things.

I don't use Netflix, Amazon Prime Video, Plex etc. So everything was removed from the Shield.

This is my ADB batch file to uninstall pretty much everything unneeded:

Code:
adb shell pm uninstall -k --user 0 com.google.android.speech.pumpkin & adb shell pm uninstall -k --user 0 com.google.android.tts & adb shell pm uninstall -k --user 0 com.google.android.videos & adb shell pm uninstall -k --user 0 com.google.android.tvrecommendations & adb shell pm uninstall -k --user 0 com.google.android.syncadapters.calendar & adb shell pm uninstall -k --user 0 com.google.android.backuptransport & adb shell pm uninstall -k --user 0 com.google.android.partnersetup & adb shell pm uninstall -k --user 0 com.google.android.inputmethod.korean & adb shell pm uninstall -k --user 0 com.google.android.inputmethod.pinyin & adb shell pm uninstall -k --user 0 com.google.android.apps.inputmethod.zhuyin & adb shell pm uninstall -k --user 0 com.google.android.tv & adb shell pm uninstall -k --user 0 com.google.android.tv.frameworkpackagestubs & adb shell pm uninstall -k --user 0 com.google.android.tv.bugreportsender & adb shell pm uninstall -k --user 0 com.google.android.backdrop & adb shell pm uninstall -k --user 0 com.google.android.leanbacklauncher.recommendations & adb shell pm uninstall -k --user 0 com.google.android.feedback & adb shell pm uninstall -k --user 0 com.google.android.leanbacklauncher & adb shell pm uninstall -k --user 0 com.google.android.apps.mediashell & adb shell pm uninstall -k --user 0 com.plexapp.android & adb shell pm uninstall -k --user 0 com.zattoo.player & adb shell pm uninstall -k --user 0 com.nvidia.tegrazone3 & adb shell pm uninstall -k --user 0 com.plexapp.mediaserver.smb & adb shell pm uninstall -k --user 0 com.google.android.play.games & adb shell pm uninstall -k --user 0 com.netflix.ninja & adb shell pm uninstall -k --user 0 com.amazon.amazonvideo.livingroom & adb shell pm uninstall -k --user 0 com.amazon.amazonvideo.livingroom.nvidia & adb shell pm uninstall -k --user 0 com.google.android.youtube.tvmusic & adb shell pm uninstall -k --user 0 com.android.vending & adb shell pm uninstall -k --user 0 com.google.android.gms

Keep in mind this is an extensive removal of pretty much everything. Payed apps etc. wont work with such cleanup. Most apps however do work- Kodi, Firefox, SmartTube, Speedtest, Fdroid, AdAware, Aurora Store (with private login, if you want to update some apps), Aptoide, Twitch, all sorts of Emulators etc.

The thing is that Google Play Store automaticall updates itself in the background, even if you disable it (it gets reenabled automatically) and I dont need that. If I want to update something, I will go to Aurora Store or Aptoide and update manually, but I dont want some sheety apps to be doing whatever they want in the background without asking.

And I didnt install a 3rd party Android Launcher, I use the default one, there are no more ads though after removing like 80% of trash bloatware and adware. The Android TV Home version is 2.1.3-320113730-f and I'm on ShieldOS 8.2.3. No ads to be seen and since even the Nvidia-OTA service was removed, it will never update the Shield by itself or even show a notification that there are updates available- which is exactly how I want it. Everything I need works fine in 8.2.3 and if I ever need an update, I will do it manually.

Also, while we're at it- it is possible to skip the initial login after factory restore, as seen on the picture attached. Source of it is: https://www.reddit.com/r/ShieldAndroidTV/comments/o8tpkx
However it is actually not required to downgrade Android TV Home app to version 2.0.10 to remove ads from the home screen. By simply downgrading to ShieldOS 8.2.3 (down from 9.1.1), the ads were removed from the main screen automatically. Then if you do some additional cleanup (like removing ATV Core Services and disabling autoupdate for Apps in Google Play Store), the ads will never show up.
Which command uninstalls the Nvidia Games ?
 

Starz04

New member
May 31, 2023
3
2
Which command uninstalls the Nvidia Games ?
In this tutorial https://florisse.nl/shield-tweaks/ it is described quite well how to uninstall unwanted apps etc.

you just need to figure out the name of the app / package you want to uninstall and then use the command:
Code:
adb shell pm uninstall -k --user 0 com.nvidia.xxxxxxx

Should you uninstall something you didn't really want to get rid of- its not a problem as you can easily reinstall the app again via adb.

You can try my adb batch code in my previous post, it is quite extensive and removes tons of stuff, even Playstore, Playservices and much more stuff that I personally dont use.
 
  • Like
Reactions: RM-808

teeboz

Member
Apr 19, 2007
42
3
is there root for 2015 shield on 8.2.3 i only saw for 9.0. never-mind saw how to make your own
 
Last edited:

kidhudi

Senior Member
Feb 1, 2011
792
170
Jackson
Is this possible for the 2019 tube? I can connect only by adb wifi debugging. once i get into fastboot i cannot see the device with fastboot devices it shows nothing.

any help in this regard would be much appreciated.
 

aouamed

Member
Aug 31, 2016
12
11
Is this possible for the 2019 tube? I can connect only by adb wifi debugging. once i get into fastboot i cannot see the device with fastboot devices it shows nothing.

any help in this regard would be much appreciated.
 
  • Like
Reactions: tnomtlaw

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    I came across this thread last night and decided to root my 2019 pro. The process to root it was far easier than I thought. One work around I used with the fastboot Win driver issue was since the machine refused to install the inf files from Nvidia I ended up going into device manager and updated driver manually. I chose the "left me choose" option and selected the pre existing Samsung ADB drivers I had installed last year. I clicked it and after a slight hesitation it worked and my Win box starting talking to the shield. I used the prepatched 9.1.1 img someone had linked to. The shield booted into the OS normally and installed the magisk manager apk and again rebooted. It came up rooted and I was happy. But AI up scaling and Dolby was not. Dolby was greyed out and said bootloader next to it. AI up scaling could be checked but also was nonfunctional and said bootloader. I ended up installing following magisk mods: Magick hide props, safety net fix, audio modification, audio compatibility, built in BusyBox, Hi-Res Audio Enabler, and Dolby Atmos Magic Revision. I also enabled zygisk and set to enforce deny list. In the deny list I checked all of the Nvidia services, and Google Playstore, Google play services, and possibly a couple other Google ones. I rebooted and both worked. The Dolby switch was selectable and it did activate Atmos. I didn't check Vision but dont care about that honestly. Everything is working great. I initially figured that if I couldn't get Dolby back I'd install Viper for the sound but didn't need it and didn't install it. Yes, I still have the orange warning nag screen at the start of the boot process but am confident that can be dealt with also. Someone figured out how to get rid of that in the OnePlus 9 pro section and the rom I'm using (Jaguar) In my phone the dev figured out how to relock the bootloader and retain Magisk root. It's been a long day so I'll look at that tomorrow
    1
    I came across this thread last night and decided to root my 2019 pro. The process to root it was far easier than I thought. One work around I used with the fastboot Win driver issue was since the machine refused to install the inf files from Nvidia I ended up going into device manager and updated driver manually. I chose the "left me choose" option and selected the pre existing Samsung ADB drivers I had installed last year. I clicked it and after a slight hesitation it worked and my Win box starting talking to the shield. I used the prepatched 9.1.1 img someone had linked to. The shield booted into the OS normally and installed the magisk manager apk and again rebooted. It came up rooted and I was happy. But AI up scaling and Dolby was not. Dolby was greyed out and said bootloader next to it. AI up scaling could be checked but also was nonfunctional and said bootloader. I ended up installing following magisk mods: Magick hide props, safety net fix, audio modification, audio compatibility, built in BusyBox, Hi-Res Audio Enabler, and Dolby Atmos Magic Revision. I also enabled zygisk and set to enforce deny list. In the deny list I checked all of the Nvidia services, and Google Playstore, Google play services, and possibly a couple other Google ones. I rebooted and both worked. The Dolby switch was selectable and it did activate Atmos. I didn't check Vision but dont care about that honestly. Everything is working great. I initially figured that if I couldn't get Dolby back I'd install Viper for the sound but didn't need it and didn't install it. Yes, I still have the orange warning nag screen at the start of the boot process but am confident that can be dealt with also. Someone figured out how to get rid of that in the OnePlus 9 pro section and the rom I'm using (Jaguar) In my phone the dev figured out how to relock the bootloader and retain Magisk root. It's been a long day so I'll look at that tomorrow
    Are you certain that AI Upscaling is working correctly.if so Thanks a million !!!
    1
    I could be wrong but I think I remember reading that rooting the Shield TV 2019 models disables AI upscaling and Dolby Vision for some reason.
    You can read this in this topic. Because of the unlocked bootloader. But if you lock it again you lose root. That's why we ask if the solution posted above is fixing it.. Most probably it won't i predict..
  • 11
    Hello Friends~!

    We now have a working method to achieve ROOT on STOCK Firmware!

    A script has been made that can boot your shield into the bootloader, erase the old boot, flash the new boot, and install your choice of Magisk apk for you. The script is also able to revert you back to the stock boot image if needed.

    Takes only a minute or two depending if you already have adb installed, fastboot drivers setup, and bootloader unlocked. (The guide will walk you through this if you are new)

    Rooting Your Shield Will Break AI Upscaling and Dolby Vision. You /Cannot/ Lock the bootloader while rooted, you can only Lock the bootloader when you have the stock boot Image installed. This tool simply makes it easier to "Root" and to Revert back to Stock when done, so you can use your AI Enhanced Features again.

    HOW TO ROOT:

    If you are already running the STOCK firmware version you want to ROOT, Skip to step 2.
    You can check your currently installed firmware on the shield by going into Settings, selecting About, then scroll to the bottom.
    9.png

    You will see a section called SHIELD Android TV SW Version, this will show your installed FW

    STEP 1:
    Select a STOCK firmware from this THREAD, and fully install it.

    STEP 2:
    Download the BOOT MOD that correlates to your installed STOCK firmware.
    If you want to build your own "Boot Mod" the instructions are HERE
    Special Thanks to @Manzing for obtaining the 9.1 and 9.1.1 images for us!
    Special thanks to @I_did_it_just_tmrrow for taking the time to download from gameworks, patch with magisk, and install the 2015 version, and verified it works HERE as well as they verified the hashes were the same for the boot.img of the 500gb and 16gb boot.img
    If you want me to add more, let me know.

    STEP 3:
    Make sure you have usb debugging enabled in settings and your shield is ON.
    This adds an additional Minute to setup time 😊😊😊

    Attach a USB-C cable to your shield and plug it into your PC.
    (Use the USB port furthest away from the HDMI Cable)
    7.png

    Go into settings, select device preferences

    8.png


    Select About, then hit the build number 7 times
    9.png


    Back out to device preferences and now select developer options
    10.png


    Then enable USB debugging and Network debugging.
    11.png


    Here's a way to install adb quickly using powershell and chocolatey.

    Open powershell as admin and copy and paste these two lines, one line at a time:
    Code:
    Set-ExecutionPolicy Bypass -Scope Process -Force; [System.Net.ServicePointManager]::SecurityProtocol = [System.Net.ServicePointManager]::SecurityProtocol -bor 3072; iex ((New-Object System.Net.WebClient).DownloadString('https://community.chocolatey.org/install.ps1'))
    
    choco install adb

    That's it!

    Note the ip address and in a terminal on your computer, connect to this ip address.

    Example: adb connect 192.168.0.10:5555
    12.png

    This will prompt the shield to allow for a connection, say yes.

    STEP 4:
    Run your choice of .bootmod, .deltamodonly, or .magiskmodonly. MORE INFO
    Simple 1 min demo:

    How to use the new .bootmod script:

    After Enabling USB Debugging and Wireless debugging, then adb connecting to your device, run the .bootmod script

    SYSTEM MENU.PNG

    If you did everything correctly, your device should be listed, and you may proceed by pressing 1 and enter.

    If you forgot to adb connect you may now do so with option 3, just type in your Shield's IP address.
    ipadd.PNG


    After you select 1 on the main menu, the script will then reboot your device into the bootloader and will wait for you to press a key so the script can run fastboot devices to verify that your device has posted.

    fastboot.PNG

    Wait to press any key until you see your shield's lights come on and then you hear the window's chime on your computer. (see 0:16 in the video) Then Press 1 if your device is listed like above.
    Run option 2 again, in case the script went too fast or you hit a key too quickly.

    If your device is still not showing, make sure you have unlocked the bootloader and installed the fastboot drivers for your device.

    DOWNLOAD:

    Now open Device Manager and follow the steps below:
    1.png
    2.PNG
    3.PNG
    4.PNG
    5.PNG
    NOTE THAT UNLOCKING YOUR BOOTLOADER WILL ERASE ALL DATA ON THE DEVICE!

    The shield should now be at the bootloader menu, simply select unlock bootloader
    6.PNG

    flash.PNG

    Now you can select which boot mod you would prefer. The script will erase the old boot image, flash the new one, reset, then the script will pause for us.

    6.png

    When your shield has fully rebooted and is on the main menu, you can press any key in the terminal and the script will finish the magisk installation for us by installing the apk to the device.

    apk.PNG

    If you accidentally pressed a button too quickly, you can always access the apk menu to adb install the Magisk apk.

    FULL RUNDOWN OF V2 CHANGES

    Remember that you can always revert back to the Stock Boot Image and Lock your bootloader (again you can only lock it with a Stock boot flashed) to get your AI Upscaler and Dolby Vision working again when you are done with Root.

    STEP 5:
    Now Opening Magisk will trigger this alert:
    MAGISK APKINSTALL.jpg


    Select OK and after the reboot, your Magisk of Choice will be fully installed!

    6.jpg


    You will now have Root and still be able to use apps and features that you shouldn't be able to. Normally with root (or at least on the Dev Rooted Images) we cannot install Disney +, but as you see, we Sure Can Now~! ;-)

    IF YOUR PLAYSTORE IS MISSING APPS, SEE THIS POST. REQUIRES MAGISK DELTA
    SOURCE CODE --- You may repurpose / share this as you see fit.

    DELTAMODONLY.BAT
    Code:
    fastboot erase boot
    fastboot flash boot bootmod2.img
    fastboot reboot

    MAGISKMODONLY.BAT
    Code:
    fastboot erase boot
    fastboot flash boot bootmod1.img
    fastboot reboot

    BOOTMOD.BAT ---- There is unused code, the :UNLOCK code will be removed later, it didn't work how I would have liked in testing and I forgot to remove it. It isn't harming anything right now so will remove it with the next update.
    Code:
    @echo off
    title [BOOTMOD]
    color 0A
    if "%1" neq "" ( goto %1)
    
    :MENU
    cls
    echo BOOTMOD -- Version 2
    echo =========================================
    adb devices
    echo =========================================
    echo 1. Enter Bootloader Menu for Mod Flashing
    echo 2. Enter APK Menu
    echo 3. ADB Connect
    echo 4. Reboot to System
    echo 5. HELP
    echo 6. EXIT BOOTMOD
    echo =========================================
    set /p answer= Please Enter your Selection:
    if %answer%==1 goto BOOTLOADER
    if %answer%==2 goto APK
    if %answer%==3 goto ADB
    if %answer%==4 goto REBOOT
    if %answer%==5 goto HELP
    if %answer%==6 goto EXIT
    :ADB
    cls
    set /p answer= Type in SHIELD IP Address:
    adb connect %answer%
    goto MENU
     
    :APK
    cls
    echo ===========
    echo APK MENU
    echo ===========
    echo 1. Magisk by TopJohnWu
    echo 2. Magisk Delta fork by HuskyDG
    echo 3. Return to Main Menu
    echo ================================
    set /p answer= Please Enter your Selection:
    if %answer%==1 goto MAGISKAPK
    if %answer%==2 goto DELTAAPK
    if %answer%==3 goto MENU
    
    :MAGISKAPK
    adb install magisk.apk
    goto MENU
    
    :DELTAAPK
    adb install delta.apk
    goto MENU
    
    :HELP
    cls
    echo Adb must be installed on the computer and USB debugging must be enabled on the Shield.
    echo You will need the Fastboot USB drivers installed on your PC.
    echo Check the GUIDE on XDA for more help.
    echo LINK: https://forum.xda-developers.com/t/bootmod-root-your-shield-in-1-minute-2015-2017-2019.4524873/
    echo =====================================================================================
    set /p answer=Press 1 to return to Main Menu:
    if %answer%==1 goto MENU
    
    :UNLOCK
    cls
    fastboot oem unlock
    echo ==============================================================
    echo Use your shield to select yes. Then press any key to continue
    echo ==============================================================
    pause
    set /p answer=Press 1 to Enter Flash Menu or 2 to return to Main Menu:
    if %answer%==1 goto FLASH
    if %answer%==2 goto MENU
    
    :BOOTLOADER
    cls
    adb reboot bootloader
    pause
    cls
    echo =====================================================
    fastboot devices
    echo =====================================================
    echo Is your device listed above?
    echo =====================================================
    set /p answer=Press 1 for yes or 2 for no or 3 for Help:
    if %answer%==1 goto FLASH
    if %answer%==2 goto BOOTLOADER
    if %answer%==3 goto HELP
    
    :FLASH
    cls
    echo How would you like to flash your boot today? Do you want to include:
    echo ====================================================================
    echo 1. TopJohnWu's Magisk
    echo 2. HuskyDG's Magisk Delta
    echo 3. Revert Back To Stock Boot Image
    echo 4. Reboot Shield to System
    echo 5. Return to Main Menu
    echo ====================================
    set /p answer=Select a number and press enter:
    if %answer%==1 goto MAGISK
    if %answer%==2 goto DELTA
    if %answer%==3 goto STOCK
    if %answer%==4 goto REBOOT
    if %answer%==5 goto MENU                                                                                 
    
    :MAGISK
    cls
    fastboot erase boot
    fastboot flash boot bootmod1.img
    fastboot reboot
    echo =====================================
    echo Wait for your Shield to fully Reboot.
    echo =====================================
    pause
    adb install magisk.apk
    goto MENU
    
    :DELTA
    cls
    fastboot erase boot
    fastboot flash boot bootmod2.img
    fastboot reboot
    echo =====================================
    echo Wait for your Shield to fully Reboot.
    echo =====================================
    pause
    adb install delta.apk
    goto MENU
    
    :STOCK
    cls
    fastboot erase boot
    fastboot flash boot boot.img
    echo ================================================================================
    echo REMEMBER TO LOCK YOUR BOOTLOADER FOR AI UPSCALING AND DOLBY VISION FUNCTIONALITY
    echo ================================================================================
    echo 1. Reboot Shield to the System
    echo 2. Return to Main Menu
    echo =========================
    set /p answer=Enter your selection:
    if %answer%==1 goto REBOOT
    if %answer%==2 goto MENU
    
    :REBOOT
    fastboot reboot
    goto MENU
    
    :EXIT
    exit /b
    Here are the sources for the Magisk apk's and their respective projects, used in making the boot mods.

    Topjohnwu's Magisk APK Direct Download Link (v25.2):

    Github Project Page:

    HuskyDG's Forked version of Magisk "Delta" Direct Download Link:

    Github Project Page:

    All original boot images come from NVIDIA's Gameworks:
    SPECIAL THANKS TO OUR FRIENDS IN THE XDA COMMUNITY <333
    Thank you to @topjohnwu for making Magisk
    @huskydg For making the forked magisk with magiskhide enabled and other features
    @nooted1 for teaching us about the magisk variant "delta" that has magiskhide still configured inside the apk
    @ajolly for their efforts in educating us about safetynet modules that can be used within magisk
    @louforgiveno for their efforts in reverse engineering apks, determining that it would be better to clear data in the google playstore instead of cache, and providing excellent feedback on pretty much every step of the way.
    @abc1054 for testing the ai upscaler and teaching me how to even use the silly thing.
    @Zer0_rulz for testing the upscaler and teaching us about link2sd and providing a useful idea for studies, to "freeze apps" as opposed to straight deletion in tests. I will use both methods in the future!
    @pinvok3 for their script they made to teach us how to more efficiently locate the apps tied to the ai upscaler and determining the "tvsettings.apk" to potentially be culpable in jailing our upscaler. They also taught me about the dolby vision feature on the shield
    @Renate for allowing me to bother her in the AVB thread while I try to learn how to talk to people like her. haha
    @Manzing for stepping up and being the hero we needed for the 2017 shield community! They were able to locate the correct pathing for the OTA Firmware as well as provide us the stock 9.1 boot and complete OTA!!
    @I_did_it_just_tmrrow For taking the time to verify magisk is able to indeed patch the 2015 version of the Shield HERE and more so they explained the boot images provided on gameworks for the 2015 version have the same hash, therefore a patched boot will work on both the 16gb and 500gb models. Thank you!

    AI UPSCALER FIX:
    THERE'S SOME TROUBLE WITH THE UPSCALER STILL, THE COMMUNITY IS WORKING TOGETHER IN THE COMMENTS BELOW
    Please note that patching the boot with Magisk causes problems like the AI upscaler and Dolby vision being unavailable. You may want to wait for updates unless you have a reason to root with stock but otherwise feel free to join us in troubleshooting!

    NOTE THAT THIS METHOD REQUIRES A FIX SO ONE COULD RUN ADB AS ROOT OUTSIDE OF THE SHELL. (adb shell su works, but not adb root outside of shell) Trying to mod this binary. Bare with me

    Verified Working on the Shield:
    4
    An update has been released and pushed to all the zip files. (These are just QoL things for the BOOTMOD script.) As usual, the OP's guide has been updated again with the new source code and pictures.

    You are now presented with a menu that will show if your device is connected via adb.
    SYSTEM MENU.PNG


    In case you forgot to adb connect, option 3 will allow you to type your ip address and connect to the shield.


    Option 2 will allow you to install just the magisk apk, this will be useful for updates.
    apk.PNG


    Option 1 pushes the shield into the bootloader menu and verifies it is posting before entering the flash menu, like the original version did before.

    "Reboot shield to system" "escapes" have been added to the menu in a couple of places.

    A Friendly reminder was added to the stock boot flash, to re-engage bootloader lock for upscaler, and a pause before system reset to do so.
    3
    I wanted to share something I discovered today that I didn't know about before and this deals with TWRP.

    Today I rewrote a GUIDE going over how to install Lineage OS on the shield.

    I noticed that TWRP when opened will then establish a root shell with the device named RECOVERY
    2.png

    So I adb shell ls and noticed that the contents /are not/ the same as what we see in a regular adb shell or in root exploring apps.
    1.PNG
    In fact, the view we are used to seeing is referred to as "system_root" as listed above. If you were to ls that, you would see your traditional filesystem layout.

    So therefore I was not seeing the full picture before... There's files here I pulled that I hadn't read before, I have to sort between the leftover lineage garbage and what not but I will share the native file dump later.

    This also makes me wonder if I was trying to flash the "roms" wrong for this device. Maybe a new approach would be to make a modified and preinstalled system_root that could be adb pushed.

    Not sure just wanted to share

    --edit have to select the MOUNT option in TWRP and then system + vendor to see the full picture, otherwise a lot of empty folders
    3
    Okay, I'm grasping straws right now, but my shield just crashed after I have started a movie with Dolby Vision enabled. Can someone confirm if Dolby Vision is grayed out (unavailable) on rooted devices but available on nonrooted ones? After this fix I was able to enable Dolby Vision but my system just died with this log:

    12-20 23:12:18.951 3725 3839 E WindowManager: Exception checking for game stream. Exception: android.content.pm.PackageManager$NameNotFoundException: ComponentInfo{com.android.tv.settings/.MainSettings}
    12-20 23:12:18.951 3725 3839 I InputDispatcher: Dropped event because of pending overdue app switch.
    12-20 23:12:18.953 3725 3864 E AudioService: Audioserver died.
    12-20 23:12:18.982 4578 5347 D DolbyAudioService: IMs12 implementation died... Restoring settings after restart
    12-20 23:12:18.983 4578 5347 D DolbyAudioService: Attempting to connect to IMs12
    12-20 23:12:18.992 4578 12382 I DolbyAudioService: Waiting 1 second before attempting to connect to IMs12...
    12-20 23:12:19.037 12385 12385 D audiohalservicemsd: main() Starting [email protected] from vendor/dolby.
    12-20 23:12:19.050 12385 12385 D : Calling decrypt_blob. err(0)
    12-20 23:12:19.056 3432 3432 E Ipprotectd: decrypt_blob: Error during launch operation. err(0xffff0011)
    12-20 23:12:19.056 3432 3432 E Ipprotectd: Error occurred at decryption. err(ffff0011)
    12-20 23:12:19.058 12385 12385 E : Decryption failed
    12-20 23:12:19.058 12385 12385 E : decrypt_blob failed! err(0)
    12-20 23:12:19.058 12385 12385 E : Failed to decrypt.
    12-20 23:12:19.058 12385 12385 E : Failed decrypt .text section.
    12-20 23:12:19.059 12385 12385 F libc : Fatal signal 11 (SIGSEGV), code 2 (SEGV_ACCERR), fault addr 0x4ec98e90 in tid 12385 (android.hardwar), pid 12385 (android.hardwar)
    12-20 23:12:19.062 12384 12384 I ServiceManagement: Removing namespace from process name [email protected] to [email protected].

    It seems like some encrypted communication fails which takes the whole system with it. It makes me more suspicious that the bootloader unlock removes/hides/blocks some DRM keys required for AI/Dolby Audio to work. If we could somehow hook into the bootloader unlocking phase to see what's happening ..
    3
    @pinvok3 Gosh WOW just wow! Thank You for your Amazing Share!! I will absolutely follow your advice and I will get that app pulled now to poke around.

    Are you rolling 8.2.3 or one of the 9's btw??

    Lastly "Or we lost some kind of DRM keys during the boot unlocking phase." Is this something we can obtain with a serial UART or JTAG adapter? I just got mine in and am not afraid to break the shield open here in a few days if there's something that could be obtained and shared there. I am new to all this so I appreciate everyone sharing the things