Develop Bugs

[ROM][SHT-AL09][Fenris_SHT-AL09]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Fenris Features
Built in current MicroG
Built in Magisk
Built in BusyBox
Built in GNU Utils compiled for android ( bash etc )
Radically debloated
Built for Lucky Patcher ( lvm already patched and modded playstore in place )
Working Desktop Mode ( PC mode ), Yes you read that right
320 DPI and working camera UI etc.
Better sized Launcher icons.
Shipped as a old school zip so fully customisable by anyone with winrar
Bugs
Wallpapers etc missing ( belongs to an apk i deleted and cant be bothered to track it down ) fixed in beta 2
Standard filemanager is replaced by CM native file manager ( dont want the big H knowing whats on your drive ) so some share functions may not be available
but SMB over the network is fine and thats all im interested in.
Both the TWRP 's are flaky, this version https://forum.xda-developers.com/honor-view-10/development/recovery-twrp-3-2-1-0-t3769917 has just refused to boot on me twice despite a decrypted data partition. But thats not down to Fenris in any way. The second twrp ( view 10 ) is no longer possible. It requires formating /data and by doing that wipes all the themes/wallpapers and screws the theming engine so i am having to stick with the first TWRP.
Unfortunately it BARELY works, just good enough to flash Fenris and associated zip kind of correctly.
Because of a crap TWRP Magisk needs to be setup on first use and download the manager, ie internet needed. It also can not update its zip so that has to be flashed by hand
Battery.... Tablet manager had to go, it deliberately interferes with LP in-app spoofing, but it also provides battery statistics and possibly with it missing, battery life could be worse than stock
( memory handling could also be compromised ). Its a damn hard thing to check since i have never run the tab stock. Tablet manager is back, it controls the recents screen which is broken without one of tablet managers services. Writing a startup script to disable some TM services, but at moment i use MyAndroidTools to do same
Maybe more, this is a beta.
Dev Info.
Huawei have done a good job with their Andfroid shell, its very memory aware and frugal ( unlike samsung and HTC ), its a very good base for Fenris
I would have kept a lot more native apk's but then there are some security concerns so anything with a free line out had to go ( except HwShare, use at your own risk )
If there is demand i will release a total stock zip so peeps can mix-match and roll their own.
Information
Based on MediaPad M5 8.4 SHT-AL09 hw eu Schubert-AL09A 8.0.0.196(C432) Firmware 8.0.0 r1 EMUI8.0 05014XYF.
the link for this firmware https://androidhost.ru/tuA
You must be on this firmware to grantee Fenris operating correctly ( currently Fenris does not ship the vendor or kernel due to issues with the TWRP available being flaky )
, fenris may work on other firmware ( Android O ) but this is for you to try.
I will most prob keep Fenris SHT-AL09 updated as i find stuff i like/do not like, but i AM NOT a Dev, i only get my hands dirty when i need to, so as far as support goes, dont expect much and you will not be disappointed.
My tested method of getting fenris on your SHT-AL09
......download Fenris from here https://mega.nz/#!BKpX2YpT!DhotPKAkJvASYQUPeUlNz3MrZanmFNCxmm6tcd4qcE4
......download Huawei MediaPad M5 8.4 SHT-AL09 hw eu Schubert-AL09A 8.0.0.196(C432) Firmware 8.0.0 r1 EMUI8.0 05014XYF from here https://androidhost.ru/6n0
......downgrade using the dload method
......Get a bootloader unlock code using DC unlocker method ( keep the bootloader unlock code, you will friggin need it )
......Unlock bootloader using Fastboot Unlock Method
......download MediaPad M5 8.4 SHT-AL09 hw eu Schubert-AL09A 8.0.0.196(C432) Firmware 8.0.0 r1 EMUI8.0 05014XYF. from here https://androidhost.ru/tuA
......Upgrade using the Dload method
......Unlock bootloader using Fastboot Unlock Method ( dont worry the code is the same )
......Go into you new 196 system and Activate ADB and OEM-Unlock
......Flash this TWRP https://forum.xda-developers.com/mediapad-m5/development/recovery-twrp-3-2-2-1-t3813825 using TWRP fastboot method
......DO NOT LET IT BOOT INTO SYSTEM, BOOT INTO TWRP INSTEAD
......Have a OTG USB adapter ( you can also use the sd card but that is a pain ) and Stick ready , copy all the files your going to need in the further steps onto it
......Hook up the stick and Flash Disable_Dm-Verity_ForceEncrypt_Quota_05.21.2019.zip from here https://zackptg5.com/android.php#disverfe
......Also Kernel-Sepolicy-Patcher.zip from here also https://zackptg5.com/android.php#disverfe
......THen finally flash Fenris
......Boot ito Fenris
TWRP fastboot method
1.... Make sure you have latest HW adb drivers installed ( check by getting an adb shell to work )
2.... Download latest Android platform tools https://developer.android.com/studio/releases/platform-tools
3)... Decompress etc, get to fastboot dir, open a CMD there
4)... Copy your TWRP image to same dir
5).... Boot into Download mode ( vol down while plufgging USB into computer with drivers set up )
5).... fastboot.exe flash recovery_ramdisk xxxxxxxxxx.img
6).... Get frigin ready to pull the usb and hold power + vol UP ( to reboot int TWRP you just flashed ) DO NOT LET IT BOOT INTO SYSTEM
7).... fastboot.exe reboot
8).... Pull USB, Boot into TWRP
9).... TWRP reboot Menue to shutdown
Dload Method
1.... extract the archive
2.... copy dload folder to root of a fat32 formated sd card
3.... boot up, enable dev options
4.... In dev options enable OEM-unlock ( you will need to be on internet from setup onwards ) unlock and adb
5.... In phone dialer dial *#*#2846579#*#*
6..... Get to upgrade from sd card and hit it.
7..... Phone reboots and does the ****
8..... If you have used online Erecovery downgrading may fail but if setting up from new ( unboxing) this will def work
Dc Unlocker Method ( copied from a p20lite thread , but works for m5 identically )
1)First connect your phone to the PC using the original USB cable.
2)When drivers are installed a popup screen would appear to view the "HiSuite" drive. This is a created drive-letter which contains a HiSuite Software downloader. Click to open or use the Windows Explorer to browse to this virtual drive.
3)Install the HiSuite software - this is important to get the correct drivers AND correct COM ports installed on your system. Skipping this step will result in non working DC Unlocker software.
4)When all is done go to the settings in your phone and open: System -> About Phone and tap the Build-number line about 7 to 8 times. Most likely the phone will ask for a PIN to active the developers mode. This is the code you've setup to use your phone. If you're already have a "developers option" you can skip this step.
5)Now click the "back" arrow once and select "Developer options".
6)Tap OEM-Unlock to activate it (confirm if needed), scroll down and tap USB Debugging to turn it on.
7)Your phone should ask permission to connect your PC (with some MAC address). Confirm it so the connection is approved. If that doesn't show up disconnect the USB cable and check if the USB debug mode is still active in the "Developer options". Than reconnect the cable to your PC.
ready to use the DC-Unlocker software to get our unlock code:
8)First you need some credits and you can buy the using this link: https://www.dc-unlocker.com/buy
9)Just fill in the the fields User-name, E-mail and Credits. Leave the "New user account" option selected if you are a new user.
10)For the Credits you only need 4 of them. I, initially, bought 5 so I still have one left
11)You'll receive a confirmation e-mail with a username and password. These are needed a bit later.
12)Extract the DC-Unlocker client to a fold and start it by clicking dc-unlocker2client.exe using the Windows Explorer (or any other file manager). To be sure you can also right-click the file and start the program using Administrator credentials.
13)Select in the right portion of the program the tab "Server" and enter the username and password you've received by mail. Check the "Remeber" box and click "Check login" to verify your account.
14)Click in the left portion of the program the dropdown list below "Select manufacturer" and choose "Huawei phones".
15)Leave the droplist "Select model" selected at "Auto detect (recommended)".
16)Grab your phone and open your dialer to type this code: *#*#2846579#*#* - this will get you into the service menu of the phone.
17)Tap 1. Background Settings -> USB Port Settings and select Manufacture Mode and than tap Close.
18)Put the phone done and let your PC install the newly found drivers.
19)If that's done click the Magnifying glass in the DC-Unlocker client software.
20)If all is connected correctly your phone is detected and a message in the white part of the program will tell you so. Also the "Select Model" field should display Huawei HiSilicon Kirin Android if the detection is succesfull.
**ready to read the unlock code! Yeah!
21)Click in the right portion of the DC-Unlocker client on the tab Unlocking.
22)Several buttons are visible but just click Unlock which could take a few moments before something is displayed in the white area at the bottom of the program window.
23)The unlock code can be copied and pasted - so please do copy the number to a text file and store it savely on your computer or in your cloud.
Fastboot Unlock Method
1).... Make sure you have latest HW adb drivers installed ( check by getting an adb shell to work )
2).... Download latest Android platform tools https://developer.android.com/studio/releases/platform-tools
3)... Decompress etc, get to fastboot dir, open a CMD there
5).... Boot into Download mode ( vol down while plugging USB into computer with drivers set up )
6).... fastboot oem unlock xxxxxxxxxxxxxx

