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

[How-To] Force 2/2/2010 OTA Update

The procedure:

1. obtain the update.zip file
2. reboot into the bootloader
3. select recovery
4. apply sdcard:update.zip

Specifics

Obtain the file from here:

https://android.clients.google.com/updates/passion/signed-passion-ERE27-from-ERD79.a487b405.zip -Thanks Fabolous

OR

signed-passion-ERE27-from-ERD79.a487b405.zip - Thanks DEMO_BURN

ONLY IF YOU ARE ROOTED AND HAVE AN UNLOCKED BOOTLOADER, get the file from here:
03/Feb ERE27 - New update rooted and unrooted, optional radio, optional himem - Android @ MoDaCo - Thanks FLT


-Rename the file to update.zip (in Windows, just rename to update - it is already a zip file)

-Make sure the update.zip file is on the root of your sdcard (not in any folders)

-To reboot into the bootloader, turn off the phone. Then power on while holding down the trackball.

Navigate to the option 'recovery' using the volume up/down keys - Thanks peader

When the Android w/ caution logo pops up, hold down the power button then press volume up (while still holding down power) - Thanks FLT

Select 'apply sdcard:update.zip'

Thanks chief99 for the bootloader specific instructions.

Enjoy!
-----------------------------------------------------------------------

FAQ

-Does this work on any other phones besides the Nexus One? Absolutely not! Do not do it!

-Will this void my warranty? How do I know it's legit? No, this won't void your warranty. The source above is the exact location that people who legitimately got the OTA update downloaded their update.zip files from. Also, after the update has been applied, it is impossible to distinguish between those that got it OTA or forced it.

-Does this wipe my settings or applications? No, the update only touches your system files and radio. All your apps and settings will be preserved!

-If I force update with this method, will I still receive an OTA update? No, once you've updated, you will not get any further notices to update.

-If I'm in an unofficial country (not launched by Google yet) with an unlocked N1, will I still get the update OTA? I'm not certain yet, but as confirmed by many users, this update will work on your phone. There is no danger is forcing the update, rather than waiting for Google to (maybe) push it out to you.

-Will this method work if I have a rooted N1 with unlocked bootloader? No, you'll have to download a modified version of the update file (link above) that will not break your root access.

-It's 'frozen' at a picture of an Android, and arrow, and a box. Is my phone bricked?! No, you're okay. Just be patient as the update is doing it's thing.

It was a breeze, thanks pal!
I was hoping to do a custom install to remove multi-touch pinch zoom, yep you read it right.... I'm not fond of it because in many cases it requires both hands to operate: One to hold phone while other pinch zooms. Not a problem for guys like me who can drive with knee all while pinch zooming maps for a close-up followed by an up-shifting to 3rd without missing a beat. :D Anyway, much to my surprise the NX-1 retained its native (one hand to operate) zoom in addition to installing pinch zoom. Go Google Go! = )
 
Upvote 0
Hi everyone.

A couple of weeks ago, I unlocked the bootloader on my N1 (i.e. when I first boot the phone up, there is an unlocked pad lock icon under the Nexus One logo) for the purpose of applying the 'unofficial' pinch-to-zoom modification to the browser. I've been trying to manually apply the OTA update with little success. I've downloaded the zip file specified on this thread's first page for an unlocked bootloader, renamed it to update.zip (not update.zip.zip or anything of the like) and placed it squarely in the root of the SD card. Whenever I get to the point where I want to actually apply the update, I always get the following:

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.

I've tried this several times with the same exact result. If anyone could give me a hand with successfully applying this update, I'd really appreciate it. Thanks!
 
Upvote 0
Hi everyone.

A couple of weeks ago, I unlocked the bootloader on my N1 (i.e. when I first boot the phone up, there is an unlocked pad lock icon under the Nexus One logo) for the purpose of applying the 'unofficial' pinch-to-zoom modification to the browser. I've been trying to manually apply the OTA update with little success. I've downloaded the zip file specified on this thread's first page for an unlocked bootloader, renamed it to update.zip (not update.zip.zip or anything of the like) and placed it squarely in the root of the SD card. Whenever I get to the point where I want to actually apply the update, I always get the following:

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.

I've tried this several times with the same exact result. If anyone could give me a hand with successfully applying this update, I'd really appreciate it. Thanks!

I have the exact problem.
From what I understand its because when we put the unofficial' pinch-to-zoom modification, this changed the devices file signatures.
Now when you go to put on the official patches they fail with a signature error because they are now different.
Not sure how to fix this a I am new to android and I am not sure about future updates will work because of this file change.
I think we need to reset back to the original state or stick on a modded ROM when the become available..
Trying to find out how to do this and if it will wipe data?
any ideas ?
 
Upvote 0
I have the exact problem.
From what I understand its because when we put the unofficial' pinch-to-zoom modification, this changed the devices file signatures.
Now when you go to put on the official patches they fail with a signature error because they are now different.
Not sure how to fix this a I am new to android and I am not sure about future updates will work because of this file change.
I think we need to reset back to the original state or stick on a modded ROM when the become available..
Trying to find out how to do this and if it will wipe data?
any ideas ?

before u wipe your phone, try to "save as" locate your SD card then download the file straight to your SD card. then rename the file to update, it should already be a zip file.

this worked for me and i was also having the same problem.
 
Upvote 0
FLT,

I've tried the same process with the update zip file for stock N1s. I get the following this time:

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

--Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
Installing update...
assert failed: apply_patch_check("/system/app/Browser.apk", "<a whole bunch of numbers and letters>", "<more numbers and letters>")
Error:Error in /sdcard/update.zip
(Status 7)
Installation aborted.

