Well, we've been in Skype and direct EMail communication because I was one of few seen online. :|
Time for some finger wags ....
1. always ... always ... always ... leave at least one user set to manual that has admin levels of access. The logical user is id 2 as it was the first user account created with moodle was installed. Leave that account alone ... set to manual and know that even if you forget the password, the password can be re-set via moodlecode/admin/cli/reset_password.php
2. if you hack core code ... keep a copy of what you hacked handy.
3. Always research upgrades ... plugin compatibility etc. *before* pulling the trigger. Matter of fact, best to try out things with a clone of the production site ... especially when doing any 'hyperjump' ... ie, skipping versions. Many upgrades are not 'business as usual'.
4. Always have a full site backup and know how to restore without any minor upgrade in the series.
5. Learning to use git witd updates and upgrades **will simply** admin life!!!
End finger wags ...
Going forward .... the mdl_user table must be manually manipulated to make the transition from old Google Auth logins to new Oath2. While site is 3.2.x use mysql to query mdl_user table for id, auth.username,firstname,lastname,email.
Compare that output to the user at ID 2.
Make a list of accounts that are admins ... one can work with changing various columns for all users while excluding those users who are admins. Hint: the 'not in' parameter ... which would include the id numbers of those whose accounts should remain manual and are admin levels.
Op has dodged a bullet this time ... better not play Roulette!
Thanks for sharing back what you did for others to try if they find themselves in the same issue.
Bet if you looked at the theme you were using you'll find the hack that was added to get the 'red button' for Google to show. With that line in config.php, please remember that overrides what one does in Moodle admin interface for themes - can't change theme.
'spirit of sharing', Ken