• 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 feel really ******ed that this is so difficult. I did as you said and hit allow first. this time it went further but got to verifying current system...

assert failed (a whole bunch of letters and numbers)
E:Error in /sdcard/update.zip
(status 7)
Installation aborted

Download a new copy of the file - delete all the older copies you have of it.

I get to the part where I root the file. I hold X like it ways wile i turn off my phone. But thats all it does, turn off. It wont go to the recovery screen. What am i doing wrong. This seems like a pretty simple task and yet its not working. Ive tried like 10 times now. tips? Or im just dumb.

OK, ummm, read the instructions carefully.

You turn OFF the phone, and then when it is OFF you turn ON the phone holding down X.

Holding it down when you're turning it off does nothing, as you've already realized.

Factory reset didn't resolve the marketplace issue either. Guess I just have to wait and see.

Try waiting until tomorrow.

I can say that I had some missing apps that would nto show when I first tried my first FroYo build, but when I came here to complain the next day...they were there.
 
OK, this was a complete pain but I finally got it working. I was running the leaked 2.2 from a few months ago rooted. I use Linux, specifically Fedora 13, but the following should work on any Linux box (within reason):

1. Download sbf_flash:
OPTICALDELUSION: sbf_flash

2. Download stock 2.1u1 sbf. File name is VZW_A855_ESE81_QSC6085BP_C_01.3E.03P_SW_UPDATE_02.sbf
md5 sum is 06e79f8d0810be281e8afbbd9be7442c
MEGAUPLOAD - The leading online storage and file delivery service

3. Boot your Droid into bootloader mode:
3-A : shut down
3-B: hold down d-pad up and Power until old school white text appears
3-C: Plug your phone in to the computer

4. Make sbf_flash executable and run it:
$ chmod a+x sbf_flash
$ sudo ./sbf_flash VZW_A855_ESE81_QSC6085BP_C_01.3E.03P_SW_UPDATE_02.sbf

That should run, take a while, and reboot. Don't unplug or lose power. If something goes wrong google it, pray, whatever.

When the phone boots back up you'll be stock no-BS 2.1u1. Then download update.zip, reboot into recovery mode, apply the update, and your good.

I had the same problem and had been trying all day to fix it. This solved my problem in 10 minutes. If you were rooted 2.2 and want the 2.2 release unrooted use the above sbf before updating to 2.2. It works! Thank you so much zylogz80!!!
 
this is great, but have an issue.

battery life has gone down WAY WAY too quickly. Three hours after updating battery is dead.

Ive done everything to keep battery ok, ie. task killer brightness down timeout to 15 sec.

it all worked fine with the 2.1 but now battery is really bad. And it doesnt work with the multimedia dock =/

has anyone had any issues like this??
 
No, b/c the OTA update is nonrooted, meaning you'll need to root in order to flash - and if you root the OTA, then you're already running rooted 2.2 so what's the point of flashing a rooted 2.2 over a roted 2.2?
I guess I should have said are there ROM's available like BuglessBeast for those of us who have the OTA 2.2 update? I want to be able to get tethering/hotspot capability without paying Verizon's ridiculous fee.
 
Well I just finished installing it (I used the method without a PC). No problems at all, and my apps on the market are indeed showing up. I just downloaded Adobe Flash Showcase.
 
hi, i'm from venezuela, and i'm trying to get into the recovery mode, holding the x button but i get nothing... the phone boot it self normally
 
this is great, but have an issue.

battery life has gone down WAY WAY too quickly. Three hours after updating battery is dead.

Ive done everything to keep battery ok, ie. task killer brightness down timeout to 15 sec.

it all worked fine with the 2.1 but now battery is really bad. And it doesnt work with the multimedia dock =/

has anyone had any issues like this??

I noticed the quick battery drain also, although I chalked this up to the actual process of upgrading. I am currently charging it back up to see.

I had no problem with the dock. The docking app has changed, but seems to work fine.
 
^hmm alright. hopefully battery is good when i wake up in the morning. i really cant afford to charge every 3 hours.

i take it back lol. the dock works now i just pressed home and it worked. but again hopefully battery is gonna be alright. thats my only complaint.
 
I had the same problem and had been trying all day to fix it. This solved my problem in 10 minutes. If you were rooted 2.2 and want the 2.2 release unrooted use the above sbf before updating to 2.2. It works! Thank you so much zylogz80!!!

I began to suspect this also so I began the process of flashing back to the original sbf and stumbled across your post with success on doing this.

I'll reply back here with the results.
 
Not to be a ****** but Are you 100% sure this is the official 2.2 Update Because i have heard this is the Beta Version still and the official won't be out till probably 1 or 2 days So yea are yall 100% this is the Verizon's Official Release of the update cause i have not got a pop up saying update or even when i went and checked to see if it would check for updates it found nothing .
 
