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?

How to skip(bypass) Google sign-in NSTV Pro 2019 with any firmware versions!

*** You should unlock bootloader ***
-In fastboot mode:
Code:
twrp-3.4.0-0-20200926-UNOFFICIAL-foster.img
(Download here!)
-Make sure the system mounted (use twrp mount option)
-Pull build.prop file: adb pull /system/build.prop
-Open build.prop file and append new line: ro.setupwizard.mode=DISABLED
-Push build.prop file: adb push build.prop /system
-Reboot NSTV: fastboot reboot
-Wait for bootup (It may take a while)
-Finish! F.ck the spy.
For safe Your privacy You have to stop Google from spying You.
The Age of Surveillance Capitalism: The Fight for a Human Future at the New Frontier of Power, Zuboff, Shoshana

Wow you know how long I have been waiting for this?
I did not test it yet but I will soon, hopefully today. Will work with both Dev image and regular image?
Thanks @mrhamed
By the way, Do you know if this method also works on a 2017 Pro 16gb version?

This method should not device specific because it related to android build ecosystem, so it could be work on any device.
Have a good time...
{
"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"
}

mrhamed said:
This method should not device specific because it related to android build ecosystem, so it could be work on any device.
Have a good time...
Click to expand...
Click to collapse
awesome.
by the way what is that screenshot?
If the google skip sign in works on all devices and on both developer image and default image, what is it that is stopping us to root and flash regular image for NS Pro 2019 and get AI Enchancer to work?

cHECKjAM said:
awesome.
by the way what is that screenshot?
If the google skip sign in works on all devices and on both developer image and default image, what is it that is stopping us to root and flash regular image for NS Pro 2019 and get AI Enchancer to work?
Click to expand...
Click to collapse
It's my device screen.
I don't like to lock-bootloader, so AI not works at this time, I'm testing "MagiskHide Props Config" to try hide the booloader-state and I hope enable AI with unlocked bootloader:
https://forum.xda-developers.com/showpost.php?p=83972471&postcount=4626

@mrhamed Im testing this method now for my NS 2017 Pro 16gb - on developer image 8.2
What Im hoping is that bluetooth will work. Because when I flash the dev image earlier and used the ↑ ↑ ← ← method and choose skip setup, bluetooth has not been working. Can not find any bluetooth devices when i search for them. The same problem on 2 different devices.
So now Im trying this method right now to see if it works better.
If it does not work I need to try the the none-developer image instead.
However this method seems to bootloop.. Im not sure whats happening.. I see the nvidia logo and then reboots again and same..
---------- Post added at 08:31 PM ---------- Previous post was at 08:26 PM ----------
The steps I took:
I boot to TWRP first through bootloader.
Format and wipe all partitions basically making it totally fresh.
Then I boot to bootloader and run the flash-all without the reboot continue.
Then I boot back to TWRP and mount system.
Then pull the file and append the line, then push it back.
Then reboot to system.
Now bootloop...
just Nvidia logo for a while then back to the ""your device is unsafe" window.. then back to nvidia logo..

cHECKjAM said:
@mrhamed Im testing this method now for my NS 2017 Pro 16gb - on developer image 8.2
just Nvidia logo for a while then back to the ""your device is unsafe" window.. then back to nvidia logo..
Click to expand...
Click to collapse
-Remove "ro.setupwizard.mode=DISABLED" from (end of file: system/build.prop).
-Try to bootup completely and setup ethernet with internet connection. then power off device.
-Make sure the system mounted (use twrp mount option)
-Pull build.prop file: adb pull /system/build.prop
-Open build.prop file and append new line: ro.setupwizard.mode=DISABLED
-Push build.prop file: adb push build.prop /system
-Reboot NSTV: fastboot reboot
I hope it works.

If above steps does not works, please try:
- Flash mdarcy.dtb.img:
Code:
fastboot flash dtb mdarcy.dtb.img
extract from nv-recovery-image-shield-atv-2019-pro-8.2.0.zip package.
- Flash vbmeta_skip.img:
Code:
fastboot flash vbmeta vbmeta_skip.img
extract from nv-recovery-image-shield-atv-2019-pro-8.1.0-dev_rooted.zip package.
If two steps does not works too! you have to: Root and install Magisk

