Develop Bugs

Secure Boot: Enabled (no RPMB)

Today I rebooted my device into bootloader mode to check some stuff and noticed that Secure Boot display "no RPMB" next to "Enabled". What does it mean?

Banan PL said:
Today I rebooted my device into bootloader mode to check some stuff and noticed that Secure Boot display "no RPMB" next to "Enabled". What does it mean?
Click to expand...
Click to collapse
Did you recently receive a refurbished device? "No RPMB" in effect means your bootloader will automatically re-lock itself on reboot. I believe it has something to do with a replaced main board.
Sent from my Nexus 5X using Tapatalk

SlimSnoopOS said:
Did you recently receive a refurbished device? "No RPMB" in effect means your bootloader will automatically re-lock itself on reboot. I believe it has something to do with a replaced main board.
Click to expand...
Click to collapse
Yep, I received it yesterday, they replaced motherboard. So it's mean no more mods? That's the reason why I bought this device. Can it affect DRM protected multimedia, because I can't watch videos in Play Movies app?
Sent from my Nexus 5X using XDA Labs

Banan PL said:
Yep, I received it yesterday, they replaced motherboard. So it's mean no more mods? That's the reason why I bought this device. Can it affect DRM protected multimedia, because I can't watch videos in Play Movies app?
Sent from my Nexus 5X using XDA Labs
Click to expand...
Click to collapse
There's a temporary workaround if you're a stock rooted user:
Here's a reddit link regarding a workaround:
https://www.reddit.com/r/nexus5x/comments/5hj0r0/bootloop_after_lg_replaced_mainboard_bootloader/
However, this isn't helpful if you're a regular custom rom user as you'll notice in the details.
As for DRM, I think so. I have been looking for confirmation about DRM being impacted by this "No RPMB" status. I've only seen one other person outright mention this. It's hard to find users who get this issue and even harder to get them to respond on my inquiry on whether they can use DRM apps. What issue are you seeing with Play Movies? Can you open the app? Or are you given an error message of any kind? I'm interested from the troubleshooting perspective so that I can help ID when others have the same issue. Also, can you confirm this affects other multimedia apps with DRM protection? I was thinking that Hulu, Netflix, HBO would be apps that utilize DRM if you have subscriptions.
Sent from my Nexus 5X using Tapatalk

I don't care much about custom OS, at least for now. I can open Play Movies browse feed and library, but it ain't play any video (Couldn't fetch license (error -1)). Unfortunately I don't have subscriptions in these services, but I used local TV streaming app that uses DRM and it showed error 203 (whatever that means). I tried also watch movies from Google's app on YouTube, no luck.
Sent from my Nexus 5X using XDA Labs

Hi there, same case, no rpmb after replacing motherboard, Netflix won't start (error 500 device failure). Tried with stock but now PureNexus rom.
Sent from my Nexus 5X using Tapatalk

send phone on warranty "No possibility to use value based on drm license" after LG should fix your mb

tuningsea said:
send phone on warranty "No possibility to use value based on drm license" after LG should fix your mb
Click to expand...
Click to collapse
Thanks for the advise, however I want to find a way to create this Rpmb at home, for users who warranty has gone, still looking..
Sent from my Nexus 5X using Tapatalk

Netflix norpmb
can anybody of you with the norpmb issue test the netflix app again ? after the oreo update its working again for me. confused

kmike243 said:
can anybody of you with the norpmb issue test the netflix app again ? after the oreo update its working again for me. confused
Click to expand...
Click to collapse
I confirm it's working. Has anybody found a different solution for no rpmb from the one posted on reddit?
Inviato dal mio Nexus 5X utilizzando Tapatalk

kmike243 said:
can anybody of you with the norpmb issue test the netflix app again ? after the oreo update its working again for me. confused
Click to expand...
Click to collapse
Netflix app will crash few times, try to hide with Magisk Btw. Re open few times, like 10 and login. Then you will be redirected to the homepage.
Envoyé de mon Nexus 5X en utilisant Tapatalk

hi guys, i have the same no rpmb model
how do i fresh install oreo as the bootloader keeps relocking? is there a way? also i'd like to root!

androidfreak11 said:
hi guys, i have the same no rpmb model
how do i fresh install oreo as the bootloader keeps relocking? is there a way? also i'd like to root!
Click to expand...
Click to collapse
I'm also looking for a solution all the time
but I haven't found one yet

openyourmind said:
I'm also looking for a solution all the time
but I haven't found one yet
Click to expand...
Click to collapse
Unlock bootloader, flash newer version of it and newer radio. Reboot bootloader, unlock it again*, flash rest of the stuff.
*In my case OEM unlock toggle doesn't disable itself after bootloader lock itself. It also stays enabled even after factory reset.
To get root simply flash TWRP instead stock recovery and install SU package of your choice. You can also run customs on locked bootloader and use Jolla's multirom if you want, just keep TWRP installed**.
**Honestly I prefer 4core TWRP modded, it might be life saving one day.
If you use Oreo and want to downgrade it to Nougat or Marshmallow just flash system and vendor in TWRP.
NOTE ABOUT RADIO:
Oreo's radio MIGHT not work on every Marshmallow based ROM (example: XOSP, multibooted Stock - they doesn't detected SIM card also baseband is unknown in my case) it work on CM13, not sure about call quality. It work on every Nougat based without issues.
Sent from my Nexus 5X using XDA Labs

