Technically incorrect. If they move to a new security, it may work, but it may not.
The security I'm referring to is in the CDT.bin file - currently, it is what is preventing people from reverting to a working, bootable .905 build.
If we were to get a new leak / final OTA with a new (read: incremented) CDT.bin security, we theoretically should be able to use HoB to install it - but if the final OTA script actually checks for the version of the CDT.bin that is already on the phone, we get hosed, b/c we cannot install the one it will be looking for - installing the previous CDT.bin after having updated to .235+ on your phone breaks on boot, even when booting directly into the bootloader. I am the one that tested trying to revert .235 down to .905 extensively. If you leave out the CDT.bin (which is one of the things that HoB leaves out as it does not factor into the updater-script) you can flash the other components of .905 and fool the updater-script in the leak / OTA into thinking that you have a valid .905 system (which has the right files, even though there is a mismatch between the bootloader, CDT.bin, etc., so it is unable to boot) and allow the upgrade to proceed.
I'm pretty sure you know all this already, but I'm reiterating it for the benefit of all the readers of this thread.
As I said, there is a very unlikely chance that this will happen, but the chance does exist - which is the ONLY reason I am not advocating everyone throw caution to the wind and install .247. Otherwise, if there were a guaranteed way to make sure you could take the OTA when it came out no matter what leak you were on, I'd be pushing everyone onto the latest every single time.