mrhamed said:
If above steps does not works, please try:
- Flash mdarcy.dtb.img:
Code:
fastboot flash dtb mdarcy.dtb.img
extract from nv-recovery-image-shield-atv-2019-pro-8.2.0.zip package.
- Flash vbmeta_skip.img:
Code:
fastboot flash vbmeta vbmeta_skip.img
extract from nv-recovery-image-shield-atv-2019-pro-8.1.0-dev_rooted.zip package.
If two steps does not works too! you have to: Root and install Magisk
Click to expand...
Click to collapse
I dont get any method working..
The other thread with the "how to root" is lacking so much details and steps I have no idea how it is supposed to be done..
So I tried flashing the totally default dev image 8.2 . Everything boots and goes in to the setup mode
From there if I unplug ethernet I cant go anywhere.. I then reboot to bootloader and from there boot in to twrp.
Mount the system and modify the prop file as you said. then reboot to system again. Still cant bypass setup.
I also tried the exact same with flashing the vb skip image instead of default vbmeta
same result..
And it is painfully long process and every new try is a pain.
Can you please buddy please:
Write a step by step n exactly how to from scratch:
Flash 8.2 image + root + bypass google setup entirely..

Let me share my working build.prop file with you.
Make sure the permission of this file is proper too.

mrhamed said:
Let me share my working build.prop file with you.
Make sure the permission of this file is proper too.
Click to expand...
Click to collapse
Hey buddy..
I have not had time until now to try this again.. My shield has been semi-bricked since last try and have not been able to use it until now. So maybe can look in to getting this working during the vacation.
Have you gotten any better idea on how exactly to make this work? I followed all your steps last time and failed twice..

Is there anyone out there except for @mrhamed that has got this method working?
If so please share any real tutorial/steps/guide or whatever that can help.. thanks

mrhamed said:
Let me share my working build.prop file with you.
Make sure the permission of this file is proper too.
Click to expand...
Click to collapse
Are you MIA?

EDIT: oops. wrong thread.

8.2.3 - 2019 Pro here, removing ethernet works like a charm.

LifelessLife said:
8.2.3 - 2019 Pro here, removing ethernet works like a charm.
Click to expand...
Click to collapse
Maybe you can explain a bit more?

mrhamed said:
*** You should unlock bootloader ***
-In fastboot mode:
Code:
twrp-3.4.0-0-20200926-UNOFFICIAL-foster.img
(Download here!)
-Make sure the system mounted (use twrp mount option)
-Pull build.prop file: adb pull /system/build.prop
-Open build.prop file and append new line: ro.setupwizard.mode=DISABLED
-Push build.prop file: adb push build.prop /system
-Reboot NSTV: fastboot reboot
-Wait for bootup (It may take a while)
-Finish! F.ck the spy.
For safe Your privacy You have to stop Google from spying You.
The Age of Surveillance Capitalism: The Fight for a Human Future at the New Frontier of Power, Zuboff, Shoshana
Click to expand...
Click to collapse
I tried this method on the 9.0.0 2019 shield pro but I still received the google login requirement. Has anyone been able to get around this? Would like to try this out before reverting back to 8.2.3.

jolsowka said:
I tried this method on the 9.0.0 2019 shield pro but I still received the google login requirement. Has anyone been able to get around this? Would like to try this out before reverting back to 8.2.3.
Click to expand...
Click to collapse
I think 9.0.0 broke alot of things we have been taking for granted. if not using a Google account is that important to you, best to go ahead and revert back for now.

jolsowka said:
I tried this method on the 9.0.0 2019 shield pro but I still received the google login requirement. Has anyone been able to get around this? Would like to try this out before reverting back to 8.2.3.
Click to expand...
Click to collapse
Are you sure about these tow steps:
-Open build.prop file and append new line: ro.setupwizard.mode=DISABLED
-Push build.prop file: adb push build.prop /system

mrhamed said:
Are you sure about these tow steps:
-Open build.prop file and append new line: ro.setupwizard.mode=DISABLED
-Push build.prop file: adb push build.prop /system
Click to expand...
Click to collapse
Just pulled the build.prop again and the setupwizard was still disabled. Did a reboot and still requires Google sign in. Guess its back to 8.2.3.

