Develop Bugs

Shield TV 2015 (full) OTA 5.1 [Feb, 17] zip file (NON-PRO) uploaded on MEGA

Shield TV 2015 (NON-PRO) Nougat update version 5.1 is live since yesterday:
{
"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"
}
OTA is downloaded to the usual folder: /data/data/com.nvidia.ota/app_download
Filename: PUBLICc5a95c683d62900b0a84163b9e5b05c6.zip
MEGA .zip link:
https://mega.nz/#!pIZXiZhb!rnkf0HYsIWWXq3AOl0MzMQUgs0usoTOJWT2Yd_Jg734
P.S.: This time OTA release nomenclature match System version in "About".

How to flash this stuff ? There are no .img files for system and vendor... Has anyone tried flashing this ?

I just came here to tell you that this post saved my life twice. If you flash this with TWRP you can get your system back aftera brick. for me the nvidia method does not work, so this is the only way i managed to fix my shield. TWRP will give you erors but just reboot and you are saved.
Any chance of getting a full 5.2 image since I can't update ?

THANK YOU
:good:
sammarbella said:
Shield TV 2015 (NON-PRO) Nougat update version 5.1 is live since yesterday:
OTA is downloaded to the usual folder: /data/data/com.nvidia.ota/app_download
Filename: PUBLICc5a95c683d62900b0a84163b9e5b05c6.zip
MEGA .zip link:
https://mega.nz/#!pIZXiZhb!rnkf0HYsIWWXq3AOl0MzMQUgs0usoTOJWT2Yd_Jg734
P.S.: This time OTA release nomenclature match System version in "About".
Click to expand...
Click to collapse

pendragon666 said:
I just came here to tell you that this post saved my life twice. If you flash this with TWRP you can get your system back aftera brick. for me the nvidia method does not work, so this is the only way i managed to fix my shield. TWRP will give you erors but just reboot and you are saved.
Any chance of getting a full 5.2 image since I can't update ?
Click to expand...
Click to collapse
I'm waiting to update my Shield TV 2015 16 GB to 5.2 , this little update is not like the full OTAs we got before (5.02/5.1).
I unlocked My Shield TV 16 GB bootloader and flashed TWRP and got root on 3.1 (MM) then it upgraded to 5.'2 and 5.1 without problem.
The 5.2 full OTA rooted image will be available soon in the Nvidia SHIELD Developer OS Images site:
https://developer.nvidia.com/shield-developer-os-images
I can wait a few days more...

Yeah, but i can't get that method to work, it tells me the data is too large when flashing system.img

tomhunter33 said:
How to setup Shield TV on my Windows? I want to watch the content of Shield TV on my laptop screen.
Click to expand...
Click to collapse
What has this got to do with the OP? Start your own thread for your topic, don't jump on someone else's.

pendragon666 said:
I just came here to tell you that this post saved my life twice. If you flash this with TWRP you can get your system back aftera brick. for me the nvidia method does not work, so this is the only way i managed to fix my shield. TWRP will give you erors but just reboot and you are saved.
Any chance of getting a full 5.2 image since I can't update ?
Click to expand...
Click to collapse
Hi,
could you explain in more detail how you flashed the OTA through TWRP?
Thanks in advance!

Well, you just flash twrp and then the recovery image. You can find how to get twrp onto shield fromnvidia shield zone. It's a fan site with good tutorials.

pendragon666 said:
Well, you just flash twrp and then the recovery image. You can find how to get twrp onto shield fromnvidia shield zone. It's a fan site with good tutorials.
Click to expand...
Click to collapse
Hmm curious, from your previous post I got the idea you had flashed the PUBLIC*.zip or some content from it inside twrp. so you are saying you took the recovery image file, flashed it as if a zip install file and it unblocked the shield, right? (just confirm if this is it and if this works you are getting a big thanks!)

Well, i flashed the link from the first post. It failed, but it fixed my shield. I wouldnt recommend doing this. It was my last ditch effort before i realized that the nvidia tutorial for recovery is wrong