Glad to read that the development of our Schubert isn't dead

massima said:
Glad to read that the development of our Schubert isn't dead
Click to expand...
Click to collapse
Not sure about that Seems barren in terms of real development. But in this case stock is a very good base, and in terms of memory usage very competitive with LOS, so in this case do not miss real open source code for the device.
The TWRP for our device is not great, and thats something i will get hands dirty fixing.

Any chance you could upload few pictures to show us how pc mode looks on smaller device, and will ever update your rom to 9.0?
Thanks in advance.

xabat said:
Any chance you could upload few pictures to show us how pc mode looks on smaller device, and will ever update your rom to 9.0?
Thanks in advance.
Click to expand...
Click to collapse
Yes sure will get a few screenshots out.
Will update to 9 when the dev community ( LP, Xposed, and all the other projects ) catches up.
At the moment we are prob a year away. ( Xposed barely works on EMUI 8 ).
Fenris is not your normal developers rom, its not about the latest version or untested beta code. Its about providing a stable platform for "alternative" open source code projects focused on Penetration testing, and pushing the boundaries.

any chance you could tell us how to activate desktop mode on stock rom ?

Are you rooted with the TWRP mentioned in the post ?
If not not much point in going further, plus its not an easy job mate, you good at messing around with your internal files ? Permissions and selinux contexts ? Edify script ? If so then you prob could do it. Otherwise best not even start.

vecna said:
Are you rooted with the TWRP mentioned in the post ?
If not not much point in going further, plus its not an easy job mate, you good at messing around with your internal files ? Permissions and selinux contexts ? Edify script ? If so then you prob could do it. Otherwise best not even start.
Click to expand...
Click to collapse
Yes, I unlocked bootloader months ago and I have root.

xabat said:
Yes, I unlocked bootloader months ago and I have root.
Click to expand...
Click to collapse
And twrp ? Cos your going to have to write an edify script to flash everything.

vecna said:
And twrp ? Cos your going to have to write an edify script to flash everything.
Click to expand...
Click to collapse
No I don't have twrp at the moment. I can't find working recovery for emui 9.
I wanted to see if desktop mode will work on android 9

xabat said:
No I don't have twrp at the moment. I can't find working recovery for emui 9.
I wanted to see if desktop mode will work on android 9
Click to expand...
Click to collapse
Well on EMUI 9 not happening, and not happening without TWRP anyway.
So why exactly are you on EMUI 9

I guess there is no external monitor support as I dident read that anywhere.
Is it a hardware limitation?

Well, this ROM is clean and awsome, i have the 10 inch tablet but i envy those who have the Schubert model as they can try this ROM??

Fenris is now at Beta 4, front post updated.

any development for this rom?

[GUIDE] 8.2.3 + Magisk root + MagiskHide + TWRP

