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

Namrepus221 said:
Slide the keyboard out and hold it down with a pen cap (which I had to do my first time cause of my fat fingers) and continue to hold it while you power it on. It's possible you're holding down more than one button
Click to expand...

Sadly, no luck. I'm at my wits end here. It was worth a shot, as this buttons are close together.
 
This is really odd, I dont really post. One being a systems admin I am busy all the time. I did this update in less then 2 minutes start to finish, I have some apps I bought, Touchdown, and PDA Net, both work perfect, the wireless is fine, the only issue and only issue is the voice to text. Speed is fast, gallery is perfect, NO freezes, no issues. My Droid was stock, nothing on it at all, no custom rom or anything, just 2.1. Its odd being in the tech industry to see such wide issues... some have, some not, usually technology is almost across the board, like Vista or ME, they sucked for everyone not just a few. This seems really to go all over the place. To me was it worth it, yes because I am a so called techie, is it all that, not really, speed is nice, I much prefer my Droid X, and when that gets updated it will be a awsome device. Oh well had a day off and thought I would post. Peace out
 
Ok I've tried several links given to do the update, and I keep getting this:

E:Can't open /cache/recovery/command

--Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted

Its getting frustrating trying this so much and having to restart phone over and over. So help please! :) THANK YOU! Private messaging me would be best please and thank you:)
 
wrstone said:
In fact, rebooting the router and re-establishing the wireless connection was one of the first things I tried. I'll mess with the router, but I'm unclear what I'd change and what effect it might have on other wireless devices on my home network.

It's obviously not feasible for users to mess with routers at their workplace or public location. ;)

I wonder what the difference between our devices is? My specific situation is:

I was one of the first purchasers of the Droid on release day. Theoretically, I would have an early physical version of the device. If there were any engineering changes from that manufacturing to when others bought their devices, that might account for the difference.

I also applied FRG01B to a stock, non-rooted phone. Perhaps others upgraded from a different circumstance?

I suppose it comes down to a buggy networking stack somewhere. Consequently, any individual device's reaction to the bug(s) may be unpredictable. There may be other apps installed that impact network connectivity in the background, etc.

If anyone's interested, I just blogged about this, retracting yesterday's blog about how to install FRG01B.

Bill Stone
Click to expand...

I got my Droid day 1 of release also. Seems to me there were some wifi issues with early releases of the Droid. I don't recall if it was SW or HW. I never experienced them (other than having to change my droid wifi connecion to always on, rather than reconnecting every time I turned the screen on and off. It constantly made my router reboot). I agree. It sucks that 2.2 would send anyone to their router control panel to get their phone connecting. Pulling 80211b mode out of the compatibility worked for me though.
 
DavidC said:
is there a way to force the new update FRG22?
Click to expand...

Not that I've seen ... and trust me, I'm looking.

In fact, I'm about to downgrade to 2.1u1 just to keep from going insane trying to use the Droid.

The procedure using a Linux workstation appears to be as follows. I'd appreciate any input about this procedure before I potentially brick my phone:


  1. Download sbf_flash.

  2. Download stock Verizon Android 2.1u1 sbf. The file name is
    Code: 
    VZW_A855_ESE81_QSC6085BP_C_01.3E.03P_SW_UPDATE_02.sbf
  3. Boot the Droid into bootloader mode.
    1. Shut down
    2. Hold down the D-PAD Up and Power buttons simultaneously until white text appears.
    3. Plug your Droid in to the computer

  4. Make sbf_flash executable and run it.
    From a Linux shell prompt on your computer, type:
    Code: 
    $ chmod a+x sbf_flash
$ sudo ./sbf_flash VZW_A855_ESE81_QSC6085BP_C_01.3E.03P_SW_UPDATE_02.sbf

According to what I've read, this process will run for a while, during which you must neither lose power nor unplug the Droid from the computer. To do so risks bricking your Droid.

When the phone boots back up, it should be running stock Android 2.1u1.

Has anyone done this procedure, and can you concur that it works before I set off to try it ... ? :)

Thanks in advance,

Bill Stone
 