Well the link submitted in this thread is for the non-pro so I can't really use it, but the method you use is interesting because it would be my only way out of the stuck nvidia logo.
My Shield Pro 2015 has been stuck in nvidia logo for a long time. I tried to throw at it all images from nvidia dev and non-dev up to 7.0.1 using the nvidia method as described in their webpage.
I get to recovery and flash successfully all files but the nvidia logo still stays. I can boot TWRP and even browse the disk contents, so I wanted to flash an OTA PUBLIC*.zip in TWRP like you did, but there seems to be none available.
I found a possible compatible file here but I have no idea if it is compatible with my shield pro and even how to flash it like you did.

guardiman said:
Well the link submitted in this thread is for the non-pro so I can't really use it, but the method you use is interesting because it would be my only way out of the stuck nvidia logo.
My Shield Pro 2015 has been stuck in nvidia logo for a long time. I tried to throw at it all images from nvidia dev and non-dev up to 7.0.1 using the nvidia method as described in their webpage.
I get to recovery and flash successfully all files but the nvidia logo still stays. I can boot TWRP and even browse the disk contents, so I wanted to flash an OTA PUBLIC*.zip in TWRP like you did, but there seems to be none available.
I found a possible compatible file here but I have no idea if it is compatible with my shield pro and even how to flash it like you did.
Click to expand...
Click to collapse
Hey guardiman have you been able to fix your shield pro? If it still hasn't worked out, then maybe I know a solution. Let me know.

yuseigachi said:
Hey guardiman have you been able to fix your shield pro? If it still hasn't worked out, then maybe I know a solution. Let me know.
Click to expand...
Click to collapse
Hi, yuseigachi
No, I haven't. The shield is still waiting for some available time to try a hard drive replacement. The thread leading to this option is here:
https://forum.xda-developers.com/shield-tv/help/nvidia-shield-tv-pro-2015-stuck-nvidia-t3780927
If you have an alternative option to try, I'd be more than happy to go for it
Cheers

[Unofficial] HTC U11+ TWRP Recovery

{
"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"
}
It have been about 2 years, I finally get a U11 plus to make TWRP device tree with working decrypt function.
Source: https://github.com/sabpprook/android_device_htc_ocm
Please download latest TWRP build in following link.
[Android 8.0]
twrp-3.3.1-0-ocm_171001.img
twrp-3.3.1-0-ocm_171201.img
twrp-3.3.1-0-ocm_180601.img
twrp-3.3.1-0-ocm_180901.img
twrp-3.3.1-0-ocm_181001.img
twrp-3.3.1-0-ocm_181101.img
[Android 9.0]
PS. watch out the last 6 digits at the filename, it must equal to your system's android patch level. e.g. 2017-12-01 (Dec, 2017) = 171201, otherwise TWRP will not decrypt data partition.
PS2. U11+ already get Android Pie update, but this update will break data decrypt function in TWRP recovery.
@nkk71, thanks all the works you've done for us.

Thank you very much!
https://i.imgur.com/71t8xrY.png
https://i.imgur.com/qebNB0C.png
https://i.imgur.com/ubxYZsN.png
https://i.imgur.com/gsbaG2K.png
https://i.imgur.com/xIW8llN.png
https://i.imgur.com/Fzrdhwt.png

Awesome!!

yay. now to get more dev support behind this!

excellent! Please, try to put up a github repo for it, if not already
Hopefully it works fine.
If HTC rolls out kernel sources, I might try some blind development, as I don't have the device, but wanna support it.

Should you need to unlock the official htcdev before they can put?

mapleshadow said:
Should you need to unlock the official htcdev before they can put?
Click to expand...
Click to collapse
Yes, unlock then you can boot it.

Thanks for this! Going to try and get it up and running later today - Need to unlock the BL first.

Thanks for this however it doesn't seem to work for me. I've unlocked the bootloader, rebooted into bootloader mode via adb (adb reboot bootloader), tried to boot the twrp image (fastboot boot twrp-3.1.1-2_unofficial-ocm_2.img) and all I get is a black screen even though the commands seem to work at first:
fastboot boot twrp-3.1.1-2_unofficial-ocm_2.img
downloading 'boot.img'...
OKAY [ 0.894s]
booting...
OKAY [ 10.112s]
finished. total time: 11.006s
Click to expand...
Click to collapse
Any idea what's going on?

