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: DIFFERENCES
The main difference between a dev root and a stock root will be the apps available in the playstore. With the Dev Root, adb works as Root outside of the shell. With stock root, right now adb cannot work as root outside of the shell, only adb shell su works.
Stock root allows stock apps like Disney + to operate, whereas the Dev rooted images cannot (natively) download Disney + and other apps that check for things like user models vs userdebug, etc... See the links at the bottom of the post for Stock root, or use the Dev rooted firmware if you Need a userdebug firmware.
Spoiler: FIRMWARE VERSIONS AND DOWNLOADS
Further information on what the mirrors are can be located here
Spoiler: 2019 16GB PRO
Spoiler: STOCK RECOVERY IMAGES
Spoiler: 9.0.0
DOWNLOAD (909M)
9.0.0.zip
drive.google.com
{
"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"
}
Spoiler: 8.2.3
DOWNLOAD (799M)
8.2.3-stock.zip
drive.google.com
Spoiler: 8.2.2
DOWNLOAD (800M)
8.2.2.zip
drive.google.com
Spoiler: 8.2.1
DOWNLOAD (797M)
8.2.1.zip
drive.google.com
Spoiler: 8.2.0
DOWNLOAD (814M)
8.2.0.zip
drive.google.com
Spoiler: 8.1.1
DOWNLOAD (770M)
8.1.1.zip
drive.google.com
Spoiler: 8.1.0
DOWNLOAD (756M)
8.1.0.zip
drive.google.com
Spoiler: DEVELOPER ONLY ROOT IMAGES
Spoiler: 9.0.0
DOWNLOAD (947M)
9.0.0.zip
drive.google.com
Spoiler: 8.2.3
DOWNLOAD (825M)
8.2.3.zip
drive.google.com
Spoiler: 8.2.2
DOWNLOAD (825M)
8.2.2.zip
drive.google.com
Spoiler: 8.2.1
DOWNLOAD (823M)
8.2.1.zip
drive.google.com
Spoiler: 8.2.0
DOWNLOAD (839M)
8.2.0.zip
drive.google.com
Spoiler: 8.1.1
DOWNLOAD
8.1.1.zip
drive.google.com
(795M)
Spoiler: 8.1.0
DOWNLOAD (795M)
8.1.0.zip
drive.google.com
Spoiler: 9.1 & 9.1.1 OTA FIRMWARE PACKAGES
For Me, and those that know what to do with these. They are not like the other firmwares
9.1 OTA PACKAGE (783M):
PUBLICf77c312b128b6bde79b389a322706382.zip
drive.google.com
9.1.1 OTA PACKAGE (783M)
PUBLIC18e513b8a32a039975ecfcfa316d8217.zip
drive.google.com
KNOWLEDGE:
Can be found here and here
Spoiler: 2017 16GB
Spoiler: STOCK RECOVERY IMAGES
Spoiler: 9.0.0
DOWNLOAD (1.1G):
9.0.0.zip
drive.google.com
Spoiler: 8.2.3
DOWNLOAD (1G):
8.2.3.zip
drive.google.com
Spoiler: 8.2.2
DOWNLOAD (1G):
8.2.2.zip
drive.google.com
Spoiler: 8.2.1
DOWNLOAD (1G):
8.2.1.zip
drive.google.com
Spoiler: DEVELOPER ONLY ROOT IMAGES
Spoiler: 9.0.0
DOWNLOAD (1.2G):
9.0.0.zip
drive.google.com
Spoiler: 8.2.3
DOWNLOAD (1.0G):
8.2.3.zip
drive.google.com
Spoiler: 8.2.2
DOWNLOAD (1.0G):
8.2.2.zip
drive.google.com
Spoiler: 8.2.1
DOWNLOAD (1.0G):
8.2.1.zip
drive.google.com
Spoiler: 8.0.1
DOWNLOAD (1.0G):
8.0.1.zip
drive.google.com
Spoiler: 9.1 & 9.1.1 OTA FIRMWARE PACKAGES
For Me, and those that know what to do with these. They are not like the other firmwares
9.1
PUBLICfd1e9f9188e7bd88cffbfae53e376fe2.zip
drive.google.com
9.1.1
PUBLICffdca8e754c68400eb333ee4fa37d8ae.zip
drive.google.com
KNOWLEDGE:
Can be found here and here
Spoiler: 2015 16 GB
Spoiler: STOCK RECOVERY IMAGES
Spoiler: 9.0.0
9.0.0-2015-STOCK.zip
drive.google.com
Spoiler: DEVELOPER ONLY ROOT IMAGES
Spoiler: 9.0.0
9.0.0-2015-DEV.zip
drive.google.com
Spoiler: PREREQUISITES
Spoiler: ADB
Here's a way to install adb quickly using powershell and chocolatey.
Open powershell as admin and type:
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!
Spoiler: UNLOCKED BOOTLOADER
To unlock your bootloader, enter the fastboot menu either by sending "adb reboot bootloader" or by pulling the power cord from your shield. Reattach the power cord.
Using either a wired Nvidia Shield Controller or a USB 3.0 keyboard, press and hold A+B until this screen comes up
Select Unlock Bootloader with your controller or keyboard
Spoiler: SHIELD USB DRIVER
DOWNLOAD (9M)
Shield Drivers.zip
drive.google.com
Attach a usb-c cable to your shield (use the port furthest from your hdmi cable) and connect the c end to your pc, then open device manager and right click on fastboot device
Spoiler: LOCK BOOTLOADER
WORKS FOR STOCK ONLY FIRMWARE RIGHT NOW
Remember to Lock your bootloader when you're done flashing your firmware if you want to use AI upscaling and other features. Just reboot into the bootloader, then select lock bootloader.
Spoiler: TWRP
For those that need:
TWRP.zip
drive.google.com
Spoiler: NVIDIA ANDROID FIRMWARE SOURCE CODE
Spoiler: 9.0.1 - ALL MODELS
nvidia-9.0.1.zip
drive.google.com
Spoiler: 9.0.0 - ALL MODELS
Nvidia-9.0.0.zip
drive.google.com
Spoiler: 8.2.3 - ALL MODELS
nvidia-8.2.3.zip
drive.google.com
SOURCE: https://developer.nvidia.com/shield-open-source
Instructions for downloading the repo yourself
Some limited knowledge regarding these open source shares
TO USE:
(WITH THE SHIELD IN THE BOOTLOADER MENU)SIMPLY RUN ERASE ALL PARTITIONS FILE, THEN SHIELD ROOT. REQUIRES ADB. SEE THE ADB PRE-REQS SPOILER FOR MORE INFO
SOURCE FOR SYSTEM IMAGES:
Gameworks Download Center
Get the latest Gameworks software for your game development work.
developer.nvidia.com
IF YOU WANT ROOT ON STOCK FIRMWARE, SEE THIS GUIDE:
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...
forum.xda-developers.com
IF YOU WANT LINEAGE OS, SEE THIS GUIDE:
How To Install Lineage OS on the 2019 Pro
Hello Friends! Today I wanted to re-write a guide for installing Lineage OS on the 2019 Pro. This guide will be more to the point and have only the needed tools. The version of lineage used is of the 17 variant. SOME NOTES: This is not a...
forum.xda-developers.com
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
A Very Special thank you to @Manzing for being a hero and taking the time to get the 9.1 boot image and OTA for the 2017 shield!!!
Spoiler: SHIELD SDK AND DOCUMENTATION
Something new I hadn't seen on gameworks before, an actual development link for the Shield. It includes an SDK for the Shield. For anyone interested.
Well it was probably already there and I probably already saw it but yeah.
NVIDIA SHIELD
Get the best Android development tools for NVIDIA SHIELD: the ultimate Android gaming family. The NVIDIA® SHIELD™ family of devices provide the most immersive Android gaming and media experience. They are built on the Android operating system - the most popular mobile OS in the world. Powered by...
developer.nvidia.com
There's also extensive documentation in gameworks
NVIDIA GameWorks Documentation
docs.nvidia.com
CODEWORKS:
CodeWorks-1R8-windows_b181.exe
drive.google.com
NVIDIA GameWorks Documentation
docs.nvidia.com
Hey ,i have problems locking the bootloader..
Unlocking and installing all above went fine, i choose the 8.2.3 version.
Using the fast boot menu, or adb, both say they locked the bootloader.. but when i go into the android settings, and go to AI upscaling, it still shows me that the bootloader is unlocked. I also CANT find disney plus in the store. means the loader is unlocked.
What can i do?"
@tarreltje You are able to flash back the recovery (Stock) images from gameworks.
I will download those now and add them to the OP, the images I originally shared are the Dev Images, so this is my bad.
The dev images are for people using magisk or twrp and that is likely what is still flagging the ai upscaler bc the build props and other files are different.
I will add the images you need and clarify the post and I will tag you when they have been added;
Sorry for the trouble~! But thank you for telling me about the problem
Spoiler: UPDATE
@tarreltje the upload has completed https://drive.google.com/file/d/18jKNMUBFY4JrXHYL0-njrSmc4rIWBy0X/view?usp=share_link is the 8.2.3 stock version Please let me know if you still encounter any issues. I will add that link and the others as they complete to the OP. Oh and unfortunately that requires unlocking the bootloader one more time to flash and then relocking but it should fix the problem
Looks like I missed a version as well, on the dev end 8.1.1 I'll get that added as well with everything likely being finished by tomorrow afternoon
Just tested this myself, with a relocked bootloader. Was able to turn AI upsccaling on, disney plus Does show in playstore on Stock I don't have a disney account to test playback or anything
Hey jenneh,
All is working fine now!! Locked bootloader, AI upscaling works, and as expected i could find the disney plus app again in the store!
Thnx for your time and effort!
All of the STOCK images have been uploaded and added to the OP along with the missing 8.1.1 dev image. The dev pack all in one has been repacked and reuploaded.
Wow thank you so much for this! Any plans to put up 9.1.1 dev now that it's stable?
Sage2050 said:
Wow thank you so much for this! Any plans to put up 9.1.1 dev now that it's stable?
Click to expand...
Click to collapse
Yes as soon as nvidia releases it on Gameworks I sure will. If its not done by the time I get bored enough and out of a few projects, I can probably pull the Firmware
an edit I was able to pull the firmware I just dont know what to do with it exactly yet.
Long time no talk, Jen! You rock, thank you for this! Care to elaborate on the magisk module for upscaling? I will immediately install it haha, I've waited years for something similar.
nooted1 said:
Long time no talk, Jen! You rock, thank you for this! Care to elaborate on the magisk module for upscaling? I will immediately install it haha, I've waited years for something similar.
Click to expand...
Click to collapse
Hi there Noot Noot! I'm not stuck in a fever dream this year I promise! Haha. Tbh I never tried this personally, I had read somewhere that this was possible using a magisk module but idk which or how. Ever since that day you messaged me about trying to figure out a work around I never stopped wondering.
Let me find that link
@nooted1 https://github.com/kdrag0n/safetynet-fix this is the addtional module that allowed some users to bypass. I am curious. I will look at it here in a couple hours when I get bored of reading this avb nonsense x.x
@nooted1 I think it worked? It is no longer saying "bootloader unlocked"
I had to use 9.0.0 dev version
jenneh said:
@nooted1 I think it worked? It is no longer saying "bootloader unlocked"
I had to use 9.0.0 dev version
View attachment 5768967
Click to expand...
Click to collapse
Ooo okay I'll give it a shot right now and let you know!
@nooted1 Thank You So Much for taking the Time! I really tried to just get you the answer but I could not figure out how to test it myself x.x could you share how you are able to test the upscaler when you are done? Do you just use a certain video of like 1080p or do you use an app? I just really want to understand the tech but I can't without even seeing it in action x.x
@jenneh I'm gonna DM you to see if you wanna be part of my Plex, you can use videos from that for testing.
I discovered today you can root the regular non-developer images and it boots without issues; I'm using Magisk Delta (https://huskydg.github.io/magisk-files/) combined with Displax's SafetyNet-Fix MOD v2.0 (https://github.com/Displax/safetynet-fix/releases) and the app YASNAC is reporting that I am totally passing SafetyNet. 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 @nooted1, for making the Shield Fun Again. Haha. This is super interesting, running root on stock. I had tried this on 8.2.3 and got bootlooped. I will check out magisk delta now and play with things. THANKS YOU now all I can think about is going home and trying to root 9.1 x x
Sage2050 said:
Wow thank you so much for this! Any plans to put up 9.1.1 dev now that it's stable?
Click to expand...
Click to collapse
Well thanks to Noot Noot, we are now able to patch the STOCK images. I was successful in Rooting the STOCK 9.1 image. I've installed Root Explorer, given it Super User Access, and when the 9.1.1 firmware is finishes downloading to the OTA folder, I will get it pulled, then Using Magisk Delta, I can patch the boot.img for 9.1.1 and then we should have full root on the latest stock images.
So a TLDR. 9.1.1 Root method is coming. Just being tested and then I can bundle things up and write something to make it easy for people learning
amazing!
YAYYYY It Worked! It Actually Worked! I'm so happy I could cry haha. Gosh. Why couldn't I understand this stuff a year ago?
I will start with the TLDR: We can achieve root on stock in two simple steps now!
1. Run a batch that will erase the original stock boot partition and flash the new modded one
2. Install Magisk Delta APK and Viola~!
3. Optional - Install Safetynet Module ---edit this did not work how i thought it did for the ai upscaler, this is only for APPS stock apps that you dont want to be root detected
A new guide will be made so this one doesn't get too convoluted. On it I will share modded boot.imgs for all the firmwares ready for flashing. As well as a full technical rundown for those that want to know how to do for themselves and give proper credits to our lovely xda community members who helped to figure this stuff out.
Small technical banter for anyone interested:
I was able to modify that boot.img I collected from the OTA update. Then to be absolutely sure it would work from scratch. I COMPLETELY erased my system, reflashed stock 9.0, manually upgraded to 9.1 , then to 9.1.1, then rebooted to the bootloader.
I erased the stock boot partition in fastboot, flashed the modded one, rebooted, and then you have to install the apk on top of the modded boot.img, bc with delta it comes in at version 1 same as the regular magisk, but for me it wouldn't update on it's own.
So I installed the apk which brought it up to 25.2 and after the reset I was able to install zygisk and verify root with root explorer.
One step closer I think to being able to just pull the system with everything preinstalled and or cleaned up / code tweaks / whatever. Idk but I'm gonna try to figure it out. Then we can make roms. Dang it. I want to make roms and I want the community to be able to make roms.
Good night x.x
Related
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
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?
{
"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"
}
LineageOS 19.1 for the Pixel 6 Pro (raven) and Pixel 6 (oriole).
While there is another build of LineageOS 19.1 on XDA for the P6P, it is unstable and has issues with incoming calls on T-Mobile US, so I built my own Lineage image which fortunately runs far better (sorry to brag, I don't mean to put down others).
Known issues:
Touch and hold does not work on screen edges of Pixel 6 Pro/raven, at least for me. This is a software issue, as other ROMs (stock and custom) work fine with touch-and-hold. I do not know if Pixel 6/oriole is affected, since I do not own one (anymore). UPDATE: The 20220808 build does not have this issue, yay!
Incoming calls with a T-Mobile US SIM coming from an iPhone on the same account and carrier may not work. If you have this issue, download the T-Mobile DIGITS app and enable it for your SIM line, this makes calls work (albeit by routing it over the internet versus VoLTE). This is not an issue with the ROM but rather my old P6P's modem, so crossing out.
Flashing via 'adb sideload' can be unreliable based on system. It could be your cable, but if not, it can also be some USB controllers play poorly with the Tensor SoC. My work laptop works well with flashing raviole on W11, but not my newer personal laptop on both W11 and Linux. If Windows/Mac/BSD doesn't work, try Linux via a USB and vice versa, or an older PC (or different Linux distro via LiveUSB) if you can use one.
Install instructions:
Spoiler: Install Instructions
Note: You need to be on the latest Android 12 firmware for your device before flashing this ROM.
Install the Android Platform Tools and Google USB Drivers if on Windows
Download your device's boot.img, vendor_boot.img and Lineage ZIP
In a terminal/command prompt, type in "fastboot flash boot boot.img"
In a terminal/command prompt, type in "fastboot flash vendor_boot vendor_boot.img"
Boot the recovery
Navigate to "Factory Reset" -> "Format data/Factory reset"
Navigate to the "Apply Update" -> "Apply from ADB"
In a terminal/command prompt, type in "adb sideload NAME_OF_LINEAGE_ZIP" (rename the bold part with the Lineage ZIP)
(Optional) If you want GApps and Magisk, navigate to "Advanced" -> "Reboot to recovery"
(Optional) Navigate to the "Apply Update" -> "Apply from ADB"
(Optional) In a terminal/command prompt, type in "adb sideload NAME_OF_ADDON_ZIP" (rename the bold part with the GApps/Magisk ZIP)
(Optional) Repeat steps 10 & 11 for each addon ZIP you want to flash
Go to "Reboot System Now"
Note: You need to flash both boot.img and vendor_boot.img from my image, otherwise your device won't be able to access recovery. These are provided in the AFH download.
Note about updates: You need to flash GApps when you update (if you installed it before first boot), and Magisk if used.
Download:
Pixel 6 Pro (raven)
Pixel 6 (oriole)
Kernel source: https://github.com/LineageOS/android_kernel_google_raviole (although this build uses a prebuilt kernel).
NOTE: This ROM is discontinued. I have an Android 13/LOS 20 build here: https://forum.xda-developers.com/t/...eos-19-1-for-the-pixel-6-pro-pixel-6.4475257/
This new build also supports the 6a.
ChangeLog:
9/5/2022:
I am no longer working on this ROM. Later Lineage builds don't boot even recovery on both raven and oriole. I am currently using stock A13.
If you want to flash this ROM and are using A13, flash the developer support build first and then flash thig.
I also "downgraded" to oriole, since raven was too big for my tastes.
8/8/2022:
Update to the LOS 8/8/2022 build for raven/oriole
While still unofficial, replace custom patches with now-committed LineageOS equivalents for GApps/cellular
Fix the touch-and-hold issue with the Pixel 6 Pro, along with other stability issues
8/1/2022:
Initial unofficial LineageOS 19.1 build for raven/oriole
Based on custom patches to enable GApps installation and cellular
Reserved 2.
Going to give this a try. You're syncing daily builds from LOS?
i42o said:
Going to give this a try. You're syncing daily builds from LOS?
Click to expand...
Click to collapse
More or less. I can't promise a build everyday but I can try my best to do it as frequently as possible.
neelchauhan said:
More or less. I can't promise a build everyday but I can try my best to do it as frequently as possible.
Click to expand...
Click to collapse
Fair enough. Thanks for the builds. Looking forward to your work.
So far so good. Definitely a better build than others available I installed the boot image as well as the vendor boot image and installed it seemed to have hanged for a little bit but give it time and patience and it will flash correctly reboot to bootloader and boot magisk patched boot image ( use the one provided , and patch via magisk before you actually flash ROM ) boot up, install magisk directly reboot, and flash bit gapps ( they are less intrusive than most gap packages ) works equally the same as regular gaps . Highly recommend. What won't work is ok Google and other Google proprietary apps...
i42o said:
So far so good. Definitely a better build than others available I installed the boot image as well as the vendor boot image and installed it seemed to have hanged for a little bit but give it time and patience and it will flash correctly reboot to bootloader and boot magisk patched boot image ( use the one provided , and patch via magisk before you actually flash ROM ) boot up, install magisk directly reboot, and flash bit gapps ( they are less intrusive than most gap packages ) works equally the same as regular gaps . Highly recommend. What won't work is ok Google and other Google proprietary apps...
Click to expand...
Click to collapse
Thanks for the kind words!
I am using MindTheGApps recommended by Lineage, and got many Google proprietary apps, even Google Pay working (provided I use Magisk), so probably is a BiTGApps problem. I also installed Magisk via the ZIP flash, but there's no one right way to install.
Not judging you, but I'm betting BiTGApps has some Google apps not working since it excludes many non-essential components. I'm no expert on GApps packages, sorry.
neelchauhan said:
Thanks for the kind words!
I am using MindTheGApps recommended by Lineage, and got many Google proprietary apps, even Google Pay working (provided I use Magisk), so probably is a BiTGApps problem. I also installed Magisk via the ZIP flash, but there's no one right way to install.
Not judging you, but I'm betting BiTGApps has some Google apps not working since it excludes many non-essential components. I'm no expert on GApps packages, sorry.
Click to expand...
Click to collapse
No, you're absolutely right. Battery life is thanking me though. I'll run this for a day and night mind the gapps later. Can you dm me your gapps link please
i42o said:
No, you're absolutely right. Battery life is thanking me though. I'll run this for a day and night mind the gapps later. Can you dm me your gapps link please
Click to expand...
Click to collapse
I'm using the ones off Lineage's wiki: https://wiki.lineageos.org/gapps
neelchauhan said:
I'm using the ones off Lineage's wiki: https://wiki.lineageos.org/gapps
Click to expand...
Click to collapse
Did app locker disappear after you flashed this gapps package? Also does call screen work for you
i42o said:
Did app locker disappear after you flashed this gapps package? Also does call screen work for you
Click to expand...
Click to collapse
App locker did not disappear for me, although I do not use that feature.
Call screen works fine for me, if I install the Google dialer (as opposed to the Lineage one).
neelchauhan said:
App locker did not disappear for me, although I do not use that feature.
Call screen works fine for me, if I install the Google dialer (as opposed to the Lineage one).
Click to expand...
Click to collapse
How do you access app locker?
i42o said:
How do you access app locker?
Click to expand...
Click to collapse
I don't know if it is the app locker you are looking for, but try:
Tap and hold anywhere on the screen except the edges
Press Home Settings
Press Hidden & Protected apps
Use your fingerprint/pin ID if necessary (as was for me)
You should be in the protected apps section
neelchauhan said:
I don't know if it is the app locker you are looking for, but try:
Tap and hold anywhere on the screen except the edges
Press Home Settings
Press Hidden & Protected apps
Use your fingerprint/pin ID if necessary (as was for me)
You should be in the protected apps section
Click to expand...
Click to collapse
Thank you. Found it
FOR ANYONE LOOKING TO FLASH A CUSTOM ROM THAT WORKS PERFECTLY FINE IT'S JUST LIKE STOCK VERY OPTIMIZED GREAT BATTERY LIFE USEFUL FEATURES MINIMALISTIC APPROACH TO AOSP I WOULD DEFINITELY RECOMMEND THAT YOU TRY THIS OPERATING SYSTEM IT IS THE BOMB.COM I HAVE TRIED SEVERAL DIFFERENT FORKS AND I CAN HONESTLY SAY THAT THIS IS THE SMOOTHEST THE MOST BATTERY FRIENDLY AND MINIMALISTIC ROM THAT I HAVE USED SINCE I FLASHED A CUSTOM OS ON MY PHONE AGAIN MINIMALISTIC APPROACH GREAT BATTERY LIFE USEFUL FEATURES AND IS BUILT VERY VERY SOLID UNLIKE OTHER BUILT OUT THERE
Would be adding 6a to the supported list be a hard task?
24ky said:
Would be adding 6a to the supported list be a hard task?
Click to expand...
Click to collapse
It is dependent on Lineage adding the 6a in their Gerrit. I just compiled the sources from Gerrit/GitHub. As of now, there is no 6a on the LOS source.
I have no access to a 6a, sorry.
Plz add step by step install method... Some beginners will be very appreciated also"the new" guys need to know that bootloader needs to be unlocked. And that the recovery means stock android recovery as for now there is no TWRP ?
meilbox said:
Plz add step by step install method... Some beginners will be very appreciated
Click to expand...
Click to collapse
To install,
Flash both boot.img and vendor_boot.img in fastboot
fastboot flash boot (boot.img location)
fastboot flash vendor_boot (vendor_boot.img location)
Reboot bootloader >> recovery mode >> apply update >> apply update adb ( sideload )
Once recovery is set for adb update you're going to go on command line and type
adb sideload ( lineage19.zip ) .... Wait until process reaches 47% and from there wait until process is complete ( usually within 5 minutes )
Reboot to recovery >> update >> adb sideload >> flash mind the gapps package >> reboot .
Done.
Finally got this sideloaded with an old 2XL cable. Type-c to type c 3.0 wasn't playing nice.
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features:
https://github.com/crdroidandroid/crdroid_features/blob/13.0/README.mkdn
Flashing Instructions:
Pre-installation:
Recovery (Download from here)
gapps (Download from here)
Magisk 25.0 or newer for root (after first boot) - (Download from here)
First time installation:
NOTE : Make sure you have the bootloader unlocked(This thread will not entertain bootloader unlock method/discussion on Docomo phones as officially its not allowed by SONY).
NOTE : If your bootloader is not unlocked, Please search on google and DO NOT POST THE QUESTIONS RELATED TO IT HERE.
Step 1 : Flash Stock ROM and boot into it atleast once.
Step 2 : Download the recovery from above link and flash it from fastboot.
fastboot flash boot boot.img
Step 3 : Now reboot into recovery to verify the installation.
With the device powered off, hold Volume Down + Power.
Step 4 : Download the CrDroid ROM(Link in second post).
Step 5 : Now tap Factory Reset, then Format data / factory reset and continue with the formatting process. This will remove encryption and delete all files stored in the internal storage, as well as format your cache partition (if you have one).
Step 6 : Return to the main menu.
Step 7 : Sideload the crDroid .zip package but do not reboot before you read/followed the rest of the instructions!
On the device, select “Apply Update”, then “Apply from ADB” to begin sideload.
On the host machine, sideload the package using: adb sideload filename.zip.
Step 8 : Installing add ons : Even though you are already in recovery, click Advanced, then Reboot to Recovery
When your device reboots, click Apply Update, then Apply from ADB, then adb sideload filename.zip for all desired packages in sequence.
Once you have installed everything successfully, you can now reboot your device into the OS for the first time!
Update installation:
step 1 : OTA is supported for upgrades montly.
step 2 : If you want manuall installation please refer to first time installation instructions.
step 3 : If OTA update fails, you can download the rom manually and apply update via updater app (Settings >> System > Updater >> Local update)
step 4 : Update via OTA or Local Update is recommended
Sources:
ROM: https://github.com/ShujathMohd
Kernel: https://github.com/ShujathMohd/android_kernel_sony_sdm845
Known issues:
Please test and report.
Visit official website @ crDroid.net
Changelog :
24-04-2023
Initial Release
Download : https://sourceforge.net/projects/so...roid-13.0-20230425-xz2c_dcm-v9.4.zip/download
Is it a ported/cooked ROM?
What's the difference between H8324 XZ2C and Docomo?
DrTrax said:
Is it a ported/cooked ROM?
What's the difference between H8324 XZ2C and Docomo?
Click to expand...
Click to collapse
Its built from source.
There are two major changes between Global and Docomo Variant.
1.) System parition size is different in both models.
Global variant have approx 4.2 GB
Docomo have approx 3.7 GB
2.) NFC Chip and drivers are different on both models.
Shujath said:
Its built from source.
There are two major changes between Global and Docomo Variant.
1.) System parition size is different in both models.
Global variant have approx 4.2 GB
Docomo have approx 3.7 GB
2.) NFC Chip and drivers are different on both models.
Click to expand...
Click to collapse
Uf... never had a chance to build a ROM like this... I'd like to try to "create" one for XZ2C since there are almost no other custom ROM there...
Although... I'm already trying to port OrangeFox recovery from akari to xz2c (first dirty mods works fine!)
Shujath said:
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features:
https://github.com/crdroidandroid/crdroid_features/blob/13.0/README.mkdn
Flashing Instructions:
Pre-installation:
Recovery (Download from here)
gapps (Download from here)
Magisk 25.0 or newer for root (after first boot) - (Download from here)
First time installation:
NOTE : Make sure you have the bootloader unlocked(This thread will not entertain bootloader unlock method/discussion on Docomo phones as officially its not allowed by SONY).
NOTE : If your bootloader is not unlocked, Please search on google and DO NOT POST THE QUESTIONS RELATED TO IT HERE.
Step 1 : Flash Stock ROM and boot into it atleast once.
Step 2 : Download the recovery from above link and flash it from fastboot.
fastboot flash boot boot.img
Step 3 : Now reboot into recovery to verify the installation.
With the device powered off, hold Volume Down + Power.
Step 4 : Download the CrDroid ROM(Link in second post).
Step 5 : Now tap Factory Reset, then Format data / factory reset and continue with the formatting process. This will remove encryption and delete all files stored in the internal storage, as well as format your cache partition (if you have one).
Step 6 : Return to the main menu.
Step 7 : Sideload the crDroid .zip package but do not reboot before you read/followed the rest of the instructions!
On the device, select “Apply Update”, then “Apply from ADB” to begin sideload.
On the host machine, sideload the package using: adb sideload filename.zip.
Step 8 : Installing add ons : Even though you are already in recovery, click Advanced, then Reboot to Recovery
When your device reboots, click Apply Update, then Apply from ADB, then adb sideload filename.zip for all desired packages in sequence.
Once you have installed everything successfully, you can now reboot your device into the OS for the first time!
Update installation:
step 1 : OTA is supported for upgrades montly.
step 2 : If you want manuall installation please refer to first time installation instructions.
step 3 : If OTA update fails, you can download the rom manually and apply update via updater app (Settings >> System > Updater >> Local update)
step 4 : Update via OTA or Local Update is recommended
Sources:
ROM: https://github.com/ShujathMohd
Kernel: https://github.com/ShujathMohd/android_kernel_sony_sdm845
Known issues:
Please test and report.
Visit official website @ crDroid.net
Click to expand...
Click to collapse
Good job sir, rom is very smooth, and no bug. This my new daily driver rom. Thank you.
DrTrax said:
Uf... never had a chance to build a ROM like this... I'd like to try to "create" one for XZ2C since there are almost no other custom ROM there...
Although... I'm already trying to port OrangeFox recovery from akari to xz2c (first dirty mods works fine!)
Click to expand...
Click to collapse
I will build xz2c Global this weekend.
Shujath said:
I will build xz2c Global this weekend.
Click to expand...
Click to collapse
OMG Thank you very much ♥ BTW I found once an AICP ROM version 8.4 for XZ2C... Do you want that too for comparison if there are any troubles?
So far, the only issue is netflix playback specification, DRM widevine: L3, max playback resolution is only SD. I have tried crdroid feature, spoof netflix, but no luck. Any solution for this?
avatarwan13 said:
So far, the only issue is netflix playback specification, DRM widevine: L3, max playback resolution is only SD. I have tried crdroid feature, spoof netflix, but no luck. Any solution for this?
Click to expand...
Click to collapse
you loose DRM once you unlock the bootloader,
I don't think there is a way to get widevine L1 back on unlocked bootloader
Thanks for making this. I had Docomo device and this is the only flash-able ROM at the moment.
If possible, may I request a brightness slider on statusbar? Not on quick settings. Its where you just slide anywhere on the statusbar to control the phone brightness. I miss this feature.
Also, whenever I pull down the quick settings, it feels quite jerky/lagging. Is it just me?
I only have like 5 tiles.
Shujath said:
you loose DRM once you unlock the bootloader,
I don't think there is a way to get widevine L1 back on unlocked bootloader
Click to expand...
Click to collapse
My xiaomi 11T pro's bootloader is unlocked (currently using evolution-x rom) and no problem with DRM, playback resolution is full hd.
avatarwan13 said:
My xiaomi 11T pro's bootloader is unlocked (currently using evolution-x rom) and no problem with DRM, playback resolution is full hd.
Click to expand...
Click to collapse
Xiaomi&Redmi is one of the only vendors that still gives you Widevine L1 even after BLU. Not gonna happen here on Xperia phones.
Hello,
I would like to know, if the known Front micriphone Software issue is fixed in this OS Form?
Thanks. EW
Thanks for your awesome work!To my surprise, the touching bug that has been bothering me for long seemed to has disappeared after burning this ROM.
Excellent ROM! Thank you so much for making this, I can now finally actually Use my XZ2 Compact.
One small problem - and it might just be me, but I can't seem to get 4G connectivity, only 3G/H+. I checked the bands this device has and I should be able to get a 4G connection with the provider I use in Australia but no luck. Not a big deal right now as 3G hasn't been shutdown here (yet) but just wanted to see if anyone else who uses this ROM has the same issue.
EdgarWollust said:
Hello,
I would like to know, if the known Front micriphone Software issue is fixed in this OS Form?
Thanks. EW
Click to expand...
Click to collapse
Please explain the issue, I dont have any issues with the microphone.
drychemical said:
Excellent ROM! Thank you so much for making this, I can now finally actually Use my XZ2 Compact.
One small problem - and it might just be me, but I can't seem to get 4G connectivity, only 3G/H+. I checked the bands this device has and I should be able to get a 4G connection with the provider I use in Australia but no luck. Not a big deal right now as 3G hasn't been shutdown here (yet) but just wanted to see if anyone else who uses this ROM has the same issue.
Click to expand...
Click to collapse
Does 4g works for you on stock rom?
Also did you try to set 4g/LTE manually in the settings?
Shujath said:
Please explain the issue, I dont have any issues with the microphone.
Does 4g works for you on stock rom?
Also did you try to set 4g/LTE manually in the settings?
Click to expand...
Click to collapse
Yeah I did try manually adding an APN (if that's what you were meaning) but yeah no luck.
I'll see if the SIM works on the stock ROM when I have more time.
Hi,
I thaught this issue is well known, but maybe im missinformed.
I already got the Phone opened an put a New bottommicrophone in, but still its not working while be in a call. (like discribed here https://forum.xda-developers.com/t/microphone-and-speaker-problems.4100053/)
Thanks a lot.
unable to enter into fastboot mode. Getting this error as in the image
is there any other method to install recovery or flashing this rom. BTW im noob in Flashing and this custom rom thing.
{
"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"
}
{
"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"
}
A couple of days ago my mom gave me this phone. So, i want a new Android (and kick the s**t out all the bloatware of Samsung). After several tries, i make TrebleDroid vanilla works. And really good! Hell, even shows dual sims!
...And since there's no trace of someone doing this (or a guide), here are the steps. It was trial and error but i did it and it worked. (Sorry for english, i'm a native spanish speaker):
On original firmware:
- Activate OEM unlock in Developer Options
- Enable USB debugging
This is the version I used for Android 13 (at the moment, system-td-arm64-ab-vndklite-vanilla.img.xz from ci-20230510)
Releases · TrebleDroid/treble_experimentations
Scripts to automatically build/CI/Release TrebleDroid GSI - TrebleDroid/treble_experimentations
github.com
Vendor-Quack is required for SaR.
[SAR][Vendor][10][A530F/A530W/A730F] Vendor Quack V2.5 For Galaxy A8/A8+ 2018
Dude did you tried to enable magisk hide from settings? That should pass safety net on all Android 10+ roms :) Hey, i'm succesfully flashed magisk 21.1 beta version with safety net passed on Android R
forum.xda-developers.com
Vendor-Quack_V2.6
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
To load TWRP and change the system to Treble-compatible, instructions here. Download TWRP-jackpot2lte-Treble.img and TrebleCreator-A730F.zip
[GUIDE][TREBLE][A730F] Project Treble Guide for Galaxy A8+ 2018 (18/04/2019)
Project Treble Guide for Samsung Galaxy A8+ Just to make it clear I'm not responsible for whatever damage this could possibly cause to your device. Treble is everywhere, so why shouldn't we join it? I'm proud to announce that Galaxy A8+...
forum.xda-developers.com
ONCE TWRP IS LOADED, THE PHONE SHOULD NOT BE RESTARTED OR IT WILL BE OEM LOCK AND YOU WILL HAVE TO INSTALL THE ORIGINAL FW AND DO THE TRICK TO ELIMINATE THE KG-RMM STATUS:
[GUIDE][17.06.2019] RMM/KG bypass - Root/Install TWRP on Exynos Samsung after 2018
UPDATE 17.06.2019 - NEW RMM/KG bypass patch UPDATE 23.02.2019 - Pie and more Please take some time and read carefully the whole post. I am not and i won`t be responsable for anything. Disclaimer I am not responsible for bricked devices, dead...
forum.xda-developers.com
download patch:
https://forum.xda-developers.com/attachments/rmm_bypass_v3_corsicanu-zip.4778435/
YOU MUST LOAD THE PATCH.
In my case to not wait 7 days:
RMM a730f
I commented my experience on my a730f with bit 4, 1.- After flash rom, select a manual date 10 days before the current date. 2.- remove the automatic update option, and select manual download, then restart. 3.- Verify that the phone shows the...
forum.xda-developers.com
1.- After flashing OEM rom, select a manual date 10 days before the current date of the phone.
2.- remove the automatic update option, and select manual download, then restart. Check that developer options is disable.
3.- enter google and samsung account on the phone.
4.- wait 3 hours (in my case, less. 1 hour), enable developer options and there will be the OEM unlock enabled.
With ODIN load TWRP-jackpot2lte-Treble.img (it's version 3.2.3 - 3.3.0 didn't give me good results)
All of the following steps refer to TWRP:
- After installing TWRP without entering the rom, /data must be formatted. After that, reboot into recovery mode using the reboot menu. If /data is not formatted, the partitions will remain encrypted and the rest cannot be wiped.
-------------------------------------------------- -----------------------
From now on, every time you make a change, you must reboot, because without this step, loading anything via TWRP will fail (if you didn't reboot, the rom will not start or froze, or the zip will not load correctly, or you'll see partition access errors on the log). ALL STEPS MUST BE FOLLOWED OR THE SYSTEM WILL REMAIN ON THE ANDROID LOADING SCREEN FOREVER.
-------------------------------------------------- -----------------------
- After reboot, Wipe in /cache,/vendor (if it exists. Otherwise it will be created later),/system,/data,/dalvik. Reboot into recovery mode using the reboot menu.
- Load TrebleCreator-A730F.zip. It will create the partitions for treble. It has an automatic reboot. After the reboot it should show the script and then reboot again and go back to TWRP. If the automatic reboot does not happen and the script screen doesn't show up, you will have to start again from the /data format step. It is vital since the automatic reboot and script screen indicates that the partitions were all correctly loaded.
- Load RMM_Bypass_v3_corsicanu.zip. This is to bypass the OEM lock. It should be done before Vendor-Quack, as the vendor zip encrypts the /vendor partition and makes it inaccessible. Reboot into recovery mode using the reboot menu.
- Load Vendor-Quack_V2.6.zip. Reboot into recovery mode using the reboot menu.
- Finally, the .img of Android 13. One last reboot to recovery and THEN reboot to system.
After this the rom should start without problems. TWRP builds with treble are now LOCKED once booted. When trying to enter recovery, they get frozen at the TWRP boot screen. In order to load gapps, you must load the "latest" version of TWRP (in quotes because TWRP version 3.7.0 does not load since it is larger than the /boot partition. In this case, you must load 3.6.2 ) using Odin and Download mode.
Download TWRP for jackpot2lte
Download TWRP Open Recovery for jackpot2lte
dl.twrp.me
Once the latest version of TWRP is loaded, the zips can be loaded without problems. IN THIS VERSION OF TWRP IT IS SUGGESTED NOT TO MAKE ANY CHANGES. ZIP INSTALLATION ONLY. Surely something will ruin this version of twrp if something is done with it since it does not show the /vendor partition.
Gapps that works: NikGapps. That's it
Go! Get crazy and share the results!
THINGS THAT DONT WORK SO FAR:
- Lantern (with the system doesn't work. If u use flash on camera, WORKS)
- Brightness is very picky. (on settings you'll find "Phh Treble Settings". There are some extra functions disabled -- by default? -- go check and see whats best for u. BUT! Careful, Icarus. Don't mess with stuff u dont know.)
- i don't have a SIM at the moment, so i can't tell if phone works.
- Root? Don't need it. Don't know if it's working.
THANKS TO:
@phhusson for TrebleDroid and Exynos updates, and aaaall his long work!
@prashantp01 for Vendor_Quack, Treble, and the patched TWRPs for this phone.
@corsicanu and all the people behind the KG bypass patch.
@juankp9086 for the guide to reset KG status.
aaand finally the team behind TWRP.
Is this a GSI? If not, you MUST provide the source you used for your kernel, as required by the GPL Policy.
Further, did you base this on someone else's work? You MUST give credit where due, per the Forum Rules.
V0latyle said:
Is this a GSI? If not, you MUST provide the source you used for your kernel, as required by the GPL Policy.
Click to expand...
Click to collapse
Yes. It's a GSI from @phhusson. All vanilla, no modification whatsoever. Kernel is included on Vendor_Quack, a SaR posted here too, from @prashantp01 . All is based on guides and files from this same forum (and all files and sources are linked here), except the steps.
V0latyle said:
Further, did you base this on someone else's work? You MUST give credit where due, per the Forum Rules.
Click to expand...
Click to collapse
No problem. I'll quote everyone involved for making this Done
As for the steps, as i said, it was trial and error. There was no guides or something that i know of (FOR ANDROID 13). I just take a leap of faith based on last good know version working (Android 11) and use that, since Android 12 was no good in some details.
BernoO said:
Yes. It's a GSI from @phhusson. All vanilla, no modification whatsoever. Kernel is included on Vendor_Quack, a SaR posted here too, from @prashantp01 . All is based on guides and files from this same forum (and all files and sources are linked here), except the steps.
Click to expand...
Click to collapse
A GSI does not include a kernel, but since you linked to an established project that already has a published source, everything is good.
Thank you for adding credits.
I don't know if you saw this, but the Magisk installation instructions include details on how to defeat KG/Vaultkeeper.
Did Android 13 worked for you , and did you try setting lock as that seems to cause a bootloop .
If it worked can you tell me how you did it as my phone's seems to bootloop after trying to set a lock (pin,etc) on Android 12 and 13 and I have already tried PixelExperience and LineageOs .
NVM wrong topic
AlphaMaster08 said:
Did Android 13 worked for you , and did you try setting lock as that seems to cause a bootloop .
If it worked can you tell me how you did it as my phone's seems to bootloop after trying to set a lock (pin,etc) on Android 12 and 13 and I have already tried PixelExperience and LineageOs .
Click to expand...
Click to collapse
Can confirm. Since i was just testing, didnt need to lock it. After trying to set a pattern or pin lock (and systemUI crashes), ive reboot and then a soft bootloop (for 3 seconds i can see lock screen, then android boot screen, 3 sec lock screen and so...).
After another reboot, bootloop.
I dont have this issue since lock screen was just sliding.
Another issue: bluetooth is working, but when wireless speakers are on sync, no sound whatsoever. A common fault on several android 13 installations as i can tell.
Remember that @phhusson is adding exynos updates on TrebleDroid, so we should expect (or beg, cant tell ) that more fixes are on the way?
And BTW if Someone needs it the best Roms/GSI for A8+ are TreeUi(S20 Port) , PixelExperience (11) and FusionX(10,maybe) and Don't try Android 12 /13Gsi as they don't work currently.
AlphaMaster08 said:
And BTW if Someone needs it the best Roms/GSI for A8+ are TreeUi(S20 Port) , PixelExperience (11) and FusionX(10,maybe) and Don't try Android 12 /13Gsi as they don't work currently.
Click to expand...
Click to collapse
Thanks!
This guide most of all was because a couple of users were asking if there's a way to run Android 13 on their A8s. So there's an answer for that now. Almost.