Based on the work done in https://forum.xda-developers.com/t/how-to-root-and-install-magisk-on-nstv-2019-pro-v8-2-0.4189567/
User friendly guide written for Windows. Bash script for Linux flashing edited as well, but guide is focused on Windows users.
Enhanced upscaling is confirmed to work, have not been able to confirm AI upscaling (Unsupported content). Dolby Vision unconfirmed as I do not yet have a TV that supports it. If someone can verify if this works or not I will update this post accordingly.
Prerequisites:
USB-A male to USB-A male cable.
USB mouse.
USB drivers: https://developer.nvidia.com/gameworksdownload#?search=SHIELD Family Windows USB
Android SDK: https://developer.android.com/studio/releases/platform-tools
Premade archive: https://drive.google.com/file/d/1XDzQyWviwVbjxNRsWJ8pG-HPSKW-Kzyl/view?usp=sharing
Unlocking the bootloader:
Go into Settings > Device Preferences > About.
Select "Build" several times until "You are now a developer!".
Go into Settings > Device Preferences > Developer options.
Activate USB debugging.
Connect one end of your USB-A to USB-A cable into the port furthest away from the HDMI on your SHIELD TV and the other into your computer.
Open a command shell (command prompt, powershell, bash, etc) on your computer.
Navigate to where you extracted the Android SDK.
Run command:
adb devices
Confirm that your device appears in the list of devices. If not this may be due to:
USB cable not connected properly. Check cable.
Device not recognized. Reinstall drivers/restart computer. Generic Android USB drivers may work if NVIDIA doesn't.
Run command:
adb reboot bootloader
Wait for fastboot to start.
Run command:
fastboot devices
Confirm that your device appears in the list of devices. If not see above reasons.
Run command:
fastboot oem unlock
Flashing:
On your computer navigate to where you have extracted the archive from the post.
Run command:
flash-all.bat
If all goes well you should be rebooted into TWRP recovery once the procedure is done.
Connect your USB mouse to the USB port closest to the HDMI port on your SHIELD TV.
Slide to unlock.
Go into Mount.
Select "Enable MTP".
Move "Magisk-v23.0.zip" from the downloaded archive to your SHIELD TV.
Select "Disable MTP".
Go into Install.
Select "Magisk-v23.0.zip" and install it.
Go into Reboot.
Select "System".
Getting Magiskhide to work:
Install Termux from Google Play.
Open Termux and run:
su
cat >/data/post-fs-data.d/bootfix-post.sh
resetprop ro.boot.verifiedbootstate orange
Press Ctrl+d.
Run:
chmod +x /data/post-fs-data.d/bootfix-post.sh
cat >/data/service.d/bootfix-service.sh
resetprop ro.boot.verifiedbootstate green
Press Ctrl+d.
Run:
chmod +x /data/service.d/bootfix-service.sh
Open Magisk (Settings > Apps > See all apps > Magisk > Open)
Select the shield icon on the bottom bar.
Enable MagiskHide
Reboot system
ALL DONE!
Sources of the premade archive contents are the following:
Android SDK: https://developer.android.com/studio/releases/platform-tools (fastboot)
The following Shield ROMs from https://developer.nvidia.com/gameworksdownload#?search=2019&tx=$additional,shield:
NVIDIA SHIELD ANDROID TV 2019 Pro Developer Only OS Image 8.1.0 (vbmeta_skip.img)
NVIDIA SHIELD ANDROID TV 2019 Pro Developer Only OS Image 8.2.0 (mdarcy.dtb.img)
NVIDIA SHIELD ANDROID TV 2019 Pro Developer Only OS Image 8.2.3
Latest TWRP recovery from https://twrp.me/nvidia/nvidiashieldandroidtv2019.html (recovery.img)
Latest Magisk from https://github.com/topjohnwu/Magisk/releases

reboot to recovery command fails with error and doesnt reboot to twrp. manually booting twrp from fastboot via fastboot boot recovery.img works

can someone explain the "MagiskHide" section of the guide? i dont have those .sh files present in /data/ . Should i just create them with the resetprop commands as the content? i just dont see where you even got those from

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I revised some steps and am now passing CTS fully... AI upscailing still says unspoorted content but i dont know if thats cuz i dont have a 4k TV, enhanced works.... i'll write up a quick and dirty guide later tonight... I need to look through everything and make sure i didnt install unneeded ****... but mainly just some props changes

Can this work on the 2017 model?

Is this the most updated guide also for the magisk hide section whats the easiest way to copy and paste this all in terminal .

albinoman887 said:
View attachment 5402781
I revised some steps and am now passing CTS fully... AI upscailing still says unspoorted content but i dont know if thats cuz i dont have a 4k TV, enhanced works.... i'll write up a quick and dirty guide later tonight... I need to look through everything and make sure i didnt install unneeded ****... but mainly just some props changes
Click to expand...
Click to collapse
Did you get around to make that guide?
Im struggling getting around the cts check.

albinoman887 said:
View attachment 5402781
I revised some steps and am now passing CTS fully... AI upscailing still says unspoorted content but i dont know if thats cuz i dont have a 4k TV, enhanced works.... i'll write up a quick and dirty guide later tonight... I need to look through everything and make sure i didnt install unneeded ****... but mainly just some props changes
Click to expand...
Click to collapse
Did you get around to make that guide?
Im struggling getting around the cts check.

bolme123 said:
Did you get around to make that guide?
Im struggling getting around the cts check.
Click to expand...
Click to collapse
Ahh crap... I'll be totally honest I completely forgot . I'll get that done by the time I go to bed today. . to be honest though I think what might have done it was I changed my device fingerprint using MagiskPropsConfig module and chose the one for sheid that's included with your IPTV service ... Other than that I just made sure there was no like things exposed that didn't need to be and removed

albinoman887 said:
Ahh crap... I'll be totally honest I completely forgot . I'll get that done by the time I go to bed today. . to be honest though I think what might have done it was I changed my device fingerprint using MagiskPropsConfig module and chose the one for sheid that's included with your IPTV service ... Other than that I just made sure there was no like things exposed that didn't need to be and removed
Click to expand...
Click to collapse
Thank you man, you nudged me in the right direction.
I was able to successfully pass the ctsCheck, and i accumulated new knowledge, thanks man!
Have a blessed day.
Before i go along with my day, did you have any success with LSPosed?
I''m gonna check now if i'm able to disable the SECURE_FLAG without tripping the SafetyNet.

bolme123 said:
Thank you man, you nudged me in the right direction.
I was able to successfully pass the ctsCheck, and i accumulated new knowledge, thanks man!
Have a blessed day.
Before i go along with my day, did you have any success with LSPosed?
I''m gonna check now if i'm able to disable the SECURE_FLAG without tripping the SafetyNet.
Click to expand...
Click to collapse
has anyone gotten AI- Upscaling to work ?

tokoam said:
has anyone gotten AI- Upscaling to work ?
Click to expand...
Click to collapse
no just the enhanced

Nvidia Shield TV pro 2019 :
I did all the steps and I have this error
I start again several times the same problem
Pasteboard - Uploaded Image
Simple and lightning fast image sharing. Upload clipboard images with Copy & Paste and image files with Drag & Drop
pasteboard.co
in start there is the following message...
Photobox | Online Photo Printing & Personalised Photo Gifts
Make stories from your photos. Print photos online or create personalised gifts with Photobox, the photo specialists. Photo Books, Prints, Canvases, more.
www.photobox.co.uk

So, any idea what to do when having diligently followed along and the result is those errors and now a Shield that can't boot and doesn't respond to ADB/Fastboot calls...
I can't believe I just blindly followed along and now my favourite thing in existence is bricked. I use it literally 24/7. Any ideas?

jamiethomaswhite said:
So, any idea what to do when having diligently followed along and the result is those errors and now a Shield that can't boot and doesn't respond to ADB/Fastboot calls...
I can't believe I just blindly followed along and now my favourite thing in existence is bricked. I use it literally 24/7. Any ideas?
Click to expand...
Click to collapse
its not bricked, and you didnt follow along else you wouldn't be in your current state. I literally just did this on my 2019 shield pro coming from the private beta without issue. The OP instructions need a few updates but most of those steps you should be familiar with anyway if you're going to be modding your devices
I lied, infinite loop, seems some derpy protection is getting tripped
0bin - encrypted pastebin
0bin is a client-side-encrypted alternative pastebin. You can store code/text/images online for a set period of time and share with the world. Featuring burn after reading, history, clipboard.
0bin.net

aouamed said:
Nvidia Shield TV pro 2019 :
I did all the steps and I have this error
I start again several times the same problem
Pasteboard - Uploaded Image
Simple and lightning fast image sharing. Upload clipboard images with Copy & Paste and image files with Drag & Drop
pasteboard.co
in start there is the following message...
Photobox | Online Photo Printing & Personalised Photo Gifts
Make stories from your photos. Print photos online or create personalised gifts with Photobox, the photo specialists. Photo Books, Prints, Canvases, more.
www.photobox.co.uk
Click to expand...
Click to collapse
its because Android is retarded and the script needs modified. After that error it should have booted into system setup, simply reboot into bootloader and `fastboot boot recovery.img` then continue onto installing magisk

Thank you for your reply...
I succeeded rooted my NSTV 2019 Pro v8.2.3
NVIDIA SHIELD ANDROID TV 2019 Pro Recovery OS Image 8.2.3
NVIDIA SHIELD ANDROID TV 2019 Pro Developer Only OS Image 8.1.0 (vbmeta_skip.img)
TWRP : twrp-3.5.2_9-0-mdarcy.img
Magisk : Magisk v23.0 'beta'
Tested :
Safetynet checks pass fine...
reboot with magiskhide without probleme script 'bootfix-post.sh' 'bootfix-service.sh'
Demo mode work only Enhanced Mode
Other work well ...
Thank xda

Any solution for unlimited loading android splashscreen after enabled MagiskHide in Magisk after reboot shield?

Enable MagiskHide :
open PowerShell :
adb shell
su (confirm permission with remote control )
cat >/data/adb/post-fs-data.d/bootfix-post.sh
resetprop ro.boot.verifiedbootstate orange
Press Ctrl+d:
chmod +x /data/adb/post-fs-data.d/bootfix-post.sh
##############################
cat >/data/adb/service.d/bootfix-service.sh
resetprop ro.boot.verifiedbootstate green
Press Ctrl+d:
chmod +x /data/adb/service.d/bootfix-service.sh
Reboot system

do i need to have the nvidia controller/gamepad for this? everything that needs to adb or fastboot, so far, works but ill get to a screen and itll ask to confirm something and so on. except i dont have the gamepad. if you guys say i need one, of course ill go buy one but in the mean time, if not, how are you going through it?
edit:
also, does 8.2.0 or 8 .2.3 matter? the first time, i did do it on 8.2.3 but had to restart because i didnt have a gamepad.

How To Guide Ultra - Fast and Stable ROG PHONE 6 PRO ROOT GUIDE !!!!!!!!!!!!!!!!!!!! (Updated)

So, i was the first to provide the update for this beauty. 6 and 6 pro.
This file will allow you to have ROOT on yout device, extracted with some tools, Terminal/adb typing, etc.
JUST TWO STEPS!
Step 1: Flash the Magisk package on Terminal, CMD or whatever (fastboot flash boot.img) www.mediafire.com/u6weyjcf7edg/igjva0go25fgtcy/magisk_patched-25200_8b9nH.img
Step 2: Download Magisk.apk and that's all!!!!!!
-----
&&&&&&&&&&
Workaround:
- computer doesnt detect phone:
Install this and double click! https://forum.xda-developers.com/t/tool-windows-adb-fastboot-august-2022.3944288/
-¿hou can Y Flass Both.IMGG?
- https://forum.xda-developers.com/t/tutorial-how-to-flash-a-new-boot-img-via-fastboot.1752270/
- I brake my phony please jelp:
Flash RAW or, Flash EDL.
- How do I preseve root with OTA UPDATE?
[GUIDE] [Magisk] [Unlock / ROOT / Keep Root] OOS 13.1.0.500
Different variants of Magisk that are available for use : Magisk Variant Stable / Beta / Canary Release Official Android / OOS OOS 11 and above Maintainer topjohnwu Project Link GitHub Zygisk No...
forum.xda-developers.com
3. Tap "Download and install" or local update if OTA from ASUS WEBSITE
4. Wait until you are prompted to reboot - DO NOT REBOOT NOW!
5. Open Magisk Application
a. Select the Install option.
b. Use Install to inactive slot
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Step 2 - Reboot and enjoy your device still rooted with latest OTA installed !​

Thank you for this guide!
Is there a way to go from CN to WW without root?

insideoft said:
Thank you for this guide!
Is there a way to go from CN to WW without root?
Click to expand...
Click to collapse
You don't need root. You can just flash the RAW file. But you MIGHT not be able to update it because updater won't recognize WW update zip file if you don't change that COUNTRY file.

Hello. Is there a link for the OPEN BL?
i searched google but cant find any links for it from the asus side.
i dont really want to install the ones belonging to the older generation of the ROG Phone.
Thanks

BaronBeef said:
Hello. Is there a link for the OPEN BL?
i searched google but cant find any links for it from the asus side.
i dont really want to install the ones belonging to the older generation of the ROG Phone.
Thanks
Click to expand...
Click to collapse
Yes! I don't know if they really work from you, maybe gets you error. But those are in Asus Website as well.

insideoft said:
Thank you for this guide!
Is there a way to go from CN to WW without root?
Click to expand...
Click to collapse
No, you need BL unlock to flash things.
And... "Root is temporary, rom is forever"
So, you can stay without root NOT FOLLOWING the latest'step.

Moderator Information
Dear all,
Two points on the current discussion: 1. give proper credit and 2. follow XDA rules on sharing other's works.
A refresher:
XDA-Developers FORUM RULES

BaronBeef said:
Hello. Is there a link for the OPEN BL?
i searched google but cant find any links for it from the asus side.
i dont really want to install the ones belonging to the older generation of the ROG Phone.
Thanks
Click to expand...
Click to collapse
insideoft said:
Thank you for this guide!
Is there a way to go from CN to WW without root?
Click to expand...
Click to collapse
YOU MAY NOT UNLOCK YOUR BL AFTER YOU UNLOCKED IT ONCE AND RELOCK IT! NOT VERIFIED ON ROG 6 SO PROCEED WITH CAUTION.

The link in step one doesn't work.

williamcll said:
The link in step one doesn't work.
Click to expand...
Click to collapse
FXD!

How to unroot after rooting? Do i need to extract the current boot.img & re flash it to unroot it?

