I have a still working updated 4a which I use for a second phone account I have because it is so pleasant to carry around. I bought it late in the 4a production cycle and I think it must therefore have a battery that is different in some way to that included with earlier models and that is the reason the update did not brick my phone. I think what happened here is Google knew of a flash bang fault in those batteries which touch on wood later ones did not have so sent a targeted update to hash those specific early devices for safety. The question is not did Google intentionally scupper those phones but when did it know about the fault. My guess is it discovered it during production and that is why later models are altered and now remain usable after the update. The upshot of that is Google had some idea they were faulty very early on but chose not to recall them then but instead only disable them very late in their life. This is just speculation of course, I could just have been lucky and Google could have just recently found some fault with aging batteries.

Yes as with almost everything the ability to do a thing is just a function of how much you want to do it.

You can always see the signal in the noise, that is the point of the signal and therein lies the rub.

It will all end with us back on dialup speeds once the counter-DAITA throughput machine learning de-obfuscation analysis of defense against AI guided traffic analysis of proxy anomised packets starts. I think I might just read a book.