aurelienlux said:
Thanks for this however it doesn't seem to work for me. I've unlocked the bootloader, rebooted into bootloader mode via adb (adb reboot bootloader), tried to boot the twrp image (fastboot boot twrp-3.1.1-2_unofficial-ocm_2.img) and all I get is a black screen even though the commands seem to work at first:
Any idea what's going on?
Click to expand...
Click to collapse
Did you flash the custom recovery ..?
P.S. Nothing of linked below worked out?
http://featuresunlocker.com/root-install-twrp-recovery-htc-u11/
Yet sent from my amazing silver U11

jauhien said:
Did you flash the custom recovery ..?
P.S. Nothing of linked below worked out?
Yet sent from my amazing silver U11
Click to expand...
Click to collapse
I didn't flash since I wanted to test it out before using the fastboot boot command recommended in the original post. However this does not seem to work. I wanted to get twrp running so I could use magisk for root

Went ahead and flashed it anyway and I'm happy to report that it worked and did not brick my device. So I still don't know why it won't let me fastboot boot but at least TWRP is now installed.

aurelienlux said:
Went ahead and flashed it anyway and I'm happy to report that it worked and did not brick my device. So I still don't know why it won't let me fastboot boot but at least TWRP is now installed.
Click to expand...
Click to collapse
Be aware that you're now lacking the ability to ota update if you cannot get ahold of a stock recovery.
That's why booting only and making a backup of stock recovery boot and full system partition, is highly recommended.

tbalden said:
Be aware that you're now lacking the ability to ota update if you cannot get ahold of a stock recovery.
That's why booting only and making a backup of stock recovery boot and full system partition, is highly recommended.
Click to expand...
Click to collapse
I bought the right version of the stock rom I'm running from en.pars-hamrah.com. It's a slightly sketchy looking site and it cost me 9$ but it should allow me to go back to stock easily
I'll share it here if people are interested. It's version 1.05.400.13 which is the latest version for the Hong Kong version

aurelienlux said:
I bought the right version of the stock rom I'm running from en.pars-hamrah.com. It's a slightly sketchy looking site and it cost me 9$ but it should allow me to go back to stock easily
Click to expand...
Click to collapse
OK, that's very professional. :good:
Just others be aware that you should make sure you have a way backwards.

aurelienlux said:
I bought the right version of the stock rom I'm running from en.pars-hamrah.com. It's a slightly sketchy looking site and it cost me 9$ but it should allow me to go back to stock easily
I'll share it here if people are interested. It's version 1.05.400.13 which is the latest version for the Hong Kong version
Click to expand...
Click to collapse
That would be fantastic and very good of you if you could share it. Many thanks!

@nkk71 Any idea of decryption problem?
Seems "/firmware" not symlink and "/vendor/bin/qseecom" sepolicy not set correctly

sabpprook said:
@nkk71 Any idea of decryption problem?
Seems "/firmware" not symlink and "/vendor/bin/qseecom" sepolicy not set correctly
View attachment 4342230
Click to expand...
Click to collapse
Looks like you're building in android 7.1 for Oreo decrypt, won't work without the needed sepolicy changes and plat/non_plat contexts, please check the current gerrit updates for the standard HTC U11:
TWRP vold_decrypt patch: https://gerrit.omnirom.org/c/26652/
EDIT2: U11 Oreo decrypt device tree changes needed for a 7.1 build: https://gerrit.twrp.me/c/2756/
If you end up with decryption successful, but it doesn't actually mount /data, then you may even need an updated kernel https://gerrit.twrp.me/c/2761/
which is what we needed. EDIT: Obviously that's a U11 kernel update not a U11+ one, so don't try to use that kernel
Some things will still get changed. I also recommend you build in real DEBUG mode, the straces have much more info than a log or dmesg. by using TW_CRYPTO_SYSTEM_VOLD_DEBUG := true

Prot02018 said:
That would be fantastic and very good of you if you could share it. Many thanks!
Click to expand...
Click to collapse
There you go: https://drive.google.com/open?id=1nkzK_wbSgC6HSlOsNqOc79f94p7v_3wz
That's version 1.05.400.13. I managed to decrypt it successfully using the latest RUU Decryption Tool on Windows. I have a decrypted boot.img and system.img but I haven't yet uploaded those to my drive.