I have no more idea and it should works!
add more options to build props:
ro.setupwizard.network_required=false
ro.setupwizard.wifi_required=false
ro.setupwizard.enable_bypass=1
ro.setupwizard.mode=DISABLED

12" Chinese Review Mirror Bootloader Unlock/Firmware Update/Theme

Using Ubuntu inside VirtualBox:
Ensure your VirtualBox is setup to see all USB devices, has internet, folder share, and drag & drop enabled.
1. Go to files and create a folder under /home/username/ called “Media”
2. Give permissions to the folder and all subsequent files by right clicking, going to properties, and setting them to allow “create and delete files”.
3. Give permissions for local network share by sharing folder, allowing others to create and delete files in the folder, and allowing guest access.
4. Inside the “Media” folder you will place a modified fastboot zip folder and extract it’s contents into this location. The zip file can be downloaded from here: Modified_fastboot
Now that you have your Computer setup, let’s get started.
--------------------------------------------------------------------------------------------
Prepare Android Mirror: (Plugged into CPU via USB)
1. Power on Android mirror.
2. Go to "Settings".
3. Scroll down and select "System".
4. Scroll down and select "About phone".
5. Scroll all the way down and click on build number until developer mode is unlocked.
6. Click on "Baseband version" 4 times to access EngineerMode.
7. Select "DEBUG&LOG".
A. Enable Never Screen Off.
B. Disable Watch Dog.
C. Enable USB Debug.
D. Allow USB debugging “Always on this computer”, and select “ok”.
8. Click the back arrow far left bottom 2 times until back in System settings.
9. Now you should see “Developer options”. Select it and turn it on.
A. Enable Stay awake.
B. Enable OEM unlocking.
C. Verify USB debugging is enabled.
D. Enable Adb Root Privileges. Pin = 2846
10. Device is now ready.
--------------------------------------------------------------------------------------------
Using Windows with Ubuntu installed within Virtualbox:
To get into fastboot:
1. Ensure you have the latest platform tools for windows. This can be downloaded from here:
Win Platform Tools
2. Extract contents to a folder.
3. Open extracted folder, right click in folder, where you see adb.exe, and select “Open in Windows Terminal”.
**** These next steps I found are to be done in a specific order and time so pay close attention ****
4. Type “./adb devices”. Press enter after the beep sound and the 4G loading screen disappears.
./adb devices
Click to expand...
Click to collapse
If done correctly you will see the following:
List of devices attached
XXXXXXXXXXXXXX device
5. Type “./adb reboot bootloader”.
./adb reboot bootloader
Click to expand...
Click to collapse
6. Press enter. - Must be done before the screen goes black and you hear the next beep. If done correctly you will see on the far left:
fastboot mode
7. You are now in fastboot mode. Try not to take too much time with unlocking the bootloader as this may timeout and take multiple tries.
--------------------------------------------------------------------------------------------
Within Ubuntu:
Unlocking bootloader within Fastboot:
1. Open the modified_fastboot folder, right-click then select Open in Terminal.
2. Setup permissions for user by entering the following one at a time followed by enter.
sudo -i
Click to expand...
Click to collapse
sudo usermod -aG plugdev root
Click to expand...
Click to collapse
cd /home/po/Media/modified_fastboot
Click to expand...
Click to collapse
3. Test device detection using:
./fastboot devices
Click to expand...
Click to collapse
4. Get identifier Token using:
./fastboot oem get_identifier_token
Click to expand...
Click to collapse
5. You should get an output like:
Identifier token:
XXXXXXXXXXXXXXXXXXXXXXXXXXXX
OKAY [0.019s]
finished. Total time: 0.019s
6. Copy the Identifier token.
7. Run this command ; replace XXXXXXXXXXXXXXXXXXXXXXXXXXXX with your Identifier token. Should look like this:
./signidentifier_unlockbootloader.sh XXXXXXXXXXXXXXXXXXXXXXXXXXXX rsa4096_vbmeta.pem signature.bin
Click to expand...
Click to collapse
8. You should have an output like:
Identifier sign script, ver 0.10
1+0 records in
1+0 records out
50 bytes copied, 0.000257562 s, 194kB/s
Identifier sign successfully
9. You should also see a signature.bin file in the modified_fastboot folder.
10. Finally run this command:
./fastboot flashing unlock_bootloader signature.bin
Click to expand...
Click to collapse
11. When it asks to confirm bootloader unlock (volume up/volume down options):
Locate the A/V port on the top of the device, looks like a 3.5mm plug, and use a small ½” long device/toothpick/paperclip to push the button on the inside of the port at 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"
}
12. The status should now say:
Begin to erase user data…
This takes >5mins to accomplish
13. Once completed successfully, the status will say:
Info: Unlock bootloader success!
14. Wait 2 minutes and hold the power down to restart the device. The device will restart a few times and will now indicate the bootloader unlocked on the left side of mirror.
--------------------------------------------------------------------------------------------
Update to latest firmware:
1. Go to and read through the Original Post, Original Post in Russian, and ensure your device is the same device or very similar in design. If not you should not update with the mentioned firmware.
2. Download firmware update:
QC_BITE_M5_188_Media_Sleep_2021010619_202101061959_64bit.pac
The tools that will be needed and instructions:
1.Go to this website, https://spdflashtool.com/
2. Download latest version of Research Tool here: Research-tool
3. Follow instructions on how to use the Research Tool here: Instructions
A. Here is the link for the SPD driver you will need: Drivers
B. Stop at step 8 do not connect your mirror to the computer. Make sure your mirror is turned off and follow this video to complete the installation process:
--------------------------------------------------------------------------------------------
If you would rather complete with written tutorial vice watching video, here are the remaining steps.
1. Turn off the mirror if not done already.
2. Ensure firmware loaded into the Research tool and press the Play/start button.
3. With something small like a toothpick/paperclip, press the button inside the AV port at the top of the mirror. Make sure you find the button before proceeding.
4. Once you have found the button, press it and hold it.
5. Then connect the mirror to the computer with your other hand.
6. The firmware will start to download. You can now release the button.
7. Now you wait until complete and reboot(s) complete.
--------------------------------------------------------------------------------------------
Additional/Optional:
Not promoting anything, but kinda am. I get nothing in return for advising to use of any tools. This one here has helped me more than i can explain and was created by an OG of XDA, Koushik Dutta, aka. Koush. He is most famous for his work with Clockwork-mod. Show him some support if you like his work.
Tool to control pretty much any android device from your computer: Vysor
https://www.vysor.io
Here is a video showing you how to use the program. It is done with a Firestick, but once I was setup it just found the mirror itself once I plugged it in as well as my cell phone:
--------------------------------------------------------------------------------------------
Now that your bootloader is unlocked and your system is up to date, you may want to customize things a bit as most on XDA do. This is super new to me, like only 2 days working on this mirror.... I did however find a legit app, through playstore, to customize your home screen to not look like so tacky/boring. The app is called Car Launcher. There is a free version and a paid one. Paid version unlocks so much customization. I recommend installing the free version and testing it out. If all works, then the paid version is the way to go. I know the paid works very well with the above firmware. I have tested it quite extensively and so far found only one hick-up. Here are the links.
Recommended Home replacement: Free
Car Launcher Free
PRO Version is much better: cost $4.99
Car Launcher Pro
Whatever you do, don’t use program brightness settings in the themes or Car Launcher. Use the device’s settings.
Good place for some cool backgrounds I found for my Caddy that has other vehicle designs is: www.el-tony.com
Credit goes to a few places:
Iamrance.asa Bootloader Unlock
Hovatek Bootloader Unlock
Troypoint Vysor Setup
4PDA Threads
SPD Research Tool Guide