I followed Slow_racer's tip of downloading directly to the SD and still got this error. The installation does starts, but fails. The error references the Browser.apk file as a source of trouble; a couple of weeks ago, I applied the unofficial multitouch browser file. Does this error indicate that that hack is conflicting with the update? If so, is there a workaround besides re-flashing the original stock ROM? And if I have to restore to the stock ROM, could someone give me some pointers on how to do this? Sorry for the noob questions, but I really appreciate the tips you guys are giving me. Thanks.
 
Upvote 0
Does this error indicate that that hack is conflicting with the update? If so, is there a workaround besides re-flashing the original stock ROM? And if I have to restore to the stock ROM, could someone give me some pointers on how to do this? Sorry for the noob questions, but I really appreciate the tips you guys are giving me. Thanks.

Idd that's the reason :)

You can put the original browser back from the stock ROM via ADB shell
 
Upvote 0
Upvote 0
Hi everyone.

A couple of weeks ago, I unlocked the bootloader on my N1 (i.e. when I first boot the phone up, there is an unlocked pad lock icon under the Nexus One logo) for the purpose of applying the 'unofficial' pinch-to-zoom modification to the browser. I've been trying to manually apply the OTA update with little success. I've downloaded the zip file specified on this thread's first page for an unlocked bootloader, renamed it to update.zip (not update.zip.zip or anything of the like) and placed it squarely in the root of the SD card. Whenever I get to the point where I want to actually apply the update, I always get the following:

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.

I've tried this several times with the same exact result. If anyone could give me a hand with successfully applying this update, I'd really appreciate it. Thanks!


We may be holding glitchy phones.

I Just talked to a Google representative on their support line. Tried everything to get the update, manual, factory reset and nothing worked.

I was told that certain phones have had this problem with NOTHING working to get the update. I was told the matter would be looked into and I would be reached by 10 days.

Unbelievable.

:(
 
Upvote 0
To all of those who are having problems manually updating or automatically updating. Here was my problem and solution in hopes it helps someone else out there.

I was getting the dreaded
"E:signature verification failed
Installation aborted."

After checking my current build I found I was on a very old test build, not even ERD79. Since every thing was written assuming ERD79 I figured that was my first step, if you already have this then you can move on to the ERE27 portion below.

Flashing ERD79:
There are instructions for this everywhere, but basically I UNLOCKED (yes, bye bye warranty) and then flashed the ERD79 Image which I found here, at the top. I used the IMAGE not the ZIP. If you don't know how to do this just read around a bit.

After I flashed this on, I was prompted for the OTA update, but it failed with the signature errors still... Sooooo, I tried a custom recovery console...

I got Amon_Ra's custom recovery from here.

After that was downloaded, I flashed it on to my phone, overwriting the vanilla recovery.

That was done by using fastboot and the following commands:
Code:
Copy recovery-RA-nexus-v1.5.3.img to a location where fastboot can find it.
Boot your phone into fastboot mode (power on while holding the trackball)
Connect your phone via usb to your pc/mac/...
fastboot devices (to make sure that fastboot "sees" your phone)

fastboot flash recovery recovery-RA-nexus-v1.5.3.img
I rebooted and tested to make sure everything was solid, it was so I moved on to this.

I went back to the link above with the image files, here. And I downloaded the file titled: "ERE27 - update zip format" it is the ere27 update.zip meant to be applied via a MODIFIED RECOVERY, which should help kill those signature errors we are getting.(It did for me at least)

Change the file name to update.zip, drop it on the root of your SD card and boot into the modified recovery console. Then select to apply update from sdcard.


This did it for me after the install was complete I was solid and running ERE27.


I know I wrote this missing many things but honestly I am a newb at this so my intentions are that it helps another newb out there figure it out.

Good luck.
 
Upvote 0
To all of those who are having problems manually updating or automatically updating. Here was my problem and solution in hopes it helps someone else out there.

I was getting the dreaded
"E:signature verification failed
Installation aborted."

After checking my current build I found I was on a very old test build, not even ERD79. Since every thing was written assuming ERD79 I figured that was my first step, if you already have this then you can move on to the ERE27 portion below.

Flashing ERD79:
There are instructions for this everywhere, but basically I UNLOCKED (yes, bye bye warranty) and then flashed the ERD79 Image which I found here, at the top. I used the IMAGE not the ZIP. If you don't know how to do this just read around a bit.

After I flashed this on, I was prompted for the OTA update, but it failed with the signature errors still... Sooooo, I tried a custom recovery console...

I got Amon_Ra's custom recovery from here.

After that was downloaded, I flashed it on to my phone, overwriting the vanilla recovery.

That was done by using fastboot and the following commands:
Code:
Copy recovery-RA-nexus-v1.5.3.img to a location where fastboot can find it.
Boot your phone into fastboot mode (power on while holding the trackball)
Connect your phone via usb to your pc/mac/...
fastboot devices (to make sure that fastboot "sees" your phone)
 
fastboot flash recovery recovery-RA-nexus-v1.5.3.img
I rebooted and tested to make sure everything was solid, it was so I moved on to this.

I went back to the link above with the image files, here. And I downloaded the file titled: "ERE27 - update zip format" it is the ere27 update.zip meant to be applied via a MODIFIED RECOVERY, which should help kill those signature errors we are getting.(It did for me at least)

Change the file name to update.zip, drop it on the root of your SD card and boot into the modified recovery console. Then select to apply update from sdcard.


This did it for me after the install was complete I was solid and running ERE27.


I know I wrote this missing many things but honestly I am a newb at this so my intentions are that it helps another newb out there figure it out.

Good luck.

Seems waaaaay complicated and doing something that nukes the warranty just seems too scary.
 
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones