Wow? I'm not lying. My GPS now works great! Sure I'll take any additional information. I use Google maps heavily 6 days a week. It was constantly having issues getting a lock and now it works all the time and gets a lock quickly. And to the other users If your phone is already rooted its no big deal to rename a file then change it back if it doesn't work for you.
(edit, sorry for the long read, but it looks like I got busy rambling and got off topic in some areas, my bad)
I never meant you were a liar at all, if it works for you that's great but I would never recommend this to anyone, but since it's working by all means stick with it if you chose... I have been working with the AICP development team on GPS issues with G2 and have a pretty decent understanding of it.
First off, GPS issues are not common, especially among HTC devices, but of course a few handsets have had issues over the years, and some have issues and others don't. If you had seven in a row, that's just bad luck, no, more than bad luck, that's horrendous luck. I have had about the same number of devices, the only one that gave me issues was the LG G2, and I have found a work around for that for most people.
Let's tackle your fixes one at a time... First aGPS... Assisted GPS is a system that is used to help the phone lock on to satellites and is used to improve startup time and get a fix faster. It is Mobile Station Based and uses Secure User Plane Location information from a network server (usually Google, sometimes the carrier like T-Mobile, or the manufacturer like Nokia) in conjunction with NTP time servers to help the GPS receiver in the phone lock on to satellite signals faster, once the lock is achieved, only timeserver data and GPS are used. "Officially" aGPS should never slow down lock, although it will not help unless you using a valid time server for your area, you have a stable mobile data connection (for NTP timing reference), and your aGPS data is current. That being said, it has been shown slow down a lock, if the aGPS data is severely outdated or your reference timeserver is unavailable or severely inaccurate. All this information is stored in your /etc/gps.conf file. Disabling aGPS is generally considered a bad idea, if the chipset supports it and the gps.conf file parameters are good enough for it to work.
Google location services (ie. 'WiFi' location) and mobile network location are not part of GPS, although Google Location Services will use GPS and mobile location services (ie. Mobile Network location or tower based location) as part of it's location information... Mobile Network Location is an approximate location service used to determine within ~5000m your general location based on your carrier's tower's, a common use of this service is weather widgets and other services which do not require specific location information.
Google Location Services is a service that runs in the device that aggregates it's own location information based on SSID's that are visible cross referenced to a proprietary database, plus mobile network location, and GPS data to provide either an approximate location or precise location based on the app's request to it for location information. This service really likes an active data connection to work, but will use other sources to get location. Many apps now days use this service as the default location provider, often with GPS or MNL as a backup location provider. Maps uses this service as it's primary location provider, and GPS or MNL as a backup if it is unavailable. I will just barely touch on this but many people dislike this service, because they feel Google is "spying" on their location (this can easily be disabled in Google Services Location settings, but will take away some location based features of apps like Now/Search), and it can be a battery drainer. In and of itself it does not draw a lot of battery, all the other stuff it does and apps that request information are the real problem, like Now wanting to know where you are constantly. The WiFi scanning it does also is not a battery draining thing, it uses a low power scanning only mode, leaving WiFi available for scanning when sleeping is not a significant source of battery drain.
Now to the real heart of your fixes... delete/rename gps.conf... If you do this you have taken away the GPS systems "instructions" on how to function, like where to look for aGPS data, what time server to reference, what format of SUPL data and where to find it, what provides the NEMA data, etc. etc.... basically, all the location and carrier specific settings for it's variant of your device. Deleting this file forces the GPS system to disable most of it's advanced features and operate in what is essentially a dumb mode, without access to anything that isn't hard coded in the firmware. And what is hard coded into the firmware varies a lot, since this is proprietary data, little is known of what exactly is each individual chipset specifically, some handsets seem to have a full-functioning generic set of defaults, others seem to have nothing but bare-bones GPS signal only configurations. Usually, if you buy a handset from a your carrier (or one specifically for their network) the gps.conf is somewhat optimized for use in their service territory, if you have an unlocked handset or one from a different carrier or significantly different geographical region, the gps.conf file will need to updated with the appropriate information, typically the timeserver is the most important here.
Modern smartphones rely on a mobile data connection, GPS can suffer severely if you don't have an active connection to help get the lock.
I am really glad your fix worked for you, but I have never heard of anyone else doing it, and I would be really hard pressed to recommend to someone else either. It would be better to figure out what is wrong with your setup and fix it... Your GPS can be very fast and extremely accurate if it is setup correctly.