Saved for updates and customizations

Mod edit - translated by https://www.deepl.com/translator:
Hi I have a device szkj d 30 10 inch android 8.1 mirror that reboots all the time and goes into recovery on retry!Even if I do the reset it gets stuck in the same position.How do I do the data factory reset if it is stuck and won't turn off!!!!
VNDITORE Amazon says motherboard is broken!!!!
***************************
Ciao io ho un dispositivo szkj d 30 10 pollici android 8.1 mirror che si riavvia in continuazione e va in recovery su riprova!Anche se faccio il reset si blocca nella stessa posizione.Come faccio a fare il data factory reset se è bloccato e non si spegne!!!!
Spoiler
VNDITORE Amazon dice che si è rotta la scheda madre!!!!

Hello @po8pimp. Thank you very much for this tutorial, it is very useful. Hopefully someone can make a custom rom for these mirror.
I have a similar mirror, i think from HGDO brand, 4GB RAM 32Gb ROM with the firmware QC_1126bit_M5_1126_media_sleep_2020112517
Can I use your method and install that firmware?
In other hand I cant logout a google account from the mirror. Do you know how to delete and account from it?
Thank you

cregi said:
Hello @po8pimp. Thank you very much for this tutorial, it is very useful. Hopefully someone can make a custom rom for these mirror.
I have a similar mirror, i think from HGDO brand, 4GB RAM 32Gb ROM with the firmware QC_1126bit_M5_1126_media_sleep_2020112517
Can I use your method and install that firmware?
In other hand I cant logout a google account from the mirror. Do you know how to delete and account from it?
Thank you
Click to expand...
Click to collapse
I will have to check on the firmware ability. As far as the google account logout, you will more than likely have to factory reset the device.

