For those still stuck on RC19....Please read and respond back!!!

While looking at the android-info.txt in the RC30 update I noticed this:
board=trout
reject serialno=HT7*|HT80*|HT81*
require version-baseband=1.22.12.29
require version-bootloader=0.95.0000
require version-cpld=4
 
Can you please check your baseband version?  You can check this by going to menu > settings > about phone.  It is right under Firmware Version.  Reason I ask is because mine is on 1.22.12.28.  It seems like most who haven't received the update are on RC19.  And those who have manually updated to RC29 seemed to get a message saying RC30 is ready to be applied.  I am wondering if because our baseband version is not matching up with what the patch is looking for, it's not downloading and applying.
 

I got RC30 early this morning, like not long after midnight, and was previously on RC19

Hmmm...well then...that may debunk my possible lead...thanks for ruining my theory...lol

EDIT

OK, so get this.  I checked for an update by using anycut to device info.  Nothing popped up.  I decided to manually do the the RC29 update.  I wanted to see what would happen after that point.  After rebooting the phone, I went back to device info.  There was nothing there.  However, as soon as I clicked the button to check for an update, voila, it began downloading RC30.  Also, while it was still downloading RC30, I checked my baseband version and it was indeed up to 1.22.12.29.
 
This tells me a few things.  While some have have received an update right from RC19 to RC30, if you manually update to RC29 chances are you will bring down RC30 right after that.  I cannot say 100% sure that if you do the RC29 update that you will get RC30, as that could be coincidental.  I don't think it is, but it is possible.
 
Any way for any T-Mobile Techs to look into this?  It could be an Issue with the RC30 pushout where it is looking to first see if you are on the correct baseband.

I just checked, now that I have RC30 my baseband is 1.22.12.29

So RC30 didn't change the baseband version to .30

I noticed that too.  But do you believe it is only coincidental that before I did the RC29 upgrade I did not find any upgrades to apply, and then after RC29 it found RC30?

To me, that is way to coincidental.  I mean, the entire process to update to RC29 took all of 5 minutes.  And the Baseband does not equal the build number.  What could be more likely is this:  T-Mobile (and Google) have 2 separate RC30's.  One is for those still at RC19, in which it will take time to get out to people as it is again picking phones randomly on who to send it to.  Then there are those who were at RC29.  These might be the phones that technically needed the security fix in RC29.  If the server sees that you have RC29 you will automatically get the update as it is more critical for that build.

Could be more guessing on my part, however, like I said, too coincidental (even with my one off test).

I'm on 28, with build rc19. 

I really do think there are two separate RC30 releases, with two separate roll out plans.  I looked at the size of the files I had access to download, the RC29 which was posted a while ago is 45MB.  RC30 from RC29 which was posted here is only 4MB.  This shows that the one posted is only a partial upgrade from 29 to 30.  However, there are people who have gone from RC19 to RC30.  For that to even be possible, it would need to have the data from RC29 included with the RC30.  This file would be much larger than 4MB.  It would be atleast 45MB.  So this then falls in line with my theory of 2 separate rollouts.  They can let anyone who already had RC29 download the next time the phone syncs with the server since it is a relatively small download.  However, they are probably doing a longer roll out for those on RC19 as a 45MB file would be a bigger hit on the server.

I think technology is not an absolute, so things can go wrong.  I would take the device into a corporate store for correction if you have concerns.

First off, there is really only one update that was RC28. While that update was being randomly pushed out a bug was found so they fixed the bug and switched everyone to RC29. The bug found wasnt a huge deal so they could take some time with those that already got RC28. Then they found that everything being typed was being entered at the command line thus causing things like reboots. This was a huge deal and needed to be fixed right away. Thus everyone who had RC29 needed RC30 fast. Now this whole time the original update random pattern is still being followed. Those with RC19 dont have the bugs of RC28 or RC29 and therefore arent in dire need of either of the last two updates.

Are there two different RC30 updates? Possibly, or the system knows to only send whats needed.

As to getting updates the only thing i can suggest is using the anycut app to make a shortcut to device info. Check to make sure there were no errors in downloading an update. I had this happen when i got RC29, I checked device info to see if there was any indication of RC30. It listed a bunch of errors so i had it check for update and it started to download RC30 again. Shortly after i got the notice that there was an update avail. So check the shortcut info out, its possible there was an error during the check.

HTH