Waiting for your Good news.

Android P on Redmi 5 Plus

For those who want to try Android P here are the how-to.
I just sharing the experience, I´m not involved in the project.
The sources will free-up for the ends of the month so maybe some dev could put his hands on it.
For now it´s unlikely unstable and with some bugs but usable for a basics and sharing some issues could be solved.
A good introducing for a better comprehension :
https://www.xda-developers.com/android-p-beta-port-snapdragon-project-treble-devices/
This is the general thread:
https://forum.xda-developers.com/pr...ment/rom-android-p-developer-preview-t3816659
These are the steps for our device:
https://forum.xda-developers.com/showpost.php?p=77101817&postcount=308
Maybe someone can wipe too system adding to the steps of wiping from recovery and only will stay vendor partition needed to boot.
Other links:
Treble rom base: https://forum.xda-developers.com/redmi-note-5/development/rom-cardinalaosp-t3774232
Recovery used for this: https://forum.xda-developers.com/re.../official-orangefox-recovery-project-t3807479
I tried before with the latest recovery provided for miui 10 (vince_treble_twrp-jay-port-v3), I formatted data to can boot as indicated for some users in the thread but never boot and never recovered the ability to see files and flash nothing more directly (but adb sideload) from this twrp version, any of the three no-verity/lazyflasher/antibootloop worked for this so I started again with Orange Fox recovery. (although any treble recovery could work following right steps indicated)
No need to flash callfix.zip.
Some screenshots:
{
"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"
}

would appreciate if you provide the list of bugs and what about major things like volte and camera2api?

ridersam said:
would appreciate if you provide the list of bugs and what about major things like volte and camera2api?
Click to expand...
Click to collapse
I didn´t try many, for me it´s in beta level yet but as far as I know VoLTE is a global bug in all devices yet and camera2api it´s not working for me but maybe with other mods can work so in some devices it works, but we can expect that as many users and devs take part of this then we get more advance. I hope that users can share the experiences and so help others.

I use android p. And for me this gsi is much better than los 15.1 ... except for fingerprint. 2api camera works great! only first you need to flash .zip 2api, only after that install the camera application! The battery holds well, and is pleasant and smooth to use.)) I love the new from Google)

I am currently on DP 3 so should i flash clean or dirty flash over DP 3

I did the exact steps and still it goes directly to fastboot and does not boot the os

ibbi.ir7 said:
I am currently on DP 3 so should i flash clean or dirty flash over DP 3
Click to expand...
Click to collapse
DP3 is the GSI, what do you want to flash over DP3?

seekahaa said:
I did the exact steps and still it goes directly to fastboot and does not boot the os
Click to expand...
Click to collapse
Did you made wipes before to flash Cardinal treble?

SubwayChamp said:
Did you made wipes before to flash Cardinal treble?
Click to expand...
Click to collapse
Yes I wiped everything as I supposed to, still nothing.
I will try the same steps again now.

SubwayChamp said:
Did you made wipes before to flash Cardinal treble?
Click to expand...
Click to collapse
I started from start to flash DP 4 and it is more fluid than DP 3.

Anyone tried with a treble enabled custom kernel?

why cardinal treble rom ? cant we use other treble based roms ?

---account closed

---account closed

