[Samsung Galaxy Nexus] DX///M:
Alright, I'm still trying to understand what your situation is and what you want to do. below i just comment along.

And I appreciate any correction and criticisms you guys have for what i put down here. I can be wrong.

Yes, you usually don't OTA after manual programming. Because OTA is automated programming, and what we do here is its counterpart.

yes, at least also for VZW/PagePlus. My understanding is that a phone would only use one data profile in certain environment (area, reception, carrier), and would only switch to alternative profiles when the first (which is "profile 0") is not accessible.

There is only one MSID. The "000-000-xxxx" you mentioned is just a dummy, or something automatically generated when phone sees your correct MSID. Keeping the keys as same as you pulled from your donor is perfectly fine.

And a little wiki here: MSID = MIN; It doesn't have to be identical as MDN, which is your phone #.

whether you have 1x data or not, should be depending on the prl and data menu programmed on your phone (can be done through ETS too)

That seems an obvious mistake here - you seem to look for a solution that your method won't lead you to. Why I'm saying so?

(1) "Hybrid Mode" basically gives your phone ability to use both 1xRTT and EvDo data. Since your phone was programmed only to have 1x speed for some reason, toggle to this option from any 1x speed won't improve your data speed - cuz 1x was your max speed back then.

(2) "EHRPD 1x" = 1x EvDO; "CDMA", according to the menu layout, I guess it's "1x RTT". "EvDo" should be referring to "EvDo Rel 0" and "Rev A/B" according to the network this phone can access. In short "EvDo" mean what we call "true" 3G speed.

(3) when toggling to anything other than "EHRPD 1x" or "Hybrid Mode", your signal bar became a blank triangle, this is because the phone didn't find any network. It could be your manual programing was not right, in terms of keying in items responsive for data connection; or simply due to a wrong prl, which the phone uses to locate itself in carrier's network and define itself a connection and speed.

Because you mentioned earlier, you always had 1x speed, after following whatever guides. That suggests the data programming in your phone is only correct in terms of 1x EvDo speed. So there's no surprise when you toggled to other data connection and returned no network.

This menu you talked about here, only allows your phone to see certain connection protocol supported with current carrier in current area/reception. It doesn't program the items/keys in your phone to be able to connect. You have to have those programming done correctly before trying to ask carrier network recognize it. So to sum up, choose "Hybrid Mode", and other modes wouldn't do any good, but only as a diagnostic tool.

Again, this is a wrong solution. What ROM really doesn't matter, AS LONG AS it keeps the manual programming menu (*#*#3282#*#*, and similar stuff). All recent Team EOS ROM and maybe CM10 Rom (as I heard) has kept that menu. So flashing ROM won't do anything to your carrier network programming. Stock ROM for sure has that option though.

Radio does matter, but as long as you are on the ones mentioned in OP, you are fine. Flashing stock ROM would change radio version, and that is normal and as supposed. Because stock ROM has radio included. Custom ROMs has may (or may not) contains every component identical/alternative to that in stock ROM. And flashing a custom ROM would only replace components packed in that custom ROM; components not included in the stock ROM would stay as stock.

Many has issue struggling with the programming, because many of us, me included, don't fully understand it all, and as an end-user, we don't really care to understand it all, but only the parts needed to do what we want to achieve. If we understand "it" properly, we can all find a good job in either QualComm, or VIA. So no shame here, and we just need to be careful about what others say in their posts. Some are right, some are wrong, some are partially right, or conditionally right, whatever.... there are too many situations.

But i felt in your case, at least shown in your toggling data connection type for 3g speed, complaining OTA messing up manual programmed keys, and also flashing many ROMs, I feel you are so eager that you tried out as many things as you can do, rather than to understand what the solutions you tried can do, or to think about what you should/need do. So this convince me about what I mentioned in my previous post - take a break, day or two, think about what you have done and what is needed to be done; what are useful, what are not. Find answers to a question, rather than go through everything you can do, most of which are sort of irrelevant.

If you have manually programmed Epic D700, which I assume you used some donor phone to program it to some carrier rather than Sprint (SPH-D700 is designed for Sprint as I remember), then you are awesome!!! Epic is a phone using Qualcomm chip for communication. So I believe you can easily program most Qualcomm chip equipped CDMA android phones.

Qualcomm chip is so widely used in mobile phones, so that there are way more information than that for VIA chip phones, which includes GNex, Droid Charge, and maybe some others I'm not aware of.GNex uses a different chip, thus it requires a different software "ETS" to manually change keys/items in your phone (written in that chip). Because that is the only communication tool you have between your desire and your phone. Using a Qualcomm designed programming software - QPST and QXDM, just can't let you talk to GNex, right. And you also need to understand why other commonly used programming tools (DFS, CDMA WS, etc) won't work on GNex - because those are just tools have only Qualcomm programming integrated, but not VIA. Those are just more user-friendly as they are designed to improve that. QXDM is almost as confusing as ETS, because those are not designed for us consumers and end-users. They are, I believe, internally used by Qualcomm and VIA technicians/employees.

I had to admit I sound very mean here, although it's nothing personal. Fight back with me if you want. And any comments with merit are welcome. I definitely can be wrong, especially in the "Hybrid mode" part, I used wikipedia and google to educate myself about differences between things like "1xRTT" and "1xEvDo". The latter was faster, :)

Once again, I'm puzzling what you tried to do here, so you want to program a VZW GNex to Sprint? Or Boost? I don't quite follow your situation, so earlier I gave some suggestions that are probably very misleading, I'm sorry if any of those happened...