Related
So it looks like the major feature added is the Google Play assistant, which I don't even use on my phone.
But also, I believe the latest version of YouTube will be the stock app, which I just don't like.
I am rooted, which I realize will go away after the upgrade. But also, I don't have anything installed that requires root really. I wanted to take advantage of some xposed features, but apparently there is no version of the framework that supports nvidia shield tv 5.2?
So is it worth upgrading right now? Has anyone tried it? Anything notable worth upgrading for?
I'm in the same situation (rooted) as you. I tried to update, but I end up in TWRP and I don't know what to do from there. If I boot system it just start up as normal and ask me again to update.
Any ideas? Anyone?
What to do, what to do?
Kickasscowboy said:
I'm in the same situation (rooted) as you. I tried to update, but I end up in TWRP and I don't know what to do from there. If I boot system it just start up as normal and ask me again to update.
Any ideas? Anyone?
What to do, what to do?
Click to expand...
Click to collapse
Most likely have to wait for the developers image .
jionny said:
Most likely have to wait for the developers image .
Click to expand...
Click to collapse
And flash through FlashFire
orificium said:
So it looks like the major feature added is the Google Play assistant, which I don't even use on my phone.
But also, I believe the latest version of YouTube will be the stock app, which I just don't like.
Click to expand...
Click to collapse
I have a stock shield (not rooted), but had backed off the YouTube app to be the old one (the one that works with secondary accounts).
I let it upgrade and it did not force a YouTube update. After it finished, I'm still running YT 1.3.11. So you should be okay there.
Of course other than Google Assistant, I haven't found much new. What I really want is for Google Assistant to work with Google Play Music, but it doesn't do that (yet?).
I'm in the same boat as you guys. Currently rooted and debating the upgrade. I would think that we could update via flash fire if someone knows where the ota is stored once it downloads.
Sent from my Pixel XL using Tapatalk
I hear you guys. I will wait for OTA update to be downloadable or I might even consider returning to stock. I really don't have any use for root now.
FYI, Doesn't work with flashfire.
https://m.imgur.com/a/4ZKy6
n1gh7mar3 said:
FYI, Doesn't work with flashfire.
https://m.imgur.com/a/4ZKy6
Click to expand...
Click to collapse
That's not a developer image right? wouldn't think it would work unless it is the developer image or your bootloader is locked
I got mine to update even though its rooted.
After it finished downloading, it rebooted into twrp and installed the update automatically with no issues.
I did however get some issues after it finished updating.
The recovery/twrp is gone and cant boot into that anymore.
Root is of course gone.
And now im also just getting a black wallpaper in the launcher instead of the default nvidia one.
WisdomWolf said:
I'm in the same boat as you guys. Currently rooted and debating the upgrade. I would think that we could update via flash fire if someone knows where the ota is stored once it downloads.
Click to expand...
Click to collapse
data/data/com.nvidia.ota/app_download
jionny said:
That's not a developer image right? wouldn't think it would work unless it is the developer image or your bootloader is locked
Click to expand...
Click to collapse
I would assume the OTA is a developer image. Since it couldn't get flash fire to work, I reflashed the stock recovery image and applied the OTA, but it kept freezing and after about 10 minutes it would just boot into the original os.
n1gh7mar3 said:
I would assume the OTA is a developer image. Since it couldn't get flash fire to work, I reflashed the stock recovery image and applied the OTA, but it kept freezing and after about 10 minutes it would just boot into the original os.
Click to expand...
Click to collapse
Sorry I meant the developer rooted image that Nvidia usually releases shortly after a upgrade that you can flash over a unlocked bootloader and root and keep root
jionny said:
Sorry I meant the developer rooted image that Nvidia usually releases shortly after a upgrade that you can flash over a unlocked bootloader and root and keep root
Click to expand...
Click to collapse
I totally understand what you mean, I was already on 5.2.0 developer image, so I assume if presented with an OTA it's of the same type.
n1gh7mar3 said:
I totally understand what you mean, I was already on 5.2.0 developer image, so I assume if presented with an OTA it's of the same type.
Click to expand...
Click to collapse
No you have to get that from Nvidias site however last time I checked it was not up yet
n1gh7mar3 said:
I would assume the OTA is a developer image. Since it couldn't get flash fire to work, I reflashed the stock recovery image and applied the OTA, but it kept freezing and after about 10 minutes it would just boot into the original os.
Click to expand...
Click to collapse
you have to flash all the files inside, not only recovery. (nv-recovery-image-shield-atv-5.2.0.zip)
now it worked
Screen flickers
My shield got the latest upgrade (non root) and now my screen flickers from time to time. Any known solution to this issue ?
Tifulb said:
My shield got the latest upgrade (non root) and now my screen flickers from time to time. Any known solution to this issue ?
Click to expand...
Click to collapse
I've seen a few fixes for screen issues, either making sure in advanced display resolution settings things are correct, or disabling/renabling the CEC in settings.
You may want to check out the nvidia geforce forums thread, I'd probably start out middle to last several pages (assuming you read this soon, in a few days you'll just have to take a guess as there will be way more pages) https://forums.geforce.com/default/.../shield-experience-upgrade-6-0-for-shield-tv/
I think there's a post about chroma clipping which may be what yours is doing, but it could be some of the HDR stuff or something with the HDMI or CEC issues for all I know.
Hi,
i have a 2015 Shield (root) with 5.2 image.
I would back to stock image and unroot my shield.
I have download the "nv-recovery-image-shield-atv-5.2.0".
my approach.
*** Prerequisites:
1. Ensure that the bootloader is unlocked (see above step)
*** Flashing instructions:
1. Execute these commands on the host PC:
fastboot flash staging blob
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot reboot
Is this the right way?
Thanks!
OTA zip shield 2015 6.0
if someone need:
Original ota zip for Shield TV 2015 (non pro) 5.2 -> 6.0
https://mega.nz/#!BChlSbaR!em9CV5PoRzalWnMWf7iqAj4oVeDQqLhrz_Q1GGXy0Ug
Hi all,
I'm in need of some guidance with regards to a downgrade that I'd like to perform.
About 1 week ago the phone updated itself OTA. I don't remember which version was last before this update .. but what I remember is that the download was quite consistent (over 1G) and then the update took a while. Everything went by without any errors, but at the end I got Android Pie ... and I don't like it.
Reading through the forums I found that flashing a Xperia is doable .. with the right care and tools. So I started to get acquainted with newflasher and Xperifirm - but for now not connecting the phone and / or trying anything and here are the questions for anyone who might guide me a bit:
1. the phone is warranty (about 4-5 months old in fact). I believe the latest firmware that it was running with Oreo was 47.1.A.16.20-R6B. Reference = h**ps://xpericheck.com/cda/1310-4373. I don't see that version in Xperifirm => how can I get access to it for re-flashing?
2. as far as I read, I don't need to root it or unlock the boot loader. Just flashing would be enough to go back one firmware "edition".
3. backing up user data does not interest me so much. I have a list of all apps that are currently installed and within a few hours of tinkering I could get them all re-installed.
4. Would the process of downgrading be visible afterwards? - i.e. warranty would be "bye-bye", right?
.. any other comment / note / reference or observation is highly appreciated.
Best wishes!
metalik said:
Hi all,
I'm in need of some guidance with regards to a downgrade that I'd like to perform.
About 1 week ago the phone updated itself OTA. I don't remember which version was last before this update .. but what I remember is that the download was quite consistent (over 1G) and then the update took a while. Everything went by without any errors, but at the end I got Android Pie ... and I don't like it.
Reading through the forums I found that flashing a Xperia is doable .. with the right care and tools. So I started to get acquainted with newflasher and Xperifirm - but for now not connecting the phone and / or trying anything and here are the questions for anyone who might guide me a bit:
1. the phone is warranty (about 4-5 months old in fact). I believe the latest firmware that it was running with Oreo was 47.1.A.16.20-R6B. Reference = h**ps://xpericheck.com/cda/1310-4373. I don't see that version in Xperifirm => how can I get access to it for re-flashing?
2. as far as I read, I don't need to root it or unlock the boot loader. Just flashing would be enough to go back one firmware "edition".
3. backing up user data does not interest me so much. I have a list of all apps that are currently installed and within a few hours of tinkering I could get them all re-installed.
4. Would the process of downgrading be visible afterwards? - i.e. warranty would be "bye-bye", right?
.. any other comment / note / reference or observation is highly appreciated.
Best wishes!
Click to expand...
Click to collapse
There is a post in different thread that should answer all of your questions. I couldn't write it better myself, so here you go https://forum.xda-developers.com/xperia-xz1-compact/development/help-t3889845/post78673359
I hope it helps.
Hello,
Thanks for the quick reply.
For sure it confirms my understanding of the process.
Would there by any chance to find my Oreo 8 previous firmware (47.1.A.16.20) but for my "Customized DE" version?
It intrigued me that Xperifirm has just the latest one.
metalik said:
Hello,
Thanks for the quick reply.
For sure it confirms my understanding of the process.
Would there by any chance to find my Oreo 8 previous firmware (47.1.A.16.20) but for my "Customized DE" version?
It intrigued me that Xperifirm has just the latest one.
Click to expand...
Click to collapse
I don't think there will be any difference between customised DE and customised UK, there will be VoLTE and fingerprint enabled.
If you have to start asking other xda users for historical firmware then you can't guarantee its validity.
All the firmwares on Xperiafirm are direct from Sony servers.
Didgesteve said:
I don't think there will be any difference between customised DE and customised UK, there will be VoLTE and fingerprint enabled.
If you have to start asking other xda users for historical firmware then you can't guarantee its validity.
All the firmwares on Xperiafirm are direct from Sony servers.
Click to expand...
Click to collapse
I secured the Oreo firmware (customized UK) and the Pie firmware (customized DE) .. using xperifirm. I downloaded Pie just to have the current release that's running on the phone nearby, in case any of my attempts go bad and I'd need to restore it.
By chance, I have for about 2 weeks the possibility to have a non-branded original "Customized UK" XZ1c. As far as I've seen, there 1 app only that's different compared with my original customized DE. I might flash this one to Oreo and back to Pie ... just to learn the process ... and only afterwards to get to work on mine.
I also took my time to look around the web before jumping into flashing.
There are topics which I don't quite grasp yet .. like DRM .. or attest keys.
The thing is that I don't want to break anything in doing this downgrade to Oreo. I don't need to root it, to unlock the boot loader, to break any X-Reality or other functionality. I'm truly amazed by the battery life, btw: I get 3 1/2 days plus with Stamina activated non-stop. The phone is very snappy even with Stamina ... and that's another issue: by downgrading, I wouldn't like to ruin anything of the battery management internal apps / features.
Another thing is this: i don't intend to preserve any data. Whatever I have as apps, currently, will be backed-up and re-installed from scratch + restore of personal data.
I'm now at the point of going through:
1. flashing with flash tool + xperifirm
OR
2. flashing with newflasher.
Basically, I'm trying to understand what the differences (risks) are and what's the safest to use.
Any advice from the XDA community is welcome on this one.
Best wishes,
@metalik download the firmware with xperifirm and from settings select to decrypt/decompress (don't remember how it is). Then delete all .ta files from the folder and persist*.sin (to avoid losing android attest keys and flash with newflasher.
Flashtool has some problems with newer phone models so it's not recommended for xz1c.
the right question would be, how to get the latest security patches but staying with oreo?
vofferz said:
@metalik download the firmware with xperifirm and from settings select to decrypt/decompress (don't remember how it is). Then delete all .ta files from the folder and persist*.sin (to avoid losing android attest keys and flash with newflasher.
Flashtool has some problems with newer phone models so it's not recommended for xz1c.
Click to expand...
Click to collapse
gentlemen,
your input is highly appreciated.
aside from the persist*.sin and all .ta files .. should I take care of anything else?
P.S. I followed this tutorial (link) and it clearly indicates that warranty would not be voided if I would attempt such a re-flashing. Is it true?
P.S. the last question in the thread remains valid: how to apply the upcoming patches on top of Oreo? .. can those be obtained and flashed in a similar way? ... I doubt it would be a good approach because Sony is supposed to take the Google patches and make sure they integrate properly in their Android customization ...
metalik said:
I secured the Oreo firmware (customized UK) and the Pie firmware (customized DE) .. using xperifirm. I downloaded Pie just to have the current release that's running on the phone nearby, in case any of my attempts go bad and I'd need to restore it.
By chance, I have for about 2 weeks the possibility to have a non-branded original "Customized UK" XZ1c. As far as I've seen, there 1 app only that's different compared with my original customized DE. I might flash this one to Oreo and back to Pie ... just to learn the process ... and only afterwards to get to work on mine.
I also took my time to look around the web before jumping into flashing.
There are topics which I don't quite grasp yet .. like DRM .. or attest keys.
The thing is that I don't want to break anything in doing this downgrade to Oreo. I don't need to root it, to unlock the boot loader, to break any X-Reality or other functionality. I'm truly amazed by the battery life, btw: I get 3 1/2 days plus with Stamina activated non-stop. The phone is very snappy even with Stamina ... and that's another issue: by downgrading, I wouldn't like to ruin anything of the battery management internal apps / features.
Another thing is this: i don't intend to preserve any data. Whatever I have as apps, currently, will be backed-up and re-installed from scratch + restore of personal data.
I'm now at the point of going through:
1. flashing with flash tool + xperifirm
OR
2. flashing with newflasher.
Basically, I'm trying to understand what the differences (risks) are and what's the safest to use.
Any advice from the XDA community is welcome on this one.
Best wishes,
Click to expand...
Click to collapse
First take a screenshot of your current keystore status by typing this in the dialler *#*#7378423#*#*, then go to Service tests or Service info -> Security
I used newflasher since it's the last updated software for flashing.
Extract your ftf if required, put only the required files to downgrade in newflasher's folder. For me I only used kernel, system, userdata and cache.
Boot to flash mode, flash using newflasher, reboot and done! Make sure your keystore is intact by comparing the status of all keys with your screenshot.
I've used this method to downgrade temporarily, get temp root, backup my TA partition and then go back to current firmware. All keys intact.
metalik said:
gentlemen,
your input is highly appreciated.
aside from the persist*.sin and all .ta files .. should I take care of anything else?
P.S. I followed this tutorial (link) and it clearly indicates that warranty would not be voided if I would attempt such a re-flashing. Is it true?
P.S. the last question in the thread remains valid: how to apply the upcoming patches on top of Oreo? .. can those be obtained and flashed in a similar way? ... I doubt it would be a good approach because Sony is supposed to take the Google patches and make sure they integrate properly in their Android customization ...
Click to expand...
Click to collapse
I would flash everything else but the .ta and persist*.sin to ensure it works as intended with all files from the firmware you're using. Of course that resets all your userdata, but I guess a downgrade would require that anyway.
Warranty should be just fine - you're still just using official Sony firmware without any modifications to the device or system.
I don't think it will be possible to stay in official Oreo fw with locked bootloader and get recent security patches.
Sony will most probably implement the new patches only into the latest fw version - and that's Pie.
And if someone would make a custom rom with the latest patches on Oreo, you won't be able to install it with a locked bootloader.
Hello again,
what's the impact of flashing persist*.sin ... I believe that's connected with the attest keys, right?
Later edit: I downgraded from Customized DE Pie to Customized UK Oreo. I used newflasher, deleted all *.ta from the root & boot folder ... but by mistake I forgot about the one small persist*.sin file.
Long story short: yes, leaving persist*.sin file in the folder and flashing with newflasher destroyed the Attest keys (I get them as NOT provisioned).
The phone seems to work without problems nevertheless. I re-flashed to an older Customized DE Pie and got the last valid OTA update. Going back to Customized UK Oreo did remove everything from the Service Tests > Security (it showed "none"). But on that the Xperia Companion did the trick (software repair). So it's back on the initial Customized UK Oreo - just attest key shows NOT provisioned ... so
Lessons learned: /*.ta + /persist*.sin + /boot/*.ta must be removed before flashing with newflasher.
Hey, sorry to bring up this old thread but I don't suppose you still have a copy of 16.20? I've been looking for a working copy of it everywhere and I'm getting desperate
Joecalone said:
Hey, sorry to bring up this old thread but I don't suppose you still have a copy of 16.20? I've been looking for a working copy of it everywhere and I'm getting desperate
Click to expand...
Click to collapse
Hey,
sorry for the late reply ...
I kept everything that I (historically) downloaded with Xperifirm ...
I just checked and one folder is this "G8441_Customized UK_1310-6856_47.1.A.16.20_R18B" ... about 2.55 GB in size.
the content of fwinfo.xml is this:
<?xml version="1.0" encoding="utf-8"?>
<fwinfo>
<project>Lilac</project>
<product>Xperia XZ1 Compact</product>
<model>G8441</model>
<market>United Kingdom</market>
<operator>Customized UK</operator>
<swId>1307-7511</swId>
<swVer>47.1.A.16.20</swVer>
<cda>1310-6856</cda>
<cdfVer>R18B</cdfVer>
<fsVar>GENERIC</fsVar>
</fwinfo>
and update.xml is this:
<?xml version="1.0" encoding="utf-8"?>
<UPDATE>
<SYSTEMPARTITIONIMAGE>partition.zip</SYSTEMPARTITIONIMAGE>
<BOOT>boot.zip</BOOT>
<NOERASE>appslog_X-FLASH-ALL-C93B.sin</NOERASE>
<NOERASE>diag_X-FLASH-ALL-C93B.sin</NOERASE>
<NOERASE>ssd_X-FLASH-ALL-C93B.sin</NOERASE>
<NOERASE>Qnovo_X-FLASH-ALL-C93B.sin</NOERASE>
<FACTORY_ONLY>persist_X-FLASH-ALL-C93B.sin</FACTORY_ONLY>
<NOERASE>userdata_X-FLASH-CUST-C93B.sin</NOERASE>
<SIMLOCK>simlock.ta</SIMLOCK>
<NOERASE>cust-reset.ta</NOERASE>
<NOERASE>master-reset.ta</NOERASE>
<RESETNONSECUREADB>reset-non-secure-adb.ta</RESETNONSECUREADB>
<NOERASE>reset-wipe-reason.ta</NOERASE>
</UPDATE>
in a nutshell: I can zip the folder and find a way to send it to you.
Best regards,
Joecalone said:
Hey, sorry to bring up this old thread but I don't suppose you still have a copy of 16.20? I've been looking for a working copy of it everywhere and I'm getting desperate
Click to expand...
Click to collapse
I have my copy of 16.20 and related firmware. They are all Generic Latin America versions.
Xperia XZ1 Compact 47.1.A.16.20 Firmware Search
metalik said:
in a nutshell: I can zip the folder and find a way to send it to you.
Click to expand...
Click to collapse
Shahnewaz said:
I have my copy of 16.20 and related firmware. They are all Generic Latin America versions.
Click to expand...
Click to collapse
Great! I have also been searching desperately for a G8441 47.1.A.16.20 firmware. The country doesn't matter.
If either of you are able to send a zip, I would love to host it on my drive for anyone else who comes looking.
@cynthi4 Customized NOBA (nordic/baltic) latest Oreo: http://aeitis.org/xz1c/
It's downloaded and decrypted via xperifirm and zipped.
I'll keep it there for a while, but might remove soon.
cynthi4 said:
Great! I have also been searching desperately for a G8441 47.1.A.16.20 firmware. The country doesn't matter.
If either of you are able to send a zip, I would love to host it on my drive for anyone else who comes looking.
Click to expand...
Click to collapse
Here you go:
https://bigboidrive.duckdns.org/nextcloud/s/ZW4FQmqBE8Dfcp2
Hello, I just got a xz1c and I'm on 47.1.a.2.281. I haven't updated because of reported battery drain issues. Should I stick with this? Do you recommend pie at all? If not, what's the most stable build you'd recommend?
moist_line said:
Hello, I just got a xz1c and I'm on 47.1.a.2.281. I haven't updated because of reported battery drain issues. Should I stick with this? Do you recommend pie at all? If not, what's the most stable build you'd recommend?
Click to expand...
Click to collapse
Unless you have any specific issues with Oreo or see some advantage with upgrading to Pie, I wouldn't. I am not a big fan of Pie and went through this downgrade to 47.1.A.16.20 to avoid it. If you're interested in custom ROMs, I am running LineageOS 15.1 on my xz1c and it's been great!
That's strange. Being still happy with my locked device, I've always regretted switching to pie so today I actually did the whole process to restore Oreo: downloaded the latest Costumized NOBA oreo the user few posts above linked, deleted *persist.sin and every *.ta files in the folder (even the one inside boot folder), run newflasher and then reboot. Too bad I found stock camera broken
I re-checked multiple times searching for those *.ta files to be sure to avoid this issue, but that's it: I got Oreo but now I have lost stock camera and who knows what else.
Does it mean I've lost those functionality forever? Is there any way to restore stock camera? Happy to see this thread still active
My wife had been on whatever stock ROM came on her Pixel 2 since i bought it with no issues. She ran into a problem after maxing out her storage that the phone wouldn't boot and stayed stuck at the "G" boot screen. I got that fixed by sideloading an OTA of what seems to be some pre-release version of Android. it says "R" version. Many vital apps aren't working correctly - messaging, gmail, can't search from google bar, camera stopped working properly. So i am thinking i should start fresh and install something else now that at least the OS is back booting properly and hopefully everything will work ok.
I just want to make sure if anyone can help tell me what i'm dealing with, i believe this was a locked bootloader? not sure i can or need to unlock it.... > Install twrp... > Flash stock rom...? she doesn't need a fancy rom just something simple and stable.
Here's some of her vital info, any tips greatly apprecaited as i'm out of the loop on this stuff and an old pedestrian user at best.
Android Version
R
Baseband version
g8998-00020-1912200251
kernel version
4.4.210-gf13e65034114-ab6213703
Build Number
Rpp2.20227.009
Since your phone boots now. Simply wiping out everything should do the trick i guess.
Yeah. You can a factory reset. Your are currently on Android 11(R) preview ROM, it's still in the early phases and not suitable as a daily driver.
If all fails you can always flash a factory image, just remember to backup your data first.
Is this device a carrier device and if so, which carrier? You can only flash factory images with an unlocked bootloader so you need to figure that out first.
To figure out if you can unlock the bootloader you will first have to figure out if you have a Google or Verizon variant. Google variants can be unlocked. Verizon variants, for the most part, can't (although there is a thread where I believe someone may have done it on a Verizon variant). To figure out if you have a Google or Verizon, go here... https://www.imeipro.info/check_lg.html
Under "Buyer Name", if it says Google you're good to go. If it says Verizon or VZW, then you can't unlock the bootloader (unless the method in the thread I mentioned above actually works).
If you find you have a Google variant then via fastboot unlock the bootloader and fastboot flash the latest Q factory image.
https://9to5google.com/2020/04/23/h...d-11-dp1-to-android-10-on-google-pixel-video/
u need check ur phone can or not unlock bootloader.
if can... first thing u need to do is enable " oem unlock" in "development options"
when u unlock u can flash whatever firmware you want.
.
the problem u in android 11 . this very much bug.
Once you unlock, it'll wipe the phone.
You say you're running 11 DP1... At this point, I'd suggest signing up for the beta program and let the system update to I'd imagine the latest preview. Doing this should not wipe the phone.
From there you should have a working device and can back up what you want.
You should be given the option to unenroll on the beta website. Doing that, will downgrade the phone to the latest 10 release. it WILL also wipe the phone.
Go here. I see there's a link that could help you out.
google.com/android/beta
Im replacing my Pixel 6 Pro due to a bad accelerometer sensor. My phone is rooted with latest Magisk, has Kiri kernel installed as well. What's the most efficient way to prep the phone for a return to Google?
Official Google Android Flash Tool
and
Official Instructions for Locking/Unlocking the Bootloader
roirraW edor ehT said:
Official Google Android Flash Tool
and
Official Instructions for Locking/Unlocking the Bootloader
Click to expand...
Click to collapse
So just running the flash tool will remove root, reset to factory default and return kernel to stock? After that just lock the bootloader and good to go?
Starzboy77 said:
So just running the flash tool will remove root, reset to factory default and return kernel to stock? After that just lock the bootloader and good to go?
Click to expand...
Click to collapse
Yes. All of that.
Starzboy77 said:
So just running the flash tool will remove root, reset to factory default and return kernel to stock? After that just lock the bootloader and good to go?
Click to expand...
Click to collapse
If you like, for further explanation, flashing the 100% official stock ROM will both remove root and overwrite whatever kernel you currently have with the stock kernel that's included in the stock ROM. If you choose any option anywhere (on that official stock flashing site of Google's, or via any other method) to *not* factory reset the phone, sure you'd have any root-oriented apps still installed on your phone, but the phone wouldn't be rooted because the stock kernel is 100% official now.
There are many ways to do the same thing, but this is the safest and 100% sure method that it's all stock. i.e. my answering this way isn't dependent on anything you've possibly done to your phone - if you or someone had gone out of the way to modify the software of the phone even more than typically, this method would still completely overwrite any changes you've done, because you're flashing the completely stock ROM.
I haven't used the Official Google Android Flash Tool but countless others in this section alone have reported their situations on their phones being saved by this method - even when flashing the stock ROM in only a slightly more manual way via the official Platform Tools had failed to solve their issues: manually downloading the stock firmware, extracting it, and running the flash-all.bat file included (if on Windows). Since I haven't used it myself, I'm just going by memory of what others have reported about using it and I'm under the impression that it gives you the choice to wipe (factory reset) or not wipe your phone when it flashes it.
I wouldn't be surprised if by default it wipes, as that's what the flash-all.bat script from the manual full factory image zip file does by default.
Also, heads up. You never want to lock the bootloader unless you are 100% certain the phone is 100% stock. Ergo, why even though there are other methods to unroot and "return to stock", there is no good reason to use them unless you just don't have access to a computer, or a cable, or it's some kind of unroot emergency or some other circumstance that calls for more manual methods - which also leave a greater chance for accidental human error and can just plain brick your phone - although that might not matter since you're returning the phone.
roirraW edor ehT said:
If you like, for further explanation, flashing the 100% official stock ROM will both remove root and overwrite whatever kernel you currently have with the stock kernel that's included in the stock ROM. If you choose any option anywhere (on that official stock flashing site of Google's, or via any other method) to *not* factory reset the phone, sure you'd have any root-oriented apps still installed on your phone, but the phone wouldn't be rooted because the stock kernel is 100% official now.
There are many ways to do the same thing, but this is the safest and 100% sure method that it's all stock. i.e. my answering this way isn't dependent on anything you've possibly done to your phone - if you or someone had gone out of the way to modify the software of the phone even more than typically, this method would still completely overwrite any changes you've done, because you're flashing the completely stock ROM.
I haven't used the Official Google Android Flash Tool but countless others in this section alone have reported their situations on their phones being saved by this method - even when flashing the stock ROM in only a slightly more manual way via the official Platform Tools had failed to solve their issues: manually downloading the stock firmware, extracting it, and running the flash-all.bat file included (if on Windows). Since I haven't used it myself, I'm just going by memory of what others have reported about using it and I'm under the impression that it gives you the choice to wipe (factory reset) or not wipe your phone when it flashes it.
I wouldn't be surprised if by default it wipes, as that's what the flash-all.bat script from the manual full factory image zip file does by default.
Also, heads up. You never want to lock the bootloader unless you are 100% certain the phone is 100% stock. Ergo, why even though there are other methods to unroot and "return to stock", there is no good reason to use them unless you just don't have access to a computer, or a cable, or it's some kind of unroot emergency or some other circumstance that calls for more manual methods - which also leave a greater chance for accidental human error and can just plain brick your phone - although that might not matter since you're returning the phone.
Click to expand...
Click to collapse
Thank you for the indepth explanation. Really appreciate it.
Just factory reset it so your data is wiped and send it back. Google has never cared about them being rooted when you return them.
TonikJDK said:
Just factory reset it so your data is wiped and send it back. Google has never cared about them being rooted when you return them.
Click to expand...
Click to collapse
Is this accurate? Can anyone else confirm? What about having a different kernel? Does the bootloader have to be locked?
Starzboy77 said:
Is this accurate? Can anyone else confirm? What about having a different kernel? Does the bootloader have to be locked?
Click to expand...
Click to collapse
As I said, you should not lock the bootloader unless the phone is 100% stock. To me, it doesn't matter what anyone else says about what Google cares about. If it were my phone, I'd restore it 100% stock too. 10 minutes of very little effort for some peace of mind. Rather than meh, they might not care, or meh you might be the unlucky exception. Why take the chance?
But it's your phone, your decision. No one else makes the decision for you.
roirraW edor ehT said:
As I said, you should not lock the bootloader unless the phone is 100% stock. To me, it doesn't matter what anyone else says about what Google cares about. If it were my phone, I'd restore it 100% stock too. 10 minutes of very little effort for some peace of mind. Rather than meh, they might not care, or meh you might be the unlucky exception. Why take the chance?
But it's your phone, your decision. No one else makes the decision for you.
Click to expand...
Click to collapse
This to the millionth degree. and it also goes for when purchasing a used device or a refurbished device. Reflash Android. they make it so simple now that it can be done using another phone. No PC necessary.
Flash Tool changed the game 3 years ago for how easy the process is. Heck I just reflash my phone monthly because it's such great technology (kidding, not kidding?)
Having issues installing beta 3.3 on my 6 pro.. did a factory reset then tried installing it. First time it took forever to install and phone rebooted and had missing operating system so I had to factory reset.. second time I got a failed to install message.. rebooted the phone and it said no operating system please visit this link from another device.. rebooted then phone worked normal.. what is going on here ? Phone is purchased from att, so idk if it's considered global version but whatever either way . Is there something stopping it from being installed? Was trying to do all this OTA.. thanks kinda new to it
I'm not sure if it being an att version has anything to do with it or not.. maybe the version google releases is only working on unlocked global models?? Someone shine some light on this..
You can use https://flash.android.com/ to flash with a computer.
So why would the flash tool work but not the ota method ?? Really curious cause when the official comes out hopefully I can flash that ota without any issues.. right now I opted out of the beta cause I really want the ota method to work and it doesn't ..
Can someone tell me why the ota wouldn't install ? Installed it the way I installed any other update on the phone through check for updates.. Id rather get ota working vs hassling with a computer to install it. That can mess things up if done wrong .
Is it failing to ota install the beta cause of a locked bootloader ? It does fine with install ota security patches on Android 12. Trying to install 13 ota on the phone itself fails.. I don't see why that would be though ?
@Redbeardkevv Welcome to XDA. Instead of posting multiple times in a row, please use the Edit button to edit your post and just add to it, in the future.
Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own)
^ That Google site has saved many users on XDA. It has revived or corrected a mistake on their devices (mine too, once) when even flashing the full factory image didn't fix the problem. I have no idea what exactly it does that manually flashing doesn't. I normally use the full factory image zip, and that alone sometimes fixes issues that users have when they have issues flashing via the OTA method.
Oem unlocking toggled on isn't an option on this phone , purchased at att . I'll just wait till they release the official ota. But what would of been holding it up and making the installs corrupt??
Redbeardkevv said:
Oem unlocking toggled on isn't an option on this phone , purchased at att . I'll just wait till they release the official ota. But what would of been holding it up and making the installs corrupt??
Click to expand...
Click to collapse
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developer.android.com
Important excerpt:
Android Flash Tool guides you step-by-step through the process of flashing your device—there's no need to have tools installed—but you will need to unlock your device and enable USB Debugging in Developer options.
Click to expand...
Click to collapse
If I remember correctly from other AT&T variant Pixel 6 Pro users in this section, once you pay off the phone and/or own the phone for long enough, AT&T should carrier unlock the phone, and that will likely make it so that you can OEM Unlocking and unlock the bootloader. (this also applies to T-Mobile, but does not apply to Verizon)
Well it's a far ways from being paid off I'll just add that .. what are my flashing options ? Also why would a security patch install just fine, then I enroll into beta ,try to install it, and bam it won't install and is corrupt install. Just doesn't seem right to me.. should I just wait until official release early August and then the OTA install from phone will work ?
Why would a security patch install without any issue , but I go to install this beta 13 and it fails and is corrupt . Same method as installing a security patch , only difference is beta won't install . Will it install correctly OTA when they release the final version in August ???
Redbeardkevv said:
Why would a security patch install without any issue , but I go to install this beta 13 and it fails and is corrupt . Same method as installing a security patch , only difference is beta won't install . Will it install correctly OTA when they release the final version in August ???
Click to expand...
Click to collapse
Firstly, unlocked bootloader is required to flash custom or beta firmware. While you can sideload OTA packages on a locked bootloader, I would highly recommend against doing so as you may end up with no way to recover your device.
When installing a beta, it is generally best to wipe and perform a clean flash. OTA is not recommended because beta software by nature is not yet suitable for public release, and may not appropriately handle everything correctly coming from older firmware.
As has been mentioned before, I recommend you use the Android Flash Tool to flash the beta. To ensure you have a fresh start, tick the Wipe device and Force flash all partitions boxes. Do not re-lock the bootloader.
So in short, wait for the official ota to roll out in August and install from phone then?? Cause I won't be able to unlock bootloader , phones not paid off... Would this explain why it's failing to install an beta from within the phone itself cause the bootloader's locked? So I have to wait for official ota rollout like I said earlier ??
Redbeardkevv said:
So in short, wait for the official ota to roll out in August and install from phone then?? Cause I won't be able to unlock bootloader , phones not paid off... Would this explain why it's failing to install an beta from within the phone itself cause the bootloader's locked? So I have to wait for official ota rollout like I said earlier ??
Click to expand...
Click to collapse
Most likely. I doubt the beta will pass signature verification until it is updated to public release.
So not passing signature verification would be the reason it won't install ( ota ) most likely ? I'm just confused why a patch will install ota but the beta cannot .. must have something to do with bootloader being locked and it not being an official verified release or something
Just curious
Redbeardkevv said:
Just curious
Click to expand...
Click to collapse
Yes, you need the bootloader unlocked. So you cannot use those builds - only officially released OS builds.
NippleSauce said:
Yes, you need the bootloader unlocked. So you cannot use those builds - only officially released OS builds.
Click to expand...
Click to collapse
Well that explains it not installing and saying corrupted install ... Lol
Redbeardkevv said:
Well that explains it not installing and saying corrupted install ... Lol
Click to expand...
Click to collapse
It's a beta, so there will be issues for sure (but your last comment said you are getting an error [device is corrupt] that was common a few months ago so read on). You don't need to have an unlocked bootloader to enroll in the beta. Tons of users on Verizon and AT&T with a locked BL have installed the beta. Most are fine, some have had issues.
I wouldn't install a Beta on a locked BL. Why risk it? If something goes wrong, you'll need to get a warranty replacement. Seems like such a hassle.
For your issue, since you said you're getting a device corrupt message. This message is caused by q few different things (there's a thread on here about it). To fix it, users needed to do a factory reset in recovery mode. If you really wanted to try installing the beta (and you understand the risks), you'd probably need to: go to recovery mode and perform a wipe/factory reset.
From there, you could install the latest stable ota (via recovery mode) then see if the beta will update for you (via beta enrollment like you are trying to do), or directly flash the beta ota (link below). I'm just not sure if you can flash a beta ota image, over a stable build. I haven't tried it but according to xda, you can be on Android 12, and flash the Beta 13 ota (instructions found here).
There's two ways to flash an Android image: ota builds via recovery mode (doesn't require BL unlock) and factory image via fastboot which can be done manually or using Google's web flash tool (flash.android.com) - both if these require BL unlock.
You can find all the latest image downloads here. Google strongly recommends to flash the beta with an unlocked bootloader using their flash web tool. It's a beta so I would stay away until you can unlock your bootloader. Don't risk it. But I still think it might be a good idea for you to eventually perform a factory reset from recovery mode, since you are seeing the device is corrupt error message.
Had same problem, tried installing it twice and gave up