langster- said:
I got DP4 installed on the Redmi 5 Plus 3GB version. It does work and you can use it but there are some major problems and the rom is totally unusable.
- the launcher crashes constantly (pixel launcher isn't responding) so you lose your navigation and phone is unusable
- even when the launcher isn't crashed everything is so slow (20 seconds to open any app) and the pill switcher is 10 seconds to open
- no double tap to wake phone is a joke
- no fingerprint sensor at all
- no volte
- no camera
- google treble is full of bloatware that you are forced to download for the phone to work
- dark theme doesn't work on settings
All in all a total fail by google just like their new gmail interface, but well done to the developer who tried to port it.
Guys don't waste your time with this just install a normal custom rom.
If you must try it take a nandroid backup first and after restoring your nandroid backup there is a stupid bug in TWRP you have to use file manager to delete /data/system/locksettings.db to get back into your phone!
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=-oksFOzjR1o this guy was able to run it flawlessly. You must have done something wrong i guess.

---account closed

langster- said:
see how he doesn't open playstore, that is because the playstore patch is not installed installed yet.
once he installs the playstore patch it will turn into what i described.
i was very excited because of videos like that also, but no, i will reinstall just in case I did something wrong, but i highly doubt it.
Click to expand...
Click to collapse
maybe you are right but atleast i get a hope that our device will soon be running Android P.
another thing do u know why every developer has stopped working on Treble ROMS?

---account closed

I got it to work, and it is cery smooth for a port. My main issue is the wifi keep disconnecting and random freezes on the os. Other than that everything works as smooth as it should even the fingerprint.

---account closed

How To Make A Rom or "How To Backup" Your Installed Apps and Features, For Personal Use, Or Sharing~!

THIS IS OUTDATED
2015, 2017, & 2019 Nvidia Shield TV Firmware Repo & Source Code Repo
Normal Users seeking only Backup Stock Copies should use the Stock Recovery Images Below. AI Upscaling Works. Using the Developer Only Rooted (Full Read Write) Images will break AI upscaling [/SPOILER] [/SPOILER] [/SPOILER]...
forum.xda-developers.com
REPLACES THIS
===================================
How To Make A ROM.
==========================
=================
====​Here's the Source Code For The Three Roms I'm Releasing...
Spoiler: SOURCE CODE
Spoiler: RECOVERY, AKA STOCK ROM
RECOVERY.zip
drive.google.com
Run erase all partitions, then Recovery.bat
Spoiler: NVIDIA SHIELD STOCK ROM WITH ROOT
ROOT-ANDROID11.zip
drive.google.com
This includes the developer's partitions from Nvidia and all the tools needed to get root, I.E, TWRP, Magisk...
Run erase all partitions, Then Shieldroot.bat, then reboot into the bootloader, load twrp, and flash Magisk, etc
Spoiler: LINEAGE OS ROM
ROOT-LINEAGE.zip
drive.google.com
Run erase all partitions, Then Shieldroot.bat, then reboot into the bootloader, load twrp, and flash Magisk, etc
This includes everything as we Used in the Very first Rooting method, but with all files involved, updated.
Note that Lineage does Not support a lot of the functionality that Nvidia's Stock Rom does~!
But gives you more privacy, so to each their own~~!
===========================================
THIS Is an untested Lineage Micro-G build that operates under the theory, that if you have a booting shield, and you only want to use Lineage, you can boot into twrp and just flash lineage. The source code can be used in other similar methods for lineage, just replace the files.
LINEAGE MICRO-G.zip
drive.google.com
In order to maintain the project, you should ensure you have the latest images, for whatever build you are going for.
Check the sites listed below for any fresh uploads~!
Spoiler: NVIDIA IMAGES
Gameworks Download Center
Get the latest Gameworks software for your game development work.
developer.nvidia.com
You need to sign up for a developer account, and then using this link you will have access to Nvidia's latest Image Releases.
Spoiler: TWRP
Download TWRP for mdarcy
Download TWRP Open Recovery for mdarcy
dl.twrp.me
Spoiler: LINEAGE OS
LineageOS Downloads
download.lineageos.org
Spoiler: LINEAGE MICROG
mdarcy
Spoiler: GAPPS
The Open GApps Project
OpenGApps.org offers information and pre-built packages of The Open GApps Project. The Open GApps Project is an open-source effort to script the automatic generation of up-to-date Google Apps packages. All Android versions and platforms supported.
opengapps.org
Select ARM 64, your choice of android version, your choice of tv mini or the tv stock.
Spoiler: LIKE 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"
}
You would then Flash as Normal any images, Custom apps, Launcher etc to your system. Build your Rom with stuff you like.
MAKE SURE TO LOG OUT OF ALL ACCOUNTS ON THE DEVICE BEFORE SHARING OR SAVING ANYWHERE~!
The best way to protect yourself is to never login to any ROM you plan to share OR store for personal use on the Cloud or even on hardware... Learn how to flash your apps in the build process.....
When your build is complete, open TWRP and save your file.
Spoiler: LIKE THIS
Since TWRP is open you should have an Option for the shield posting in file manager
Spoiler: LIKE THIS
Which will make it easier to retrieve your new images with all your custom apps installed, to share to us~!
Spoiler: PLEASE NOTE
I will not be Actively releasing Updates On These Roms~!
These will Just be a resource for anyone willing to takeover~!
Please Feel Free To Use The Tools However You Choose~!
Start a hustle, maybe make a site for your roms, youtube channel, etc~!
You could even port These Tools to another version of Shield with the correct images and code adjustments.
If you Ever have a question, ask on here... I don't get my Youtube Comments for whatever reason~! ....Probably Karma ;-) but Anyway.. I will be More than Happy to Help~!
Love You Guys,
Jen
Spoiler: THE ORIGINAL THREAD AND METHOD
Root Nvidia Shield TV Pro 2019 Version
THIS IS OUTDATED https://forum.xda-developers.com/t/bootmod-root-your-shield-in-1-minute-2015-2017-2019.4524873/ REPLACES THIS IF YOU WANT ANDROID OR USE THIS GUIDE...
forum.xda-developers.com

