[Motorola Droid 3] drfsupercenter:
What's curious to me is that the bootloader is the same (0A.64) between the newest Verizon 2.3.4 ROM and the China Telecom/ACG ROMs.

I was messing around with this phone and used RSD Lite to flash a few different .zip files to it, most recent:

solana_cdma_solana-user-2.3.6-5.5.1.1-84_d3g-25-120731-release-keys-acg-ntelos-us.xml.zip

Now when I try to go back to VRZ_XT862_5.5.1_84_D3G-66_M2-10_1FF_01a.xml.zip I get a message that cdt.bin flashing failed.

When I try using moto-fastboot.exe...

F:\moto-fastboot>moto-fastboot.exe flash cdt.bin cdt.bin

sending 'cdt.bin' (16 KB)... OKAY [ 0.003s]

writing 'cdt.bin'... INFOPreflash validation failure

FAILED (remote: )

I also get errors with boot and recovery. Here's the entire process as I use moto-fastboot in place of RSD Lite...

F:\moto-fastboot>moto-fastboot.exe flash mbm allow-mbmloader-flashing-mbm.bin
sending 'mbm' (256 KB)... OKAY [ 0.027s]
writing 'mbm'... OKAY [ 0.452s]

F:\moto-fastboot>moto-fastboot.exe reboot-bootloader
rebooting into bootloader... OKAY [ 0.002s]

F:\moto-fastboot>moto-fastboot.exe flash mbmloader mbmloader.bin
sending 'mbmloader' (39 KB)... OKAY [ 0.007s]
writing 'mbmloader'... OKAY [ 0.291s]

F:\moto-fastboot>moto-fastboot.exe flash mbm mbm.bin
sending 'mbm' (256 KB)... OKAY [ 0.030s]
writing 'mbm'... OKAY [ 0.448s]

F:\moto-fastboot>moto-fastboot.exe flash cdt.bin cdt.bin
sending 'cdt.bin' (16 KB)... OKAY [ 0.004s]
writing 'cdt.bin'... INFOPreflash validation failure
FAILED (remote: )

F:\moto-fastboot>moto-fastboot.exe erase cache
erasing 'cache'... OKAY [ 0.007s]

F:\moto-fastboot>moto-fastboot.exe erase userdata
erasing 'userdata'... OKAY [ 0.007s]

F:\moto-fastboot>moto-fastboot.exe erase emstorage
erasing 'emstorage'... OKAY [ 0.061s]

F:\moto-fastboot>moto-fastboot.exe flash lbl lbl
sending 'lbl' (16 KB)... OKAY [ 0.003s]
writing 'lbl'... OKAY [ 0.433s]

F:\moto-fastboot>moto-fastboot.exe flash ebr ebr
sending 'ebr' (16 KB)... OKAY [ 0.004s]
writing 'ebr'... OKAY [ 0.935s]

F:\moto-fastboot>moto-fastboot.exe flash devtree device_tree.bin
sending 'devtree' (512 KB)... OKAY [ 0.052s]
writing 'devtree'... OKAY [ 0.473s]

F:\moto-fastboot>moto-fastboot.exe flash system system.img
sending 'system' (262144 KB)... OKAY [ 25.915s]
writing 'system'... OKAY [ 11.307s]
sending 'system' (175872 KB)... OKAY [ 17.093s]
writing 'system'... OKAY [ 7.716s]

F:\moto-fastboot>moto-fastboot.exe flash boot boot.img
sending 'boot' (8192 KB)... OKAY [ 0.771s]
writing 'boot'... INFOPreflash validation failure
FAILED (remote: )

F:\moto-fastboot>moto-fastboot.exe flash recovery recovery.img
sending 'recovery' (9216 KB)... OKAY [ 0.868s]
writing 'recovery'... INFOPreflash validation failure
FAILED (remote: )

F:\moto-fastboot>moto-fastboot.exe flash cdrom cdrom
sending 'cdrom' (12032 KB)... OKAY [ 1.131s]
writing 'cdrom'... OKAY [ 2.174s]

F:\moto-fastboot>moto-fastboot.exe flash preinstall preinstall.img
sending 'preinstall' (262144 KB)... OKAY [ 25.496s]
writing 'preinstall'... OKAY [ 10.991s]
sending 'preinstall' (229376 KB)... OKAY [ 22.891s]
writing 'preinstall'... OKAY [ 10.109s]

F:\moto-fastboot>moto-fastboot.exe flash emstorage emstorage.img
sending 'emstorage' (11651 KB)... OKAY [ 1.095s]
writing 'emstorage'... OKAY [ 1.983s]

F:\moto-fastboot>moto-fastboot.exe flash radio radio.img
sending 'radio' (14368 KB)... OKAY [ 1.354s]
writing 'radio'... OKAY [ 2.119s]

The phone does work fine with the cdt.bin and boot/recovery from the nTelos image, but it's just annoying that I can't go completely back to Verizon. Given the bootloader is the same revision I don't understand what's causing this.

Is this something I can fix or did I basically screw this phone permanently? I can root it if there's any way to wipe the cdt or whatever using root.