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

I've officially had it. I can't stand FRG01B a moment longer, and there doesn't appear to be an FRG22 fix in the wild yet.

I'm flashing the SPRecovery_ESE81 ROM followed by FRG22-Release, as shown here.

I'd really rather not, but watching YouTube lag and die for the millionth time has finally broken my will. Wish me luck.

Bill Stone
 
For those of you wondering about Flash on 2.2, please note the following:

1. Flash was not included in FRG01B
2. Flash Beta 3 can be downloaded here, and it works fine for me on FRG01B
3. Flash will officially be available in the Market on August 18
 
I've officially had it. I can't stand FRG01B a moment longer, and there doesn't appear to be an FRG22 fix in the wild yet.

I'm flashing the SPRecovery_ESE81 ROM followed by FRG22-Release, as shown here.

I'd really rather not, but watching YouTube lag and die for the millionth time has finally broken my will. Wish me luck.

Bill Stone

Good Luck! Let me know how it goes!
 
LOL at all the people who wanted this 2.2 SO badly that they got a version that is all jacked up.. I feel zero remorse for you fools.. LOL again..
 
Ok ... so having gotten sick of waiting for an official FRG22 to appear and fix my numerous FRG01B bugs, I decided to flash back to 2.1, then install FRG22 as outlined in this thread.

The flash/upgrade process worked like a charm. Here are the results on my FRG01B bugs, by item:


  • Apparent speed of the device has increased dramatically. I'm not clear that it appears any faster than 2.1, but running craptastic FRG01B for a day has colored my perceptions.

  • The networking issues appear to be resolved.

  • YouTube works as advertised.

  • The Gallery works as advertised.

  • Apps that need Internet connectivity are now working as advertised.

  • "Trap!" is still a bit slow, but nowhere near as horrible as under FRG01B.

    As regards the 2D graphics bug introduced in the 2.1 upgrade, LagTest consistently shows 60fps with no sudden dips down to 20fps. The 2D bug seems to have been fixed.

  • Flash still sucks. Playing Falling Girl (one of the oldest, simplest Flash games out there) remains impossible. The girl falls slow as molasses in January at roughly 2FPS.

    The simple control of click-and-hold doesn't translate into press-and-hold on the handheld. There's no way to interact with the game.

    Even if you did, it's so laggy as to be pointless. This can't be due to networking issues, as those seem to have been fixed. It's just due to crappy Flash implementation.

    However, as Flash 10.1 for Droid is still in beta, I'm willing to overlook this. It better be fixed in the public release, however.


Basically, this proves to me that FRG01B was indeed buggy as a cockroach nest. Furthermore, it also tells me that Flash sucks. If this crap is any indication, I'm starting to come around to Apple's way of thinking.

Bill Stone
 
I've had the forced update installed for almost 48 hours and am not experiencing any of the problems that some users are. I'd bet there are more users having no problems than those that are.

Seems those that have problems post way more than those who don't.

Thanks Trident for an awesome how-to!
 
Verizon pushed to a FEW people and everyone else wanted to drink the kool-aid and ended with crap because they cant freakin wait.

I'm unclear: if a vendor is releasing an official upgrade (which FRG01B was), how does it matter if you get it installed? OTA from Verizon or downloaded and installed: what's the difference?

Again, it was an official upgrade from the vendor.

When I've played with ROM replacements, I know I've been in fairly uncharted territory and entirely on my own. If I frak up my Droid, it's my own fault.

But when the vendor releases an official upgrade, that's usually a sign that it's undergone rigorous testing before being released to the public.

It's like this: imagine that Microsoft released a patch for some Windows 7 bug (which, by the way, they do constantly) that breaks your OS, who's to blame? You, for having the temerity to install the update? Or Microsoft for releasing a buggy patch?

You seem to be arguing that if a vendor releases a patch, one should wait to install it until it's been thoroughly tested by other users. While there's some merit to this (and in fact, professionally I avoid being on the bleeding edge precisely because this kind of thing sometimes happens), the reality is that if the vendor says the patch is good, the user has no choice but to trust them to be correct.

Again, not looking for sympathy. I'm a professional systems administrator and I've seen these kinds of issues repeatedly over the last 20 years. It happens.

But when a vendor releases a bad patch, it's not the user's fault.

Let me ask this: if a vendor releasing an official patch isn't an appropriate signal that it's ok to install the patch, what is a good signal in your mind?

It's certainly true that bleeding-edge adopters like myself would have avoided trouble by waiting a week. No question. There is, however, a reasonable expectation that an officially-released patch has been tested.

Bill Stone
 
Seems those that have problems post way more than those who don't.

This is probably true. It seems as though the people bitten by this bug were fewer than those who weren't.