All dls working~! Forgot to update this xD

Hey how can I Flash the img file to my Nvidia Shield Tv 2019 PRO?

Jacob Lundin said:
Hey how can I Flash the img file to my Nvidia Shield Tv 2019 PRO?
Click to expand...
Click to collapse
You would run the erase all partitions batch file, then run the recovery batch file, the recovery file flashes the partitions over for you. I have not tested these yet, these are the stock images provided from nvidia, and well, their quality control is questionable to me as far as maintaining their drivers and providing all the partitions needed

So I just do the same step as in your root tutorial but I run those 2 instead?

Jacob Lundin said:
So I just do the same step as in your root tutorial but I run those 2 instead?
Click to expand...
Click to collapse
Correct, so, just go into fastboot mode on the shield like at the very beginning, then you should be able to run the wipe first to remove the root, then recovery.bat, if you have any trouble, you can right click the batch file, select "edit" then you can see the code used. So you could type cmd into the Recovery folder's toolbar to open a command prompt there and paste individually to see if it fails anywhere. I included the code to relock the bootloader if anyone needs it for refurb or return purposes

But how do I run a img file like the TWRP 3.60 img file? And the reason why I want to remove the root is because my Bluetooth headphones connected to the TV makes YouTube and Disney Plus don't want to load YouTube only buffering and like the same thing with Diseny Plus

Jacob Lundin said:
But how do I run a img file like the TWRP 3.60 img file? And the reason why I want to remove the root is because my Bluetooth headphones connected to the TV makes YouTube and Disney Plus don't want to load YouTube only buffering and like the same thing with Diseny Plus
Click to expand...
Click to collapse
you would run the command: fastboot boot the.img file name
so if it was twrp.img
type fastboot boot twrp.img and it will boot in team win

I don't know how to run a command sorry for that

This is one other problem I got after root

Jacob Lundin said:
This is one other problem I got after root
Click to expand...
Click to collapse
It does that to me when I remove and readd the hdmi. But yeah, the original method I taught people used lineage and that image is old, they do nightlies. I think using the rooted stock image would be better but again the stupid drivers are limiting me :/
Very Nice setup BTW

Yea is my parents tv in the living room my dad fixed the setup

So if I use the Android 11 Stock Root files and try again?

Jacob Lundin said:
So if I use the Android 11 Stock Root files and try again?
Click to expand...
Click to collapse
If you would like to keep your root, I would advise giving those files a try. NVIDIA just updated them like 3 or 4 days ago, so they may actually work correctly this time, and just skip the TWRP this time, I put NVIDIA's recovery and boot image in there that should supposedly be rooted already, meaning when you flash, reboot, then run the system, in theory, you should have your shield back to stock, except now you should be able to install magisk without trouble by whatever method you choose

And have you have the same problem with Bluetooth headphones connected to the device if you have tried?

Jacob Lundin said:
And have you have the same problem with Bluetooth headphones connected to the device if you have tried?
Click to expand...
Click to collapse
I haven't tried, but I would imagine the complications come from the method we used to root last time. Last time we used twrp to flash a new operating system. So instead of Using Android 11 like NVIDIA does stock, we used Lineage OS, which does not have the same apps, build.prop, etc as those that come with NVIDIA'S Android OS. So, if NVIDIA did Their job in properly sharing these rooted images, then yes your bluetooth should work as it did originally and that should also fix the AI Upscaling issue for those who asked about that in the past

