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

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

Related

Shield TV 2015 (full) OTA 5.02 zip file (NON-PRO) uploaded on MEGA

Shield TV 2015 (NON-PRO) Nougat update version 5.02 is live.
OTA is downloaded to the usual folder: /data/data/com.nvidia.ota/app_download
Filename: PUBLIC02360be7475c0283d8953276654991ff.zip
size: 1.03 GB (1,115,129,317 bytes)
https://mega.nz/#!1VoVSbrR!s4XbFCGF6QSilIL6TBHg-DBU1ogMgOwXVofELfLxBro
I wonder if we can expect this One to land on Launch Day? Which would/should be on 20170130.
@sammarbella
I think you have posted a wrong zip, first the size is not 1.03 gb and secondly it looks like is v5.0 instead 5.0.2
Thanks! Can anyone please post the flash instruction for this update?
xanthrax said:
@sammarbella
I think you have posted a wrong zip, first the size is not 1.03 gb and secondly it looks like is v5.0 instead 5.0.2
Click to expand...
Click to collapse
Nothing wrong was posted.
It's the 5.02 (full) OTA zip file for Shield TV 2015 16 gb version, the posted size is once downloaded.
Copied from my Shield TV 2015 yesterday after it was downloaded by the OS software update service.
There is no such "5.0" for Shield TV 2015 16 gb version, the first one is this one: 5.02.
Ok, I'll check again later today, I've flashed it and I have checked the version and it was 5.0... maybe I didn't see properly
Sent from my Darkside of Oneplus 3T
xanthrax said:
Ok, I'll check again later today, I've flashed it and I have checked the version and it was 5.0... maybe I didn't see properly
Click to expand...
Click to collapse
...Or maybe Nvidia devs and Nvidia reps are not in sync in relation to OS upgrades nomenclatures.
https://forums.geforce.com/default/...grade-5-0-2-feedback-thread-for-shield-2015-/
sammarbella said:
...Or maybe Nvidia devs and Nvidia reps are not in sync in relation to OS upgrades nomenclatures.
https://forums.geforce.com/default/...grade-5-0-2-feedback-thread-for-shield-2015-/
Click to expand...
Click to collapse
Would you mind to check your update version shown on your device? This is mine after flashing your zip, do to root and maybe other twrp reasons I couldn't update it ota
{
"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"
}
Sent from my Darkside of Oneplus 3T
xanthrax said:
Would you mind to check your update version shown on your device? This is mine after flashing your zip, do to root and maybe other twrp reasons I couldn't update it ota
Click to expand...
Click to collapse
Who said that i already upgraded to Nougat?
I uploaded to MEGA the OTA file i got yesterday in my Shield TV 2015 16 GB but i didn't upgraded yet.
I'm not in a hurry to upgrade until i'm completely sure that i can update the old TWRP i have right now with the new hacked one and flash OTA and flash supersu from it without problems.
As i posted in my previous post a Nvidia rep made a sticky post announcing on Nvidia Geforce forums that the Shield TV 2015 (FINALLY) got the Nougat upgrade and labelled it 5.02 OTA upgrade and that upgrade is the one i posted.
This 5.02 OTA upgrade is pressumed to have the same fixes already added to 5.01 and 5.02 OTA fixes released for Shield TV 2017 version and therefore the proper number should be 5.02 and not 5.00 even on Shield TV 2015 16 GB.
If some Nvidia dev forgot to name the 2015 OTA properly as 5.02 (or 5.0.2) i can't help...
Hopefully for the Shield TV 2015 owners the Shield TV 2017 owners were the betatesters (5.00 and 5.01) and early adopters can skip 2 OTA versions bugs and get directly the 5.02 OTA version.
Great, many thanks!
I converted the contents to system.img and vendor.img.
This is in build.prop:
ro.build.display.id=NRD90M.1915764_835.9903
ro.build.version.incremental=1915764_835.9903
ro.build.version.sdk=24
ro.build.version.release=7.0
ro.build.date=Sun Jan 22 04:42:16 PST 2017
ro.build.version.ota=5.0(24.28.401.110)
Click to expand...
Click to collapse
So it is android 7.
I woke up this afternoon and i see this nice advice when i tried to watch some TV:
I checked then the downloaded OTA zip file and it's exactly the same name and size that i already uploaded to MEGA:
1,115,129,317 bytes
It's funny different file managers report the exact same size in bytes: 1,115,129,317 bytes but one (X-plore) say it's 1.04 GB and the other (Directory Opus) 1.03 GB:
Nvidia loves you apparently ...hmmm ... grab it and put it up in the cloud lol
xanthrax said:
Nvidia loves you apparently ...hmmm ... grab it and put it up in the cloud lol
Click to expand...
Click to collapse
LOL
I don't care if the installer says "5.0.2" and the about say "5.0" after install for my Shield TV 2015 IF we are getting the 5.01 and 5.02 bugfixes already added to Shield TV 2017 third Nougat OS version.
true ... actually the update is running fine so far , no problems founded , cheers pal !
Does anyone know if it's possible to flash this via Fastboot? I tried to downgrade a 2015 Shield TV from 5.0 to 3.3 to get DRM working again for the HDHomeRun Green app, and it won't boot now. I can get to the Fastboot menu but that's it. Of course Nvidia hasn't posted the 5.0 image for the 2015 Shield yet so I'm kind of stuck right now.
Is the 2017 firmware the same firmware that is used on the 2015 model?
My 2015 model is prompting me to update to firmware 5.02. Although mine is rooted so I don't think I can just let it update. Maybe I will just download the one from the original post. I don't see the 5.02 version available to download from their website.
scope666 said:
Does anyone know if it's possible to flash this via Fastboot? I tried to downgrade a 2015 Shield TV from 5.0 to 3.3 to get DRM working again for the HDHomeRun Green app, and it won't boot now. I can get to the Fastboot menu but that's it. Of course Nvidia hasn't posted the 5.0 image for the 2015 Shield yet so I'm kind of stuck right now.
Click to expand...
Click to collapse
You don't need the 5.0.(2) OS image if you want to downgrade to 3.3, simply flash the available 3.3.0 OS image.
Maybe you'll need the stock recovery flashed before but it's also available:
https://developer.nvidia.com/gameworksdownload
TC93 said:
Is the 2017 firmware the same firmware that is used on the 2015 model?
My 2015 model is prompting me to update to firmware 5.02. Although mine is rooted so I don't think I can just let it update. Maybe I will just download the one from the original post. I don't see the 5.02 version available to download from their website.
Click to expand...
Click to collapse
This is the OTA 5.02 for Shield TV 2015 16 GB, Nvidia will post it on his website in a week (more or less) as Nvidia rep said me in the official thread:
ManuelGuzman said:
sammarbella said:
Any ETA for Shield TV 2015 5.0.2 image upload on https://developer.nvidia.com/gameworksdownload ?
Click to expand...
Click to collapse
Usually it is about a week after a software OTA update has been released.
Click to expand...
Click to collapse
https://forums.geforce.com/default/...thread-for-shield-2015-/post/5068094/#5068094
This is NOT the same firmware as 2017.
Don't try to flash this OTA file on a 2017 model it'll brick it.
sammarbella said:
You don't need the 5.0.(2) OS image if you want to downgrade to 3.3, simply flash the available 3.3.0 OS image.
Maybe you'll need the stock recovery flashed before but it's also available:
https://developer.nvidia.com/gameworksdownload
Click to expand...
Click to collapse
It won't boot after flashing the full 3.3 image set ... that's why I wanted to try 5.0 .... perhaps something changed going from "M" to "N" ... and its preventing the downgrade. See others with the issue here:
https://forums.geforce.com/default/...attempt-to-downgrade-firmware-to-3-3-failed-/
scope666 said:
It won't boot after flashing the full 3.3 image set ... that's why I wanted to try 5.0 .... perhaps something changed going from "M" to "N" ... and its preventing the downgrade
Click to expand...
Click to collapse
If you want to flash the 5.02 image you have it in the first post of this thread.

