I just did something unbelievably stupid and I'm hoping there is some way to fix it. I'm posting this here because it is potentially R2-specific.
I was trying to go about undoing all the things I did root-wise, and one of the last things was removing koush's bootstrap. I followed some instructions online that, after uninstalling the bootstrap app and rebooting, basically just replaced (through terminal) the bootstrapped /system/bin/logwrapper with the original (which was backed-up as /system/bin/logwrapper.bin). I rebooted and that worked fine. Then I read somewhere else about how /system/bin/hijack should be deleted, then further instructed to (through Root Explorer) delete /system/bin/logwrapper and rename /system/bin/logwrapper.bin to /system/bin/logwrapper ...so, I stupidly thought "well, I did all that in terminal except deleting hijack. It worked fine this time, but I shouldn't leave anything to chance" so I deleted /system/bin/hijack and spelled my own doom. I rebooted my R2 and was caught in an infinite bootloop.
I can get into android system recovery just fine. I also have a backup made from clockwork recovery (both on my sd card and backed up on my external hard drive), but of course clockwork recovery is no longer on my phone, and regular android recovery doesn't have "backup and restore". I tried "wipe data/factory reset" because that sounded promising, but that just wiped my data...no "factory reset" at all.
I've been frantically googling to see how to either a) push that "hijack" file (which I could hopefully find somewhere or another online, perhaps from the D2 system dump) to the proper place on my phone via adb or b) recover from my nandroid backup via adb. I'm not even remotely sure how I would do either of those things from recovery mode.
Is there any hope? Even if I could, perhaps, flash any sbf that will work (however shoddily) on R2, then re-root, rebootstrap and recover from my beloved backup. Or any solution, really.
UPDATE: VZW is gonna trade it back for another one. I haven't the slightest clue why they couldn't flash the firmware. Presumably, they have it. It's like they didn't even know what that meant. Anyway, I don't need help anymore, but let this be a cautionary tale for excitable young Droid-users.