BOOTMOD - Root your Shield In 1 minute (2015, 2017, & 2019)
- Thread starter jenneh
- Start date
I checked on Gameworks and I don't see any firmware up for the tube version, but question are you able to run adb reboot bootloader and does it present with a menu to unlock the bootloader like the other shields do? Idk how to get it to post to the pc but I wonder if it at least has a proper bootloader menu or what options it presents
Also makes no sense for me. I flashed it with manual command fastboot flash boot xxxximg and I have root now
Thanks for the good work
Thanks for the good work
This is in regards to this link https://developer.nvidia.com/shield-open-source
Here is a copy of the downloaded source code:
drive.google.com
It's home will be located on the Repo Thread under this spoiler so we don't have to dig through comments to locate it
Nvidia replied to the emails about the OSS requests
Now when you select a firmware from the shield-open-source link you will see a page similar to this
The links reveal repo init code to download the actual android source code for the shield. I just did it and wrote down the steps HERE I used an ubuntu vm that I zipped the repo from and copied it to my host windows pc. The zip totaled 12.5 gb. Dunno what to do with any of it yet but the knowledge is there for all of us now
SOME EXAMPLES OF STUFF IN HERE:
Now when you select a firmware from the shield-open-source link you will see a page similar to this
The links reveal repo init code to download the actual android source code for the shield. I just did it and wrote down the steps HERE I used an ubuntu vm that I zipped the repo from and copied it to my host windows pc. The zip totaled 12.5 gb. Dunno what to do with any of it yet but the knowledge is there for all of us now
SOME EXAMPLES OF STUFF IN HERE:
nvidia-8.2.3.zip
drive.google.com
It's home will be located on the Repo Thread under this spoiler so we don't have to dig through comments to locate it
Last edited:
I have followed the new instructions and have achieved root on my shield pro 2019, however the ai upscaling is telling me no due to an unlocked bootloader. I am certain that I used the latest scripting solution for this activity. I selected the delta version to achieve root access, and the magisk-like root options seem to work as they have on other boxes where I have used magisk to achieve root. When I tried to lock the bootloader to see if that would enable ai upscaling, the shield wouldn't boot, and told me it couldn't find any operating system on my shield. Is there some configuration item(s) that I need to check to get ai upscaling to work properly on my shield? BTW, thanks to all of the people who worked on this rooting solution for the shield. I'm sure I just need to toggle some setting somewhere to get ai upscaling to work as shown in your example. lm32692
Hi there, the ai upscaler is currently not working with root enabled, and for right now the bootloader cannot be locked while rooted. Unfortunately you would have to revert back to the stock boot image in order for these features to work again. I tried to warn about this at the bottom of the OP but then again I put it at the bottom
I made "bootmod" so we can easily switch between stock and root, so one could re-engage these features when they are done doing whatever they needed root for, but for right now there are no updates in this area. We just got the full source code but its 12 gb and will take time to dig through and do things with
What's with the comment from louforgiveno 100% confirmed that the ai upscaling works without having to lock the bootloader. That comment implied to me that someone has solved the ai upscaling issue. I'm sure it's just a matter of time until one of you developers figure out the fix for ai upscaling. I am not upset that I have experimented with rooting my shield pro 2019, as I learned a lot about the workings of the shield in the process. I have multiple shields and so I use my personal device to experiment and learn. Maybe I will revert until a fix is finalized for the upscaling. [BTW....FYI, if any of the community uses a Samsung Galaxy laptop as their windows platform, the drivers for adb/fastboot offered, don't seem to work with my laptop. Samsung has issued their adb/fastboot interface drivers that work like a champ, but the "universal' adb driver, and a number of other adb interface drivers don't seem to work on the Samsung laptop H/W. Again, it's a learning experience for me as a Shield newbie, but I have done many of the activities with other less capable android devices. Good luck with solving the ai upscaling issue(s). lm32692
@lm32692 I made a mistake when I made that comment. At the time I wrote that, I did not understand how the AI upscaler worked, and misunderstood what a friend had said. This post explains the blunder Thank you and sorry for the mis-speak again!
I was just surprised that the comment mentioned that the ai upscaler worked with root active. Since you have the source code now, it's only a matter of time that you can devote to the project, until you will identify what mods are needed to have a fully functional root implementation. I'll look forward to that future event., along with all of the other folks who like to modify devices to give them more capabilities. lm32692
Hello xda community!
I have the same problem, that ai upscaler didn´t work. it shows me a message that the bootloader is unlocked. Cause of that, i cannot use it.
So i decided to go into theo bootloader menu again (via magisk) and select the option "lock bootloader".
After this, my shield 2019 cannot boot anymore.
I got only a black screen with this message:
"No valid operating system could be found.
The device will not boot."
That´s it.
After a few seconds, the shield turns automatically off.
Can anyone help me?
Best regards
legend0s
I have the same problem, that ai upscaler didn´t work. it shows me a message that the bootloader is unlocked. Cause of that, i cannot use it.
So i decided to go into theo bootloader menu again (via magisk) and select the option "lock bootloader".
After this, my shield 2019 cannot boot anymore.
I got only a black screen with this message:
"No valid operating system could be found.
The device will not boot."
That´s it.
After a few seconds, the shield turns automatically off.
Can anyone help me?
Best regards
legend0s
@legend0s Hi there! This comment answers your question. Since there seems to be some confusion here, the OP was updated to reflect that you /cannot/ lock the bootloader while rooted, for right now. This is due to selinux and AVB 2.0 signed partitions. This may be able to be fixed but it isn't right now. AI upscaling can only be used with a stock boot image and the bootloader locked, which is why the tool was made, so we can switch back and forth from root to stock quickly, when done with root.
Hi,.. wow I'm 2 mins away from over my shield tv 2017.
Was on 8. sth. rooted via magisk and wanted to update to latest shield experience because I couldn't activate the stupid Alexa skill to add the shield to Alexa. Thought this could help.
Saw that there is an official stable twrp now for my shield so I went and flashed it. Could boot into it fine. Ran the update routine on shield, after reboot I got into twrp and saw it couldn't flash the update due to some error. Turned out it is because the twrp version was too new, so I flashed an older one. Updated again, everything looked fine, but after reboot I got stuck in a boot loop.
So I tried every script here, without sucess..
So I got myself the shield experience 8.2.3 and 9.0.0 recovery images from nivdia. Flashed boot and recovery from 8.2.3 (thought the update to 9.0.0) didn't go through.
Bootloop again, and now the worst of all:
If I try to flash a boot or recovery image I get:
fastboot flash recovery recovery.img
target reported max download size of 33554432 bytes
sending 'recovery' (19493 KB)...
FAILED (remote: Bootloader is locked.)
finished. total time: 0.015s
I mean wtf?!!!! Does flashing a stock recovery automatically lock the bootloader??? If yes, where does it state that?
That is a total disaster!
Can anybody help at this point or is my whole data screwed? I know unlocking bootloader erases everything...
Edit: it gets better. If I select "boot recovery kernel" I get into the initially flashed twrp
however I cannot mount data in twrp...
over my shield tv 2017.Was on 8. sth. rooted via magisk and wanted to update to latest shield experience because I couldn't activate the stupid Alexa skill to add the shield to Alexa. Thought this could help.
Saw that there is an official stable twrp now for my shield so I went and flashed it. Could boot into it fine. Ran the update routine on shield, after reboot I got into twrp and saw it couldn't flash the update due to some error. Turned out it is because the twrp version was too new, so I flashed an older one. Updated again, everything looked fine, but after reboot I got stuck in a boot loop.
So I tried every script here, without sucess..
So I got myself the shield experience 8.2.3 and 9.0.0 recovery images from nivdia. Flashed boot and recovery from 8.2.3 (thought the update to 9.0.0) didn't go through.
Bootloop again, and now the worst of all:
If I try to flash a boot or recovery image I get:
fastboot flash recovery recovery.img
target reported max download size of 33554432 bytes
sending 'recovery' (19493 KB)...
FAILED (remote: Bootloader is locked.)
finished. total time: 0.015s
I mean wtf?!!!! Does flashing a stock recovery automatically lock the bootloader??? If yes, where does it state that?
That is a total disaster!
Can anybody help at this point or is my whole data screwed? I know unlocking bootloader erases everything...
Edit: it gets better. If I select "boot recovery kernel" I get into the initially flashed twrp
however I cannot mount data in twrp...
Last edited:
@trohn_javolta Hi there. No, it is not possible to "automatically" lock the bootloader by code or flashing on the shield, as it Requires External Input to confirm the selection. I am really not understanding what you are saying. So what I can suggest is to, unlock your bootloader again, then just dl the firmware you want from Nvidia Gameworks
and flash it normally. or patch your own boot from there if you still want to test root for your use case. No Twrp needed for any of these steps.
and flash it normally. or patch your own boot from there if you still want to test root for your use case. No Twrp needed for any of these steps.
All I can tell you is I did the above and it locked my bootloader...at least fastboot told me it's locked once I tried flashing sth. I never selected to lock my bootloader in fastboot mode... no idea how it happened.
Well yeah, I did what you wrote which, of course, worked. Data is lost now as expected, but it's not too bad.
@legend0s you can use a launcher app like wolf launcher to get rid of the apps and customize the back. There's other launchers out there too. I'm not personally trying to bring any fw backwards, would want to go forward personally, higher than what it is currently at on 9.1.1 but thats just ambitions. I'm not anywhere near there yet for that endeavor. If you are using a 2017 though, those can be flashed back to 8.0.0 or further to 6.0.0, just not the 2019s.
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.
Last edited:
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?
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
1
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:
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.1
I downgraded my shield 2019 Pro to 8.2.3 today.
Really easy and absolutely flawlessly! (-:
Thanks for this magic!!!!
Best regards! -
9Hello 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.
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
9.1.1mods.zip
drive.google.com
9.1mods.zip
drive.google.com
9.0.0mods.zip
drive.google.com
8.2.3mods.zip
drive.google.com
Special Thanks to @Manzing for obtaining the 9.1 and 9.1.1 images for us!
9.1.1mods2017.zip
drive.google.com
9.1mods2017.zip
drive.google.com
9.0.0mods2017.zip
drive.google.com
8.2.3mods2017.zip
drive.google.com
If you want me to add more, let me know.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
9.0.0-2015-MODS.zip
drive.google.com
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)
Go into settings, select device preferences
Select About, then hit the build number 7 times
Back out to device preferences and now select developer options
Then enable USB debugging and Network debugging.
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
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
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.
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.
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
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.
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.
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:
Select OK and after the reboot, your Magisk of Choice will be fully installed!
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 DELTASOURCE 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 /bHere 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:
GitHub - topjohnwu/Magisk: The Magic Mask for Android
The Magic Mask for Android. Contribute to...
github.com
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:
[GUIDE][NO-ROOT] How to install Ubuntu and other Linux Distros on Your Phone or Android TV Box, using Termux
NOTICE: THIS METHOD IS ONLY FOR NON ROOTED...
forum.xda-developers.com
3I 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
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.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 folders3I'm using 8.2.3. The newer 9 versions seem kind of sluggish. But the script should work on 9 regardless.
Sorry I have no idea. I've never worked on Android before and I've spent like 30 minutes on this.
Jtag is usually lower level stuff and I'm pretty sure it's undocumented. If it exists even.
I just remember, that on a previous phone (Sony Xperia) the drm keys were wiped once you unlock the bootloader, resulting in worse Camera image quality.
Considering that the upscale works correctly after unroot/relocking, I guess this would only be a soft lock. But still could be registered in the hardware somewhere, where we have no access to. Maybe it's still patchable though.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 things3Okay, 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:
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 ..
New posts
-
Quota and Functionality Questions related to Device Backup- Latest: jwoegerbauer
