[Google Pixel 3 Questions & Answers] DragonFire1024:
Okay so a couple of things I think updating to the latest known firmware version of this phone may have locked out my access to the little door that we have stumbled upon here but I haven't had time to sit down and look over the settings from page one which is what I intend to do on my next couple of days off later this week. However not all will be lost because from what I have been able to research in the meantime we don't even need this mode for for us to be able to flash the Titan chips firmware. So here is the deal Google was supposed to patch this possibility of exploit in a previous version of the firmware a few years ago. Supposedly the patch was supposed to include a fix that would not allow you to downgrade the chips firmware to a version that was exploitable, but if you have been following any of my posts you will see that I am easily able to achieve that goal and was able to successfully downgrade the chips firmware to aversion that was exploitable though that doesn't necessarily mean it is exploitable in the sense where the bootloader can be unlocked or the device can be rooted. There are several files inside the vendor image where there is clear indication that Citadel controls the OEM lock on the device. Unfortunately these files cannot be retrieved from the vendor directory on the device unless you have root access otherwise they have to be extracted from the stock firmware images. This also likely means` that even if we acquire these files successfully they probably will not execute properly on the device without Root access.

Now here's another possibility that I have been investigating on the side because in the beginning it didn't seem to be able to have the possibility of working due to a bug in Google's code which did not allow for this to take place. There is the option of using a dynamic system image through the developer settings known as dynamic system update or DSU. This little tool allows for the device to boot a generic system image to what extent it will allow the booting of a generic system image I am unsure however I was able to test this with a generic system image by Google and the device successfully booted this image. If I am not mistaken so I could be wrong these images come available pre-installed onto the device as an option when on Android 12 the latest firmware available it will then download the actual file and it will take quite a bit to load on to the device before I will ask you to restart and will boot the generic image. In previous earlier versions of this option the problem was the image would not flash properly or booked properly and cause VB meta to become corrupted. This doesn't actually harm or cause any damage to the device whatsoever but it does stop the DSU from overloading until you properly reflash the original stock firmware of the device. The potential way we could take with this is finding out if an edited generic system image to provide root access and other features would be allowed to boot onto the device without corrupting VB meta or any other partition images. If it does happen to allow the possibility of an image to what extent in other words would we be able to only modify an image issued by Google or could we load a generic system image onto it such as a custom ROM like lineage or even the remix ROMs? This I also do not know as I have not been able to experiment further with this option because of the failure of VB made up and previous attempts before upgrading to the latest firmware.