RgnKjnVA said:
Yes and yes. When the official build is pushed out this version we're running will be recognized as an earlier version of 2.2 and will be replaced with the latest version being pushed. The build we're running is a legitimate build not a hack so this is not a big deal. However, if you haven't 'force installed' it yet IMO you might as well just wait for the official push since it's easier and will surely start any day now.
Click to expand...


I already installed it, I was just curious!
 
Update:
Another OTA update (FRG22) will be coming soon. In order to install it, you must have the update from this thread (FRG01B) installed first. This change has been reflected in the title and OP of this thread.

In case you are to receive the second Froyo OTA update, please read this thread.

Thanks! :)
 
chevy*tough said:
have the same problem why is nobody addressing this issue!!
As for me i have sprecovery installed on mine and is completly stock.
if someone could point me to a stock sbf recovery image i would like to try since sprecovery wont let me install.

downloaded 4diff ones all same problem.HELP
Click to expand...

raid1907 said:
I did everything like ya said and it says E:Error in sdcard/update.zip (status 7) what should I do
Click to expand...


Why no answer to my question but everyone elses?
 
Trident said:
Update:
Another OTA update (FRG22) will be coming soon. In order to install it, you must have the update from this thread (FRG01B) installed first. This change has been reflected in the title and OP of this thread.
Click to expand...

I fear that this cannot occur soon enough to suit my tastes. :p

I look forward to the patch making it into the wild so that I may apply it immediately to see if it resolves my problems.

You know what it's like? It's like the Doctor's Sonic Screwdriver. You get used to it being able to do just about anything, flawlessly, no problem, every single time. Then it gets frakked up, and the next time you want to reverse the polarity of the neutron flow, it just makes a funky noise instead.

What the frak am I going to do if the Daleks show up before the fix arrives??

Bill Stone
 
Can someone please tell me how to return to 2.1. My phone is acting horribly. Please dumb it down so I can do it myself as I made my brother update my phone in the first place.
 
Unfortunately, it can't be returned to 2.1 easily.

The procedure I outlined a few posts back is supposed to work, but it requires a Linux-based computer. I'm sure there's a similar program for Windows and OS X somewhere, but it still wouldn't be a simple procedure.

It's also risky. Accidentally yanking your Droid loose from your computer while it's in-progress might brick the Droid. Losing power to your computer while it's in-progress might brick the Droid. The Droid could decide to get uppity for reasons not immediately apparent; if that happens, it might brick the Droid.

It's really not a procedure for the faint of heart.

I know it's a pain because I'm experiencing it, but the best advice is to hang tight. There's an update coming that will hopefully fix this, and experience suggests that it's probably hours away from being "in the wild". At that point, you can either wait for the push to your phone or apply the fix manually.

Bill Stone
 
I'd really appreciate if someone could tell me how uninstall this update and go back to 2.1,I have had nothing but issues since I put it on here so please help.
Thanks.
 
wrstone said:
Unfortunately, it can't be returned to 2.1 easily.

The procedure I outlined a few posts back is supposed to work, but it requires a Linux-based computer. I'm sure there's a similar program for Windows and OS X somewhere, but it still wouldn't be a simple procedure.

It's also risky. Accidentally yanking your Droid loose from your computer while it's in-progress might brick the Droid. Losing power to your computer while it's in-progress might brick the Droid. The Droid could decide to get uppity for reasons not immediately apparent; if that happens, it might brick the Droid.

It's really not a procedure for the faint of heart.

I know it's a pain because I'm experiencing it, but the best advice is to hang tight. There's an update coming that will hopefully fix this, and experience suggests that it's probably hours away from being "in the wild". At that point, you can either wait for the push to your phone or apply the fix manually.

Bill Stone
Click to expand...

Actually returning to stock really is not that bad. I flashed stock sbf files 4 or five times this week. 3/4 of the way down this post there are instructions for flashing in windows. As long as you dont yank the usb cable out or lose power(I use a laptop to prevent this) there is little to no chance of bricking the droid. I actually have yet to really hear of anyone truly bricking a droid due to software issues. If you arent comfortable with it dont do it but I am just saying its really not that big a deal.
 
