Stock rooted 2.2 Froyo


Last Updated:

  1. whiterabbitorg

    whiterabbitorg Member This Topic's Starter

    Joined:
    Aug 3, 2010
    Messages:
    24
    Likes Received:
    1
    Updated for 2.2.2 in March 2011. Everything is the same, check the site for the revised and simplified instructions, or keep reading for the older and different instructions. Which one is less confusing is for you to decide. I suck at guide writing, but this is the easiest way to keep root for sure.

    Updated for 2.2.1 on Dec 15. I am leaving the old instructions here in case they are helpful, but the ones on my web site should be easier to understand. There is a new hack for the FRG83D update there too.

    Old instructions are below.

    FRG22D update: This guide was written for FRG01B. I made a patch for FRG22D and it is on my site. The steps are the same as before, but with the new files - "copy /b signed-voles-FRG22D-from-FRG01B.688e3520.zip+FRG22D-root.zip update.zip"

    All files needed are available on my web site: Android - whiterabbit.org unless you still need to root your phone or downgrade to 2.0.1, the files needed for that will be linked to from those guides. The purpose of installing this way is to use the original OTA updates from Google, and only modify them enough to have root access. When you are done, you will have a system that is capable of installing the next OTA (gingerbread) when it arrives. Hopefully we will be able to patch it in the same way to keep root. This is only for people who don't want to run custom roms, but still want to have root.

    If you aren't rooted yet, you need to do that first: http://androidforums.com/all-things-root-droid/136508-guide-all-things-root-related.html

    If you are on stock rooted 2.1 with a custom recovery partition or the 2.1 recovery partition (you need the stock 2.0.1 recovery for this):

    First make sure you have a stock recovery partition. If you are using a custom recovery partition like sprecovery, get recovery.img, put it on your sdcard, get to a prompt (connectbot, local connection - or adb shell) and run su. run "flash_image recovery /sdcard/recovery.img". Now you have the stock 2.0.1 recovery partition. Go to the next step.

    If you are on stock rooted 2.1 with the stock 2.0.1 recovery partition:

    Download signed-voles-FRG01B-from-ESE81.e48e48ff.zip and FRG01B-root.zip, then at a dos prompt where both files are, run "copy /b signed-voles-FRG01B-from-ESE81.e48e48ff.zip+FRG01B-root.zip update.zip" and then copy that update.zip to your sd card. Boot holding down X and hold down volume up and tap the camera button. Select apply sdcard:update.zip with the dpad and press enter. Now wait a long time for it to apply the update, and you will have rooted stock froyo. You are done and can stop reading this thread.

    If you are on unrooted 2.2, you should probably read this thread instead: http://androidforums.com/all-things-root-droid/141116-guide-rooting-2-2-a.html

    Your other option is to downgrade to stock 2.0.1 using this guide: Unroot/Unbrick using .sbf post from -ikithme- - Droid Forum - Verizon Droid & the Motorola Droid Forum

    You will lose everything, so back anything important up. Hit the menu button from the home screen, pick settings, privacy settings, and pick "back up my data". That will go a long way towards backing things up. Then follow that guide.

    Now you have unrooted 2.0.1, so upgrade to rooted 2.1. Download signed-voles-ESE81-from-ESD56.fa406da6.zip and ESE81-root.zip, then at a dos prompt where both files are, run "copy /b signed-voles-ESE81-from-ESD56.fa406da6.zip+ESE81-root.zip update.zip" and then copy that update.zip to your sd card. Boot holding down X and hold down volume up and tap the camera button. Select apply sdcard:update.zip with the dpad and press enter. Now wait a long time for it to apply the update, and you will have rooted stock 2.1 along with the stock 2.0.1 recovery partition, which means you can go back to the beginning of this guide.
     

    Advertisement
    5enator likes this.
  2. RichSmithSWM

    RichSmithSWM Member

    Joined:
    Apr 27, 2010
    Messages:
    6
    Likes Received:
    0
    I downloaded the stock-recovery.zip and extracted it to the root of my sdcard I get the following messsages.

    #sh install-recovery.sh
    sh install-recovery.sh
    contents of MTD partition "recovery" didn't match MTD:recovery:2048:52420c65aa9e
    182cfe9fa995be4f2784ec4914cd
    file "MTD:recovery:2048:52420c65aa9e182cfe9fa995be4f2784ec4914cd" doesn't have a
    ny of expected sha1 sums; checking cache
    failed to stat "/cache/saved.file": No such file or directory
    failed to load cache file
    applying patch to MTD:boot:2504704:0b5ee101da41148aa026a32848f609fa4b05403e
    LoadMTDContents called with bad filename (MTD:recovery)
    contents of MTD partition "recovery" didn't match MTD:recovery
    contents of MTD partition "boot" didn't match MTD:boot:2504704:0b5ee101da41148aa
    026a32848f609fa4b05403e
    source file is bad; trying copy
    failed to stat "/cache/saved.file": No such file or directory
    failed to read copy file
     
  3. whiterabbitorg

    whiterabbitorg Member This Topic's Starter

    Joined:
    Aug 3, 2010
    Messages:
    24
    Likes Received:
    1
    You have both files (install-recovery.sh and recovery-from-boot.p) in the same folder? Also I want to be sure, are you using stock rooted 2.1 with an sprecovery partition, or are you using a custom rom?
     
  4. RichSmithSWM

    RichSmithSWM Member

    Joined:
    Apr 27, 2010
    Messages:
    6
    Likes Received:
    0
    Both files are in the same folder (root of sdcard). Stock 2.1 rooted with no custom ROM. SPRecovery is installed. I juust rooted to add the screenshot application and wifi tether.

    *** Edit I also tried "sh ./install-recovery.sh" while in the folder to make sure it was running the correct one.
     
  5. whiterabbitorg

    whiterabbitorg Member This Topic's Starter

    Joined:
    Aug 3, 2010
    Messages:
    24
    Likes Received:
    1
    I used these same files before on a friends droid, but it was running 2.0.1 and sprecovery. Maybe this script only works under 2.0.1 and not 2.1.

    I'll have to update my original post to reflect that. I think your choices now are to downgrade, or use a non-stock rom from someone else. Sorry.
     
  6. OMJ

    OMJ Bazinga VIP Member

    Joined:
    Nov 27, 2009
    Messages:
    3,288
    Likes Received:
    825
    Do you have the .img file of the stock recovery? If so it could be flashed using flash_image.
     
  7. RichSmithSWM

    RichSmithSWM Member

    Joined:
    Apr 27, 2010
    Messages:
    6
    Likes Received:
    0
    Thanks for the help. I think maybe I'll see what happens with the OTA and wait for root. If that doesn't work then I'll revert to 2.01.
     
  8. whiterabbitorg

    whiterabbitorg Member This Topic's Starter

    Joined:
    Aug 3, 2010
    Messages:
    24
    Likes Received:
    1
    Yeah I'm looking around for that right now, but really don't have the time. I thought more people were still using stock recovery like me, but I guess everybody who got the droid after the 2.0.1 update came out had to flash sprecovery to get root.
     
  9. whiterabbitorg

    whiterabbitorg Member This Topic's Starter

    Joined:
    Aug 3, 2010
    Messages:
    24
    Likes Received:
    1
    I found the stock 2.0.1 recovery. I'm updating the guide right now.
     
  10. whiterabbitorg

    whiterabbitorg Member This Topic's Starter

    Joined:
    Aug 3, 2010
    Messages:
    24
    Likes Received:
    1
    Thanks for the advice. I found the recovery.img needed on xda, and then ripped it from my own droid to compare md5sums and they matched. Anyone following this guide can be sure that the recovery.img linked to from my site is identical to the one I am running.

    I did the same with the 2.0.1->2.1 OTA update since Google isn't hosting it any more. I found a copy on mediafire, downloaded it, and compared it to the one I got from Google months ago and it was identical.

    The MD5SUMs for both mediafire files in question are:
    1b28a5406a21bd2cb2e3edbe2615599a recovery.img
    b8ad1c0ca28e2cd34b54c67a4dadb466 signed-voles-ESE81-from-ESD56.fa406da6.zip
     
  11. OMJ

    OMJ Bazinga VIP Member

    Joined:
    Nov 27, 2009
    Messages:
    3,288
    Likes Received:
    825
    I flashed the recovery and it worked fine. Glad to have a copy of the stock recovery back. I had it in the past and must have deleted it from my sd card. Although I did quickly flash back to clockwork
     
  12. 5enator

    5enator New Member

    Joined:
    Sep 28, 2010
    Messages:
    1
    Likes Received:
    0
    @whiterabbitorg : could you please help me, i send message to you. - Thanks
     
  13. OMJ

    OMJ Bazinga VIP Member

    Joined:
    Nov 27, 2009
    Messages:
    3,288
    Likes Received:
    825
  14. whiterabbitorg

    whiterabbitorg Member This Topic's Starter

    Joined:
    Aug 3, 2010
    Messages:
    24
    Likes Received:
    1
    It wasn't even related to this unfortunately. Thanks for staying subscribed to this thread :D

    I updated my phone to stock rooted 2.2.1 today and put the files on my site. If anyone is still reading this and/or using the droid 1, let me know if it works for you.
     
  15. OMJ

    OMJ Bazinga VIP Member

    Joined:
    Nov 27, 2009
    Messages:
    3,288
    Likes Received:
    825
    Im still reading although Im a couple phones removed from the D1. Still hoping to pick up a spare at a good price all the craigslist deals I work for D1s seem to fall through.
     
  16. whiterabbitorg

    whiterabbitorg Member This Topic's Starter

    Joined:
    Aug 3, 2010
    Messages:
    24
    Likes Received:
    1
    Once again, updated to 2.2.2. Shameless bump for a painless upgrade procedure while keeping stock root. Hundreds of downloads, but few replies. Stop by and say hi if it works for you! :)
     
  17. whiterabbitorg

    whiterabbitorg Member This Topic's Starter

    Joined:
    Aug 3, 2010
    Messages:
    24
    Likes Received:
    1
    Sorry to anyone who downloaded the new update - I linked FRG83G-root.zip to FRG83D-root.zip. You will need to re-download it if you want it to work.
     

Share This Page

Loading...