V0latyle said:

If your bootloader is locked, one of the dumbest things you can do is try to install potentially unstable firmware. If something goes wrong, you won't be able to recover your device.

If you did anyway, the only way you should try to return to stock is with the Android Flash Tool, which should work as long as OEM Unlocking is enabled.

If you're on a device that cannot be unlocked, you should wait the Android 13 official release.

I got my device from T-Mobile and yes the bootloader is locked. I was on the A13 beta and opted out. I am now back on A12. Yes it took some extra steps to get back to A12 but you can do it with a locked bootloader.

truckerdewd said:

I got my device from T-Mobile and yes the bootloader is locked. I was on the A13 beta and opted out. I am now back on A12. Yes it took some extra steps to get back to A12 but you can do it with a locked bootloader.

Not everyone has been so lucky. Glad it worked for you, though.

roirraW edor ehT said:

Not everyone has been so lucky. Glad it worked for you, though.

True. I posted the steps I followed in this thread.

Android Beta to Factory Reset mucked up, plus a bunch of troubleshooting I've already tried

Okay. The android beta program was messing with an app I use regularly so I backed up my phone on google 1 and all that fun stuff then did the opt out and just ran stuff like it was supposed to. Then, it got stuck in fastboot mode and said that...

forum.xda-developers.com

Lughnasadh said:

I'm a firm believer that unless you are using some apps (mostly banking apps) that will absolutely not work with these enabled, that before doing anything you should toggle on "OEM unlocking" and "USB debugging", regardless if you're using Stable or Beta or whatever you're doing. It will open up a bunch of possibilities to recover your phone if you hit a glitch in the matrix.

For me it's the very 1st thing I do when getting a new phone.

I'm not sure toggling these would trip device security. As long as the bootloader remains locked the device should meet HARDWARE_BACKED integrity (key attestation), and if the firmware is factory the device should meet BASIC integrity as well.

V0latyle said:

I'm not sure toggling these would trip device security. As long as the bootloader remains locked the device should meet HARDWARE_BACKED integrity (key attestation), and if the firmware is factory the device should meet BASIC integrity as well.

We are not actually talking about tripping device security or being able to pass Play Integrity API, etc.. Even with the bootloader locked, apps can still check to see whether OEM Unlocking and USB Debugging are enabled, and if so, make it so the app fails to work properly, if at all. Apps can even check to see if you have Developer Options enabled.

USB debugging definitely does interfere with some apps being able to work. I have to disable it to use one of my apps and many others have reported the same for a variety of apps. I have also seen having OEM Unlocking enabled interfere with some apps as well, as reported by others.

In my case I just disable USB Debugging, use the app, then re-enable when done using the app.

gpvecchi said:

Sorry, but if you just enable the OEM unlock? Then, just in case things go bad, you can unlock bootloader...

Basically yes, as long as you have an unlockable bootloader, can get into fastboot, etc..

For example, if things go haywire for you and you have OEM unlocking enabled, you can use Android Flash Tool to help recover your device. Or you can use fastboot to manually unlock the bootloader and flash whatever.

Lughnasadh said:

We are not actually talking about tripping device security or being able to pass Play Integrity API, etc.. Even with the bootloader locked, apps can still check to see whether OEM Unlocking and USB Debugging are enabled, and if so, make it so the app fails to work properly, if at all. Apps can even check to see if you have Developer Options enabled.

USB debugging definitely does interfere with some apps being able to work. I have to disable it to use one of my apps and many others have reported the same for a variety of apps. I have also seen having OEM Unlocking enabled interfere with some apps as well, as reported by others.

In my case I just disable USB Debugging, use the app, then re-enable when done using the app.

Click to expand...

Yeah I think my brain was somewhere else. Interesting though.

bobby janow said:

@Lughnasadh Just curious which apps? I've not come across any.

Of the ones I use, Spectrum TV requires USB Debugging to be disabled.

Lughnasadh said:

Of the ones I use, Spectrum TV requires USB Debugging to be disabled.

I obviously do not use Spectrum TV. I almost always have debugging on and have never come across a need to turn it off, I actually didn't even know it was a thing. But it makes sense since it is an opening into the device. One thing I have noticed when I flip the OEM switch though. I only keep it active when I'm either sideloading or, heaven forbid, install a beta or custom rom. After it's done and booted I flip the switch back off and it has me reboot for added security that is not available when the switch is active. What's that all about?

bobby janow said:

I obviously do not use Spectrum TV. I almost always have debugging on and have never come across a need to turn it off, I actually didn't even know it was a thing. But it makes sense since it is an opening into the device. One thing I have noticed when I flip the OEM switch though. I only keep it active when I'm either sideloading or, heaven forbid, install a beta or custom rom. After it's done and booted I flip the switch back off and it has me reboot for added security that is not available when the switch is active. What's that all about?

Yeah, if you go through the Magisk, SafetyNet and similar threads you'll see people who have come across apps that won't work when USB Debugging is enabled. It's really up to the app developer as to whether it checks for it or not.

I'm not entirely sure why after you switch OEM Unlocking off that it has you reboot as I've never switched it off once switched on. My guess would be that a reboot is needed to set ro.oem_unlock_supported to 0. But that's just a guess.

V0latyle said:

If your bootloader is locked, one of the dumbest things you can do is try to install potentially unstable firmware. If something goes wrong, you won't be able to recover your device.

If you did anyway, the only way you should try to return to stock is with the Android Flash Tool, which should work as long as OEM Unlocking is enabled.

If you're on a device that cannot be unlocked, you should wait the Android 13 official release.

The way Google implements there otas and installs now is a fail safe, the devices will not be bricked what so ever, if on stock that is