HOWEVER - I gotta feeling my ISP is blocking - not sure - tried the BRIDGES METHOD (TOR solution) - but I get a "Vidalia goes half way" bar - then stalls...nothing cures it - tried a different wifi hit - they may have it blocked as well.
To better understand what is happening, activate a copy of the Bundle that you have not attempted to reconfigure. Then select Vidalia's "Message Log" and "Advanced" options to see the steps that Vidalia takes to initialize the Bundle. The last step should be "Bootstrapped 100%: Done". At that point Vidalia will activate Aurora, which should eventually display a tab that verifies that you are connected to the Tor network. It can take several minutes to get the Bundle working.
So...perhaps its the PROXY SETTINGS? I saw something where you set them all to localhost 8118 - and the last one to 9050 - tried that - same problems - halfway - stalls - hangs - no TOR.
Those settings were for using a stand-alone Tor with an existing browser. The Tor Browser Bundle is self-contained and preconfigured. See Aurora / Edit / Preferences / Advanced / Connection Settings to see how the Bundle configures Aurora's proxy.
If you used the new -t option to build the Bundle with Tor listening on port 9050 instead of a random port and if you also have the regular Tor extension installed, the two versions of Tor may be interfering with one another. Either remove the regular Tor extension or rebuild the Bundle without the -t option.
I also don't see a "TOR BUTTON" or any other indicator that the Aurora browser is using TOR....
See Aurora / Tools / Add-ons / Extensions. You should always visit
https://check.torproject.org/ to determine whether or not your browser is using the Tor network.