Bricked droid, need some ideas

Discussion in 'Android Hacks and Help' started by 4d7, Jan 6, 2010.

  1. 4d7

    4d7 New Member

    Joined:
    Jan 5, 2010
    Messages:
    28
    Likes Received:
    0
    Trophy Points:
    1
    Ratings:
    +0
    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.
     
  2. alf

    alf Member

    Joined:
    Nov 17, 2009
    Messages:
    65
    Likes Received:
    0
    Trophy Points:
    6
    Ratings:
    +0
    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.
     
    Last edited: Jan 6, 2010
  3. MNTNBKR

    MNTNBKR Member

    Joined:
    Dec 9, 2009
    Messages:
    572
    Likes Received:
    2
    Trophy Points:
    18
    Location:
    Fenton, MI
    Ratings:
    +2
    ...good thing there's some brainy people here.
     
  4. mammlouk

    mammlouk Member

    Joined:
    Dec 13, 2009
    Messages:
    316
    Likes Received:
    0
    Trophy Points:
    16
    Ratings:
    +0
    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.
     
  5. alf

    alf Member

    Joined:
    Nov 17, 2009
    Messages:
    65
    Likes Received:
    0
    Trophy Points:
    6
    Ratings:
    +0
    You can issue commands during a boot loop.
     
  6. 4d7

    4d7 New Member

    Joined:
    Jan 5, 2010
    Messages:
    28
    Likes Received:
    0
    Trophy Points:
    1
    Ratings:
    +0
    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.
     
    Last edited: Jan 6, 2010
  7. alf

    alf Member

    Joined:
    Nov 17, 2009
    Messages:
    65
    Likes Received:
    0
    Trophy Points:
    6
    Ratings:
    +0
    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.
     
    Last edited: Jan 6, 2010
  8. 4d7

    4d7 New Member

    Joined:
    Jan 5, 2010
    Messages:
    28
    Likes Received:
    0
    Trophy Points:
    1
    Ratings:
    +0
    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.
     
  9. alf

    alf Member

    Joined:
    Nov 17, 2009
    Messages:
    65
    Likes Received:
    0
    Trophy Points:
    6
    Ratings:
    +0
    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
     
    Last edited: Jan 6, 2010
  10. TimChgo9

    TimChgo9 Member

    Joined:
    Dec 26, 2009
    Messages:
    408
    Likes Received:
    0
    Trophy Points:
    16
    Location:
    NE Illinois
    Ratings:
    +0
    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...
     
  11. 4d7

    4d7 New Member

    Joined:
    Jan 5, 2010
    Messages:
    28
    Likes Received:
    0
    Trophy Points:
    1
    Ratings:
    +0
    I am not running a custom recovery, all I have is the default "Android system recovery <2e>"

    and yes I had it rooted, thats good news that data wipe doesn't remove root.

    I just tried reinstalling the moto drivers, and typed in "adb shell", results in No device detected. I tried "adb wait-for-device" and rebooted into the boot loop, so far adb can't see it.

    I know windows is detecting it though, when I plug it in I can here the device connected "thudumph" sound ha

    I'll also mention that I am running windows7x64, which means my method of adb is through command prompt. Android sdk fails in W7x64
     
    Last edited: Jan 6, 2010
  12. 4d7

    4d7 New Member

    Joined:
    Jan 5, 2010
    Messages:
    28
    Likes Received:
    0
    Trophy Points:
    1
    Ratings:
    +0
    working on applying your fresh 2.01. rapidshare servers seem to be full.
     
  13. alf

    alf Member

    Joined:
    Nov 17, 2009
    Messages:
    65
    Likes Received:
    0
    Trophy Points:
    6
    Ratings:
    +0
    well the only thing I can think of is to take out the sdcard and put it in a reader so you can get to it from your pc. go to Verizon website and download a 2.01 zip and place it on the sdcard using the reader. only thing is I'm not sure if it will pass the check-sum . Since some of the system files have been changed. maybe someone with a little more cowbell wants to jump in.
     
  14. alf

    alf Member

    Joined:
    Nov 17, 2009
    Messages:
    65
    Likes Received:
    0
    Trophy Points:
    6
    Ratings:
    +0
    look on the first page of hacks there is a mirror link to it.
     
  15. doug piston

    doug piston Premium Member Rescue Squad Premium Member

    Joined:
    Dec 19, 2009
    Messages:
    1,203
    Likes Received:
    4
    Trophy Points:
    38
    Ratings:
    +4
    i did this myself today. i had nanoand a backup though. sorry to hear man
     
Search tags for this page
2j 2handroid debug brigde
,

2handroid debug bridge

,
←[2j←[2handroid debug bridge
,
adb status-window 2j[android debug brigde state:recovery how
,

restore factory setting on bricked android