I just deleted it of my sdcard. Redownloaded and tried to reinstall. Same error message as my last post.

Can you post the exact error message? I find it hard to beleive that you're getting this with different files - are you trying to rename the files in any way? Are you extracting them before moving them to the SDCard root?

this is great, but have an issue.

battery life has gone down WAY WAY too quickly. Three hours after updating battery is dead.

Ive done everything to keep battery ok, ie. task killer brightness down timeout to 15 sec.

it all worked fine with the 2.1 but now battery is really bad. And it doesnt work with the multimedia dock =/

has anyone had any issues like this??

Put your phone to charge over night.

battery life is going to go down a bit b/c 1) JIT is enabled, and 2) The CPU is finally 'factory' overclocked, to 800 Max, I believe.

yes i got mine to work. thanks . but still no farmville. so sad.

sad about no farmville on your phone? Is it because you need flash? See http://androidforums.com/motorola-droid/106331-so-where-can-i-get-official-flash-player.html

I guess I should have said are there ROM's available like BuglessBeast for those of us who have the OTA 2.2 update? I want to be able to get tethering/hotspot capability without paying Verizon's ridiculous fee.

The filoe was released about 12 hours ago. I doubt anyone has made a ROM based upon it thus far (although this version *has* been out in leaked form for a while now).

Go check out the all things root forum - in there is another forum for just ROMs.

Well I just finished installing it (I used the method without a PC). No problems at all, and my apps on the market are indeed showing up. I just downloaded Adobe Flash Showcase.

Showcase is nothing wihtout flash itself. See http://androidforums.com/motorola-droid/106331-so-where-can-i-get-official-flash-player.html

hi, i'm from venezuela, and i'm trying to get into the recovery mode, holding the x button but i get nothing... the phone boot it self normally

Do you ahve SPRecovery on the phone?
 
I noticed the quick battery drain also, although I chalked this up to the actual process of upgrading. I am currently charging it back up to see.

I had no problem with the dock. The docking app has changed, but seems to work fine.

Yup, the battery is going to be a bit shorter as I noted in my previus post. It should not be a major change, though.

^hmm alright. hopefully battery is good when i wake up in the morning. i really cant afford to charge every 3 hours.

i take it back lol. the dock works now i just pressed home and it worked. but again hopefully battery is gonna be alright. thats my only complaint.

give it a full charge first. I over clock my phone to 1200 MHz, 700 minimum (well above specs) and the only time I get less than 5 hours is if I am *constantly* on it playing a graphics-instesie game or reading Manga online (yes, I have read manga for 5 hours straight! lol)

I began to suspect this also so I began the process of flashing back to the original sbf and stumbled across your post with success on doing this.

I'll reply back here with the results.

Kewl, please do.

Not to be a ****** but Are you 100% sure this is the official 2.2 Update Because i have heard this is the Beta Version still and the official won't be out till probably 1 or 2 days So yea are yall 100% this is the Verizon's Official Release of the update cause i have not got a pop up saying update or even when i went and checked to see if it would check for updates it found nothing .

try reading my post here: http://androidforums.com/motorola-d...froyo-update-motrola-droid-7.html#post1300999
 
I am still having problems with the Market (some apps that I have, and some that I don't, are missing). I'll wait and see.

But I am also having wifi issues. I keep losing network connection (despite control panel saying I am connected. If I dsconnect and reconnect, wireless connectivity comes back. I have tried forgetting the wifi connection and reconnecting. Works for a bit then the phone loses connection.

I rooted and ran Froyo leak months back and then reverted to rooted 2.1 and the recently rolled back to 2.0* and then flashed stock 2.1. Stock 2.1 ran fine with no probs.

Any opinion as to whether this might be contributing to my problem?
 
I am still having problems with the Market (some apps that I have, and some that I don't, are missing). I'll wait and see.

But I am also having wifi issues. I keep losing network connection (despite control panel saying I am connected. If I dsconnect and reconnect, wireless connectivity comes back. I have tried forgetting the wifi connection and reconnecting. Works for a bit then the phone loses connection.

I rooted and ran Froyo leak months back and then reverted to rooted 2.1 and the recently rolled back to 2.0* and then flashed stock 2.1. Stock 2.1 ran fine with no probs.

Any opinion as to whether this might be contributing to my problem?

The WiFi could be any of a number of things - have you performed a baseband update? Is your connection going flaky and you just not knowing about it? Can you test other devices on th network? Have you tried disabling the WiFi for a few minutes? Have you used a WiFi analyzer to see how the signal strength it?
 
I began to suspect this also so I began the process of flashing back to the original sbf and stumbled across your post with success on doing this.

I'll reply back here with the results.

Ok this worked.

Problem: Rooted 2.2 users attempting upgrade to official 2.2 receiving error during flash - "Verifying the current system" and it stops with a string of numbers.

Solution: I followed the instructions here http://androidforums.com/all-things-root-droid/136508-guide-all-things-root-related.html. Under How to revert back to Stock 2.0, 2.0.1, or 2.1 it explains everything you need to get back to a stock SBF/ROM.

I flashed back to 2.1 SBF, rebooted, dropped the official 2.2 update.zip file on the phone, rebooted to recovery mode, installed the update.zip and viola`

I hope this helps someone else out.
 
Hi.

FIrst time poster, and acctually first time viewer of the site. I have a few questions about this. I really wanna have a back up of my current software incase I wind up making this thing totally FUBAR, I can't find a good tutorial without having root on how to do it, nor any files to download or instructions on how to do it off my phone in general.

Can anyone help me? I just wanna have a backup plan incase somethign really really bad happens like the battery instantly dying or something happening to the phone.

It's only a week and a half old to boot, just bought it from verizon. Has 2.1update1 on it, unrooted.
 
Hi.

FIrst time poster, and acctually first time viewer of the site. I have a few questions about this. I really wanna have a back up of my current software incase I wind up making this thing totally FUBAR, I can't find a good tutorial without having root on how to do it, nor any files to download or instructions on how to do it off my phone in general.

Can anyone help me? I just wanna have a backup plan incase somethign really really bad happens like the battery instantly dying or something happening to the phone.

It's only a week and a half old to boot, just bought it from verizon. Has 2.1update1 on it, unrooted.

Do you ahve the Android SDK on your computer, and a USB cable that you can connect your phone to the computer with?
 
Do you ahve the Android SDK on your computer, and a USB cable that you can connect your phone to the computer with?

Unforutantely no... Like I said, the phone is a week old and I dont' have the SDK just yet.

I do have the USB cable however.

I dont' wanna really "root" the phone itself and have the file (verified to be real as well) on my phone and in the downloads directory, and ASTRO File Manager able to move it to the root dir when needed.
 
First and foremost thank you very much for the help. this last time I tried the install from my phone and followed the directions exactly. I made sure there were no other update.zips on my sd card or computer.

The error message will take awhile to post....

It gets all the way to
Verifying current system...
assert failed :apply_patch_check("MTD:boot:2504704:0b5ee101da41148aa026a32848f609fa4b05403e:2875
392:d104d2ec84a2d0660e786c0fb8174bfacb40796")
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted
 
Unforutantely no... Like I said, the phone is a week old and I dont' have the SDK just yet.

I do have the USB cable however.

I dont' wanna really "root" the phone itself and have the file (verified to be real as well) on my phone and in the downloads directory, and ASTRO File Manager able to move it to the root dir when needed.

Not asking you to root, as this does not require root access.

It *does* require the SDK on your computer.

See my post here: http://androidforums.com/all-things-root-droid/51037-alternate-way-back-your-apps-your-computer.html

First and foremost thank you very much for the help. this last time I tried the install from my phone and followed the directions exactly. I made sure there were no other update.zips on my sd card or computer.

The error message will take awhile to post....

It gets all the way to
Verifying current system...
assert failed :apply_patch_check("MTD:boot:2504704:0b5ee101da41148aa026a32848f609fa4b05403e:2875
392:d104d2ec84a2d0660e786c0fb8174bfacb40796")
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted

I am working with another user who gets this issue too - if I get ti solved with him I'll post back here to let you and everyone else know also.
 
First and foremost thank you very much for the help. this last time I tried the install from my phone and followed the directions exactly. I made sure there were no other update.zips on my sd card or computer.

The error message will take awhile to post....

It gets all the way to
Verifying current system...
assert failed :apply_patch_check("MTD:boot:2504704:0b5ee101da41148aa026a32848f609fa4b05403e:2875
392:d104d2ec84a2d0660e786c0fb8174bfacb40796")
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted

scroll up a few posts and you'll see solution that myself and a few others discovered. In general it appears you were running a rooted version of 2.1 or the early release (and rooted) 2.2. Follow the directions up a few posts and you'll be back in business.
 
scroll up a few posts and you'll see solution that myself and a few others discovered. In general it appears you were running a rooted version of 2.1 or the early release (and rooted) 2.2. Follow the directions up a few posts and you'll be back in business.

Problem is that the guy I am working with is *not* rooted....
 
Oh Wait... I didn't mean my Apps being backed up.

I ment the acctual ROM image itself.

I saw on here that someone basically bricked their phone because they botched their update to 2.2 and they didn't have a back up of their original ROM and had a dead phone basically.
 
Back
Top Bottom