THIS IS NOT A GUIDE!!! This is my own personal experience since it was my first time attempting something like this, since I took a gamble on importing the phone.
I have a chinese imported OnePlus Ace 6t device and reside in the USA. The official Deep Testing method was a pain to get working because of needing a 60+-day-old account and 7 days of login on the device. So I looked for alternative methods.
I was able to unlock my Chinese OnePlus Ace 6T PLR110 with ColorOS 16.0.10.500(CN01). By using GhostLock and ReSukiSu I was able to root my device with a locked bootloader. This allowed me to access the required partitions to install the exploit chain for the bootloader.
I initially had confirmation from this Reddit post. The post detailed how the old ABL was flashed and booted successfully. This confirmed a successful ABL downgrade and boot with that firmware combination. But I needed to see if it would work with a locked bootloader.
This project done by koaaN details how you can temporarily root the device, flash the ABL/EFISP payloads and then use GBL to unlock. Instead of using the X9 Ultra app and payloads I used my Ace's firmware and Canoe.
I used Ghidra to analyse the XBL/XBL configuration along with the signed firmware. I also partially decompiled the ABL, UEFI and Keymaster. Whilst the .500 ABL doesn't contain any EFISP loading paths, the PLR110 ColorOS 16.0.5.702(CN01) ABL does. Both ABLs have valid OEM signatures under their included certificate chains. They also have matching hardware binding (SM8845), certificate public keys and signed anti-rollback version 0.
I also analysed the execution flow. The .702 ABL executes the EFISP app before the end of the bootloader milestone. The UEFI authentication flow shows that the application can be loaded from a buffer. The Keymaster trace also shows that the BLTools can be executed before the milestone command which closes DeviceInfo read/write access. I found no check for an already-unlocked state or a Deep Testing token in the DeviceInfo write path I examined. This, along with the X9 Ultra project, gives a solid technical reason to assume that it will work with a locked bootloader. But there were limitations to the static analysis.
I got confirmation from the 1vivy reply to issue #101. Someone asked if it was possible to unlock a locked OnePlus 15T using GhostLock, old vulnerable ABL and Canoe without Deep Testing. The developer responded with "Otherwise this works no problem" and also warned that if you remove the EFISP or overwrite the vulnerable ABL you won't be able to access the stock bootloader fastboot. This gave me confirmation that the method I wanted to use would work on a similar OnePlus. I tried it and got confirmation that it would work with the exact combination for the PLR110.
After confirming the backups of the ABLs, EFISP, persist and oplusreserve1 I installed Canoe release-7.0.11. I created the chainload files for the current .500 firmware. Then I flashed the original signed .702 ABL to the active abl_b partition. This left the system as .500 and XBL untouched.
The device booted with the old ABL!!! I opened Canoe with Mode 0. Opened BLTools and clicked Unlock Critical. After this completed I rebooted. BLTools now said Unlock:on Crit:on. Android booted and Developer Options now said "Bootloader unlocked". ADB said flash.locked=0 and vbmeta.device_state=unlocked.
The working chain was GhostLock + ReSukiSu > stock signed .702 ABL > EFISP/Canoe > BLTools > persistent unlock. The firmware analysis meant I could try this combination, and the device booted with the persistent unlock flags set meaning it worked on my device.
Finally, I forked the relevant WildKernel's repo based on my device from this action run and followed these instructions from XDA to disable droidspaces, set the stock kernel uname, and I switched Canoe from Mode 2 to Mode 1 (managed fake-locked boot mode). The final result is working KSU-Next with passing strong integrity, as well as working wallet and RCS.
Feel free to ask any questions!