Complete How-To on How to Mod Your Phone (2.1 ROM, O/C, MM, Boot Animation, etc)

[BladeOfAnduril]

If you need to know how to upgrade using the update.zip method...keep going, otherwise, skip this section


NOTE: This will only work if you ALREADY have a 2.1 ROM installed on your phone! Also, if you want to upgrade using a ROM other than Bugless Beast, simply download the update.zip (if available) from a different developer (Ultimate Droid, Smoked Glass, Simply Stunning, etc).

90. Download Pete's newest update.zip here. Mount your phone to the PC as you have done several times now. Rename or delete any update.zip files currently on the SD card. Move the NEW update.zip that you just downloaded to the root of your SD card.

91. Reboot the phone in recovery mode (you should be a pro at this by now).

92. Choose install.

93. Choose allow update.zip installation. Don't forget this step. If you do, you will get "installation blocked" or something to that effect. This is the feature that prevent OTA updates from being able to be installed to your phone. In the future, if you want to accept a Google update for you phone you will need to download the file, then boot into this menu, and hit "allow update.zip installation" or it won't work.

94. Choose Install /sdcard/update.zip (deprecated). Deprecated is a software developer's term that means "something that should not be used or is dangerous to use and recommended against". Obviously we want to use this update.zip, so in this case, think of the term deprecated as a warning...as in "Are you sure you want to overwrite your current OS?" It's perfectly safe to complete this step, but many people do not know what this word means.

95. Reboot the phone.

Can this be used to install Bugless Beast on Stock OTA 2.1?

[wmosby]

6. Press the 'volume +' and 'camera' buttons together until you see the screen change to a menu.

[xl1]

I have soo much fun with this !! thank u very much!!! great work!!!

[LyCke7y SpLy7]

Just wanted to say thanks Matthew. This thread has helped me tremendously. You guys on these forums are awesome and you are definately appreciated by me. Thanks again.

[NLaris]

does this root method work for 2.1 firmware?
or does the "2.1" in the thread title just mean that the ROM is v2.1?

[tgrillot87]

When I do the rooting process detailed at the beginning of this forum it gives the following error:
E:Can't open /cache/recovery/command
-- Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:EOCD marker occurs after start of EOCD
E:signature verification failed
Installation aborted.

Rebooting after this I checked and I do not have su permissions. I tried doing a factory reset through the settings>privacy menu but that didn't help. Can anyone shed some light on this? What am I doing wrong and/or what do I need to do to fix it?

[*MotoDroid13*]

Hey there,
Im having some issues with my droid. I had sholes mod for awhile and decided to change it up and i used Rom manager. It worked great for the first two roms i did, first i went to Cyanogen, wiped and all restored all my stuff, then decided to go to Ultimate droid V10 and the change was fine! wiped and all restored, went great, even put up a new up boot animation. Worked awesome the whole day!...till i changed to a different rom (not exactly sure what it was or why it trashed everything) i loaded it, then somthing happened, my boot went away, everything was different on the inside, my app backups (using Titanium backup) were saying they werent installed and all! i found out they appear back in the market place but i never had to re do all of them before. So now i have be up for 2 days straight cause its really bothing me my phones messed up, currently on BB v1.1 (switched around to a few trying to fix, roms too) and nothing seems to bring her back to how she used to be! force closes, slow, ALL MY PICTURES ARE GONE, all my music is gone, txts etc, home button doesnt work, it seems like everyone else is fine! PLEASE HELP!

[stealthgriffin]

When I do the rooting process detailed at the beginning of this forum it gives the following error:
E:Can't open /cache/recovery/command
-- Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:EOCD marker occurs after start of EOCD
E:signature verification failed
Installation aborted.

Rebooting after this I checked and I do not have su permissions. I tried doing a factory reset through the settings>privacy menu but that didn't help. Can anyone shed some light on this? What am I doing wrong and/or what do I need to do to fix it?

I had the same problem. I followed How-To Root your stock 2.1 Droid and now I'm all rooted

[droidr2]

Hi, I am looking for a little help. I bought my Motorola Droid a few months ago. It had 2.0.1 on it. I rooted my phone a few months ago. Then I had installed the rooted version of 2.1. The root and the update to 2.1 went on the phone with no problems and it worked fine. I was even trying to install Debian on the phone. The img was for HTC so I stopped playing with it but still had root access. (I showed a friend which had the same phone.) I just recently was just trying to install Froyo 2.2 on it and this is where I had the problem. I kept having inssues, mainly trying to install the ROM Manager. The ROM Manager would pull up saying "An error occurred while attempting to run privileged commands." So I tried everything I could think of. Irebooted, took out the battery, rebooted to recovery mode (which was missing a few options), and tried to overclock. The overclock apk is where I found that it stopped getting Root privileges. I then went to a terminal and tried to sudo, PERMISSION DENIED.

Not sure where, why, or when I lost the root access, but I would like it back so I can install ROMs and to install Froyo 2.2.

I tried to re-root by doing the same steps I used originally but it didn't work, probably because of the update.

Any help or thoughts would be appreciated.

I have computers running Windows 7 and Ubuntu. My Windows 7 has Android SDK on it and I am fairly familiar with it. (Still learning)

Thanks

[jstafford1]

Hi, I am looking for a little help. I bought my Motorola Droid a few months ago. It had 2.0.1 on it. I rooted my phone a few months ago. Then I had installed the rooted version of 2.1. The root and the update to 2.1 went on the phone with no problems and it worked fine. I was even trying to install Debian on the phone. The img was for HTC so I stopped playing with it but still had root access. (I showed a friend which had the same phone.) I just recently was just trying to install Froyo 2.2 on it and this is where I had the problem. I kept having inssues, mainly trying to install the ROM Manager. The ROM Manager would pull up saying "An error occurred while attempting to run privileged commands." So I tried everything I could think of. Irebooted, took out the battery, rebooted to recovery mode (which was missing a few options), and tried to overclock. The overclock apk is where I found that it stopped getting Root privileges. I then went to a terminal and tried to sudo, PERMISSION DENIED.

Not sure where, why, or when I lost the root access, but I would like it back so I can install ROMs and to install Froyo 2.2.

I tried to re-root by doing the same steps I used originally but it didn't work, probably because of the update.

Any help or thoughts would be appreciated.

I have computers running Windows 7 and Ubuntu. My Windows 7 has Android SDK on it and I am fairly familiar with it. (Still learning)

Thanks

Did you install 2.2 through ROM manager? and do you have a nandroid backup with working root??