Hi mbrsolution. I had it locked down to prevent visitors from seeing while it was messed up.
I finally solved. For anyone in a similar boat (hope not), there may have been an easier way but after almost 2 days of trying easier ways I did this:
Via phpadmin (cPanel) I searched thru the database tables and changed the prefix back to “wp_”. There is a search-and-replace function in here that works on, at least, a table by table basis. I deleted the plugin via ftp. I deleted all table columns (?) that were related to the plugin (had aio… in it). I downloaded the version of WP that the site was using (which was the most current) and replaced all the folders/files via ftp except the content folder. I then, to be overly safe, created a new user for the database and added in the missing info in the wp-config.php file. You can search for the how-to on that. Not hard.
That restored the site back to the way it was with the exception of still not allowing me to access the WP dashboard. I could login via a homepage plugin that I had, but got a permission error when trying to access /wp-admin.
At this point, I threw in the towel, hired a pro via freelancer.com and for $25, he fixed the rest in about 40 minutes. Though the first fix didn’t give me Administrative privileges though it acknowledge me a an admin. He fixed that too.
So the biggest mistake I made was not backing everything up, as the plugin strongly suggests.
Let me extra clear for anyone thinking about this plugin: It is beyond amazing. It does everything that it promises to do and more. It has so many options that it is mind boggling and if you only understand a fraction of them, your site will still be far more secure. I have used every function at one time or another on another site with ZERO issues. This is incident, though unfortunate, was an anomaly and likely due to something specific about the site I was implementing it on.
