• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

[How-To] Force the Official Android 2.2 Froyo Update for the Motrola Droid (FRG01B | Update 1 of 2)

mdidonato said:
Can anyone tell me if the multimedia DOCK app looks any different?
Click to expand...

Yes there is a nice improvement in the multimedia dock. It now has the wallpaper background, the battery charge level, time, weather in the middle, and the bottom row has icons for alarm, gallery, music and home. I like it way better imo.
 
StrifeJester said:
Installed using the google.com link provided so I thought I would help out. The file is uploaded and ready to go at http://www.strifejester.com/update.zip 45.2MB. Thanks for the great info and the original find.
Click to expand...

Verified:

MD5: 2e155b3f08fd2e953ce9c0948cf9eb12

BTW, this had the fastest DL speed thus far, peaking at over 1800 KB/s (even Googles was hurting at only 1.2 MB/s)

dusttones said:
Thanks to all that made this possible. Delicious froyo!
Click to expand...

Indeed - a lot of people worknig hard on this.
 
I can usually figure stuff like this out no problem but I cannot apply this update with sprecovery. I was running on an old release of 2.2. I used sprecover to do an advanced restore of my old 2.1u1 image. During the advanced restore I elected to restore all partitions (cache, system, so on.) I rebooted and verified I was stock unrooted 2.1u1. I rebooted into sprecover, selected install, allow update.zip and then apply /sdcard/update.zip. It threw an assertion failure, but not in verifying the update but in when verifying the system. I then re-downloaded from 2 different mirrors and verified the md5sum. Fine in both cases. I tried with both new downloads. Same assertion failures.

What can I do? Will I not be able to update. I do not have access to any Windows boxes for sbf recovery stuff. Anyone else hitting this?
 
zylogz80 said:
I can usually figure stuff like this out no problem but I cannot apply this update with sprecovery. I was running on an old release of 2.2. I used sprecover to do an advanced restore of my old 2.1u1 image. During the advanced restore I elected to restore all partitions (cache, system, so on.) I rebooted and verified I was stock unrooted 2.1u1. I rebooted into sprecover, selected install, allow update.zip and then apply /sdcard/update.zip. It threw an assertion failure, but not in verifying the update but in when verifying the system. I then re-downloaded from 2 different mirrors and verified the md5sum. Fine in both cases. I tried with both new downloads. Same assertion failures.

What can I do? Will I not be able to update. I do not have access to any Windows boxes for sbf recovery stuff. Anyone else hitting this?
Click to expand...

Hmm.. my suggestion was going to RSD, buy you said that you don't have access to any Windows computers.

Hmm... I'm just not sure. Sorry.. :(
 
zylogz80 said:
I can usually figure stuff like this out no problem but I cannot apply this update with sprecovery. I was running on an old release of 2.2. I used sprecover to do an advanced restore of my old 2.1u1 image. During the advanced restore I elected to restore all partitions (cache, system, so on.) I rebooted and verified I was stock unrooted 2.1u1. I rebooted into sprecover, selected install, allow update.zip and then apply /sdcard/update.zip. It threw an assertion failure, but not in verifying the update but in when verifying the system. I then re-downloaded from 2 different mirrors and verified the md5sum. Fine in both cases. I tried with both new downloads. Same assertion failures.

What can I do? Will I not be able to update. I do not have access to any Windows boxes for sbf recovery stuff. Anyone else hitting this?
Click to expand...

If you have ROM manager, try that, if not, use the 2.0.1 SBF or a 2.1 SBF if you can find it.
 
A Big Thank You. So far it looks great, under setting "about phone" it states 2.2 so I'm happy.
Looking around, it’s got USB tethering and some other little changes (still looking), but thanks again.
 
johnlgalt said:
Did you follow the guide exactly and slowly? Since hte file is named update.zip, it should work fine with SPRecovery. If the file is not 45.2 MB in size / the MD5 does not match as posted ( MD5: 2e155b3f08fd2e953ce9c0948cf9eb12) then you have a bad download.
Click to expand...

