Instead of downloading a risky repack from an unknown source, you can build your own xmldefault.cnf.xml from scratch. This is the definitive way to solve the downloading loop.
If your Cisco IP Phone is stuck "Downloading xmldefault.cnf.xml" and you suspect a repack issue, follow this checklist:
Verify file naming. The TFTP server is case-sensitive. XMLDefault.cnf.xml is not the same as xmldefault.cnf.xml (though phones typically request lowercase).
Check file size. A valid XMLDefault.cnf.xml is usually 1KB to 8KB. If your repack has a 0-byte file, delete it.
Monitor phone logs. For a 7960, press Settings > Status > Network Statistics > TFTP Server. Verify the IP matches your repack’s TFTP server.
The "Factory Reset" repack fix. On a 7960/7940:
When a Cisco IP phone boots up, it attempts to contact the TFTP server to download its configuration. If the phone displays a message like "Downloading XMLDefault.cnf.xml" and gets stuck, reboots, or fails to register, it indicates a specific breakdown in the communication between the phone and the Call Manager (CUCM) or TFTP server.
From a working phone of the same model:
Via OS Administration > File Management > TFTP File Management:
Or via CLI:
utils tftp put XMLDefault.cnf.xml