Therazorsedge said:
Hi, I see a lot of threads, so, I open my own.
This is a tutorial of how you can have root permanently AND updates (root+updates) on this beauty.
And also, you can switch to CN (more battery, but less features -> themes, stuff) or WW ROM.
First of all, there's this files you should download on your computer or your beauty:
(A) Log by Google: MOD EDIT: LINK REMOVED, please provide proper credits when sharing others' work
(B) Download OPEN BL from Asus website, the APK to open it.
(C) Root the Asus (Fastboot flash boot on CMD) with a GOOD CABLE (**** cables doesn't work, sorry.) AND with the LATERAL PORT. You need PLATFORM TOOLS AND/OR MINIMAL ADB (GOOGLE IT AS EVERYTHING...) TO RUN...
(D) "Buy" the root explorer APK on play store, don't think for a minute you can find that on Google, or you can find it, I don't know
(E) Install Magisk APK check everything works as ROOT ENVIROMENT SUCCESFULLY INSTALLED.
(F) On ROOT EXPLORER APK press on the ‘ROOT‘ tab to access the root storage of your phone. Navigate to the ‘/Vendor/Factory‘ folder and find the file with the name ‘COUNTRY‘. Tap on the file and open it with the ‘Text Editor‘. put there CN if you want China (capital letters) or, WW if you want global, reset phone.
(G) Go to the big 4GB file you first downloaded and search the FLASH ALL AFT bat, (extract it first); then, put the phone to BL with power+vol. UP until you see in GREEN Start. Put cable on side port, and double click on FLASH ALL. Voila! You have your phone converter and -it can eat updates.
(H) To update it search for updates on Asus; rog 6 firmware on Google.
Troubleshooting
If your phone isn't detected use another cable go to device manager and check for ASUS ADB INTERFACE TO SHOW if not, change cable and/or download ADB drivers on XDA the .exe file.
The magisk image is to root the phone Fastboot flash boot .IMG (put it on CMD window)
Bonus:
To remove HARDWARESTUB download Notifications off root on play store and install it.
(10) The last step of this very good and awesome tutorial; to keep root after update; download the file, put on root directory; let it update DONT DONT DONT reboot; go to Magisk,
a. Select the Install option.
b. Use Install to inactive slot
Reboot, done.
I'm not asking for donation but; you can "donate" me more "Freely" through subscribing to my YT channel if you really want is the same and it's indeed, Free. https://youtube.com/channel/UCRFpKkKvIOrkFY5eDUG_VBg
Click to expand...
Click to collapse
Thank you for the instructions.
My phone's product code has been changed to "WW_AI2201" and could be updated the firmware from ASUS site once. However, after update the product code returned "CN_AI2201". Could you please help me to keep it "WW"?
And also please tell how to change the fingerprint from "CN" to "WW", if you know.

finallau said:
How to unroot after rooting? Do i need to extract the current boot.img & re flash it to unroot it?
Click to expand...
Click to collapse
To unroot you can just go into magisk and click uninstall, but then you probably also want to relock your bootloader MAKE SURE YOU FACTORY RESET AND HAVE STOCK ROM BEFORE YOU RELOCK YOUR BOOTLOADER!!!
Code:
fastboot oem lock
#OR
fastboot flashing lock
Then you probably also want to go to settings -> developer mode afterwards and disable -> 'OEM Unlocking'

I can't get root explorer to mount R/W on root to get COUNTRY file changed from CN to WW..
Though I could save the file but device info HW shows my fingerprint is still CN..
unable to perform manual update as fingerprint is still CN..
Had my root checker checked, running latest magisk as well..
Tried multiple root explorer versions & other file manager with root access..
Some file manager showed "file is read-only"
anybody having the same issue? any solution?

PiPpikachu said:
Thank you for the instructions.
My phone's product code has been changed to "WW_AI2201" and could be updated the firmware from ASUS site once. However, after update the product code returned "CN_AI2201". Could you please help me to keep it "WW"?
And also please tell how to change the fingerprint from "CN" to "WW", if you know.
Click to expand...
Click to collapse
I'm having the same issue too.. looks like it wasn't R/W but R/O only in root explorer hence it's the cause you won't permanently change the COUNTRY file..
Did a fingerprint check using device info HW app still shows my fingerprint as CN...

hi how i can look boot

nadeer88 said:
hi how i can look boot
Click to expand...
Click to collapse
fastboot oem lock
Or
fastboot flashing lock

AzimBahar said:
fastboot oem lock
Or
fastboot flashing lock
Click to expand...
Click to collapse
I have tried but it always doesn't go through..
I use:
adb devices and it I can see it reads my phone.. but when I type adb reboot bootloader, it doesn't continue after this for me to be able to use the commands that you gave.
Is there any way that I am doing wrong? Kindly help me lock my phone again.
Thank you!

PiPpikachu said:
Thank you for the instructions.
My phone's product code has been changed to "WW_AI2201" and could be updated the firmware from ASUS site once. However, after update the product code returned "CN_AI2201". Could you please help me to keep it "WW"?
And also please tell how to change the fingerprint from "CN" to "WW", if you know.
Click to expand...
Click to collapse
Same as me! Just update zip once, then 2n update will be fail, but i saw the country file show WW in root explorer .....any method can flash zip directly?

iMoc said:
You don't need root. You can just flash the RAW file. But you MIGHT not be able to update it because updater won't recognize WW update zip file if you don't change that COUNTRY file.
Click to expand...
Click to collapse
I bought the version with 12GB Ram and 128GB SSD, and I think that's what happens to mine, because I can´t update it OTG, what steps should I follow? What risk do I run that I already have a root and the seller did, and I don't know by what method he did or what he did to pass it from CN to WW

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

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.
Spoiler: GUIDE
HOW TO ROOT:
If you are already running the STOCK firmware version you want to ROOT, Skip to step 2.
Spoiler: HOW TO CHECK YOUR INSTALLED FIRMWARE VERSION
You can check your currently installed firmware on the shield by going into Settings, selecting About, then scroll to the bottom.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
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.
Spoiler: BOOT MODS
If you want to build your own "Boot Mod" the instructions are HERE
Spoiler: 2019 PRO (16 GB MODEL)
Spoiler: 9.1.1
9.1.1mods.zip
drive.google.com
Spoiler: 9.1
9.1mods.zip
drive.google.com
Spoiler: 9.0
9.0.0mods.zip
drive.google.com
Spoiler: 8.2.3
8.2.3mods.zip
drive.google.com
Spoiler: 2017 (16 GB MODEL)
Special Thanks to @Manzing for obtaining the 9.1 and 9.1.1 images for us!
Spoiler: 9.1.1
9.1.1mods2017.zip
drive.google.com
Spoiler: 9.1
9.1mods2017.zip
drive.google.com
Spoiler: 9.0
9.0.0mods2017.zip
drive.google.com
Spoiler: 8.2.3
8.2.3mods2017.zip
drive.google.com
Spoiler: 2015 (16 GB MODEL & 500 GB MODEL)
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
Spoiler: 9.0.0
9.0.0-2015-MODS.zip
drive.google.com
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.
Spoiler: IF YOU NEED HELP WITH THIS STEP
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.
Spoiler: YOU WILL NEED ADB INSTALLED, HERE'S AN EASY WAY TO INSTALL IF YOU NEED
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
Spoiler: NEW BOOTMOD SCRIPT OPTIONS
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.
Spoiler: IF YOUR DEVICE ISN'T SHOWING
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.
Spoiler: HOW TO INSTALL FASTBOOT DRIVERS
DOWNLOAD:
Shield Drivers.zip
drive.google.com
Now open Device Manager and follow the steps below:
Spoiler: UNLOCKING THE BOOTLOADER
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:
Spoiler: RUN YOUR MAGISK APK ON THE SHIELD
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 DELTA
Spoiler: SOURCE CODE
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
Spoiler: SOURCES
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):
https://github.com/topjohnwu/Magisk/releases/download/v25.2/Magisk-v25.2.apk
Github Project Page:
GitHub - topjohnwu/Magisk: The Magic Mask for Android
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
HuskyDG's Forked version of Magisk "Delta" Direct Download Link:
https://github.com/HuskyDG/magisk-files/releases/download/2304d221-delta/app-release.apk
Github Project Page:
GitHub - HuskyDG/magisk-files
Contribute to HuskyDG/magisk-files development by creating an account on GitHub.
github.com
All original boot images come from NVIDIA's Gameworks:
Gameworks Download Center
Get the latest Gameworks software for your game development work.
developer.nvidia.com
Spoiler: THANK YOU TO OUR COMMUNITY <3
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
Spoiler: MORE PROBLEMS WITH ROOT
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 DEVICES PROOT-DISTRO GITHUB PAGE Hello Friends! Today I wanted to start a thread that will house prebuilt Linux environments, as well as instructions for building the Linux environments yourself...
forum.xda-developers.com