I've actually tried it 5 times with 5 different downloads all 45MB did it 3 times with the USB cord, then twice with just the phone. and still nothing I got the same response as the guy up there, assertion something like that. I'm itching to have this but doesn't look like its made for me.
 
A Big Thank You. So far it looks great, under setting "about phone" it states 2.2 so I'm happy.
Looking around, it
 
Hi guys I have a question... So i followed the directions to manually update from android 2.1 to 2.2 using my computer and am running into a major problem. Everything worked fine until it started to install the update and it gave me the error "E:signtature verification failed" so i thought I would just re download and try again but the problem is my phone will not boot back into 2.1 every time I turn it on the only thing that pops up is the white M. Please tell me i didn't brick my phone. Any help would be greatly appreciated!!!
 
Hmmm, so reflash back to old rooted 2.2, use rom manager to downgrade to stock and go from there? Sure, sounds doable to me.

/me goes for it.

I'll let yall know.
 
Trident said:
Just in the notification panel.
Click to expand...
I'm sorry. If I want to unmount my SD Card while using the "Droid only" install and not by using my computer. How do I do that.

Again, apologies b/c I know these are dumb questions, but I want to be sure that I am careful with this as I am not nearly as experienced as you guys with this type of stuff.

Thanks in advance!
 
running android 2.1. tried installing update.zip from various locations via mac and keep getting "E:signtature verification failed". help?
 
skyscraper38 said:
I've actually tried it 5 times with 5 different downloads all 45MB did it 3 times with the USB cord, then twice with just the phone. and still nothing I got the same response as the guy up there, assertion something like that. I'm itching to have this but doesn't look like its made for me.
Click to expand...

What ROM are you running *now*?

Sveks said:
Hi guys I have a question... So i followed the directions to manually update from android 2.1 to 2.2 using my computer and am running into a major problem. Everything worked fine until it started to install the update and it gave me the error "E:signtature verification failed" so i thought I would just re download and try again but the problem is my phone will not boot back into 2.1 every time I turn it on the only thing that pops up is the white M. Please tell me i didn't brick my phone. Any help would be greatly appreciated!!!
Click to expand...

Try waiting for a while and seeing if the M finally goes away.

Next try a battery pull.

Finally, try forcing yourself back into recovery using either adb (connect phone to computer an duse
Code: 
 adb reboot recovery
or else power off phone, then power on while holding down the X key on the physical kb.

zylogz80 said:
Hmmm, so reflash back to old rooted 2.2, use rom manager to downgrade to stock and go from there? Sure, sounds doable to me.

/me goes for it.

I'll let yall know.
Click to expand...

Kewl, keep us posted.

deadpoolkilla said:
I'm sorry. If I want to unmount my SD Card while using the "Droid only" install and not by using my computer. How do I do that.

Again, apologies b/c I know these are dumb questions, but I want to be sure that I am careful with this as I am not nearly as experienced as you guys with this type of stuff.

Thanks in advance!
Click to expand...

If you're using the phone only method you never mounted your SDCard to your computer, so you don't unmount it either.
 
skyscraper38 said:
I'm not running a rom at all. I'm not even rooted, nor have superuser. But for some reason I have SPRecovery, how is this?
Click to expand...

The OS on your phone is called a ROM.

A non-official ROM is called an alternate ROM.

If you're not running a ROM, you're not running anything on your phone - i.e. it is off / bricked.

So, which version are you running currently (Settings --> About Phone )
 
johnlgalt said:
What ROM are you running *now*?



Try waiting for a while and seeing if the M finally goes away.

Next try a battery pull.

Finally, try forcing yourself back into recovery using either adb (connect phone to computer an duse
Code: 
 adb reboot recovery
or else power off phone, then power on while holding down the X key on the physical kb.


I have tried pulling the battery and letting it sit. Its been on the big white M screen for almost an hour now. Do you think it would help If i went into my phone and deleted the "update.zip" file? this ADP reboot does this work with the droid?
Click to expand...
 
You must log in or register to reply here.
Back
Top Bottom