peashooter14 said:
Ok, so what is the least painful way to get back to Threshold 2? Will Threshold 2 eventually bump up to the 10.0.14267.XXXX range, or do you have to wait for Redstone to hit production?
For your first question: there is no "least painful" way, I'm afraid you will have to reflash your device with Windows Device Recovery Tool if you want to return to 10586.xxx branch (Threshold 2).
As for your second question, not sure to fully understand. Threshold 2 devices ("retail", aka non insiders) will upgrade to Redstone 1 (14XXX) when Redstone is released officially later this year. In other terms, VVM support on dual sim devices, etc. is coming to retail devices, but later, when RS1 is the new stable branch (it's the development one, or unstable). As for non W10M native devices (let's say a 640), as long as their baseline ROM on Microsoft servers are WP8.1 based, they won't get redstone builds (even in fast ring). But once they're upgraded officially to Windows 10 Mobile (TH2, 10586.xxx, probably 10586.164), then they'll be eligible to redstone fast ring.
I can understand your frustration of having been pushed to the development branch because you were in Fast Ring. Note that for non W10 devices, this won't happen or at least less. For instance, I have a Lumia 535, which was on Fast Ring. But to get the latest Insider builds I had to switch to Slow or Release Preview. If the 535 is soon officially upgraded to W10M and Microsoft pushes Redstone via the Fast channel, I won't receive it unless I explicitly switch to Fast (or until they push Redstone on Slow). That's the advantage of older devices lol