This is great news for the Shield...the ai upscaling not working was the main reason i haven't rooted yet. Thank you for your time and efforts getting this together!
Bravo!

@louforgiveno it's only thanks to the Community haha. I was trying to do things in a much more complicated way and thanks to nooted and renate I understand that there is no need to reinvent the wheel and we can use the tools already made. (magisk + safetynet modules shared by ajolly) [still going to do complicated things tho.. got my uart serial adapter in today. idk how to use it but will find out and or bother renate till she blocks me ]
This guide is a good reference to bypassing safetynet
--edit now after rewatching the video a few times I understand what nooted is talking about when they say this
" The Magisk Hide settings need to be set such that everything under Google Play Services is toggled on EXCEPT FOR the GMS one at the top. Also, toggle it on for Google Services Framework."
Thank you again sosososo much @nooted1 I feel so stupid I didn't realize what magisk actually is, or does. You are the reason I learned how to select the boot.img in magisk and tell it to patch it so I can share a modded image. Now I am like a million percent certain we can do something with the system and then we would have a rom after a little customizations!

@louforgiveno 100 Percent Confirmed! Disney + is in the playstore and the ai upscaling is functional without having to relock the boot loader, YAY! Haha. The guide has been updated with the steps. It was super easy thankfully
Now I am going to learn how to get the system pulled with all of this preinstalled so we never have to do this mess. again Idk how or how long it will take but it will happen. At least folks can use this for now

jenneh said:
@louforgiveno 100 Percent Confirmed! Disney + is in the playstore and the ai upscaling is functional without having to relock the boot loader, YAY! Haha. The guide has been updated with the steps. It was super easy thankfully
Now I am going to learn how to get the system pulled with all of this preinstalled so we never have to do this mess. again Idk how or how long it will take but it will happen. At least folks can use this for now
Click to expand...
Click to collapse
Nice, that's great news! I'm gonna dig into this over the weekend

HOW TO BUILD YOUR OWN "BOOT MOD":
For anyone who wanted to know how I made the boot mods I shared, so you can make it yourself if you want.
You can take the boot.img provided to us from NVIDIA and push it to your sd card.
Code:
adb push boot.img /sdcard/Download
Then use magisk to patch the image. I didn't know what this option Meant until yesterday. Haha
YOU HAVE TO DO THIS ON THE SHIELD OR A PHONE. AN EMULATOR WILL NOT WORK; This example uses nox because I didn't feel like recording my TV
Your browser is not able to display this video.
Magisk will tell you at the end what it named the file, then you could pull the image, rename it to whatever you like, and share it. (for instance i named mine bootmod.img with a batch to erase and reflash the partition)
This should work for other devices. So that's how you patch a boot now a days
Spoiler: SIDENOTE
A Sidenote. Something funny I discovered. DON'T Do this haha.
IDK why it is but, if you push the build.prop from the ROOT 8.2.3 to the stock version, it crashed it in an interesting way. After reseting, the shield would post to the nvidia logo, make it to the google logo, crash, reboot to nvidia logo then android literally died. Haha.
Whereas, if you sent the STOCK build.prop to the ROOT system, it would not crash, and would instead allow you to do some things you normally couldn't, like download the 9.1 OTA package

Fantastic, glad it worked out. Thanks for testing it!
I mostlly want to go run cf.lumen on my shield to help with sleep.
Btw, I suspect patching the boot.img will work on any device with the same architecture - ie your phoe.

Spoiler: PLAYSTORE FIX IF YOUR PLAYSTORE IS MISSING APPS
This is only for those that need. Most shouldn't need this
NOTE this only works with the magisk delta version as it has magisk hide.
Hit the settings button at the top right
Enable ZYGISK:
STEP 1:
Download the safetynet module HERE and name it safety. MIRROR
Code:
adb push safety.zip /sdcard/Download
STEP 2:
Open Magisk and select the Modules button at the bottom right. The puzzle piece!
Select add a install from storage, navigate to Download, and install safety.zip, then reboot.
STEP 3:
MAGISK HIDE SETTINGS-
In magisk, under Settings, enable MagiskHide. Now select Configure MagiskHide
Click to show system apps
Then check all the settings for Google Services Framework
Then check everything under Google Play Services EXCEPT GMS
Now go into the SHIELD'S Settings > APPS > and force stop and Clear Data for Google Play Services, Google Services Framework, and the Google Play Store. Reboot.
Remember that you can turn the safetynet module off, which may be needed to do so you can run adb as root or perform other root operations

jenneh said:
And probably QEMU the arm architecture version too! <--Idk how to use the arm qemu yet but I have some videos stored away and some ambitions to build a proper android vm that is arm based and open source, and wont plant crap all over your drive! lol.
this man is a god send
Click to expand...
Click to collapse
Why do you want that? You’d end up converting arm code to run on x86, way more efficent to just run an x86 version.
But if you really want, its possible - https://android-developers.googleblog.com/2020/03/run-arm-apps-on-android-emulator.html

ajolly said:
Why do you want that? You’d end up converting arm code to run on x86, way more efficent to just run an x86 version.
But if you really want, its possible - https://android-developers.googleblog.com/2020/03/run-arm-apps-on-android-emulator.html
Click to expand...
Click to collapse
I want to do it to know how to, haha. not really for anything practical right now, just for practice. and Thank You so much!!

jenneh said:
I want to do it to know how to, haha. not really for anything practical right now, just for practice. and Thank You so much!!
Click to expand...
Click to collapse
i have not extensively tested it, but it seems like windows subsystem for android (on windows 11) includes an arm emulation layer. Overall its one of the nicest android emulation experiences, at the downside of not supporting all functionality properly - like notifications.

The rooting worked good, but ai upscaling does not work, I have tried your instructions. When I went to test out a video , it would only put it to basic not al-upscaling. I put it to enhance it says yes. But it's same as basic, no change in inhanced. And no to ai-enhanced. I did all the instructions that was given on this site. So I put back my Nvidia shield tv pro back to 9.1.1. thanks for all your hard work. ,. Hope someone figure it out for Ai-enhanced.

