This sounds like a bootloader issue, and I'm a little concerned about the part that says "code corrupt." Usually when we see this, someone has attempted unsuccessfully to root the device.
The first thing I would try would be a battery pull to see if it reboots the device correctly. If you still experience the same error, the next step would be a hard reset (which will result in all phone data being wiped, and it being set back to it's factory state. The good news is that once you sign back in to MOTOBLUR (you will need your motoblur ID and password to re-setup the phone) all of your accounts such as Facebook, email, etc. will be restored, although you'll probably need to redownload any apps.
To do the hard reset:
Hard Reset Procedure:
1. Turn the power off. If your Motorola CHARM is frozen, pull the battery out
and reinsert it again.
2. Press and hold the Power and Camera buttons
3. Release the Camera button when prompted
4. Press and hold the Volume Down key
5. A yellow exclamation will show and or appear on the display
6. Then, select the Wipe data/factory reset (Alt + W) option
7. Wait for the phone to reboot
8. Once complete the device is now returned to its factory settings.
If this doesn't resolve the issue, then I would recommend contacting customer care for further troubleshooting, and if still under warranty, possible exchange.
I hope this information helps, and I hope you are successfully able to re-boot!
Thank you so much for replying! I have no idea what someone attempting to "root" my device means. Is that some kind of hack thing or virus?!
Anyway, I tried taking out the battery, but it didn't do anything except go back to that same Bootloader screen. I will try the hard reset. Thank you so much for you help!
Hmm. okay. Unfortunately it sounds like something became corrupt in the programming. Could have been a 3rd party application, but we most often see this as a result of someone "rooting" their device. Rooting means to replace the operating system which comes loaded on a device, with a different system created by a developer.
Either way, I think you'll need to contact Customer Care for further troubleshooting and a possible exchange if it is still under the 1 year warranty, or through insurance if you have that.
I apologize I don't have better news for you.