[Touch Pro2 CDMA] cajunflavoredbob:
1. You can still brick your device. You are taking a risk by flashing a non-stock ROM onto your device. You should take the time to become familiar with the terminology and functions of the device before getting too far ahead of yourself. You haven't even scratched the surface of your device yet. Normally, if something goes wrong, booting into bootloader and flashing a stock ROM can clear it up. It's generally helpful to understand what exactly you are doing to your device BEFORE you do it.

If you don't understand something, ask. Be sure to search around before asking, though. Users here have lots of knowledge they can pass on to you if you show them that your are willing to do the work. If you show that you are willing to help yourself to information, most members here will bend over backward to help you solve a problem.

2. You're using a ROM not designed to run on your network. Cellular carriers often restrict or remove parts of the OS as they are intended to be used only on their network. The ROMs you've flashed are for CDMA only networks. The USC ROM does not have an option to use GSM networks to my knowledge, and the Verizon ROM manages it automatically once the device is SIM unlocked.

3. You may not be overwriting the part of the memory where this is stored. You should learn to perform task29 between flashes of any ROM. task29 is a tool that will format the internal memory of the device. This means that it erases everything, including the ROM image from the internal memory. This essentially gives you a clean slate to work from.

After doing this, you can boot back into bootloader and flash a new ROM without worrying that your data isn't fully removed. Make sure you read, read, read, on what and how task29 is and does before using it.

Think of your internal memory this way:

__

|_| = block of memory

A = ROM image

B = Program data

C = User data

__________________

|A|A|A|B|B|C|_|_|_|

If your internal memory has nine blocks to write to, it will begin to do so in order. If you then flash a new ROM image of a different size (we'll say ROM "D" in this case), the data tells it where to put the information. It is logically written in order again, overwriting the previous ROM like so:

__________________

|D|D|D|D|B|C|_|_|_|

Now the ROM "D" has overwritten the majority of the data from the previous ROM, but has left the old data in tact. It may or may not have actual access to this data causing some weird glitches on occasion as the new ROM image is moving about accessing various parts of the build. This may cause it to read old calendar dates as you've seen, or it may even have simple, but strange issues that don't normally occur. Generally a task29 will simply erase all of those blocks and allow you to start from scratch with no problems.

Hopefully this explains your problems better. In the future, however, please make sure to post in the relevant threads for what you are asking for, or use the PM system for off-topic/irrelevant questions. For example, ROM questions should be asked in their appropriate threads and task29 issues in that thread. This one is specifically for Hard SPL topics.

Happy flashing.

-CFB