So this time, you should only have to wipe, then flash the files, no TWRP is required

So all I need to do is to have root on a stock OS the Android 11 file and I basically can install root apps? And try the problems again? And how do I check for root then with Android 11?

Jacob Lundin said:
So all I need to do is to have root on a stock OS the Android 11 file and I basically can install root apps? And try the problems again? And how do I check for root then with Android 11?
Click to expand...
Click to collapse
For this model of shield, yes, all you gotta do is use the "dev rooted" stock images from nvidia, the ones I included in the Android 11 Root Stock Image: https://drive.google.com/file/d/1BxehjouEO0vw1EhMv5QN8k8nKEy63TI-/view?usp=sharing
The easiest way to check for root is with an app that requires it. For instance I use an app called "root explorer" and it will tell you whether or not you are rooted usually on boot.

How do I Flash the Stock Image? I understand how I do EraseAllPartition and Recovery bat but I'm not that good with flash image from computer with fastest and I should pick EraseAllPartition first? And should I uninstall the Android Bootloader interface?

Question Keeping Stock Camera App, Throwing out Google Analytics (boot.img, Magisk, Debloater?)

Hello community,
I have no programming experience whatsoever but I am interested in having my Oneplus 9 Pro degoogled because I value my privacy.
Installing a Custom ROM is not an option yet because I don't seem to have found a Camera app that is as satisfying as the stock one (I especially like its Pro mode).
My friend suggested installing Magisk and Debloater, delete all Google services and stay with the Stock rom. So I unlocked the bootloader, booted into fastboot, booted TWRP. I flashed an official firmware Update (Oxygen OS 11.2.10.10.LE15AA), it loaded up to 47% and then showed an Error. I pushed some buttons until I was stuck in a Fastboot-Loop. Luckily I soon found a thread and tried out "fastboot --set-active=b" which solved the issue by booting into Oxygen OS 11.2.10.10.
I would like to understand what happened - I guess I tried to flash an update that was not full and somehow got mixed up with the slots, but the Update was installed anyway on the other slot which I was able to access with changing active slots - but I don't really know.
Anyway, what I really like to know is if anyone has any suggestions for me how to move on from here.
I downloaded the Magisk App but wasn't able to install it properly as I wasn't able to extract the boot.img. I tried with Python 3.8 and payload dumper on my Mac but the command "pip install -r requirements.txt" doesn't work (neither does python -m pip install -r requirements.txt or putting ./ in front of it - it always answers with "no such file or directory").
I also couldn't flash it with TWRP as I don't have the zip file and I heard conflicting opinions about that confused me.
Can somebody help me with a guide for dummies? Or maybe even come up with a different solution for my need to access the Stock Camera App but not having Google Tracking involved in any of my phone activities.
Thank you, this will be highly appreciated!

lai.sha said:
Hello community,
I have no programming experience whatsoever but I am interested in having my Oneplus 9 Pro degoogled because I value my privacy.
Installing a Custom ROM is not an option yet because I don't seem to have found a Camera app that is as satisfying as the stock one (I especially like its Pro mode).
My friend suggested installing Magisk and Debloater, delete all Google services and stay with the Stock rom. So I unlocked the bootloader, booted into fastboot, booted TWRP. I flashed an official firmware Update (Oxygen OS 11.2.10.10.LE15AA), it loaded up to 47% and then showed an Error. I pushed some buttons until I was stuck in a Fastboot-Loop. Luckily I soon found a thread and tried out "fastboot --set-active=b" which solved the issue by booting into Oxygen OS 11.2.10.10.
I would like to understand what happened - I guess I tried to flash an update that was not full and somehow got mixed up with the slots, but the Update was installed anyway on the other slot which I was able to access with changing active slots - but I don't really know.
Anyway, what I really like to know is if anyone has any suggestions for me how to move on from here.
I downloaded the Magisk App but wasn't able to install it properly as I wasn't able to extract the boot.img. I tried with Python 3.8 and payload dumper on my Mac but the command "pip install -r requirements.txt" doesn't work (neither does python -m pip install -r requirements.txt or putting ./ in front of it - it always answers with "no such file or directory").
I also couldn't flash it with TWRP as I don't have the zip file and I heard conflicting opinions about that confused me.
Can somebody help me with a guide for dummies? Or maybe even come up with a different solution for my need to access the Stock Camera App but not having Google Tracking involved in any of my phone activities.
Thank you, this will be highly appreciated!
Click to expand...
Click to collapse
Never mind - I just found it here: https://forum.xda-developers.com/t/guide-magisk-unlock-root-keep-root-oos-12-c-65.4252373/
I'm stil open for better solutions if someone has them!

