Bricked droid, need some ideas

[4d7]

background:

2.01 firmware
rooted
busybox installed

Problem:
boot loop. cannot get past the red eye, then restarts the boot animation.

I replaced the framework-res.apk with the 2.1 instead of the 2.01 on mistake, rebooted and bricked..

I have access to the factory default recovery menu <2e> and can apply an update.zip. I have tried this but the signed update fails the md5 hash validation due to the incorrect framework-res.apk that is currently on the droid.

So my next step was to factory restore/data wipe (thought it might replace the framework-res.apk with original) so that I could apply the update.. but it did not and still hangs up on the md5 hash. Also lost my adb ability.

I never set myself up with nandroid or any custom recovery, so currently I am stuck. is there a way that I can flash my droid ?

any help or ideas, I'll try them out.

[alf]

get a fresh copy of the framework-res.apk one is on this forum somewhere. you can stop the loop from by doing adb reboot recovery then mount the system on the droid and push the framework-res.apk back to the phone. If you can't get the adb back by issuing a reboot command during the loop then I am at a loss.

[MNTNBKR]

...good thing there's some brainy people here.

[mammlouk]

get a fresh copy of the framework-res.apk one is on this forum somewhere. you can stop the loop from by doing adb reboot recovery then mount the system on the droid and push the framework-res.apk back to the phone. If you can't get the adb back by issuing a reboot command during the loop then I am at a loss.

If he is in a boot loop I don't think he can get in with adb. This is a prime example of why everyone says to install SPRecovery/nandroid before changing things.

[alf]

You can issue commands during a boot loop.

[4d7]

I cannot access adb, I did a factory data wipe. Or can I still? that would be great! Although I have tried to reconnect via adb and it says no device detected, this could be because the data wipe removed busybox.

So far I can only think of two ways to fix it, and I don't think either is possible.

somehow adb my droid while its in recovery menu, or flash the droid somehow.

[alf]

If you can get to the recovery menu but can't adb try another usb port on your pc and maybe try and re install the usb driver. If that don't work and adb is out. then your next step would be to get a sdcard reader and put a fresh copy of 2.01 using your pc.
unless anyone else has any ideas.

[4d7]

I'll try re installing the moto drivers and attempt to adb again, my only question is can you adb the droid if a data wipe has been performed? I thought you needed to have root access to be able to adb.

As far as the sdcard, I have tried a 2.01 OTA update.zip. The update starts but then fails the "validating current system" part due to the modified framework-res.apk having a different MD5 hash than what is in the update. Installation aborted.

[alf]

a data wipe does not kill root access. what version of the recovery are you running, and just so I am not missing anything you had root to begin with right? hang on a sec and I will upload you a fresh 2.01 RapidShare: 1-CLICK Web hosting - Easy Filehosting

[TimChgo9]

This is the reason why I have no plans to root my Droid. I just don't trust my ability to do it, and do it right....

Good luck on getting your Droid to work again... there are plenty of people here who know what's going on, and by reading so far, you're in good hands...