The reason you see me posting in detail is because I'm a sysadmin. Part of my job is always to test and report back any unusual, inappropriate, or buggy behavior to developers. I learned long ago to be as clear and detailed as possible in my bug reports because the more detailed you can be, the easier it is for developers to replicate the problem or locate the bug.

Furthermore, sometimes seemingly insignificant details can be vitally important. The more detail you can provide, the more threads are available for developers to begin attacking the problem.

Consequently, when I post places like this, you see a rather excruciating level of detail. Mea culpa -- it's what I was trained to do. :)

Bill stone
 
I've had the forced update installed for almost 48 hours and am not experiencing any of the problems that some users are. I'd bet there are more users having no problems than those that are.

Seems those that have problems post way more than those who don't.

Thanks Trident for an awesome how-to!

I'm with you. I've had it installed for ~24 hours now. No signal issues (unless there really is no service), almost all the apps work as expected, GMail push works (after I turned it back on, it was off for some reason so those complaining MAY want to check), Youtube app streams nicely and even defaults to HD now, Gallery opens quick, my MP3 tags on my music are accurate, phone seems pretty zippy, Flash works about as well as I'd expect (I installed Beta3) and battery life doesn't seem horrid as some say it is.

My only gripes are that IMEasy seems a little unstable though I'm sure the dev. is probably working on fixing it and Sudoku Daily has a lag on some sounds though I could turn them off as I don't REALLY need the sounds.
 
I have not had one single issue. Nothing, nada.

No issues here either! I used the Official Leaked Google Download Link to get Froyo Update 1 (The one found by Larry R.). Perhaps Trident could add that download link to this post assuming that it is still active! Maybe then people would not feel so nervious about updating to Froyo Update 1 manually!
 
This is probably true. It seems as though the people bitten by this bug were fewer than those who weren't.

The reason you see me posting in detail is because I'm a sysadmin. Part of my job is always to test and report back any unusual, inappropriate, or buggy behavior to developers. I learned long ago to be as clear and detailed as possible in my bug reports because the more detailed you can be, the easier it is for developers to replicate the problem or locate the bug.

Furthermore, sometimes seemingly insignificant details can be vitally important. The more detail you can provide, the more threads are available for developers to begin attacking the problem.

Consequently, when I post places like this, you see a rather excruciating level of detail. Mea culpa -- it's what I was trained to do. :)

Bill stone
I think it's great that you post with so much detail. That's how the info get's into the hands that need it. IMO, that's exactly what you should do! I'm an Administrator and Software Eng. so I understand completely.

It seems to me that there must be some funamental different in either the process used or the hardware for there to be such widely differing results with this update.

I was on a completely stock, launch day Droid with OTA 2.1 update 1, never rooted. Let's see if there are any diffs in the particulars between those who have good and bad results.
 
No issues here either! I used the Official Leaked Google Download Link to get Froyo Update 1 (The one found by Larry R.). Perhaps Trident could add that download link to this post assuming that it is still active! Maybe then people would not feel so nervious about updating to Froyo Update 1 manually!

I must admit no real issues here either. Everything seems to run much faster, especially after removing ATK. I followed Trident's instructions to the letter and installed on my Moto Droid stock 2.1 with just some added Market apps. Music is fine, Gallery is fine, Gmail is fine.

However, when I go to the market it on;y shows Google Maps as something I've downloaded, not real sure why or if it will be fixed.

Does anyone know when the next release will be out, FRG22, for regular non-rooted install?
 
I must admit no real issues here either. Everything seems to run much faster, especially after removing ATK. I followed Trident's instructions to the letter and installed on my Moto Droid stock 2.1 with just some added Market apps. Music is fine, Gallery is fine, Gmail is fine.

However, when I go to the market it on;y shows Google Maps as something I've downloaded, not real sure why or if it will be fixed.

Does anyone know when the next release will be out, FRG22, for regular non-rooted install?

I think that is the Million Dollar Question.
 
I have downloaded and so far love it. The only issue I am having is that I have a couple of numbers in my contacts that I have the phone sending directly to voicemail. Since the Froyo update, that function appears to no longer be working.

If anyone has any advice on how to correct this issue, it would be greatly appreciated.
 
ATK is fixed as of this morning and will now kill apps properly. I put it back on my phone and I am happier than a pig in mud.
 
I have downloaded and so far love it. The only issue I am having is that I have a couple of numbers in my contacts that I have the phone sending directly to voicemail. Since the Froyo update, that function appears to no longer be working.

If anyone has any advice on how to correct this issue, it would be greatly appreciated.

I have 2.2, and I just turned on that function for a number, called my phone from that number, and it went straight to vm. You might want to try turning it off and turning it back on.

I didn't know this function existed, so thanks for the tip.
 
1) This was an incredibly well written set of instructions. I did it directly through the phone, in my parked car. Froyo upgrade on my Droid went flawless and the phone has run fine since. Voice dial works great, Flash works, listen to radio stations, videos, look at loops etc.

