Develop Bugs

Just need a bit of help getting going

So Ive searched around and I just can't find a definitive answer so here is what I got.
I understand that this here; is how you use marshmallow with the new bootloader unlock and root: http://forum.xda-developers.com/not...t/howto-bootloader-unlock-upgrade-to-t3398144
I also know that I have to do this exploit first to unlock the bootloader: http://forum.xda-developers.com/note-4-verizon/general/note-4-verizon-bootloader-unlock-t3358913
My issue is I ended up getting forced OTA 2 weeks ago. So my current question is, Do I have to roll back to lollipop? Is root/unlock even possible for me? If so, How do I do that since I haven't rolled back before. Its been a while since I've been into rooting/roms. Is there a link to doing it for marshmallow to lollipop? Also what about the firmware?
Current Stats:
Model: SM-N910V
Baseband: N910VVRU2CPD1
Android Version: 6.0.1
Build: MMB29M.N910VVRU2CPD1
Kernel Version: 3.10.40
I just need an answer since Ive been reading threads the last 2 hours. Its confusing since the titles of most are how to unlock bootloader THEN goto marshmallow. Thanks Guys!

I think I solved it myself. Looking like I'm effed with this bootloader. Since I don't think its rootable or unlockable.

ThatRoo said:
I think I solved it myself. Looking like I'm effed with this bootloader. Since I don't think its rootable or unlockable.
Click to expand...
Click to collapse
You can try to roll back to 5.1.1 by flashing the full firmware (thanks, hsbadr!) using ODIN. You can unlock the bootloader on this version.
The question is, will your phone let you. In another thread, the success rate appears to be something less than 100%. I don't know what the harm would be... if you can't do it, ODIN will likely fail. At any rate, the attempt is on you. I can't be responsible for what happens.

douger1957 said:
You can try to roll back to 5.1.1 by flashing the full firmware (thanks, hsbadr!) using ODIN. You can unlock the bootloader on this version.
The question is, will your phone let you. In another thread, the success rate appears to be something less than 100%. I don't know what the harm would be... if you can't do it, ODIN will likely fail. At any rate, the attempt is on you. I can't be responsible for what happens.
Click to expand...
Click to collapse
I did it just trying to get cyanogen to work with wifi and data/cellular to keep. However my phone is dev now and TWRP is installed.

ThatRoo said:
I did it just trying to get cyanogen to work with wifi and data/cellular to keep. However my phone is dev now and TWRP is installed.
Click to expand...
Click to collapse
Then you're good to go.

douger1957 said:
Then you're good to go.
Click to expand...
Click to collapse
Just frustrated right now trying to get Wifi to work. It looks like its suggested to try Flashing MM Stock, Reroot and Re-unlock bootloader here:
http://forum.xda-developers.com/not...t/howto-bootloader-unlock-upgrade-to-t3398144
Then use TWRP after all that.

ThatRoo said:
Just frustrated right now trying to get Wifi to work. It looks like its suggested to try Flashing MM Stock, Reroot and Re-unlock bootloader here:
http://forum.xda-developers.com/not...t/howto-bootloader-unlock-upgrade-to-t3398144
Then use TWRP after all that.
Click to expand...
Click to collapse
Just make sure you're paying attention to what you're flashing. There are only three roms in the verizon development section that are able to utilize the 6.01 bootloader and modem. JASMINE ROM, PAULPIZZ 6.01 Beta and Cm13. The other roms are ports based on 5.1.1 so you may need to stay on the previous setup until more roms are updated
Tip the OP usually states what works/does not work and updates when things are fixed . The information changes quickly so sometimes you may need to read the thread from the end back to the beginning to see if your issues have been addressed

It was actually super simple once I found the thread on how to go back to 5.1.1 then how to take that and go unlocked w/ marshmallow chain. Last thing to figure out is disabling OTA on Jasmin ROM

[Qualcomm][MetroPCSXT1765]Do Not Take ANY Updates From March 2018 Onward