[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.

Billion Capture Plus

Billion Capture Plus
Flipkart phone with SD625
There's also a global version now for only 65€ that can be found via Chinese resellers which is a bargain.
According to 4pda the Bootloader seems unlocked since a user was alble to flash mido TWRP with no working touchscreen unfortunately.
The phone has been updated to Oreo with Camera2api enabled which makes Gcam ports work well
Unfortunately there no official downloadable firmware, unbrick guides or custom ROMs, which is surprising considering the great custom ROM community India has
Gcam with everything working except Slowmo:
*Works only on Android 7.1.2
https://f.celsoazevedo.com/file/gcamera/NoHex_MGC_6.1.021_xcam_5_beta20.apk
According to a user at 4pda forums mido TWRP can be flashed but there's no working touchscreen.
Since there's no way to find the Oreo update zip file we can't get the display driver yet
Be careful - unlocking the boot on this device leads to impossibility of OTA update to 8.1. (status 7 in recovery). Fought with this phone for almost a month, and no lucky chance to catch the update in "mid-air"(while it's being downloaded) or make the updater's apk to download the firmware in other place instead of data (owner: root). Still going for a vicious circle: we don't have root to pull the OTA update out of the phone to make a custom recovery... And we don't have TWRP to root it.
We didn't exactly flash mido TWRP, just booted it. Hardware buttons are working though, but again we don't have CWM.
Dance4Life said:
Be careful - unlocking the boot on this device leads to impossibility of OTA update to 8.1. (status 7 in recovery). Fought with this phone for almost a month, and no lucky chance to catch the update in "mid-air"(while it's being downloaded) or make the updater's apk to download the firmware in other place instead of data (owner: root). Still going for a vicious circle: we don't have root to pull the OTA update out of the phone to make a custom recovery... And we don't have TWRP to root it.
We didn't exactly flash mido TWRP, just booted it. Hardware buttons are working though, but again we don't have CWM.
Click to expand...
Click to collapse
I'm not Russian so I'm using Google translate to understand .
Should I upgrade to Oreo any downsides?
Can you upload the Google camera config files?
How can we make twrp work?
Isn't there any firmware dump tool for Qualcomm phones?
If we can get the stock boot.img we can have root without TWRP
Also has anyone tried flashing treble ROMs via fast boot?
Edit: Found this tutorial
What I wanna say is: Dumping the stock boot.img
Modify it with root via the Magisk app
Flash the modified boot.img in fast boot in order to have root
adaa1262 said:
I'm not Russian so I'm using Google translate to understand .
Should I upgrade to Oreo any downsides?
Can you upload the Google camera config files?
How can we make twrp work?
Isn't there any firmware dump tool for Qualcomm phones?
If we can get the stock boot.img we can have root without TWRP
Aldo has anyone tried flashing treble ROMs via fast boot?
Edit: Found this tutorial
Click to expand...
Click to collapse
Interesting tutorial, but the program in video saves files in unknown format. What do we do with them after we got dump?
1. Oreo update contains one little bug - it slightly interrupts the touchscreen's work. No noticeable in everyday usage, but still having its place. Can't attach the example 'çause I'm newbie here.
2. The only way to build up the TWRP is to get kernel source of stock rom (boot.img). The problem is that we can't pull it out of device - this partition is hidden under "root" privileges.
3. You can dump anything with ADB, but there is no way you see the most important partitions like data, system, boot, recovery and so on.
4. Nope, see second line;
5. No, because the chance to catch a brick (to get an empty device which won't load the system/recovery/adb/fastboot) is too high.
Dance4Life said:
Interesting tutorial, but the program in video saves files in unknown format. What do we do with them after we got dump?
1. Oreo update contains one little bug - it slightly interrupts the touchscreen's work. No noticeable in everyday usage, but still having its place. Can't attach the example 'çause I'm newbie here.
2. The only way to build up the TWRP is to get kernel source of stock rom (boot.img). The problem is that we can't pull it out of device - this partition is hidden under "root" privileges.
3. You can dump anything with ADB, but there is no way you see the most important partitions like data, system, boot, recovery and so on.
4. Nope, see second line;
5. No, because the chance to catch a brick (to get an empty device which won't load the system/recovery/adb/fastboot) is too high.
Click to expand...
Click to collapse
So is there another way ?
Have you discovered anything new?
Also as I said can you upload the Google camera config files?
You can upload them via a PC using the paper clip icon
Also how's the camera quality with Google camera?
adaa1262 said:
So is there another way ?
Have you discovered anything new?
Also as I said can you upload the Google camera config files?
Click to expand...
Click to collapse
So far we can't see another ways to get TWRP or root. Couple of configs (remove space in the end of links):
4pda.ru/forum/index.php?showtopic=944778&view=findpost&p=84721063
4pda.ru/forum/index.php?showtopic=944778&view=findpost&p=85797772
Google Camera works pretty fine, especially on 8.1. But the seventh droid has fancy photos too. Search for the gcam on the 4pda thread, there are some examples of Google Camera photos.
Dance4Life said:
So far we can't see another ways to get TWRP or root. Couple of configs (remove space in the end of links):
4pda.ru/forum/index.php?showtopic=944778&view=findpost&p=84721063
4pda.ru/forum/index.php?showtopic=944778&view=findpost&p=85797772
Google Camera works pretty fine, especially on 8.1. But the seventh droid has fancy photos too. Search for the gcam on the 4pda, there are some examples of Google Camera photos.
Click to expand...
Click to collapse
I don't have a 4pda account so I can't download them
adaa1262 said:
I don't have a 4pda account so I can't download them
Click to expand...
Click to collapse
And I don't have an ability to put them here çause I'm newbie
Dance4Life said:
And I don't have an ability to put them here çause I'm newbie
Click to expand...
Click to collapse
Can you mirror the files to gdrive or mega?
adaa1262 said:
Can you mirror the files to gdrive or mega?
Click to expand...
Click to collapse
Spaces should be removed from the end.
mega.nz/#!enRkXSy J
mega.nz/#!3jJgwIY B
Dance4Life said:
Spaces should be removed from the end.
mega.nz/#!enRkXSy J
mega.nz/#!3jJgwIY B
Click to expand...
Click to collapse
File no longer available
If i copy each it will say i neef a decrypt key
adaa1262 said:
File no longer available
If i copy each it will say i neef a decrypt key
Click to expand...
Click to collapse
So complicated... I have chosen the option "link without key". But here:
3hujYNerqEGcOlRaiaz5aXMM18FgiJcPGqTwVsOqkhw
VhdD7GPKLjFeTDvjcH2dW2b1knekeHkmPo6Hh11zSKM
XML Files for Gcam taken from 4pda forums
Thanks to @Dance4Life for uploading
Any Custom Recovery for Billion Capture Plus??
Is there any working Custom Recovery available for Billion Capture Plus (4GB+64GB model). I have tried some available recovery from TWRP and OrangeFox and it stuck in Boot screen where it just show "Billion logo and powered by Android". In this mode if I connect to my PC and using fastboot I can still access mobile and whatever I try to flash it is not working.
Any help in getting Custom Recovery or Original Bootloader so that I can use my mobile will be helpful for me.
itsKekC said:
Is there any working Custom Recovery available for Billion Capture Plus (4GB+64GB model). I have tried some available recovery from TWRP and OrangeFox and it stuck in Boot screen where it just show "Billion logo and powered by Android". In this mode if I connect to my PC and using fastboot I can still access mobile and whatever I try to flash it is not working.
Any help in getting Custom Recovery or Original Bootloader so that I can use my mobile will be helpful for me.
Click to expand...
Click to collapse
Dev on 4pda forums are still working on it
Anyone got enough language skills to translate some 4pda instructions into english? Ofc we got google translator, but personally I would feel more secure having those steps in english.
adaa1262 said:
XML Files for Gcam taken from 4pda forums
Thanks to @Dance4Life for uploading
Click to expand...
Click to collapse
File already gone?
Can someone please re-upload it?
UPDATE
Working Gcams for
Code:
Android 7.1.2
Install [URL="NoHex_MGC_6.1.021_xcam_5_beta20.apk"]http://https://f.celsoazevedo.com/file/gcamera/NoHex_MGC_6.1.021_xcam_5_beta20.apk[/URL]this apk
Download the NoHex_MGC_6.1.021_xcam_5_beta20. xml file from [URL="here"]http://mega.nz/#!enRkXSyJ[/URL] with this decryption key 3hujYNerqEGcOlRaiaz5aXMM18FgiJcPGqTwVsOqkhw
[I]Everything is working except slowmo[/I]
Code:
Android 8 Oreo
[URL="MGC_6.1.021_FINAL_V1a_A8.1+.apk"]http://https://androidfilehost.com/?fid=11410963190603855055[/URL]
How to apply config files to google camera
Open Google Camera and save a random config and get to /Gcam/config and paste the xml
Open Google Camera again and tap on the bottom between the shutter button 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"
}
Choose the xml and save

Geforce Experience Upgrade 9.0.0 [based on Android 11] [Recovery Images]

NVIDIA Recovery Images for all Gen ShieldTV consoles.
Need to be flashed with fasboot.
How to is provided on the nvidia gameworks download site,
just check the 8.2.3 versions, right side you find Instructions.
Mirrors:
ShieldTV 2015
ShieldTV Pro 2015
ShieldTV 2017
ShieldTV 2019 Tube (8GB)
ShieldTV Pro 2019 (16GB)
Happy flashing.
Thank You!!
Don't forget to erase your Partitions if on Lineage or a dev build.. Here is how:
A guide how to use the recovery images for anyone using the shield root tools:
All Codes Are In The Description Boxes
final version or rc?
Has anyone else attempted this flash? I got it booted after a fresh partition wipe, bc yesterday, the launcher kept crashing, however, even today it continues to crash. I can play around in settings and i'm sure a custom launcher would work fine, however I had someone who wanted to see the stock version early and this is erm, not quite right haa...
and what i mean by crash is it intermittently flashes black and then back into the launcher. no discernable pattern or guess as to why. going to continue to toy with it and try to update it...
---edit i jumped the gun, i think those flashes were updates
----so after flashing the system over, wait for the shield to post into the chromecast screensaver, dont mess with it, then it will be fine
Hi guys
I tried to update my 2019 non pro shield with the how-to nvidia page I found here : https://developer.download.nvidia.c...-To-Flash-Recovery-Image-shield-atv-2019.txt?
But this method fails saying E:\ FAILED TO MOUNT /SDCARD
What ami doing wrong ?
My shield is non rooted, vanilia from scratch
Thx if someone can help
Fre$h said:
Hi guys
I tried to update my 2019 non pro shield with the how-to nvidia page I found here : https://developer.download.nvidia.c...-To-Flash-Recovery-Image-shield-atv-2019.txt?
But this method fails saying E:\ FAILED TO MOUNT /SDCARD
What ami doing wrong ?
My shield is non rooted, vanilia from scratch
Thx if someone can help
Click to expand...
Click to collapse
I think My main question would Be, and forgive me, because I'm learning as I go, While Running Stock, are you able to post into TWRP, after unlocking the bootloader?
Like, through fastboot, theoretically you shouldn't have to install the developer images as i did in my examples,,, but if you could get TWRP recovery to post, while in stock, with a momentarily unlocked bootloader, you should be able to run the OEM unlock code, then flash the staging blob, as well as the new images...
i do not mean to disrespect NVIDIA... but if you read their flash codes...
you can tell their devs are much more proficient on linux,
which is a great trait~! but it doesnt translate well for windoz userz...
Does anyone know if it is possible to update to consumer release via OTA after flashing this developer release?
I'd like to install this developer release on my girlfriend's Shield TV 2017 now and once Nvidia releases the consumer release, would she be able to update it via OTA? She is not technically proficient to update it to the consumer release by herself using fastboot and ADB.
Shield Experience 9.0.0 is working perfectly. I don't know why USB devices take forever to load files on Android 11 and crashes MX Player? Anyone else having the same issue? It's a developmental image so having these bugs occur is what happens. Anyways I reverted back to 8.2.3 and my issue is now resolved
MIRROR for anyone who hate the google spying!
nv-recovery-image-shield-atv-2019-pro-9.0.0.zip - Shared with pCloud
Keep, share and access your files whenever you need from wherever you are. Create a free pCloud account and make your life easier.
e1.pcloud.link
OR
PandaFiles
Download File
pandafiles.com
Seems like this new update does not like Magisk.
FLashing Magisk.zip causes me to be stuck going into bootloader.
@ jenneh - Did your notepad not have the replace option?
{
"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"
}
If you can't get Plex Server up and running after installing this all, go here to sign up for the official hotfix from Nvidia or go here for the official hotfix from Plex.
LazorBlind said:
Seems like this new update does not like Magisk.
FLashing Magisk.zip causes me to be stuck going into bootloader.
Click to expand...
Click to collapse
NEVER MIND I LIED.
I tried to do the known working procedure from memory and missed a step, the method still works. Got latest update with root running row. Shame I had to do a factory reset while trying to figure things out but small sacrifices...
LazorBlind said:
NEVER MIND I LIED.
I tried to do the known working procedure from memory and missed a step, the method still works. Got latest update with root running row. Shame I had to do a factory reset while trying to figure things out but small sacrifices...
Click to expand...
Click to collapse
Thank you for sharing your experience, I have some issue... to prevent fragment external HDD I prefer ext4 fs and unfortunately the nvidia roms doesnt support at this time! So I install microg magisk module on LineageOS 17 but I encountered black screen! also I install official microG release: https://download.lineage.microg.org/mdarcy/lineage-17.1-20220110-microG-mdarcy.zip but I encountered black screen too!
see:
[RECOVERY] [OFFICIAL] TWRP for Shield Android TV
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven...
forum.xda-developers.com
I still only see the 8.2.3 recovery listed on the Nvidia website. I didn't sign in as a developer though. Where did you get version 9.0.0?
jolsowka said:
I still only see the 8.2.3 recovery listed on the Nvidia website. I didn't sign in as a developer though. Where did you get version 9.0.0?
Click to expand...
Click to collapse
It has been officially released. If you're not signed up as a developer or if the developer site doesn't work for you like it didn't for me, then your best bet is to lock bootloader (if it's unlocked), check for updates and then install the updates, then unlock the bootloader and add any/all of your modifications back.
Had issues bypassing Google login so jumped on the Lineage bandwagon. Is there anything worthwhile in 9.0 over 8.2.3?

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?

Categories

Resources