2) The only minor glitches with the install were my Security Pro App, kept rescanning, uninstalled it, and reinstalled it, and that was that.

3) If you want to install flash just go to this link, after you have completed the above install and download and install this

com.adobe.flashplayer-3.apk

This is the Adobie Flashplayer beta 3, skips all the adds and their trying to charge you for it.


4) If you want tethering, go to the Market, and download PDANet. Connect your phone to your laptop, follow this instructions, using the USB cord that came with your plugin charger, and let it rock. I watch full motion TV shows and MLB.com TV on a remote lake, if you got 3G, you got broad band. App is free. And the big V isn't sucking an extra $20 out of your bank account each month. If you want a secure version for like bank stuff, it will cost you a one time $23 to upgrade the PC side. Its made my June Fabrics PDA Technology Group . No I dont have any financial interest in this outfit, just like their stuff.

Hope it helps
 
Well, nobody knows for sure, but you'd have to assume so.

The push (build FRG01B) clearly has a severely buggy networking stack. Applying FRG01B risks rendered networking on the Droid unreliable. Consequently, it's no longer possible to reliably push additional upgrades via OTA.

If you can't get on the air, you obviously can't get an upgrade that comes over the air.

Consequently, Verizon had to stop the FRG01B push or risk customers being unable to get future fixes.

Logistically, the problem for Motorola/Verizon is getting the FRG22 update to those users who already have FRG01B. For those still on 2.1, it's imperative that they not be pushed FRG01B upgrade nor the FRG22 update. They must be pushed a different FRG22 that's essentially the combination of the FRG01B/FRG22 that we're seeing now.

If I were Verizon/Motorola, I'd be killing myself getting the FRG22 fix to those who need it. I'd then come up with a brand new FRG22 that can be applied to 2.1.

Clear as mud?

In short, they'll have to issue an FRG22 that installs over 2.1 because there's no other way to upgrade OTA.

This is going to get messy, revision-wise. My advice is:

Don't touch any FRG01B or FRG22 until such time as the FRG01B upgrade/FRG22 fix is known to be safe. By the time it is, the likelihood is that the combo FRG01B/FRG22 will be available for 2.1 Droids.

Bill Stone

Thanks, that cinches it for me. I'm just going to sit tight with my unrooted 2.1 until the day Verizon/Motorola can send out a stable FRG01B/FRG22.
 
I just installed the update and everything installed fine, but the phone keeps freezing and force closing basic things like home, the camera, and browser. overall it's just slow and lag-y, any advice/ideas?:confused:
thanks!
 
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 don't know what you are claiming here. Do you work for Moto or VZ or Google to know if these assertions are true?

I had FRG01B for a few days and it worked okay. Now I've had FRG22 for exactly 2 days. I can report (like many other ppl) that FRG22 is working great.. Everything from 3G, WiFi, USB tether, multiple home screens, Maps, Nav, Phone, & BT are alll working fine. May be I got lucky..
 
I followed the instructions from Trident, and installed through the computer. Again like I said am a Senior Systems Admin, I have seen software work on one machine i.e. Vista where it runs great on one machine and sucks on another.. I can tell you I had a non rooted 2.1 with Touchdown and PDA Net, and some games when I am bored watching backups and crap, but my Android is solid, NO dropped packets, no routers issues which in no way would be affected, no problems with you tube, no problems with wi-fi, no issues with PDA Net as I have been on it all damn thing all day. I did get the error some others did saying aborted, but I just waited did a re-boot, everything came up rather quickly, the shut down, pulled the battery for 30 seconds powered up the phone and BAM! Everything works awsome. So the next OTA with network issues then I wouldnt get it some say, but I have been getting my market place updating my other apps every few days. I personally think this was a good upload, and it got hit hard, servers were getting pounded, files might of been left out, I verifed the file size, the correct name, and no issues. I did 2 of my friends phones today with no issues either, they have said nothing. But just like any upgrade I prepped the phone, cleaned all the files, settings, and just the normal little stuff, I doubt it was the reason but just a thing you always do before an upgrade. I wish everyone luck in what they are trying, I wish I could help, if it was exchange server, or active directory, citrix or cisco I could help, maybe I was just one of the lucky ones when I did it. I did it the same week 2 clients totally lost their domain controllers...LOL. Everyone one wants it now guys, we all do, human nature, you roll the dice. I cant wait for it to get on the Droid X, I love that damn phone. Oh well, be patient, I do think from reading the forums that Trident and OMJ know what they are doing, and would not intentionally put crap out there. I dont know them from a hole in the wall, but they do seem like good guys so props to you for helping everyone get what they have been begging for. There is an old IT wise tale becareful what you wish for in this technology age. And I wont have this droid once the Droid 2 comes out since its preordered allready, so if it keeps running like this I will be happy as hell! It does rock. l8ter all.
 
Back
Top Bottom