cregi said:
Hello @po8pimp. Thank you very much for this tutorial, it is very useful. Hopefully someone can make a custom rom for these mirror.
I have a similar mirror, i think from HGDO brand, 4GB RAM 32Gb ROM with the firmware QC_1126bit_M5_1126_media_sleep_2020112517
Can I use your method and install that firmware?
In other hand I cant logout a google account from the mirror. Do you know how to delete and account from it?
Thank you
Click to expand...
Click to collapse
Phisung Z66 и клоны - Смарт-зеркало заднего вида - 4PDA
Phisung Z66 и клоны - Смарт-зеркало заднего вида, [Автомобиль][Зеркало][Видеорегистратор][Android]
4pda.to
This is the forum you would want to find your firmware for your device in. I recommend if you don't know Russian to get a browser with add on support to translate the pages for you. I use Firefox and Translate web pages extension which works really well.

hi i have this mirror following the guide, "./adb device" command list the device, but i can't get it to go into fastboot mode with "./adb reboot bootloader" command ...is there another method using combination of buttons?

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

How To Guide CPH2451 Rooters Please refrain to g96818 guide to Improve the Init_boot method.

Hey guys, i have tested the new method posted by g96818 and it works perfect.
Since he has more experience than me with OnePlus rooting I'll delete this post soon.
My fear is the future proofing of my method and i understand that his method is better in the case of future updates and less risky.

Finally!. Excited to see the rooting movement beginning let's go. Would have tried but I've got CPH2447.

hitzzzzzzzz said:
Finally!. Excited to see the rooting movement beginning let's go. Would have tried but I've got CPH2447.
Click to expand...
Click to collapse
Hey man, but there is a full OTA for that, you just need to subtract the info you need from it.
Since i dont have that device, i dont want to tell you what to do.

Nice. It'd be fantastic too if we could use this as a ongoing reference for future OTA's. Have someone drop by and post a patched init_boot image everytime a new OTA comes out and keep track of them for the CPH2451

scott.hart.bti said:
Nice. It'd be fantastic too if we could use this as a ongoing reference for future OTA's. Have someone drop by and post a patched init_boot image everytime a new OTA comes out and keep track of them for the CPH2451
Click to expand...
Click to collapse
Yeah that's true that would be nice.

Adb connect works better than adb pair from wireless debugging adb connect then adb shell then run reboot bootloader command For me it would connect with pair but not recognize my device

scottlam1 said:
Adb connect works better than adb pair from wireless debugging adb connect then adb shell then run reboot bootloader command For me it would connect with pair but not recognize my device
Click to expand...
Click to collapse
adb and also the fastboot drivers installed? and USB debugging activated?
and only adb works over wifi , fastboot only with usb cable