***Update August 31, 2018*** It has been reported from @Juanito216 that he's locked out of TWRP after taking an update, and this update is well past March when I first reported it. Be advised not to TAKE THE UPDATES OR YOU WILL LOSE ROOT/TWRP!
***Note*** Made a note of this under my Noob Metro PCS Guide.
This is for a MetroPCS XT1765 phone.
So the significant other finally let me get ahold of their phone (same model) because of bugs on the Stock Rom, and FINALLY I was able to unlock the bootloader. However, this phone had the forced update from March. (My phone didn't have this problem as I rooted out the box).
If you take the update, you have to push the Bootloader unlock. Motorola will give you the unlock code, but I had to keep doing it with the code until the phone "unlocked". Didn't happen on my phone out the box.
If you take the update, you WILL NOT BE ABLE TO FLASH Magisk v14. I also was unable to install @squid2 TWRP new version. Error 1 kept popping up. Did let me install the superuser and the no-verity just fine but you don't have root.
The only solution you will have to get root is to flash a custom rom and then flash Magisk. But the update did something to the root.
Hope this help you guys.

You seriously had to say that again??
Sent from my XT1766 using Tapatalk
---------- Post added at 12:44 AM ---------- Previous post was at 12:43 AM ----------
Articul8Madness said:
***Note*** Made a note of this under my Noob Metro PCS Guide.
This is for a MetroPCS XT1765 phone.
So the significant other finally let me get ahold of their phone (same model) because of bugs on the Stock Rom, and FINALLY I was able to unlock the bootloader. However, this phone had the forced update from March. (My phone didn't have this problem as I rooted out the box).
If you take the update, you have to push the Bootloader unlock. Motorola will give you the unlock code, but I had to keep doing it with the code until the phone "unlocked". Didn't happen on my phone out the box.
If you take the update, you WILL NOT BE ABLE TO FLASH Magisk v14. I also was unable to install @squid02 TWRP new version. Error 1 kept popping up. Did let me install the superuser and the no-verity just fine but you don't have root.
The only solution you will have to get root is to flash a custom rom and then flash Magisk. But the update did something to the root.
Hope this help you guys.
UPDATE 4/1/2018 - After finally being able to unlock the bootloader of the significant other and root it, I found something interesting. - if you take the pestering update that rolled out in March, you will be UNABLE to flash Magisk v14. You can flash No Verity and Superuser well, but you WILL NOT HAVE ROOT. The only alternative I have is to flash a custom rom and then flash Magisk.
Do Not Take the Update.
Click to expand...
Click to collapse
PimpMy5Ton said:
You seriously had to say that again?? Everyone I know uses custom roms anyway, just sayin'
Sent from my XT1766 using Tapatalk
Click to expand...
Click to collapse
Sent from my XT1766 using Tapatalk

PimpMy5Ton said:
You seriously had to say that again??
Sent from my XT1766 using Tapatalk
---------- Post added at 12:44 AM ---------- Previous post was at 12:43 AM ----------
Sent from my XT1766 using Tapatalk
Click to expand...
Click to collapse
Well, I said that because not everybody is going to read my guide. I've had such hell with this phone while others have sailed through it, I'm giving ALL the MetroPCS folks a head up. Most of the development is done on other variants of the phone as is, and a lot of info that is out there while Qualcomm does not really apply to us. Consider me like an ambassador for the Metro folks, lol.
If somebody said it, I haven't caught it in the threads. And honestly, hopefully this thread opens up a discussion on how we can flash back. I was completely unable to go back to the original stock on the significant other's phone AFTER that update too. Been tinkering with it since I posted that. Can't even flash some of the boot.img files successfully either that I explained in my post (in case of emergency section).
That update is something seriously nasty.
Update: Aaah...I see what I did there. Man, I'm doing too much in the middle of the night. Sorry bout that copy and paste thing. I was taking notes and writing and tinkering with the phone. Didn't want to forget the problem exactly.

Took the latest update that I know of and now I can't flash TWRP anymore. Locked the bootloader and everything back up because I thought I was going to sell this phone. It didn't sell and I decided to unlock it again and root. I hope some type of way someone can find out how to install TWRP after taking all the updates. This Metro PCS variant kind of sucks for rooting\roming.

Juanito216 said:
Took the latest update that I know of and now I can't flash TWRP anymore. Locked the bootloader and everything back up because I thought I was going to sell this phone. It didn't sell and I decided to unlock it again and root. I hope some type of way someone can find out how to install TWRP after taking all the updates. This Metro PCS variant kind of sucks for rooting\roming.
Click to expand...
Click to collapse
No, Juanito, no! That's why I said don't take the update. But now I'll correct it in my OP. Thanks for the info.
Can you follow my guide and see if you can get TWRP from ADB shell?

Im running Lineage OS, I can boot TWRP, but can no longer install it. I thought I would never root the phone again. So now at this point, I might not take it to stock ever again.

Juanito216 said:
Im running Lineage OS, I can boot TWRP, but can no longer install it. I thought I would never root the phone again. So now at this point, I might not take it to stock ever again.
Click to expand...
Click to collapse
I know you say you can't install TWRP. But can you load it through ADB Shell? If you can there's hope.
Did you start doing all this on Lineage or on Stock, or started back to stock and it crashed. You can always reunlock the bootloader through the Moto prompts on their website. It shouldn't be blacklisted.

Error when installing stock OS: SW REV. CHECK FAIL(BOOTLOADER) DEVICE: 7. BINARY: 6

Recently I rooted my S9 and installed Lineage OS but I didnt like it and decided to swap back to the stock OS. I used Frija to get the .tar.md5 files for Odin but once I select all the files and hit start the log in Odin loads up to system.img then stops and I get the SW REV. CHECK FAIL(BOOTLOADER) DEVICE: 7. BINARY: 6 error on my phone. Any idea on how to fix this? I'd really appreciate some help as I'm going to be travelling soon and I need my phone for it and I'd prefer not to use Lineage OS. Thanks in advance.

Do you have an At&t branded phone? SM-G960U?
I am having a very similar problem. A customer came in and was having issues with device. I told them to back up, wipe, and update device. That didn't work so I tried a full flash with ODIN. Now I can't get the phone to boot at all and it says, "Secure Check Fail : Modem" and "Unauthorized software visit nearest AT&T blah, blah,..)
I think it is because AT&T has pushed out the latest update(OCT. 18th), but the Odin files are not out yet. According to:
https://www.att.com/devicehowto/tutorial.html#!/stepbystep/id/stepbystep_KM1253489?make=Samsung&model=SamsungG965U
G960USQS7CSI5 is the latest FW. If you google it, there are only four results.

Yep, the problem was the phone was on the latest FW. Newer firmware was just uploaded a few days ago.
I flashed:
G960USQU7CSJ2_G960UOYN7CSJ2_CHA
and now I'm booting again.
Your problem is that your firmware is too old. Basically, you are trying to downgrade your FW. The phone is basically saying, "Hey, I have bootloader 7, I won't let you install something lower than that."

ma777 said:
Your problem is that your firmware is too old. Basically, you are trying to downgrade your FW. The phone is basically saying, "Hey, I have bootloader 7, I won't let you install something lower than that."
Click to expand...
Click to collapse
^^^^ this ^^^^
the Odin error is telling you that youre trying to flash a revision of the bootloader than was last installed on the phone. to to sammobile.com/fimrwares and get the one with the correct bootloader for your specific phone and flash that.
also download the firmware with the frija tool or samfirm. trust me, its literallt 5x faster than a direct download from the site. The 5 min it takes to get samfirm up and running is worth it, believe me on that.

I may be new to this, But I just Flashed a SM-g960u, That Had Bootloader7 locked on it, When I would go into download mode I would see FRP ON, and this Firmware G960USQU7CSK6. So I downloaded a Combination Firmware file. Used Odin Patched, Flashed it there is a guide out there. Restarted into the Settings, Turned on Developer mode, USB Debugging, and Was able to change OEM-Software install. Then I was able to load this phone after, with G960USQS7CSI5 with ease My first flash and I had to bypass a FRP and a Bootloader lock. Now I should be able to flash this to the U1 version unlocked and be good! If you need any help I did just do this last night I can guide you in the right dirrection. Litterally I had no help from here as in asking questions I am pretty savy. So you need to make sure your Version has the "7" in the Same Place. Also after I enabled those things while in the phone before Flashing it I chose the Factory Reset from within, SO it erashed EVERYTHING except Download Mode and the Combination Firm Loaded. Meaning I should have been able to flash to anything I wanted

Nightfox619 said:
I may be new to this, But I just Flashed a SM-g960u, That Had Bootloader7 locked on it, When I would go into download mode I would see FRP ON, and this Firmware G960USQU7CSK6. So I downloaded a Combination Firmware file. Used Odin Patched, Flashed it there is a guide out there. Restarted into the Settings, Turned on Developer mode, USB Debugging, and Was able to change OEM-Software install. Then I was able to load this phone after, with G960USQS7CSI5 with ease My first flash and I had to bypass a FRP and a Bootloader lock. Now I should be able to flash this to the U1 version unlocked and be good! If you need any help I did just do this last night I can guide you in the right dirrection. Litterally I had no help from here as in asking questions I am pretty savy. So you need to make sure your Version has the "7" in the Same Place. Also after I enabled those things while in the phone before Flashing it I chose the Factory Reset from within, SO it erashed EVERYTHING except Download Mode and the Combination Firm Loaded. Meaning I should have been able to flash to anything I wanted
Click to expand...
Click to collapse
got no help here? how so? I see you got the info you needed to get the phone back up and running properly via asking about it here.
with regard to the bootloader version of 7 in your case, it is a very known thing that whatever bootloader version youre on, you cant go backwards from.
In either event, im very glad that you got it up and running!!

Youdoofus said:
got no help here? how so? I see you got the info you needed to get the phone back up and running properly via asking about it here.
with regard to the bootloader version of 7 in your case, it is a very known thing that whatever bootloader version youre on, you cant go backwards from.
In either event, im very glad that you got it up and running!!
Click to expand...
Click to collapse
Getting no help was meant I hadn't Posted asking Questions, I read everything ya'll put up and I was able to do it on my own without continuing to ask, so Yeah I did get help here but not by asking only reading what is available

downgrade samsung sm-g570m
Nightfox619 said:
I may be new to this, But I just Flashed a SM-g960u, That Had Bootloader7 locked on it, When I would go into download mode I would see FRP ON, and this Firmware G960USQU7CSK6. So I downloaded a Combination Firmware file. Used Odin Patched, Flashed it there is a guide out there. Restarted into the Settings, Turned on Developer mode, USB Debugging, and Was able to change OEM-Software install. Then I was able to load this phone after, with G960USQS7CSI5 with ease My first flash and I had to bypass a FRP and a Bootloader lock. Now I should be able to flash this to the U1 version unlocked and be good! If you need any help I did just do this last night I can guide you in the right dirrection. Litterally I had no help from here as in asking questions I am pretty savy. So you need to make sure your Version has the "7" in the Same Place. Also after I enabled those things while in the phone before Flashing it I chose the Factory Reset from within, SO it erashed EVERYTHING except Download Mode and the Combination Firm Loaded. Meaning I should have been able to flash to anything I wanted
Click to expand...
Click to collapse
hi Nightfox619.! I have a samsung sm-g570m and I trying to downgrade to binary 2 when I flash with odin it give me this error message "sw rev check fail bootloader device 7 binary 3" any idea how can I downgrade .??

pol1345 said:
hi Nightfox619.! I have a samsung sm-g570m and I trying to downgrade to binary 2 when I flash with odin it give me this error message "sw rev check fail bootloader device 7 binary 3" any idea how can I downgrade .??
Click to expand...
Click to collapse
Ok so first you should post I'm your devices threads but that aside. Here's what's up. You can't downgrade the error shown is saying your device is on a bit 7 binary. Your trying to flash a bit 3 binary which isn't even 2 you need to find your respective firmware in a bit 7 or higher.

TheMadScientist said:
Ok so first you should post I'm your devices threads but that aside. Here's what's up. You can't downgrade the error shown is saying your device is on a bit 7 binary. Your trying to flash a bit 3 binary which isn't even 2 you need to find your respective firmware in a bit 7 or higher.
Click to expand...
Click to collapse
thanks 4 answering bro and sorry 4 using this thread.! so definitely I can't downgrade 2 a lower binary than 7..?

pol1345 said:
thanks 4 answering bro and sorry 4 using this thread.! so definitely I can't downgrade 2 a lower binary than 7..?
Click to expand...
Click to collapse
Like 99.9%. That's what that error is. The bootloader is blocking downgrade

pol1345 said:
thanks 4 answering bro and sorry 4 using this thread.! so definitely I can't downgrade 2 a lower binary than 7..?
Click to expand...
Click to collapse
yes, if you get a firmware version matching the one last installed on your device, itll go right thru and boot just fine. Goodlock is finally working on all modules for A10 as well. Maybe we will see more development occur with this shutdown going on. Let us know if you run into any trouble, the error you were getting is totally resolvable!

at the end I give up on it..! my internet 2 slow 4 go downloading & trying rom after rom.! i am from venezuela.

Nightfox619 said:
I may be new to this, But I just Flashed a SM-g960u, That Had Bootloader7 locked on it, When I would go into download mode I would see FRP ON, and this Firmware G960USQU7CSK6. So I downloaded a Combination Firmware file. Used Odin Patched, Flashed it there is a guide out there. Restarted into the Settings, Turned on Developer mode, USB Debugging, and Was able to change OEM-Software install. Then I was able to load this phone after, with G960USQS7CSI5 with ease My first flash and I had to bypass a FRP and a Bootloader lock. Now I should be able to flash this to the U1 version unlocked and be good! If you need any help I did just do this last night I can guide you in the right dirrection. Litterally I had no help from here as in asking questions I am pretty savy. So you need to make sure your Version has the "7" in the Same Place. Also after I enabled those things while in the phone before Flashing it I chose the Factory Reset from within, SO it erashed EVERYTHING except Download Mode and the Combination Firm Loaded. Meaning I should have been able to flash to anything I wanted
Click to expand...
Click to collapse
I have S20+ running Android 11 with U7 Binary. I tried downgrading to Androi 10 which has Binary U5. Now I have downloaded the Binary U5 file. But in some video, he is telling that you should download the Binary File with the same number as it is currently installed in your phone, which in my case is U7. So? Am I supposed to download U7 Combination Binary file and flash it in order to downgrade to Android 10
OR
Should I flash the U5 Combination File and flash the Android 10 AP, CSC, BL, HOME ???

Someone has Combination file to G960F with bootloader SF (Version 15)?

Can't install TWRP on my SM-G9600

Hello, I have been trying to install TWRP on my S9 with snapdragon processor. I'm running pie with november security patch, I enabled OEM on dev settings and followed this guide (https://forum.xda-developers.com/ga...development/twrp-3-2-1-0-sm-g9600-s9-t3803297) but I can't make it pass. I saw some other guides that skip CROM Services (anyway I can't run it as it closes right after I open it). In download mode I got KG Status Checking and OEM Lock : Off but Odin can't flash the twrp I'm using latest version and tried on 2 different PC's even tried the patched version of Odin (runned both as admin) but nothing happens just fails and keep failing. Tried different ways like 15h in the past 3 days but I can't finally make it

Hey Alessandro,
I was just wondering if you were able to overcome from this.
I am having the same issue.
Thanks

stormkingpin said:
Hey Alessandro,
I was just wondering if you were able to overcome from this.
I am having the same issue.
Thanks
Click to expand...
Click to collapse
What seems to be the issue

TheMadScientist said:
What seems to be the issue
Click to expand...
Click to collapse
I have been trying to install TWRP on my SM-9650 (Brazil). I'm running the latest A10 stock rom. I enabled OEM on dev settings and followed this guide (https://forum.xda-developers.com/ga...er-development/g9650zhu6dta7-android-t4051751) but I can't make it pass. CROM app wont work. Though in Dev Options it says my Bootloader is already unlocked. In download mode I get the "only official released binaries are allowed to be flashed" in Odin while trying to flash the twrp.

stormkingpin said:
I have been trying to install TWRP on my SM-9650 (Brazil). I'm running the latest A10 stock rom. I enabled OEM on dev settings and followed this guide (https://forum.xda-developers.com/ga...er-development/g9650zhu6dta7-android-t4051751) but I can't make it pass. CROM app wont work. Though in Dev Options it says my Bootloader is already unlocked. In download mode I get the "only official released binaries are allowed to be flashed" in Odin while trying to flash the twrp.
Click to expand...
Click to collapse
What about in download mode your rmm state or kg status

TheMadScientist said:
What about in download mode your rmm state or kg status
Click to expand...
Click to collapse
OEM LOCK: OFF
RMM STATUS : Prenormal
KG STATUS : Checking

stormkingpin said:
OEM LOCK: OFF
RMM STATUS : Prenormal
KG STATUS : Checking
Click to expand...
Click to collapse
Rmm is why
It's that 168 hour crap. Look up how to bypass rmm status prenormal. It's a security feature.

TheMadScientist said:
Rmm is why
It's that 168 hour crap. Look up how to bypass rmm status prenormal. It's a security feature.
Click to expand...
Click to collapse
Will do. I was reading about that issue.
Tried all the non-paid options and none seems to work.
I'll wait for the 168 hour window then.
Thanks again!

stormkingpin said:
Will do. I was reading about that issue.
Tried all the non-paid options and none seems to work.
I'll wait for the 168 hour window then.
Thanks again!
Click to expand...
Click to collapse
Supposedly if you flash the combo file. Then disconnect all radios. Roll back the clock, turn off auto time update flash firmware. No sim, setup. Then connect to internet and let auto time update it will bypass. Not 100% sure

TheMadScientist said:
Supposedly if you flash the combo file. Then disconnect all radios. Roll back the clock, turn off auto time update flash firmware. No sim, setup. Then connect to internet and let auto time update it will bypass. Not 100% sure
Click to expand...
Click to collapse
That is what I tried, even after flashing Stock Pie
It wont clear RMM State from prenormal. Apparently it works for some people.
I am fairly familiar with this custom ROM thing, but apparently no donut for me this time.
No worries, having to be patience is by no means a struggle for me.
Just bought this device. Will play around with the Q Stock ROM until RMM is normal.
Nonetheless, very nice of you to reply.
You sir have a good soul.

stormkingpin said:
That is what I tried, even after flashing Stock Pie
It wont clear RMM State from prenormal. Apparently it works for some people.
I am fairly familiar with this custom ROM thing, but apparently no donut for me this time.
No worries, having to be patience is by no means a struggle for me.
Just bought this device. Will play around with the Q Stock ROM until RMM is normal.
Nonetheless, very nice of you to reply.
You sir have a good soul.
Click to expand...
Click to collapse
Well you landed with a great set of devs. We got stock q rooted. Where all modding on. Plus los 17.1 was just released in beta. So it's a great time to read up on it all. There is also a Qualcomm telgram support group for help on some of the stuff. You can find that I think in the twrp and los threads

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