Banan PL said:
Unlock bootloader, flash newer version of it and newer radio. Reboot bootloader, unlock it again*, flash rest of the stuff.
*In my case OEM unlock toggle doesn't disable itself after bootloader lock itself. It also stays enabled even after factory reset.
To get root simply flash TWRP instead stock recovery and install SU package of your choice. You can also run customs on locked bootloader and use Jolla's multirom if you want, just keep TWRP installed**.
**Honestly I prefer 4core TWRP modded, it might be life saving one day.
If you use Oreo and want to downgrade it to Nougat or Marshmallow just flash system and vendor in TWRP.
NOTE ABOUT RADIO:
Oreo's radio MIGHT not work on every Marshmallow based ROM (example: XOSP, multibooted Stock - they doesn't detected SIM card also baseband is unknown in my case) it work on CM13, not sure about call quality. It work on every Nougat based without issues.
Sent from my Nexus 5X using XDA Labs
Click to expand...
Click to collapse
i was able to flash stock rom via fastbook (had to unlock bootloader 3 times, everytime it rebooted, but it worked tho)
only problem, when i install twrp and press reboot phone, it will only boot to twrp! and i have to type in a decription password or something, because i unlocked the bootloader and android should have deleted everything, but didn't cause i would have to reboot for that, but it will only boot in twrp .. so yeah, that's where i got stuck .. any idea?
otherwise i'll resell this thing and maybe get an htc 10 or a nexus 5x with stock mobo

Hi all,
I currently have stock 8.1 installed on my refurbished Nexus 5X with NO RPMB, and would like to install a custom ROM (Pixel2ROM from argraur).
If possible, I prefer NOT to get root. Maybe it helps passing safetynet.
As I understood, I should do following steps:
- Unlock bootloader
- Flash stock ROM. -> Is this step necessary since I already have stock 8.1 installed?
- Flash TWRP
- Reboot directly into TWRP
- Wipe data and cache
- Flash custom ROM
- Flash Magisk or superSU -> Without this step, would TWRP get replaced with stock recovery? Is Magisk or superSU better?
Can you please check if the steps are right, and answer the 3 questions.
Thanks!
EDIT: I tried without flashing the stock ROM nor root. Everything went fine and TWRP remains installed.

Hello I created a thread trying to help with this cases.. If someone with better knowledge see a better option, please say it there to update it..
NO RPMB (how to install TWRP, a new ROM and using Magisk)

Hi Pedro,
what will happen in case of rom update? e.g. Nightly?

ciorci said:
Hi Pedro,
what will happen in case of rom update? e.g. Nightly?
Click to expand...
Click to collapse
Without the magisk part its like you are using a normal rom with a normal boot image, just need to dirty flash the new rom..
With the magisk part it would need to make a new patched boot image..
So at least you will need to extract the new boot image of the new rom file, use it on magisk and patch it, after that I dont know... to my method work the first time it was needed a clean installation, but didn't tried it yet because the new update of my rom developer needed to be a clean installation due to many changes on the rom, so i didn't have opportunity to try update normally but when I do I will update my thread with what to do on that case and if it works..

How to downgrade from Android P to Oreo with a locked bootloader

Hi guys,
So, I installed the Android P preview via an OTA sideload to try it out, and I find it worse for my battery and it's bugging me. I decided to go back to 8.1, downloaded the stock march image, but can't unlock my bootloader for some reason. The button in Developer tools does not work (it worked before on Oreo). No big deal, I downloaded the march OTA package to flash it, but no... The device detected the image had an older timestamp, so it won't update.
Now I'm stuck with Android P and don't know what to do.
I can't unenroll from the beta program, as at this time, there is no beta program, officially.
Anyone else had this issue and figured a way out of it? Any help is welcome.
Thanks in advance.
EDIT: After second factory reset, and this time, not setting an unlock pin, or fingerprint, the OEM unlocking switch worked and I was able to unlock my bootloader and flash 8.1 back to my device.
If a moderator deems this thread useless, delete at will. I just hope it helps someone.

granets said:
Hi guys,
So, I installed the Android P preview via an OTA sideload to try it out, and I find it worse for my battery and it's bugging me. I decided to go back to 8.1, downloaded the stock march image, but can't unlock my bootloader for some reason. The button in Developer tools does not work (it worked before on Oreo). No big deal, I downloaded the march OTA package to flash it, but no... The device detected the image had an older timestamp, so it won't update.
Now I'm stuck with Android P and don't know what to do.
I can't unenroll from the beta program, as at this time, there is no beta program, officially.
Anyone else had this issue and figured a way out of it? Any help is welcome.
Thanks in advance.
EDIT: After second factory reset, and this time, not setting an unlock pin, or fingerprint, the OEM unlocking switch worked and I was able to unlock my bootloader and flash 8.1 back to my device.
If a moderator deems this thread useless, delete at will. I just hope it helps someone.
Click to expand...
Click to collapse
Can you please let me know what steps did you follow once you unlocked the bootloader?
Like did you use the factory image or the march OTA did the trick?
I unlocked the bootloader but flashing 8.1 failed and I'm stuck with P and a few apps not responding on P

April Security Update - Two Versions? April 1st vs. April 5th

Many users reported TWO different variants of the April Security Update. One which is labeled April 1st and another April 5th. I am confused by this as well, I want to get all the hotfixes but my build does not match Google's OTA page.
I'm using a Pixel XL 2 and I have April 1st version on TELUS network. I got it yesterday night, the download was 46.6 MB My build number is OPM4.171019.015.A1 BUT per Google official OTA website it says I should have 8.1.0 (OPM2.171019.029, Apr 2018)
Can anyone shed some light on these TWO variants? Many Rogers users got April 1st but a few got April 5th. Bell seems to be all on April 5th. Telus/Koodo seems to be a mixed bag also.

The one you're referring to on the Factory Images page is the stock release for non-carrier Pixel 2s.
Sometimes carrier branded releases come out the same time, but usually they're released after. Carrier branded releases will have different version numbers, as you can see in the previous release history.

ilal2ielli said:
The one you're referring to on the Factory Images page is the stock release for non-carrier Pixel 2s.
Sometimes carrier branded releases come out the same time, but usually they're released after. Carrier branded releases will have different version numbers, as you can see in the previous release history.
Click to expand...
Click to collapse
That still doesn't explain why I got April 1st variant. I don't even know if I got the new hotfixes.
Even Google were surprised to hear that. They told me that eventually. The update is pushed through anyways from Google channels. They escalated the issue.
But first time I see two variants

Waibashi said:
That still doesn't explain why I got April 1st variant. I don't even know if I got the new hotfixes.
Even Google were surprised to hear that. They told me that eventually. The update is pushed through anyways from Google channels. They escalated the issue.
But first time I see two variants
Click to expand...
Click to collapse
Then I direct you here:
http://reddit.com/r/GooglePixel/comments/8abtyt/april_update/dwxnpu5

Two versions a couple of days apart of actually pretty common.

ilal2ielli said:
Then I direct you here:
http://reddit.com/r/GooglePixel/comments/8abtyt/april_update/dwxnpu5
Click to expand...
Click to collapse
That's explained a lot, thanks!
BUT for the Pixel security update. That means im missing on all the bugfixes if I understood correctly... It says here that all the hotfixes are included in. The 2018-04-05 version.
https://source.android.com/security/bulletin/pixel/2018-04-01

The April 5 release contains all of the security patches and bug fixes plus the current updates for Pixel 2, Pixel, Nexus 6P, Nexus 5X and Pixel C. The April 1 release allows OEMs to apply specific patches to correct problems found with AOSP. This has always been the case and I can remember only one time I only had the 1st patch to apply to my Nexus.

stevemw said:
The April 5 release contains all of the security patches and bug fixes plus the current updates for Pixel 2, Pixel, Nexus 6P, Nexus 5X and Pixel C. The April 1 release allows OEMs to apply specific patches to correct problems found with AOSP. This has always been the case and I can remember only one time I only had the 1st patch to apply to my Nexus.
Click to expand...
Click to collapse
So what would explain I have only received the April 1st update ? Is it possible to have two updates in one month? I never noticed that.
This is the first time I get the 1st patch too. I'm not the only one

I was able to update to the 4/5 patch at 8PM, 4/4. I'm on the Pixel 2 XL. Which model do you have? Have you done anything to the stock software?

Pixel 2 XL 64GB Stock OS.
I used the Beta Enrollment in the past, but this is a fresh phone from RMA.

Unable to update Latest Pack
i have already unlocked bootloader, rooted with magisk.
now for latest update, i have uninstalled magisk, trying to flash factory image in fastboot mode. but unable to do so.
Please let me know how to do ?
Max memory error is coming . i have read to update factory image need to critical unlock bootloader.
please suggest ?
Device : Pixel 2 XL

navi_j said:
i have already unlocked bootloader, rooted with magisk.
now for latest update, i have uninstalled magisk, trying to flash factory image in fastboot mode. but unable to do so.
Please let me know how to do ?
Max memory error is coming . i have read to update factory image need to critical unlock bootloader.
please suggest ?
Device : Pixel 2 XL
Click to expand...
Click to collapse
You don't have to uninstall magisk to update your factory image. Have you also unlocked the _critical partition with "fastboot flashing unlock_critical"?? This WILL wipe your phone if you haven't!!
What type of pc are you using?? Laptops have been know to have difficulties with this due to improper USB cables. The pic is the procedure I use each mont to update the stock OS without wiping data :good:

Badger50 said:
You don't have to uninstall magisk to update your factory image. Have you also unlocked the _critical partition with "fastboot flashing unlock_critical"?? This WILL wipe your phone if you haven't!!
What type of pc are you using?? Laptops have been know to have difficulties with this due to improper USB cables. The pic is the procedure I use each mont to update the stock OS without wiping data :good:
Click to expand...
Click to collapse
i have seen screenshot and did the same process but failed in cmd.
i havent unlocked the critical partition . is it required to flash factory image ?
i am using windows 10 Dell Inspiron 13 7000 series.
thanks

navi_j said:
i have seen screenshot and did the same process but failed in cmd.
i havent unlocked the critical partition . is it required to flash factory image ?
i am using windows 10 Dell Inspiron 13 7000 series.
thanks
Click to expand...
Click to collapse
Yes. You have to unlock_critical to fastboot factory images to allow the bootloader to update ?