The install went great, but I have no program for use as a wireless hotspot. It shows the tethering option, but that's all...any ideas? Thanks!
 
OMJ said:
If you arent comfortable with it dont do it but I am just saying its really not that big a deal.
Click to expand...

I'm actually fairly comfortable with it, but I'm a systems admin. I tend to do a lot of this kind of thing.

The posters who've asked have wanted "simple" downgrade procedures. When users say "simple," what they usually mean is something like a big red button in the middle of the phone marked, "Press This Button To Fix the Problem".

Flashing an SBF, while straightforward, isn't a big red "Fix It" button. It carries some danger, albeit fairly minimal, that novice users should be aware of.

I've bricked phones in the past. I know how to deal with it: how to take the phone to the store, choose the most clueless-looking clerk in sight, look stupid, and say "Duh ... I turned it on and there was this weird crap on the screen." I know how to not tell a clerk or tech I was intentionally flashing ROM images, because that would get me laughed out of the store.

If someone wants to bring the phone to me to re-flash, I'll be happy to try. I just wouldn't recommend it for someone whose brother installed the upgrade and now she wants everything back the way it was. ;)

In point of fact, I think the future of these devices will ultimately include multiple boot partitions: at least a "factory" partition, a "previous OS" partition, and a "user" partition. The "factory" partition would always contain a stock image, bootable at any time, via a big red "Fix It" button. The "previous OS" image would be made immediately prior to updating the OS so that the big red "Fix It" button could boot back to the previous (hopefully stable) configuration.

Actually, now that I think of it, someone should work on that ...

Bill Stone
 
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.
 
Trident said:
Froyo Update 1 of 2:

Another OTA update (FRG22) will be coming soon. In order to install it, you must have the update from this thread (FRG01B) installed first.
--------------------------------​

This thread explains how to force the official Android 2.2 Froyo update to your Motorola Droid. It is made up of two guides. You will have the option of choosing to install the update with either the use of your computer or completely on your Droid. Both methods have been tested thoroughly and work perfectly. With both methods, it is highly recommended that go slowly and read through the entire guide before you begin. It should take no longer than 10 minutes to follow each guide all the way through.


For information about what exactly is included in this update, please see the official release document.

droidfroyo300x292.png

Warning:
-Do not attempt to install this to anything other than the Motorola Droid.
-If you are running anything other than stock 2.1, you will receive an error.
-If you attempt to apply this update with a custom ROM installed, the update will NOT apply.

*You CAN apply this with SPRecovery or Clockwork.

Disclaimer: By continuing, you understand that neither Android Forums nor myself can be held liable for any damage caused to your phone while following a guide included this thread. You do this at your own risk. No exchanges, substitutions, or refunds.

The Guides (Choose One):
-How to install the update with the use of your computer (PC or Mac)
-How to install the update entirely on your Droid without the use of a computer (OTA)


Special Thanks To...
-LarryR for the update.zip file
-Nexeo.net, Polarix, StrifeJester, wee_ag, johnlgalt, blong4life, Inphosys and Dev-Mob for file hosting
-NickMili - without his help we would'nt have this. He provided the semblance of a file name that led us to the correct file on Google's servers.
Click to expand...

So, I'm confused. Without the first update I can't get the second update. What if I haven't gotten the first OTA and don't want to force the upgrade. Will they be somehow combined?
 
So I'm still having trouble with getting into Recovery Mode on my unrooted Droid running 2.1.-update 1

If I do a system reset from the Settings Menu, do you think that will correct my problem? I have already removed the SD card so I don't lose anything on there, and I really don't care about losing texts, and my contacts are saved in the cloud anyway, and from what I understand, it won't delete my downloaded apps.... could this fix my problem with getting into Recovery Mode?

I ask before I try so I don't mess things up.
 
bluboy said:
So, I'm confused. Without the first update I can't get the second update. What if I haven't gotten the first OTA and don't want to force the upgrade. Will they be somehow combined?
Click to expand...

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
 
You must log in or register to reply here.
Back
Top Bottom