Develop Bugs

[Q]

Please when i receved update OREO for my moto G5 Xt 1676 dual ? Thanks in advance ,,??

mednazim said:
Please when i receved update OREO for my moto G5 Xt 1676 dual ? Thanks in advance ,,
Click to expand...
Click to collapse
Most probably, you will receive it in this century.. I think. :laugh:
I'll be serious now. Nobody knows when you will receive an update. It depends on your region mostly, but there are also few other factors which can delay it. However, if you don't want to wait anymore and have knowledge of flashing fastboot firmwares, full fastboot Oreo firmware (step-by-step tutorial included) for Moto G5 is already available here: https://forum.xda-developers.com/g5/how-to/official-oreo-8-1-0-opp28-85-16-t3849244. Of course, nobody is responsible for any damage you make by flashing it.

it is necessary to unlock bootloader and install recovery for install update OREO ?

mednazim said:
it is necessary to unlock bootloader and install recovery for install update OREO ?
Click to expand...
Click to collapse
No, it isn't. According to posts in the other threads, there are at least 2 requirements to successfully update to Oreo through OTA (https://forum.xda-developers.com/g5...ase-opp28-t3849273/post77771786)#post77771786).
The first one is that system, boot and recovery partitions must be 100% unmodified - restoring doesn't help. If it's once modified, only a full reflash of stock firmware (with equal or newer build) will revert it to completely unmodified state. If you decide to install an update with one of these partitions modified - in the better case, update will refuse to install. In the worse one, it will install, but you will end up with hardbrick.
The second one, your build number must be NPPS25.137-93-2-5 (install script do the checking of the build number in the beginning of the OTA install. If it finds different value, installation will be stopped with some error showing up, but nothing happens, because the whole process of updating didn't start at all).

Thanks bro i will try

Download links for all OTA/boot files for Sirocco (TA-1005)

Hi everyone, these may be of help to you. I'm not a dev so all I was doing here was using a rooted Sirocco to pull OTA files off the phone (data/ota_package). Using logcat/android bug report doesn't catch OTA URL on this device. It's my understanding they will need to be unpacked.
Files are in order of download/installation from A1N-310B-0-00WW-B03-OST604 onwards. That full firmware can be obtained here thanks to Hikari (Under Sirocco) https://hikaricalyx.com/fih-android-firmware/
The boot image for the firmware above can be found in the zip. It's already unpacked (A1N-0-310B-00WW-boot.img).
OTA 1 (Changelog - https://i.imgur.com/EeQeHyR.png)
https://mega.nz/#!SA1U3SzR!WAUtzV5AH2g6jYUYqhrUfMNh_tOe7ziNhNwZ8eZBxew
Boot image - https://mega.nz/#!2J8wBaBR!PbYVY4Ysr4l9idxReLrJe6wWu83KRy5tO29j0H2b3Ew
OTA 2 (Changelog - https://i.imgur.com/AOvs4Ps.png)
https://mega.nz/#!mB0EgCRa!oEKAxCl5iGnR3rHC91te0mgU3JgW3AXAO991kR4nj9g
Boot image - https://mega.nz/#!iU1WlKxT!mz1VrSGS987BbiPj1nvyUQzb4GEBw3686onS6ymctJI
OTA 3 (Changelog - https://i.imgur.com/nEpvMq2.png)
https://mega.nz/#!rNNAhASA!5_CdYQIym6iqc5ycN6wMqG0XvzrsCf70I3VQsy8bjFg
Boot image - https://mega.nz/#!SJt0WSxK!UkG4DbsDmUwIzExcmG1qo2xqhRk4lJlylhWHfMFJxfM
OTA 4 (Changelog - https://i.imgur.com/QH6Dnox.png)
https://mega.nz/#!HF8WlKDS!OpfBdAEUJSe_vzTebdCGg_DN_8Kzj5UZVG29x8aG6Q8
Boot image - https://mega.nz/#!7Usw1aKS!jEoZDlj5mtu5tqVpVG7XFaHLdDleiq3M6GBfy7_IUzc
OTA 5 (Changelog - https://i.imgur.com/bDSCAqX.png)
https://mega.nz/#!XUlWFKiC!_trT2aVmGQVhD-lzeZjWEn2LlmRZ4d6CMrKuAB41kkw
Boot image - https://mega.nz/#!KVl2WKqT!AcDI4YSOSo6vBe4Jb3FrOBsKGzO-KM5a8gowgNQXHog
OTA 6 (Changelog - https://i.imgur.com/ColEcRJ.png)
https://mega.nz/#!DE8QxSDQ!G1xRrjN9do28trYeQT-E9jAYmP7dszuXMKZ8kpmhcMI
Boot image - https://mega.nz/#!XB9EnY4A!UxLAX0hBabbKy09pGQz_BLQW9Hy5Lz0K4y15uVJcY7o
OTA 7 (Changelog - https://i.imgur.com/Tll0QuI.png)
https://mega.nz/#!zUsAzKLZ!TngURPA1pDUFjrmsrWvVglLmkE3GGGE4qX53-Vp38iU
Boot image - https://mega.nz/#!jck0iAjI!nEd890ZxQS1OaXX4ELNtdsIsa3TJZxddC1D7faPOB9U
OTA 8 (Changelog - https://i.imgur.com/HsZLwV4.png)
https://mega.nz/#!3dtEXQwY!CY6J3auoDeMelGSDmQiAJgOBHw3eH-sxrA3x51gXQ-U
Boot image - https://mega.nz/#!SQsUUYSD!iBwTMYd4OEDJJ7Me-zb2SnfPghc2me_ZEYR6SrdOkgU
OTA 9 (Changelog - https://i.imgur.com/eLVqDrM.png)
https://mega.nz/#!CEc1GQ7L!EiZYCubGDf5C97NNQDLZxmjcEaw555FbxHKvMNveZDw
Boot image - https://mega.nz/#!mNFzVCbD!RNTJI1_oPiHSapyykE0szjosBo_QnIoJiGZ0EQtmzqY
OTA 10 - Pie (Changelog - https://us.v-cdn.net/6031042/uploads/editor/je/y2ok3dg0norb.png)
https://mega.nz/#!fYUAgQJY!p6kO-B-IFwz0NhDv4ZlrDCQYKQGakH3fy9GbfG_kmDM
Boot image - https://mega.nz/#!qANy1a7b!ODh8ol97h8qJwZGndUCHqyG3qifnsfT7ILkggDaVoFA
Magisk patched boot - https://mega.nz/#!HYVimArR!m7BHM2iYVZVstTFx0W-zB01cSN-bb4lquKiYUmXoIm4

edit: TWRP removed, buggy

OTA 3 zip was corrupt, it has been replaced.
Also for helping out anyone who gets their Sirocco unlocked, this is a pre-rooted boot image for A1N-310B-0-00WW-B03-OST604
You can use this to do fastboot boot patched_boot.img and then use Magisk to root your device.
https://mega.nz/#!6dMgjCjL!KRkB39ppPp4RA0Wj57yjIjiXaE6B21f-B488yQFc61s
You can, of course, do the above yourself if you have a second phone that is rooted and go into Magisk and patch one of the stock file boot images above.
Now you can do OTAs and keep root
STEPS_TO_UPDATE:
1. Go into Magisk Manager -> Uninstall -> Restore Images
2. Apply Update, DO NOT REBOOT YET
3. When step to finished and it promts you to reboot go into Magisk Manager -> Install -> Install to inactive Slot
Congratulations you can now reboot and will have an updated Android while keeping full root.
Click to expand...
Click to collapse
https://forum.xda-developers.com/nokia-8/how-to/guide-how-to-root-nokia-8-ability-to-t3848390

If anyone is already on the November security update with this device and wants to root without downgrading, here is a magisk patched boot image
https://mega.nz/#!HBcHzYCB!KpqytpNth0Vfu3K9eX0vbP7heJ3MFPm6MX4ozC5L_qk

December security update added as OTA 9.
No Pie yet

Audioboxer said:
December security update added as OTA 9.
No Pie yet
Click to expand...
Click to collapse
Its a shame.

December patched boot for anyone who's had this phone unlocked and has done OTAs up to December without rooting
https://mega.nz/#!6R8RCIoB!ZPR7s-w4LWDXO1UcI7GBuhf7U0U3fujHLQIc6qlqx2g
As always, fastboot boot this image to root your phone with Magisk direct install. Do not flash my boot images, otherwise, you won't be able to do the OTA trick above with Magisk.

Removed: Oreo homebrew packages by Hikari are buggy, avoid.

So i found this...
https://mega.nz/#F!W50gzawY!nC8Yb9yE6n08gGafFi700A
The A1N-4120 is a Pie build. A guy i met on twitter installed it and said it is a decent build without bugs. I'm a bit hesitant to install it. I'm afraid that if i install it and the offical update comes out i can't update via OTA. Is there a way to revert back to 8.1?
The guy's phone isn't rooted or unlocked.
Still, he says it's the official build from HMD. They are holding it back... If that's true it's kinda sad...

marccoppers said:
So i found this...
https://mega.nz/#F!W50gzawY!nC8Yb9yE6n08gGafFi700A
The A1N-4120 is a Pie build. A guy i met on twitter installed it and said it is a decent build without bugs. I'm a bit hesitant to install it. I'm afraid that if i install it and the offical update comes out i can't update via OTA. Is there a way to revert back to 8.1?
The guy's phone isn't rooted or unlocked.
Still, he says it's the official build from HMD. They are holding it back... If that's true it's kinda sad...
Click to expand...
Click to collapse
It's the internal OTA and he wasn't sensible installing it without BL unlock
https://forum.xda-developers.com/no...ide-how-to-install-android-pie-build-t3885834
These internal builds don't pass safetynet so Google Pay will not work. It is also unknown how to get back onto retail OTAs without an unlocked bootloader. When HMD did the Nokia 8 beta test they had an official rollback method.
I'd strongly advise staying away from this if you haven't unlocked the BL. The build wasn't all that good either, missing adaptive battery, pro camera, Pie themeing and more. From above two new OTAs exist since the December pie build. I'll try them and see if anything has been added.

Audioboxer said:
It's the internal OTA and he wasn't sensible installing it without BL unlock
https://forum.xda-developers.com/no...ide-how-to-install-android-pie-build-t3885834
These internal builds don't pass safetynet so Google Pay will not work. It is also unknown how to get back onto retail OTAs without an unlocked bootloader. When HMD did the Nokia 8 beta test they had an official rollback method.
I'd strongly advise staying away from this if you haven't unlocked the BL. The build wasn't all that good either, missing adaptive battery, pro camera, Pie themeing and more. From above two new OTAs exist since the December pie build. I'll try them and see if anything has been added.
Click to expand...
Click to collapse
Thanx for the reply! Gonna stay away from it then... Usually i try everything, but since the BL is still officially locked there aren't that many people out there that can help when things go wrong. Especially with this being my daily phone, i don't want to mess it up.

marccoppers said:
Thanx for the reply! Gonna stay away from it then... Usually i try everything, but since the BL is still officially locked there aren't that many people out there that can help when things go wrong. Especially with this being my daily phone, i don't want to mess it up.
Click to expand...
Click to collapse
Yeah, it's not worth it, Pie should drop this month.
With the Nokia 8, HMD advised if you stayed on the beta you'd get 1 OTA and that would be it. You basically had to rollback.
In order for us to flash firmware packages, we need an unlocked bootloader if HMD isn't providing an official rollback method. As it seems we won't get an official beta test for the Sirocco it's a bad idea anyone with a locked bootloader flashing these internal releases.

Audioboxer said:
Yeah, it's not worth it, Pie should drop this month.
With the Nokia 8, HMD advised if you stayed on the beta you'd get 1 OTA and that would be it. You basically had to rollback.
In order for us to flash firmware packages, we need an unlocked bootloader if HMD isn't providing an official rollback method. As it seems we won't get an official beta test for the Sirocco it's a bad idea anyone with a locked bootloader flashing these internal releases.
Click to expand...
Click to collapse
That was my guess to. Thanx for the info.

You are wrong. And I am the guy he met on twitter. And btw he is referring to Nokia 8 Sirocco and sorry but could you explain how you termed as insensible. I downloaded the internal OTA and then rebooted the phone in safe mode and the update automatically installed. For your information
1. Adaptive battery is there
2. Wellbeing is there
3. Pro camera is there.
So stop being judgemental. Nokia 8 and Nokia 8 Sirocco and two different handsets. Nokia 8 is what you mentioned above . So next time mind Ur tongue while u talk

rajeev.rao87blr said:
You are wrong. And I am the guy he met on twitter. And btw he is referring to Nokia 8 Sirocco and sorry but could you explain how you termed as insensible. I downloaded the internal OTA and then rebooted the phone in safe mode and the update automatically installed. For your information
1. Adaptive battery is there
2. Wellbeing is there
3. Pro camera is there.
So stop being judgemental. Nokia 8 and Nokia 8 Sirocco and two different handsets. Nokia 8 is what you mentioned above . So next time mind Ur tongue while u talk
Click to expand...
Click to collapse
My advice was just following what Nokia devs like Calyx Hikari state. If you do not have an unlocked bootloader its best not to install internal OTAs because there is no way to revert to retail FW. The Nokia 8 had an official beta test so there was a way to rollback off of the beta Pie firmware to Oreo again, to then install the final Pie OTA.
Otherwise you need an unlocked bootloader to flash an Oreo/Pie retail package with LA OST.
I don't mean to offend anyone, I just don't want anyone installing these leaked OTAs on their bootloader locked device and being stuck.
Currently, there's no way to roll back to Android 8.1 for Nokia 8 Sirocco by yourself, so use these packages at your own risk.
It will be better if you're using prototype device or a retail device with unlocked bootloader.
Click to expand...
Click to collapse
https://forum.xda-developers.com/no...stall-android-pie-build-t3885834/post78591840

Nokia 8 Sirocco doesn't need any bootloader to be unlocked.
Nokia 8 Sirocco doesn't need bootloader to be unlocked. Like I got it and others who installed got it without doing the same. You just have to downloaded the A1N 4200 file and reboot the phone to safe mode and the phone automatically detects the update. So I assume that's pretty much official and valid .
Don't know why people end up spreading rumours without knowing the real picture. Just because one device works in a specfic way doesn't mean every device functions the same way.
Plus Nokia 8 Sirrocco gets all the features a full fledged android one device gets including the below
1. Adaptive Battery
2. Gestures
3. Digital Wellbeing
I myself wanted to write a review and a video but never written one for mobile devices, I have done for vehicles.
And most importantly Nokia 8 and Nokia 8 Sirocco are different mobiles . The only common point is The processor.

Pie OTA Rom
Now that the official PIE OTA has been released can anyone capture it and post a link to the file? It can take weeks to reach people over the air sometimes!
Thanks

Let's say they will be captured, can i install them with a locked bootloader?

marccoppers said:
Let's say they will be captured, can i install them with a locked bootloader?
Click to expand...
Click to collapse
I did on the Nokia 8 and the Nokia 7 plus by downloading to the device, renaming the file and using the phone keypad ( *#*#874#*#*) so I assume it will be the same on the Sirocco?

marccoppers said:
Let's say they will be captured, can i install them with a locked bootloader?
Click to expand...
Click to collapse
Sideloading the OTA via ADB can be done on a locked bootloader. The method by EGGMEN should work as well. :good:

Redmi Note 8 Pro freezing in Android 10

Hi. I got a Redmi Note 8 Pro Global version and I updated it to Android 10 manually. Problem is I am getting random freezes everyday. I would like to go back to Android 9 because these freezing is very annoying and ruining my experience. I am not sure if this is related to MIUI or Android 10 itself. I've done factory reset and reset via recovery mode as well. Still the same. Are any instructions to go back to Android 9?
I've read in some forums that Android 10 has some issues even in pixel devices where if an app freezes, it brings down the whole OS. Mine freeze about 10 seconds, sometimes more. It's happening very randomly in different apps so it is very difficult to replicate.

joenefloresca said:
Hi. I got a Redmi Note 8 Pro Global version and I updated it to Android 10 manually. Problem is I am getting random freezes everyday. I would like to go back to Android 9 because these freezing is very annoying and ruining my experience. I am not sure if this is related to MIUI or Android 10 itself. I've done factory reset and reset via recovery mode as well. Still the same. Are any instructions to go back to Android 9?
I've read in some forums that Android 10 has some issues even in pixel devices where if an app freezes, it brings down the whole OS. Mine freeze about 10 seconds, sometimes more. It's happening very randomly in different apps so it is very difficult to replicate.
Click to expand...
Click to collapse
use indian version android 10 which is on miui v11.0.2.0.
It works fluently without any problem but keep in mind that preloader and other safety file is for Android 9. If you use them before flashing anything in android 10. Then it might brick your device. Even magisk brick some person device in android 10. So be safe before doing modification in it. Until preloader and lk will be available for it.

Hi. Thanks for the suggestion but what if I want to go back to Android 9 Global version? Just want to back to previous version when I got it out of the box. I don't want to flash or use other region roms. Just want to go back to Android 9. Is there any available steps or instructions out there? Can't seem to find one.
1hekill0r said:
use indian version android 10 which is on miui v11.0.2.0.
It works fluently without any problem but keep in mind that preloader and other safety file is for Android 9. If you use them before flashing anything in android 10. Then it might brick your device. Even magisk brick some person device in android 10. So be safe before doing modification in it. Until preloader and lk will be available for it.
Click to expand...
Click to collapse

joenefloresca said:
Hi. Thanks for the suggestion but what if I want to go back to Android 9 Global version? Just want to back to previous version when I got it out of the box. I don't want to flash or use other region roms. Just want to go back to Android 9. Is there any available steps or instructions out there? Can't seem to find one.
Click to expand...
Click to collapse
You can easily go back to android 9 global version by flashing fastboot rom via fastboot. You can flash fastboot rom just via mi flash tool by flashing lk and preloader before flashing rom or you can easily flash every image one by one manually in fastboot mode, Just by using command like fastboot flash system system.img, fastboot flash cust cust.img and so on. It is very easy. Hope it work for you.

Thanks for this. I've been following instructions from this link https://c.mi.com/ph/miuidownload/detail?guide=2. I think you are also referring to this one. I already followed instructions but I am now stuck in the unlocking method which says I need to wait 168 hours.
You mentioned I can flash img files one by one, is still possible when without unlocking the the device first via miui unlock tool?
1hekill0r said:
You can easily go back to android 9 global version by flashing fastboot rom via fastboot. You can flash fastboot rom just via mi flash tool by flashing lk and preloader before flashing rom or you can easily flash every image one by one manually in fastboot mode, Just by using command like fastboot flash system system.img, fastboot flash cust cust.img and so on. It is very easy. Hope it work for you.
Click to expand...
Click to collapse

joenefloresca said:
Thanks for this. I've been following instructions from this link https://c.mi.com/ph/miuidownload/detail?guide=2. I think you are also referring to this one. I already followed instructions but I am now stuck in the unlocking method which says I need to wait 168 hours.
You mentioned I can flash img files one by one, is still possible when without unlocking the the device first via miui unlock tool?
Click to expand...
Click to collapse
Nope you have to first unlock bootloader. But as I read sp flash tool can work without unlocking bootloader. So if you have fastboot than first flash preloader and lk and then you can use sp flash tool without authorised account. But I am not sure if it work then inform me also. And if it don't work you have to first unlock bootloader.

The experience posted by this user only reinforces my general impression not to do a major upgrade (even an "official" one pushed by the manufacturer) on any phone that one uses for primary use, unless you want to get involved in the whole rooting process and all the time and risk that entails.
In my experience, the original version of android that ships with a device, and subsequent minor fixes, are the most adapted to the phones specs. Despite claims otherwise, every major upgrade involves more resource use, since it was designed with the latest hardware in mind. It will therefore almost certainly degrade the performance of a phone, even one not that old. I have had this happen in every phone I have owned. And unless your phone is rooted, you can not downgrade the OS.
So when MIUI 12 comes out, with Android 10, I will definitely wait for others to do it first and wait for the feedback, maybe I'll just pass on it. Right now my RN8P works great, and the additional "features" of android 10 add no functionality whatsoever. Why screw around with something that already works great?
---------- Post added at 11:25 AM ---------- Previous post was at 11:20 AM ----------
BTW the above is true on Apple devices, too, in my experience.

Question Pixel 6 Pro Flash able Firmwares

Can someone send me.a direct link to all Firmwares for the pixel 6 pro that I can flash stock Firmwares that is. I need the official Firmwares for all countries

Is this what you are looking for
https://developers.google.com/android/ota

Or the full firmwares https://developers.google.com/android/images, and the December ones that they removed from there Alternate links to December full factory images for .017, .016.A1 & A4, and OTAs for .017 & .016.A1 available.

I'm december FW without bug. If i want to clean flash the next FW what i must to do.
Can i wipe system in recovery or i must use adb/fastboot command ?

Vincent_40 said:
I'm december FW without bug. If i want to clean flash the next FW what i must to do.
Can i wipe system in recovery or i must use adb/fastboot command ?
Click to expand...
Click to collapse
You'll be able to use Official Google Android Flash Tool or the full factory image zip which as always would be available at Pixel 6 Pro Factory Images. Either will fully wipe your device. I don't have firsthand experience with Official Google Android Flash Tool so I don't know if it wipes by default but I know it can or has an option to if it's not default. The full factory images at Pixel 6 Pro Factory Images, without modification, always fully wipes the phone. Make sure and update SDK Platform Tools every month (sometimes earlier version Platform Tools doesn't work correctly and update the Google USB Driver if you're using Windows.

Ok thx i'll try to clean flash with next update with flash tool.
Hope Twrp will be released soon.

Vincent_40 said:
Hope Twrp will be released soon.
Click to expand...
Click to collapse
I wouldn't hold my breath or take any bets on that. So far without TWRP hasn't held anything back.

roirraW edor ehT said:
I wouldn't hold my breath or take any bets on that. So far without TWRP hasn't held anything back.
Click to expand...
Click to collapse
Yeah, about a month or two ago bigbiff said he was working on TWRP for Android 12 in general, but it would be a while. Honestly, haven't used it since the Nexus days. Really haven't missed it at all and probably wouldn't use it even when/if it does come out.

I'm on january security patch and I'd unlock the bL without disable the DM-Verity verification.
Can i root with last Magisk canary directly or do i need to disable DM-Verity ?
Last point, my play protect is uncertified, but it's not important

Vincent_40 said:
I'm on january security patch and I'd unlock the bL without disable the DM-Verity verification.
Can i root with last Magisk canary directly or do i need to disable DM-Verity ?
Last point, my play protect is uncertified, but it's not important
Click to expand...
Click to collapse
Yes, you can root with Canary Magisk 23016 without disabling verity & verification.

Ok i'll try
Thx for your reply

Question Android 13 beta 3.3 won't install ...

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