Localization thinks are known to be able turn Cisco phone into brick.
Even typo in Dictionary Server Script option can brick the code (I didn't tested it by self, obviously). Read SPA504G won't boot up after misconfiguration
Cisco guys never responded.
I assume that the code handling localization is buggy and phone may abend during load of dictionaries. It may be caused by either typo in Dictionary Server Script option, or by broken dictionary files or by wrong dictionary files (dedicated to other firmware that the one you are using or different model).
As phone firmware abends during boot all the times, you have no access to either WWW UI nor phone's local menu. So there is no way to delete cached dictionary files nor the phone's configuration. There is way to do nothing.
So phone is effectively dead. SOS recovery procedure doesn't apply here as there is valid firmware image inside the phone. In advance, even SOS recovery procedure seems not to delete saved configuration nor cached dictionary files.
- If you have support contract, open ticket with Cisco. You can try to open ticket even without suppport contract. But you should not put so much hope into it.
- If the phone is covered by warranty, return it to seller. Don't disclose the issue has been caused by configuration to them.
- You are out of luck otherwise as far as I know.
Note that not only broken/inappropriate files may render the phone unusable. Also improper configuration may cause the same result. I have a SPA508 that I downgraded to older firmware. Such dowgrade has been succesfull, but the firmware choke on saved configuration (saved configuration is not deleted during update). So phone is just brick now - like your phone. Cisco is not willing even confirm that misconfiguration may brick the phone forever. So no one should expect it will be patched.
