EDIT: Hah, seems I hit post just as you got ahold of Customer Service. I'll leave this here, though, cause this is bound to happen to someone else.
A friend of my husband is going through the same thing... however, the guy is too stubborn to get on the phone and actually call SE; he'd rather complain for hours about a service he's paying for but can't access. Which is likely exactly what you'll have to do:
Sit on the phone for a few hours until you get through the CS queue.
They CAN verify your account without you logging into the Mog Station or SE's site (when my husband's account was hijacked, SE utterly locked down his account for over a month but they could access it whenever he called); they'll ask you account information and for you to email a picture of your ID to prove ownership. Once they verify your ownership, they can remove the code for you.
Once you get that taken care of and get your account back, when you put the security token back on you need to remember to save the emergency removal code in a place where you can access in case of another phone update, loss of phone, etc. This was actually part of the instructions given when you set up the token ( >___>; sorry...). I have mine saved on my desktop, in one of the cloud services I use (in case of both iPod and laptop failure/loss), and onto an external harddrive.
On the bright side... this SHOULD help prove that the security token concept does work; you can't access it until you get that authorization code or prove ownership to SE <_<
A friend of my husband is going through the same thing... however, the guy is too stubborn to get on the phone and actually call SE; he'd rather complain for hours about a service he's paying for but can't access. Which is likely exactly what you'll have to do:
Sit on the phone for a few hours until you get through the CS queue.
They CAN verify your account without you logging into the Mog Station or SE's site (when my husband's account was hijacked, SE utterly locked down his account for over a month but they could access it whenever he called); they'll ask you account information and for you to email a picture of your ID to prove ownership. Once they verify your ownership, they can remove the code for you.
Once you get that taken care of and get your account back, when you put the security token back on you need to remember to save the emergency removal code in a place where you can access in case of another phone update, loss of phone, etc. This was actually part of the instructions given when you set up the token ( >___>; sorry...). I have mine saved on my desktop, in one of the cloud services I use (in case of both iPod and laptop failure/loss), and onto an external harddrive.
On the bright side... this SHOULD help prove that the security token concept does work; you can't access it until you get that authorization code or prove ownership to SE <_<