blasbenoit said:
I am not responsible for any any harm, such as bricking, or bootloops, which may happen to your device. This is what worked for me and other guys in this forum.
Important notes to consider: A big thanks to azsl1326 he got us the Patched Init_boot to make this possible.
-You need to unlock the bootloader of your device. This means you'll lose the data ect ect ect.
-People are losing Netflix access after this process, right now we haven't found a "cure" for this, but is pretty normal if you have root a Oneplus device before, when i found the fix i'll edit this right away.
-I'll write this for experts and newcomers a like just in case so they don't have to start asking for simple questions.
-After the root some people have the issue that they cant use security like passwords, fingerprint...ect ect. (as of now the only fix they have is to reset everything and doing the rooting again for 2+times). If i find the "cure" i'll let you guys know.
Spoiler: Issues connecting your device to the PC?
To some people the USB debugging is not working at all, because the phone turn it off after you try to use it or connect it to the PC.
I personally had this issue so i just workaround it. This is what i did:
1- Connect the OnePlus to the same network as your PC.
2- Turn On Wireless debugging on your OP11 and select Pair device with pairing code:
3- Then use this on your PC after you open CMD of course:
Then put the code you have.
The check with this command to see if it is connected:
Now that it is connected you can enter bootloader and connect it to your PC in that mode normally with:
OK now back to the deal:
1- Download the latest platform tools from here:
-Unzip it and put it in the desktop for easy access.
2-The bootloader
Spoiler: Unlock the Bootloader
Step 1 - Unlocking Bootloader:
1.A - Enable OEM Unlocking:
1. Open Settings Application -> About device -> Version -> Tap on Build Number 7 times
2. Open Settings Application -> Additional Settings -> Developer Options
3. Enable OEM Unlocking
4. Enable USB Debugging
1.B - Entering Bootloader
The bootloader must be unlocked in order to flash the recovery.
Ensure the device is connected to the computer via ADB by entering the following command
Code:
adb devices
The output should be something similar to this:
{
"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"
}
(note the device name on the left will not be the same)
Reboot into the bootloader by entering the following command:
Code:
adb reboot bootloader
1.C - Unlock
Once entered, enter the following command:
Code:
fastboot flashing unlock
WARNING: THIS WILL WIPE ALL DATA ON THE DEVICE
Use the volume keys to select unlocking, and then use the power button to confirm.
Once complete, enter the following command:
Code:
fastboot reboot
You will now have to go through the device setup.
Repeat steps 1.A and 1.B to enter back into the bootloader
3- Flashing the Init_Boot.img
In this case i'll provide the already patched Init_boot.img for A07!!! so you don't have to look for it, is attached to this thread.
Download the img and put it in the same folder as the platform tools for easy access.
Spoiler: Magisk Canary
After you enter the device.
1. Dowload the Magisk Canary version from this link:
2. Install it on you device.
Spoiler: Opening CMD (Command Prompt)
After you got everything in place open the platform folder and type CMD on the location box, then press Enter.
If that doesn't work, just open CMD and type:
CD and write the location of the platform folder to get it to work.
Now to the "flashing"
Enter the bootloader like before to start, now type this:
The above command should automatically flash the init_boot to both the slots. However, if you face any issues while executing that command, then you could also manually specify the slots while flashing. Like this:
And
4-Restart your phone and check the magisk canary app that everything is OK.
Spoiler: Bypassing Safetynet
This is optional; however, highly recommend
Note, due to the nature of Safetynet, this can change at anytime and may begin failing in the future.
A - Repackaging Magisk
1. Launch Magisk Manager
2. Tap Settings Icon (Top Right Corner)
3. Tap "Hide The Magisk App"
4. Enter New Application Name
5. Click OK and wait
6. Uninstall original Magisk APK if it has persisted
B - Enable Zygisk & Deny List
1. Launch Magisk Manager
2. Tap Settings Icon (Top Right Corner)
3. Enable "Zygisk"
4. Enable "Enforce Deny List"
C - Configure Deny List
it is recommended to add any application you would like to hide from Magisk here
1. Launch Magisk Manager
2. Tap Settings Icon (Top Right Corner)
3. Tap "Configure DenyList"
4. Tap the 3 dots in the top right and select "Show System Apps"
5. Select the following applications:
~ Android System
~ Google Play Store
~ Google Play Services
~ Google Services Framework
D - Delete App Data
1. Launch Settings Application
2. Select Apps
3. Select App Management
4. Clear data for the following apps:
~ Google Play Store
~ Google Play Services
~ Google Services Framework
5. Reboot the device
E - Flash Universal Safetynet Fix
1. Download the Universal Safetynet Fix
2. Launch Magisk
3. Select Modules
4. Select "Install From Storage"
5. Select Universal Safetynet Fix
6. Wait for Flashing to complete
7. Reboot
Download a safetynet check just to be sure.
And thats pretty much it, if you guys find some issues after the root, please post them here so i'll start adding more and more info about it for future references and fixes.
Click to expand...
Click to collapse
You are so helpful! This worked flawlessly!