abc1054 said:
The rooting worked good, but ai upscaling does not work, I have tried your instructions. When I went to test out a video , it would only put it to basic not al-upscaling. I put it to enhance it says yes. But it's same as basic, no change in inhanced. And no to ai-enhanced. I did all the instructions that was given on this site. So I put back my Nvidia shield tv pro back to 9.1.1. thanks for all your hard work. ,. Hope someone figure it out for Ai-enhanced.
Click to expand...
Click to collapse
Your message you mailed said you used 480 p video so no that would not work. I tried the same thing with little house on the prairies and then read an article that said to use 720p or 1080p

jenneh said:
Your message you mailed said you used 480 p video so no that would not work. I tried the same thing with little house on the prairies and then read an article that said to use 720p or 1080p
Click to expand...
Click to collapse
I also tried it on 720p , and 1080p

@abc1054 Not sure then. This is still new so as more people test things and report their results we can work out the kinks. I know some people were waiting till the weekend. Thank you for trying.

I thank everyone that has contributed to this project. Thanks for all your hard work.

I reinstall the Nvidia shield tv pro 9.1.1 and rooted it, everything works but the ai upscaling, and time before I installed 8.2.3. Even checked the safetynet and was all good. So I don't get why Ai upscaling don't work. Did everything in this forum. I'm confused, if someone ever tested it, with upscaling.. it does not work. Sorry. Test it twice now. No go. Video on 720p and 1080p. Thanks again.

I have notice that google play is not certified. With the settings that was given above.

abc1054 said:
I have notice that google play is not certified. With the settings that was given above.
Click to expand...
Click to collapse
Google play is uncertified.. but rooted. When tested safety net was passed.. but play store is uncertified.. maybe its the problem of AI up scaling.

Clean installed 9.0 then manually updated 9.1.1, then did the instruction here, and got this result

Development [ROM][OFFICIAL][13] StatiXOS v6.2 [alioth/aliothin]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
StatiXOS for Redmi K40 | Mi 11X | POCO F3 (alioth/aliothin)​
What is StatiXOS?
StatiXOS is a custom ROM based on the Android Open Source Project aiming to be minimal while providing quality of life improvements and up to date security patches.
Spoiler: Known Issues
Changing the intensity of haptics does not work.
Battery stats in Settings show nothing.
Please report anything else you run into!
Spoiler: Download StatiXOS Here!
Primary
Spoiler: How To Flash
Detailed Flashing instructions in Post #3
Download the fastbootimage zip
Unlock your bootloader, and reboot to bootloader
Type in
Bash:
fastboot format:f2fs --fs-options=casefold,projid
[This will format all of the data in your phone including internal storage (photos, files, everything!)] (Skip this step if you are coming from a previous build)
Connect your phone to PC and type in
Bash:
fastboot update statix_alioth-XXXXXX-13-v6.1-TIRAMISU-img.zip
(XXXXXX denotes the date of the build)
Wait for a while until the flashing process completes, it will reboot your device
Enjoy!
Note: This ROM has GApps!
Spoiler: Stay in touch with our Telegram channels!
Official Releases & Announcements Channel
Android version: 13
Linux Kernel Version: 4.19.157
Source code: GitHub
Kernel Source code: GitHub
Code Review: Gerrit

Changelogs
6 February 2023
Initial build
7 February 2023
February 2023 Security patch
11 February 2023
Fixed missing smartspace.
Fixed camera not working with 3rd party apps.
Some under the hood micro-optimisations on top of android bionic.
23 April 2023
April Security Patch
Upgraded blobs to MIUI 14.x
Better pickup sensor implementation
Multi-Gen LRU enabled by default
Several Battery optimisations
5 May 2023
May Security Patch
Fixed the random reboot issues faced by some users