Badger50 said:
Yes. You have to unlock_critical to fastboot factory images to allow the bootloader to update
Click to expand...
Click to collapse
OMG
can i use directly this command now or i have to use some process to do ?
thank you sir, you saved my time , i have wasted almost 3 hours trying different methods but failed everytime.

navi_j said:
OMG
can i use directly this command now or i have to use some process to do ?
thank you sir, you saved my time , i have wasted almost 3 hours trying different methods but failed everytime.
Click to expand...
Click to collapse
Just put your phone in bootloader mode, connect to pc, open up your command prompt, and run the command...fastboot flashing unlock_critical....
Again, this Will completely wipe your phone! ?

Has GPS lock issue been fixed?

Seems my thread got hijacked

Question related to "After updating, you will not be able to downgrade..." message

Question related to "After updating, you will not be able to downgrade..." message
Hope you guys are safe and well.
Currently my A50 on August update. I have no problems with this update but I like to update to Android 10 for additional features. I'm reluctant to update because of this message. I'm afraid that if I had problems or something wrong with the new update, I won't be able to go downgrade to August update.
So, Is it really impossible to downgrade using Odin with an official firmware?
I'm coming from iOS and hence the fear of updating. As you may know, iOS downgrade is impossible when Apple sign-out the old software.
Thanks in advance.

Most major OS updates (i.e. from Android 9 to 10) also update the 'bootloader', which is a little piece of software that initializes your device, and runs before the system can even start (when you turn your phone on).
Once the bootloader is updated, it's often impossible and certainly not recommended to downgrade the OS, since you may permanently brick your device.
If Android 10 is out for your device model (eg. A505G in my case), just go ahead and update. I don't have any issues with it whatsoever, in fact it has fixed quite a few bugs (wifi connection would frequently drop for me in Pie with February/March updates, and now it doesn't anymore).
Greetings.

pripyaat said:
Most major OS updates (i.e. from Android 9 to 10) also update the 'bootloader', which is a little piece of software that initializes your device, and runs before the system can even start (when you turn your phone on).
Once the bootloader is updated, it's often impossible and certainly not recommended to downgrade the OS, since you may permanently brick your device.
If Android 10 is out for your device model (eg. A505G in my case), just go ahead and update. I don't have any issues with it whatsoever, in fact it has fixed quite a few bugs (wifi connection would frequently drop for me in Pie with February/March updates, and now it doesn't anymore).
Greetings.
Click to expand...
Click to collapse
But can't I backup the boot loader too? Also, I heard that the official firmware includes the boot loader and therefore I won't have problems downgrading. I'm confused.

Screen not responding after update
Hi. I updated to the new Android 10 which my phone prompt me to install. But after updating, my screen is not responding anymore. I already tried to restart and factory reset. What can i do regarding this? Thank you very much!

sheidyly said:
Hi. I updated to the new Android 10 which my phone prompt me to install. But after updating, my screen is not responding anymore. I already tried to restart and factory reset. What can i do regarding this? Thank you very much!
Click to expand...
Click to collapse
Try to flash the ROM manually using ODIN

redymedan said:
Try to flash the ROM manually using ODIN
Click to expand...
Click to collapse
I'm sorry but I'm new to all of this and I seem to read some comments saying the phone was bricked after flashing.
And if I will try flashing, do I use the old firmware or the new one?
Thank you so much!

mistpsn said:
But can't I backup the boot loader too? Also, I heard that the official firmware includes the boot loader and therefore I won't have problems downgrading. I'm confused.
Click to expand...
Click to collapse
I think... and I could be completely wrong, but it keeps track of the highest version of bootloader you installed. So it will not allow you to boot if you flash the older one. However, I am not sure how it behaves if the bootloader is unlocked.

If anyone have the same concerns I had. I found out that only security updates seems to have this message and risk bricking your phone in case you downgrade to lower version. Some people confirms that they were able to downgrade without any problems from android 10 to android 9 on their A50.
It also made sense that there are no problems since the warning message only included with security updates. The android 10 Update change list have no warnings related to downgrading to older versions.
March security update had the warning message. And I had to do the security upgrade before the android 10 update was available OTA.

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