ChrisFeiveel84 said:
adb and also the fastboot drivers installed? and USB debugging activated?
and only adb works over wifi , fastboot only with usb cable
Click to expand...
Click to collapse
Yeah fastboot still has to be hardwired I'm just going by my experience that pair function didn't work for me adb connect did wireless you still put in the IP and port but no pair key

scottlam1 said:
Yeah fastboot still has to be hardwired I'm just going by my experience that pair function didn't work for me adb connect did wireless you still put in the IP and port but no pair key
Click to expand...
Click to collapse
i never use adb over wifi sorry

Do you by chance have the stock unpatched init_boot.img? When you say that you have to redo the whole root process a couple of times to get screen lock working, uprooting would be flashing a stock init_boot yeah?

H4X0R46 said:
Do you by chance have the stock unpatched init_boot.img? When you say that you have to redo the whole root process a couple of times to get screen lock working, uprooting would be flashing a stock init_boot yeah?
Click to expand...
Click to collapse
unrooting before the update is actually only needed if you do the update via incremental update (e.g. eu and india get full firmware packets) so you don't need to unroot first

ChrisFeiveel84 said:
unrooting before the update is actually only needed if you do the update via incremental update (e.g. eu and india get full firmware packets) so you don't need to unroot first
Click to expand...
Click to collapse
Mine is the USA model CPH 2451, I updated my phone to A.07 already by normal means, my bootloader is still locked, so I haven't even begun to mess with it YET. This might cause issues with my lock and fingerprint I'm assuming? Just wanna be sure I'm understanding this correctly. Thanks man for all your help! Much appreciated

H4X0R46 said:
Mine is the USA model CPH 2451, I updated my phone to A.07 already by normal means, my bootloader is still locked, so I haven't even begun to mess with it YET. This might cause issues with my lock and fingerprint I'm assuming? Just wanna be sure I'm understanding this correctly. Thanks man for all your help! Much appreciated
Click to expand...
Click to collapse
I didn't have an issue with my lock screen and stuff. I also didn't do anything to the phone other than unlock bootloader and root. Once I did this my lock screen and fingerprint and stuff wasn't an issue at all. Maybe I got lucky.

H4X0R46 said:
Do you by chance have the stock unpatched init_boot.img? When you say that you have to redo the whole root process a couple of times to get screen lock working, uprooting would be flashing a stock init_boot yeah?
Click to expand...
Click to collapse
The password issue has nothing to do with rooting, it is caused by unlocking the bootloader. Before you do any rooting, first lock and unlock the bootloader 3 times. After the third time, you can set the password (or pin, or pattern/etc) and THEN do the actual rooting.

Do you have boot.img instead i rather have temp root

i accidentally pushed the patched init boot img to phone before updating, now i keep getting failed system update, any way to revert back to original A06 init_boot.img so i can take update and then come back and root

SappyHanger said:
Do you have boot.img instead i rather have temp root
Click to expand...
Click to collapse
Sorry m8, they haven't release the full IMG yet, just incremental, unless you are in (UPDATE A06), i can tell you where to get it for that one.

blasbenoit said:
Sorry m8, they haven't release the full IMG yet, just incremental, unless you are in (UPDATE A06), i can tell you where to get it for that one.
Click to expand...
Click to collapse
can you point me to the init boot image on A06, i accidentally pushed the patched a07 version to a06 w/o updating to a07

So I did the above and magisk turns into a green android icon and won't start. It did start before I flashed the init boot.... ?? Tried to re-install magisk, same thing. green icon.....
Do I need to sideload magisk? (adb sideload Magisk-v25.2.zip) ???