Detailed Flashing instructions:
NOTE: These instructions are for first time users only! If you are upgrading from previous StatiX Builds, you DO NOT NEED TO FORMAT DATA!
To flash StatixOS, you need these pre-requisites:
A PC with ADB/Fastboot installed
Redmi K40/Mi 11X/POCO F3 device
USB Cable
StatiXOS Build
Backup your internal storage before this process.
This guide assumes you are coming from MIUI 13.x with an unlocked bootloader.
For Windows Users:
Download SDK platform tools for Windows (do not use the latest platform tools, use any older than the r34) and extract it to anywhere you like.
Install ADB/Fastboot Drivers
Assuming you have unlocked bootloader, and enabled Developer Options, navigate to Additional Settings > Developer Options, scroll down to find USB Debugging, and enable it.
Connect your device to PC
From your PC, navigate to the extracted platform-tools
In the folder you need to check if there are some dll files and a few executables (.exe files). We're majorly concerned with adb.exe and fastboot.exe.
Whilst pressing Shift key, Right click in the folder, and there shall be an option to "Open powershell window here" or "Open Command Prompt here"
In the powershell window, type in .\adb.exe devices, now check your phone, there will a window asking to allow connection, allow it on phone. (If you don't do quicky, it may show as unauthorised in the powershell window, which is nothing to be worried about, just repeat the command)
Once the device is authorised, type in .\adb.exe reboot bootloader, your device shall reboot to a FASTBOOT screen, this is the bootloader mode.
Now ensure your drivers are proper. Type in .\fastboot.exe devices. If it shows nothing, it means that your drivers are not proper, google search on how you should fix them as it is out of the scope of this guide. Once you get an output like 2398534953 fastboot, it means that your device is detected.
(You do not have to do this step if you are upgrading from a previous StatiXOS build) In powershell, type in .\fastboot.exe format:f2fs --fs-options=casefold,projid userdata, this will completely wipe your internal storage.
Now, type in .\fastboot.exe update ''path\to\StatiXOS\Build\zip'' (replace path\to\StatiXOS\Build\zip with actual path to the fastboot images zip file) Pro Tip: You can right click and copy the zip and then paste into powershell window. Make sure you paste in between the quotes ' '.
It should show some details and start flashing immediately. It will reboot your device automatically to fastbootd mode in Statix Recovery. DO NOT DISCONNECT THE DEVICE DURING THIS PROCESS!
Wait till the process finishes, it will reboot the device automatically.
That's all! Enjoy StatiX on your device!
For Linux Users:
Install adb and fastboot according to your distro, and install proper udev rules.
Assuming you have unlocked bootloader, and enabled Developer Options, navigate to Additional Settings > Developer Options, scroll down to find USB Debugging, and enable it.
Connect your device to PC
From your PC, open Terminal
In the terminal window, type in adb devices, now check your phone, there will a window asking to allow connection, allow it on phone. (If you don't do quicky, it may show as unauthorised in the powershell window, which is nothing to be worried about)
Once the device is authorised, type in adb reboot bootloader, your device shall reboot to a FASTBOOT screen, this is the bootloader mode.
Type in fastboot devices, you'll get an output like 2398534953 fastboot, it means that your device is detected.
(You do not have to do this step if you are upgrading from a previous StatiXOS build) In powershell, type in fastboot format:f2fs --fs-options=casefold,projid userdata, this will completely wipe your internal storage.
Now, type in fastboot update ''path/to/StatiXOS/Build/zip'' (replace path/to/StatiXOS/Build/zip with actual path to the fastboot images zip file).
It should show some details and start flashing immediately. It will reboot your device automatically to fastbootd mode in Statix Recovery. DO NOT DISCONNECT THE DEVICE DURING THIS PROCESS!
Wait till the process finishes, it will reboot the device automatically.
That's all! Enjoy StatiX on your device!

Wow,
Yet another new rom for our great device,
i will have to give it a try soon,
would it be possible to make a "simple. zip" file that could be installed using TWRP or Orangefox recovery.
NOW FIXED By using Post no. 10
I wish you well with this rom and look forward to future updates
many thanks Murali

johnr64 said:
Wow,
Yet another new rom for our great device,
i will have to give it a try soon,
would it be possible to make a "simple. zip" file that could be installed using TWRP or Orangefox recovery.
I wish you well with this rom and look forward to future updates
many thanks Murali
Click to expand...
Click to collapse
I didn't make a simple zip file as custom recoveries don't support the new emulated storage changes.
Fastboot method is easier and more convenient than AOSP or in fact any recovery method.
Always having a PC is a good thing when flashing a ROM, as you can quickly restore your device to a working state without any worries if your device goes into bootloop (which should not happen with statix).

do you have some screenshots for this on poco f3? please post them

Update!
Changelog:
February 2023 security patch
Download from OP

exodius48 said:
do you have some screenshots for this on poco f3? please post them
Click to expand...
Click to collapse
Screenshots have been attached to OP

m_vaisakh said:
Update!
Changelog:
February 2023 security patch
Download from OP
Click to expand...
Click to collapse
Murali,
Your FAST.

Hi Murali,
I use a small standalone ADB program to install Temporary Recovery.
I have modified it a bit and added some basic adb FastBoot commands,
i have now included your install files as well:
-------------------------- UPDATED ! -------------------------
Now confirmed working
================================================================================
. ---------- Connect your phone to a PC in FASTBOOT mode to use this program ----------
.
.
Select Option:
.=========
.
1) Install TWRP Recovery (Remember to MOUNT SD Card in TWRP, wait 3 seconds and plug in your OTG adaptor)
2) Install OrangeFox Recovery (Remember to MOUNT SD Card in OFRecovery, wait 3 seconds and plug in your OTG adaptor)
3) Fastboot Devices
4) Reboot Bootloader
5) Reboot Recovery
6) Reboot
7) ADB Command line:
8) (WARNING)------------------ Format:f2fs
9) (WARNING)------------------ Install Statix_alioth-XXXX-XXXX XXXX-TIRAMISU-img.zip
10) Exit
.
.
. -To enter FASTBOOT, Power Off your Phone followed by Pressing and holding the Power and Volume down Buttons for 3 seconds,
.
.------------- Please read the INSTALL.txt file ---------------
.
Type option:
================================================================================
Also included in the .7z file are Magisk V25.2 and Migrate-GPE.
Download and unzip:
Statix-XXXX-XXXX-TIRAMISU + TEMP TWRP - OrangeFox (FASTBOOT) V1.0
Download Statix_Alioth-XXXX-XXXX-TIRAMISU, Rename it to rom.zip
and copy into the Statix_Alioth-XXXX-XXXX-TIRAMISU + TWRP - OrangeFox (FASTBOOT) V1.0.7 Folder.
Using this method, it is now easy to install this ROM as Murali explained and add Recovery if needed,
Thank you Murali for all your hard work,
I hope users find this little proggie helpful.

Update!
Hotfix for camera
Changelog:
Fixed missing smartspace.
Fixed camera not working with 3rd party apps.
Some under the hood micro-optimisations on top of android bionic.
Download from OP

m_vaisakh said:
Update!
Hotfix for camera
Changelog:
Fixed missing smartspace.
Fixed camera not working with 3rd party apps.
Some under the hood micro-optimisations on top of android bionic.
Download from
Apps in playstore not updating . always shows try again. Facebook messanger chats not loading .
Click to expand...
Click to collapse

Doesn't look like a statix issue to me. Did you format data using the given commands?

m_vaisakh said:
Doesn't look like a statix issue to me. Did you format data using the given commands?
Click to expand...
Click to collapse
Yes i am from MIUI 13.0.9 and formatted data .facebook messenger chat working fine but play store app updates not working. an now when plugging charger no sign of charging shown in the battery icon though the battery % is increasing. its only me with these problem? please look those.

gulmeli said:
Yes i am from MIUI 13.0.9 and formatted data .facebook messenger chat working fine but play store app updates not working. an now when plugging charger no sign of charging shown in the battery icon though the battery % is increasing. its only me with these problem? please look those.
Click to expand...
Click to collapse
You didn't understand my question. How did you format your data? What commands?
I didn't face any issue as charging indication not showing up, but one of my testers reported it today. I'll look into the issue.

m_vaisakh said:
You didn't understand my question. How did you format your data? What commands?
I didn't face any issue as charging indication not showing up, but one of my testers reported it today. I'll look into the issue.
Click to expand...
Click to collapse
(.\fastboot.exe format:f2fs --fs-options=casefold,projid userdata ) i used this

gulmeli said:
(.\fastboot.exe format:f2fs --fs-options=casefold,projid userdata ) i used this
Click to expand...
Click to collapse
That's correct. None of my testers, or I face the play store issue.
Can you try this?
Open Play Store > Tap on your Account picture in Top Right > Settings > Expand About > tap on Update Play store.
Or if that doesn't work, try rebooting the device once and check if your updates work or not.

m_vaisakh said:
That's correct. None of my testers, or I face the play store issue.
Can you try this?
Open Play Store > Tap on your Account picture in Top Right > Settings > Expand About > tap on Update Play store.
Or if that doesn't work, try rebooting the device once and check if your updates work or not.
Click to expand...
Click to collapse
Thank You Very much. it works fine now thanks again for the beautiful rom for great device.

Hi,
I tried the rom today,
the things i found:-
it seems to take a long time between the Poco F3 Logo and the boot animation,
i wasn`t able to find Face Unlock in the security setting,
Using the "Standalone ADB program" has made a massive difference,
as it simplifies every thing for me.
The rom is good but is in need of some TLC (Tender Loving Care),
I look forward to the next update,
Thank you again for all your hard work

m_vaisakh said:
I didn't make a simple zip file as custom recoveries don't support the new emulated storage changes.
Fastboot method is easier and more convenient than AOSP or in fact any recovery method...
Click to expand...
Click to collapse
I think you could explain also that this ROM uses vendorboot-as-recovery.