Hey there!
Loading up to 47% and then throwing an error is actually quite normal, it should still succeed.
Anyway, some intelligent person was able to manage to move the stock OOS cam to custom ROM's. I'm currently running Nameless which is Android 12 which has the OOS cam.
Since you asked for a non-gapps build, you should look for a 'pristine' or 'vanilla' build. I know out of the top of my head that StagOS has builds like this, but you can also search the forums yourself. If the title of the ROM says [OOS Cam] then the stock camera app is included.
You can also use ADB to debloat (remove) all google stuff from your phone. This is a guide which could be helpful: https://forum.xda-developers.com/t/...bloating-thread-for-the-s20-u-series.4089089/
This way, you can keep the same stock software without having to go through the hassle of installing a custom ROM

GolovaRaoul said:
Hey there!
Loading up to 47% and then throwing an error is actually quite normal, it should still succeed.
Click to expand...
Click to collapse
Oh thank you, that is very satisfying to know. Why is that?
GolovaRaoul said:
Anyway, some intelligent person was able to manage to move the stock OOS cam to custom ROM's. I'm currently running Nameless which is Android 12 which has the OOS cam.
Click to expand...
Click to collapse
Are you thinking of this one: https://forum.xda-developers.com/t/apk-oneplus-camera-for-any-a11-custom-rom.4350205/ That's the 7 Pro App, which is crashing on my friend's phone on Lineage OS in macro mode
GolovaRaoul said:
Since you asked for a non-gapps build, you should look for a 'pristine' or 'vanilla' build. I know out of the top of my head that StagOS has builds like this, but you can also search the forums yourself. If the title of the ROM says [OOS Cam] then the stock camera app is included.
You can also use ADB to debloat (remove) all google stuff from your phone. This is a guide which could be helpful: https://forum.xda-developers.com/t/...bloating-thread-for-the-s20-u-series.4089089/
Click to expand...
Click to collapse
Great, thank you! As I got Magisk running, I prefer the debloater as I can play with it without Laptop access
GolovaRaoul said:
This way, you can keep the same stock software without having to go through the hassle of installing a custom ROM
Click to expand...
Click to collapse
Thank you for all your help!

lai.sha said:
Oh thank you, that is very satisfying to know. Why is that?
Are you thinking of this one: https://forum.xda-developers.com/t/apk-oneplus-camera-for-any-a11-custom-rom.4350205/ That's the 7 Pro App, which is crashing on my friend's phone on Lineage OS in macro mode
Great, thank you! As I got Magisk running, I prefer the debloater as I can play with it without Laptop access
Thank you for all your help!
Click to expand...
Click to collapse
Eeehm I don't know why it gets stuck at 47%. It's a common issue, you can google it and you'll find lots of results
{
"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"
}
And I mean these ROM's for example. Maybe some of these ROMs in the list also have the OxygenOS cam but I don't know. They are pre-built into the ROM so you don't need to do anything, just install the ROM and you should have the OxygenOS cam also

GolovaRaoul said:
Eeehm I don't know why it gets stuck at 47%. It's a common issue, you can google it and you'll find lots of results
View attachment 5742135
And I mean these ROM's for example. Maybe some of these ROMs in the list also have the OxygenOS cam but I don't know. They are pre-built into the ROM so you don't need to do anything, just install the ROM and you should have the OxygenOS cam also
Click to expand...
Click to collapse
Interesting, I thought that maybe that's what you meant but I wasn't sure if it just means "compatible" with...
Thank you so much, I guess it's time to play