• 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)

See my post back on page 12 of this thread, I had a similar issue when 2.1 came out and it turned out to be an issue with the phone, I had to have it exchanged.
http://androidforums.com/motorola-d...droid-frg01b-update-1-2-a-12.html#post1315021

I have no idea what clockwork is and what it does, but I had to buy a replacement Droid off craigslist and the guy I brought it from must have installed it and now when I try to install the 2.2 OTA update off of here, it wont let me and keeps giving me the same installation aborted prompt if anyone could PLEASE help me out with it I would GREATLY appreciate it!

Here is the complete prompt I get when trying to apply the update.zip file on the phone...

--Install from sdcard...
Finding update package...
Opening update package...
Installing update...
Verifying current system...
assert failed: apply_patch_check("/system/app/Facebook
.apk", "e0863c5f00e4b241e03cb976c861406291
9290b3", "d6a7de530af593010b31a37d2a769556a3fedb
3c")
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted.
 
update seems fine so far, but I cant seem to download flash 10.1. When I try to download from adobe.com it says I need to update to 2.2. I checked in settings and I'm definitely running froyo. anyone else have this issue?
 
So if I wait for the next less buggy version I'll still need to install this one first? I'm just debating whether to or not, since I've been hearing of a lot of problems for some.
 
So if I wait for the next less buggy version I'll still need to install this one first? I'm just debating whether to or not, since I've been hearing of a lot of problems for some.

Nobody knows for sure, but I suspect not.

Knowing what I know now, I wouldn't have touched Verizon's current FRG01B update or FRG22 fix with a ten-meter cattle prod. The only reason I'll touch FRG22 now is because I need it to fix FRG01B. If I were on 2.1, I wouldn't touch either of them.

I assume Verizon doesn't want anyone to touch them either: the more people who have it, the bigger a mess it is.

They're going to come out with a bug-fixed FRG22 that installs over 2.1. They have to. It works like this:


  • FRG01B has a buggy networking stack. If you apply it, you may not have a reliable data connection.

  • The current FRG22 fix requires a data connection to transfer that fix from Verizon to the Droid.

  • If FRG01B breaks the data connection, there's no way for the Droid to receive the FRG22 fix.

For the majority of users, the only upgrade path is a new official Verizon FRG22 that bypasses the FRG01B upgrade altogether.

If I were anyone who's not applied FRG01B, I would leave it alone. There will be an FRG22 version that works right and that installs on 2.1.

Wait around for that one. Don't install anything right now.

Bill Stone
 
I've said it before, I installed the FRG01B, haven't seen any of the issues some others have. Battery life is fine, I streamed Pandora over my WiFi for 20 mins. without interruption, the phone seems pretty zippy overall, the news app works fine.

chevy, mine was exchanged under warranty. Obviously Verizon will want to look at it first, wait till the FRG22 drops and see what happens, if it's still a problem THEN take it in and see if they can look at it or exchange it.
 
I have been waiting for this update for about 5 months now. Mainly for the wifi hotspots and flash player. So I could hardly contain myself when I found I could bypass the waiting and manual update. Now I have the update and no wifi hotspots and no flash? Am I missing something?

Verizon stated that the Droid 1 will not have WiFi tethering. Flash will officially be released on the 18th. You will have to use one of the numerous (take a quick peak around the forum) links to its' download.

Was going to update, but, seen too many posts with people having problems and 2.1 works fine for me. I will wait till I get my OTA update and install that way. Not worth it yet.
 
FWIW, I had a VERY similar issue when 2.1 came out. I tried a manual update, tried letting OTA do it, tried doing a factory wipe (THREE TIMES!). I took it in to the local VZW store, they tried and couldn't get it. They had me call Motorola, I explained what was tried and their answer was to go back to Verizon and have them exchange the phone. Exchanged the phone and all went well for updating.

For anyone getting errors similar to the one below, you MAY need to have your phone exchanged.


Do they not void all warranties if you mess with the software or root?
 
forced the update but adobe wont let me download flash and its not showing up in the market do I have to wait till update 2 for this to work
 
everything is working great, except flash wont work in the browser. clicked "download now" and it redirects me to a page that tells me "flash only works with android 2.2". whats going on?
 
I've followed all procedures to update ota but I get the can't run recovery command and incantations update do due my Droid not letting me scroll down with mydpad
I don't know where to go from there. Any suggestionswould be much appreciated. Thanks a buncj
 
I've followed all procedures to update ota but I get the can't run recovery command and incantations update do due my Droid not letting me scroll down with mydpad
I don't know where to go from there. Any suggestionswould be much appreciated. Thanks a buncj
I don't think I understand what you mean, but I'll give it a shot.
Try using the other directions on your dpad and see if any of those work... Best bet is to wait for now, this update has some bugs...
 
Do they not void all warranties if you mess with the software or root?


Mine isn't/wasn't rooted. I actually got the error both when trying the manual update and when the OTA came through for 2.1, was able to duplicate it for the tech at the VZW store. I give them credit, the guy spent an hour with me working on it. After a call to Motorola (suggested by VZW phone support, which I made since it was closing time when i left), the phone was replaced the next day at the VZW store.
 
I'm still waiting for Motorola to call me back from yesterday. I swear their customer service leaves something to be desired. I called them again today and was told they would have to have a tech call me back in 2 hrs due to "extremely high call volumes". Well I give up. Called back VZW and there sending a replacement Droid on Monday. I would suggest people who manually updated to FRG01B to do the same, If your Droid is running like mine it's gonna be a while til they fix this. Could be month or two from what I was told. VZW is receiving complaints about this update and has stopped it from pushing out further and will be sending it back to Motorola to fix it. There is no way to go back to 2.1 with out really knowing your stuff on how to do it. For me I'd rather just have VZW send me another Droid.
 
The only problem with getting another Droid is that its a refurb. My droid is still pristine I don't want something some sat on or dropped in the lake I want another new one of the shelf if they are going to replace them. That is my biggest complaint about this type of replacement plan.
 
How'd you get it to work? I tried to voice dial with my Jawbone last night and couldn't figure it out.

I just tapped the button on my earpiece to initiate the call...system then prompted me to speak a selection. I say a name in my contact list, it then repeats it for verification and then makes the call.

I can also answer a call by tapping my earpiece button, which I couldn't do before.

Just like the old days when I only had a $30 phone!!!!!
 
I just tapped the button on my earpiece to initiate the call...system then prompted me to speak a selection. I say a name in my contact list, it then repeats it for verification and then makes the call.

I can also answer a call by tapping my earpiece button, which I couldn't do before.

Just like the old days when I only had a $30 phone!!!!!

Crazy, it didn't work for me when I tried the same start of your process.
I'll wait for the next build to see if anything changes. Hopefully it's not my BT headset.
Thanks!

PS: I could always answer the incoming calls with the headset even before this update.
 
Back
Top Bottom