My current idea for this is a pdocread. Any others agree? I think that has worked for backups of bootloaders and rom images. I would think it could work for the radio too if we have a verizon user that could do a pdocread maybe this could be used for these phones. I'm sorry I left that file up with no warning. It was intended as a test to replace a radio rom on a phone that already wasn't able to be flashed.
Unfortunately i dont think this has been investigated much with the Apache. There is a very long and detailed thread on XDA about a similar issue with the hermes though:
http://forum.xda-developers.com/showthread.php?t=286755
It includes some info about the CID and the wiki has some info on the erase procedure for the HERMES (not apache, but should have some good troubleshooting ideas)
Can you get a log from during the rom update failure with USB monitor (
http://www.hhdsoftware.com/Products/...b-monitor.html ) and use Edit -> Export and Save as type "ANSI Text files" to post to the forum?
The way i see it, this can be fixed if it will connect in bootloader we should theoretically be able to write to any portion of the phone, but it seems there are intricacies with the radio portion. Although the insurance guys will probably think it looks like something that happened when your computer BSOD during the radio flash of the reccommended update
