The update in conventional zip format, with root options is here!
P
Works mint! I was running Modoco 1.3 ROM, heres the steps I performed:
recovery install: update-nexusone-ERE27-signed.zip
recovery install: update-nexusone-radio-32.24.00.22U_4.03.00.21_2-signed.zip
./fastboot-linux boot boot.ERE27.superboot.img
./fastboot-linux flash zimage zImage-2.6.29.6
./adb remount
./adb push bcm4329.ko /system/lib/modules/bcm4329.ko
Can I flash this manually WITHOUT being rooted?
I posted a thread on updating without root: http://forum.xda-developers.com/showthread.php?t=627533
Modaco's page confused me a little.
Does the "Main update" include the radio update, or did he split that off and they're completely separate?
Can the main update be installed using a rooted, but stock, rom and recovery?
In other words, if I just want exactly what the OTA would give me, on my rooted (by superboot) but stock N1, what do I need to do?
Thanks!
I'm completely stock rom / not rooted and I just did this:
http://androidforums.com/nexus-one/41504-how-force-2-2-2010-ota-update.html#post316090
1. Get the update from Google: http://android.clients.google.com/updates/passion/signed-passion-ERE27-from-ERD79.a487b405.zip
2. Put the update on your SD card & rename it to update.zip
3. Boot in recovery mode (hold down trackball + power)
4. Go to bootloader -> recovery
5. Now there's a picture of a droid with a triangle
6. Press the power button + volume up
7. Apply sdcard:update.zip
8. Updating
9. Reboot system now
10. Enjoy the multitouch
Click to expand...
Click to collapse
Worked great.
Thanks Paul. That's what I first tried, and it failed. I posted the details here, but haven't heard anything back yet.
http://forum.xda-developers.com/showpost.php?p=5528501&postcount=118
Mine is ROOTED, but stock, so.....
tonyx3 said:
Modaco's page confused me a little.
Does the "Main update" include the radio update, or did he split that off and they're completely separate?
Can the main update be installed using a rooted, but stock, rom and recovery?
In other words, if I just want exactly what the OTA would give me, on my rooted (by superboot) but stock N1, what do I need to do?
Thanks!
Click to expand...
Click to collapse
I'm in the same exact boat as you. I rooted my phone last week because i was eager to get multitouch working, so i followed this tutorial:
theunlockr[dot]com/2010/01/21/how-to-enable-multitouch-browsing-on-your-nexus-one-using-the-native-browser/
So now when i try to apply the OTA update manually in recovery mode i get:
Code:
E:Can't open /cache/recovery/command
-- Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Verifying current system...
assert failed: apply_patch_check("/system/app/Browser.apk" , "68a23e4ac9d6a783b6166b24ab79d12c6544e8f4" , "4da6d3fd306ef7fc81e19147da395f13221e70307")
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted.
Does anyone know what i can do to get this OTA up and running? Im rooted but i havent flashed any custom roms or recoveries either.
This is my first android phone so i'm a bit of a noob and new to the scene. Any help would be greatly appreciated
Paul22000 said:
Can I flash this manually WITHOUT being rooted?
Click to expand...
Click to collapse
yes, just did it 5 min ago
PhantomRampage said:
I'm in the same exact boat as you. I rooted my phone last week because i was eager to get multitouch working, so i followed this tutorial:
theunlockr[dot]com/2010/01/21/how-to-enable-multitouch-browsing-on-your-nexus-one-using-the-native-browser/
So now when i try to apply the OTA update manually in recovery mode i get:
Code:
E:Can't open /cache/recovery/command
-- Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Verifying current system...
assert failed: apply_patch_check("/system/app/Browser.apk" , "68a23e4ac9d6a783b6166b24ab79d12c6544e8f4" , "4da6d3fd306ef7fc81e19147da395f13221e70307")
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted.
Does anyone know what i can do to get this OTA up and running? Im rooted but i havent flashed any custom roms or recoveries either.
This is my first android phone so i'm a bit of a noob and new to the scene. Any help would be greatly appreciated
Click to expand...
Click to collapse
http://www.nexusforum.net/nexus-one-help-forum/493-how-manually-retrieve-new-update-your-nexus-one.html#post2000
check that guide out, it was simple and easy to follow...
Thanks JHaste.
But those are pretty much the exact instructions I followed that gave me the error.
My phone is rooted, but running the stock rom.
No custom rom, no patched browser.
The only changes I've made since rooting it are to copy some Thai fonts into the fonts directory.
The exact specifics of my error are posted in:
http://forum.xda-developers.com/showpost.php?p=5528501&postcount=118
Very similar to what PhantomRampage listed, but a slightly different cause, I think... (his is an error on Browser.apk)
JHaste said:
-Removed quoted link since i cant post them yet-
check that guide out, it was simple and easy to follow...
Click to expand...
Click to collapse
Thanks for trying but as i said before, i tried that and it fails because i have an unlocked bootloader.
Sorry if my first post was confusing, ill try again.
I unlocked my bootloader and rooted my N1 the other day, i also modified and added some files to get pinch-to-zoom working on the native browser. To do that i followed some tutorial on theunlockr, i cant post direct links so google it and you'll find it easily.
So, now i want to apply the new OTA update but it fails, either because i have root access or because i tampered with the browser files im guessing.
Knowing all that, what can i do to install the new update?
Also, will i have to download patched updates from now on since i rooted my phone? I'm really hoping i dont have to; i'd prefer to install the ota updates as they come out officially.
might have found a solution
check out:
forum (dot) androidcentral (dot) com / google-nexus-one/6469-will-my-n1-receive-ota-ere27-update-cyanogen-mod (dot) html
seems to be just what i was looking for but i think i want to re-flash the stock firmware instead, i want to stay as stock as possible so i can install future OTA updates without having to go through all this trouble. Can anyone help me with that please?
Anyways, i hope my link will help some people. Sorry for the double post
Closing Double Thread (it's also at Development).
Please do not duplicate threads if not necessary.
Related
Hi all, I followed the directions here to root my phone and unlock my bootloader and things have been great!
But, I can't get install the OTA update. When the auto-updater failed, I tried the manual install per these directions:
androidcentral.com/how-manually-update-your-nexus-one (new user can't post links)
However, I never see
"Your phone will reboot, giving you a picture of the Android robot and an exclamation point inside a triangle."
or
"Apply sdcard:update.zip"
I do have the option to "Flash zip from sdcard" and I select "SDCARD:update.zip"
Then I get the following
Build : RA-nexus-v1.5.3
.... (Confirm install stuff)
Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E; No signature (208 files)
E: Verification failed
Installation aborted.
http://android.modaco.com/content/g...-online-kitchen-optional-root-insecure-himem/
You need to follow these instructions.
Can you give me some more info about this? Will this wipe all my settings and apps? Will I have to unlock/root my phone again afterwards? Why is this necessary, is there a problem with my build or is this something that everybody has to follow who did the unlock/root process.
kesi said:
Can you give me some more info about this? Will this wipe all my settings and apps? Will I have to unlock/root my phone again afterwards? Why is this necessary, is there a problem with my build or is this something that everybody has to follow who did the unlock/root process.
Click to expand...
Click to collapse
You dont have to wipe, unless maybe you are coming from a Cyanogen ROM.
Its something that everyone who is rooted has to do. You will have to install the modified update, and then flash the boot.img of your choice, unrooted/rooted/rooted with himem.
So download this under "ERE36B - update zip format": http://android.modaco.com/content/g...-online-kitchen-optional-root-insecure-himem/
and then go here and select which one you want
http://android.modaco.com/content/g...ere27-ere36b-superboot-rooting-the-nexus-one/
cred05 said:
So download this: <first link>
and then go here and select which one you want
<second link>
Click to expand...
Click to collapse
That top link just redirects to the modaco.com home.
You dont have to wipe, unless maybe you are coming from a Cyanogen ROM.
Click to expand...
Click to collapse
I think I may have used the Cyanogen mod, is there a way to tell and should I still follow these directions if so?
kesi said:
That top link just redirects to the modaco.com home.
Fixed.
I think I may have used the Cyanogen mod, is there a way to tell and should I still follow these directions if so?
Click to expand...
Click to collapse
If you go settings>>about phone>>look towards the bottom and look for something that says cyanogen.
You can still follow the instructions, but if it doesnt want to install the update, or you get force closes once you reboot, you will have to do a wipe and do it again.
Also if you want the latest radio, install this from under the first link: "ERE36B / 32.26.00.24U_4.04.00.03_2 radio - update zip format"
Ok, I don't see anything about Cyanogen so I'm going to go ahead and try to follow these directions. What do you mean by "new radio"? My build number is ERD79
So just to confirm that I'm doing the right thing, I want to use this image "Superboot for ERE36B with himem enabled" for the most updated that will root and unlock and this will contain the OTA update?
I received 2 updates from google today installed the first one and all was well and the second one the update hung on the triangle and exclamation mark. I am not sure what to do. Any and all help is very much appreciated. I am rooted but on the stock last updated rom. I had flashed clockworkmode recovery. Since the first update of the two went well I just figured the second was a slam dunk. Boy was I wrong. How do I go about flashing back to clockworkmode recovery.?
Edit: Pulled battery and hit power button and the device booted back up to frf91 and not frd83d I am still rooted and cannot understand what just happened. I installed the first of two updates that were required and the second hung up and Now it shows me with system up to date. Do I have to flash to stock? I thought I was on stock as it was a manual install of an OTA The only thing i have done is root it with the one click root and flash clockworkmode recovery. No custom roms or anything of that nature. Am I not able to update to Gingerbread now when it comes out? Any help?/Please!!
I had the same thing happen to me about an hour ago. Any one have any info on this?
madmikethespoon said:
I had the same thing happen to me about an hour ago. Any one have any info on this?
Click to expand...
Click to collapse
Are you rooted and have flashed clockworkmode recovery? did the first update seem to install in an odd way but it finished and rebooted back up okay?
i had the same problem happen but it simply hung there with the exlamatiom mark, so i pressed Power + Volume up and this is what was displayed in the recovery:
(this was actually copied from my second retry with a manual install but i'm sure the error was mostly the same)
Finding Update Package...
Opening Update Package....
Verifying Update Package...
Installing Update Package...
Veryifying Current System...
assert failed: apply_patch_check("/system/framework/am.jar","e28...","8cf...")
Error in /sdcard/update.zip
(status 7)
Installation aborted
So i thin i'm running a stock Rom with stock Recovery but i'm not sure... i used this rom --> http://loadbalancing.modaco.com/dow.../update-nexusone-FRG83-stock-radio-signed.zip
(but the link seems to be dead) and installed it with Rom manager using the clockwork recovery later i used the Flash_image method to reinstall stock recovery but i have a feeling something isn't right... any help??
thx in advance
Booted into recovery, tried doing the update.zip got Installation Aborted error (status 7).
Full Error:
Code:
-- install from sdcard...
finding update package...
opening update package...
installing update...
assert failed: file_getprop (" /system/build.prop", "ro.build.fingerprint") == "verizion/shadow_vzw/cdma_shadow/shadow:2.2/vzw/23.15:user/ota-rel-keys,release-keys" || file_getprop(" /system/build.prop" , "ro.build.fingerprint") == "verizion/shadow_vzw/cdma_shadow/shadow:2.2.1/vzw/23.340:user/ota-rel-keys,release-keys"
E:Error in /sdcard/update.zip
(Status7)
Installation aborted.
doronster195 said:
I was rooted with z4, had apps frozen with titanium backup, have bootstrap, used dx overclocker (to undervoltage and to do a quick-boot with "android" logo rather than Droid Eye). I unrooted, unfroze, stock voltage/speed and turned off apply at boot, FORGOT to undo the quick-boot (but I thought it wouldnt matter since i'm unrooted).
Booted into recovery, tried doing the update.zip got Installation Aborted error (status 7), pressed reboot phone and got the M, followed by the "android" logo that WILL NOT GO AWAY.
Phone won't load, what should I do? Need phone to work soon!
Click to expand...
Click to collapse
Ok it sounds like you are stuck in a bootloop.....you can restart your phone by doing a batt pull then when you go to turn it on hold the power button and home at the same time until you see the exclamation mark and droid guy ..this means you are in recovery mode ...then press the search button and a menu will appear ....use volume rockers to scroll and the camera or menu button to select ....go to data wipe/factory reset and select it ...then reboot and if it works your x will be back to how it came out of box if it doesn't then you will have to sbf ...find the sbf file for whatever system version you are on and flash it and that should work
Well, I did a restore, which worked. However, I'd still like to receive the OTA update. I downloaded the update.zip and want to install it myself. Why was i given this installation aborted error? Was it truly because of what I said above--quick boot option?
Edit: Tried booting into normal recovery (not bootstrap), while not rooted, and no rooting tasks have been done since the restore. Trying to "apply sdcard:update.zip" gives me an Error in /sdcard/update.zip (status 7) Installation Aborted
Edit2: Original Post updated with issue
I'm in the same boat...
I unfroze the bloat and unrooted my phone, it was stock with all bloat froze so nothing out of the ordinary to be concerned about.
Ran update.zip and got the same error as you. I'm not savvy enough to understand or figure out what's going wrong with any certainty. My best guess is that something in the build prop doesn't jive with the build prop the update.zip file checks against. I doubt rooting would have caused any change in my build prop and I never did anything to my phone other than root and freeze bloat so my build prop should be fine.
Problem Solved
Fixed the issue thanks to the help from the guys at: (#androidchat on freenode)
specifically tabe and krayzee.
I am 2.3.15 originally, with a bootloader 30.04 (not 30.03).
I used the sbf (that I got from androidchat), and just sbfed. Before activating my phone again, I did the update.zip and it worked just fine.
Guide I used for SBF: droidxforums /forum/hacking-help/12015-complete-droid-x-sbf-flashing-guide.html
(it says you should be careful if you are on 30.04, but i did it on 30.04 so you will be fine)
Hope this helps.
Can you share the sbf I am having the same issue and it is ticking me off. Thanks in advance
i posted the link for the sbf in the above post, i cannot post actual links, so you'll have to add to figure out the url for yourself. Just go to androidchat*org and go to their file database, its in there.
doronster195 said:
Fixed the issue thanks to the help from the guys at: (#androidchat on freenode)
specifically tabe and krayzee.
I am 2.3.15 originally, with a bootloader 30.04 (not 30.03).
I used the sbf (that I got from androidchat), and just sbfed. Before activating my phone again, I did the update.zip and it worked just fine.
Guide I used for SBF: droidxforums /forum/hacking-help/12015-complete-droid-x-sbf-flashing-guide.html
(it says you should be careful if you are on 30.04, but i did it on 30.04 so you will be fine)
Hope this helps.
Click to expand...
Click to collapse
Which sbf did you use? Do you have a link to that? PM if necessary...
I have rooted my Nexus 4 with Tool Kit and flashed it with stock 4.3 image. Few days later came new small security patch for 4.3. Now every few days I get the notification on my phone but when I try to let it install, it does not get installed.
Here is phone info:
Android version: 4.3
Build number: JWR66V
Kernel: 3.4.0-perf-gf43c3d9
I will appreciate your help. Is this update available as a zip file on the forum? if it is, then I can side load it on my rooted phone.
I will appreciate any help.
I have this too
If it helps, I have to problem too.
I have rooted my phone and installed ClockworkMod Recover v6.0.2.3 but have not installed any custom ROM or other changes (that I know of).
I periodically get a messge an update has been downloaded, but when I attempt to install it, ClockworkMod informs me:
Code:
E: failed to verify whole-file signature
E: signature verification failed
Since I don't know what it is, I abort the install, but I can't tell what is happening. I would also appreciate any help.
Regards,
Bret
rookie8155 said:
I have rooted my Nexus 4 with Tool Kit and flashed it with stock 4.3 image. Few days later came new small security patch for 4.3. Now every few days I get the notification on my phone but when I try to let it install, it does not get installed.
Here is phone info:
Android version: 4.3
Build number: JWR66V
Kernel: 3.4.0-perf-gf43c3d9
I will appreciate your help. Is this update available as a zip file on the forum? if it is, then I can side load it on my rooted phone.
Click to expand...
Click to collapse
Im not good with these type of thing but here http://forum.xda-developers.com/showthread.php?t=2145848 alot of guys here can help you, and i think the OP already has a solution on the 1st page
bcw1000 said:
If it helps, I have to problem too.
I have rooted my phone and installed ClockworkMod Recover v6.0.2.3 but have not installed any custom ROM or other changes (that I know of).
I periodically get a messge an update has been downloaded, but when I attempt to install it, ClockworkMod informs me:
Code:
E: failed to verify whole-file signature
E: signature verification failed
Since I don't know what it is, I abort the install, but I can't tell what is happening. I would also appreciate any help.
Regards,
Bret
Click to expand...
Click to collapse
Yes, I have also installed ClockworkMod Recover v6.0.2.3 and running stock ROM as well. . If this update is available as a zip file then we can install it. It should not be just two of us having this issue. Everyone who rooted phone should have same issue.
HeyyMyNameIs said:
Im not good with these type of thing but here http://forum.xda-developers.com/showthread.php?t=2145848 alot of guys here can help you, and i think the OP already has a solution on the 1st page
Click to expand...
Click to collapse
Thanks for pointing towards the right direction. I tried to side load the zip but it failed. I will post the question in the other thread.
I have a seroius problem with the new OTA Update... I can't update my cellphone.
CWM-based Recovery v6.0.4.9
Swipe up/down to change selections.
Swipe to the right for enter.
Swipe to the left for back.
E: Invalid command argument
Finding update package...
Opening update package...
Verifying update package...
E: Failed to verify wole-file signature
E:signature verification failed
(At this point it displays if i want to install an untrusted zip. Of course I say "yes")
Installing update...
Verifying current system...
"/system/app/Zap.apk" has unexpected contents.
E: Error in /cache/Blur_Version.183.46.10.XT907.Verizon.en.US.zip (Status 7)
Instalation aborted.
Rebooting...
(Displays what possibly the root access is lost and if I want to fix)
WHAT TO DO!? :crying:
You must have stock recovery from (pull it) the XML, unzipped. Use Rashr tools to flash the img.
aviwdoowks said:
You must have stock recovery from (pull it) the XML, unzipped. Use Rashr tools to flash the img.
Click to expand...
Click to collapse
Sorry... What? I'm going to ask the noobest question forever (and I'm coming from I5500 and go from ROM to ROM with ODIN :silly
What img? Do you mean the stock recovery (I felt stupid asking this) or the update.zip? Assuming it's an update.zip what I don't know where it is
Pedreo1997 said:
Sorry... What? I'm going to ask the noobest question forever (and I'm coming from I5500 and go from ROM to ROM with ODIN :silly
What img? Do you mean the stock recovery (I felt stupid asking this) or the update.zip? Assuming it's an update.zip what I don't know where it is
Click to expand...
Click to collapse
In order to take the ota you need the original recovery from the build you have now. Once you unzip the firmware (xml.zip) it will be the recovery.img file. Flash that with Rashr tools from Play. I assume you have a VIRGIN phone/root file structure, if not the ota will still bomb out. In that case RSD LITE restore the whole XML. Be sure to backup the current ROM even if it is not custom.
The stock recovery img... But even with that it still may not update if you have modified your system any.... Debloated deodexed xposed these things may prevent the update..
We cannot teach people anything; we can only help them discover it within themselves.
ezknives said:
The stock recovery img... But even with that it still may not update if you have modified your system any.... Debloated deodexed xposed these things may prevent the update..
We cannot teach people anything; we can only help them discover it within themselves.
Click to expand...
Click to collapse
I really fix it making a backup of everything and after re-installing the ROM :silly: