Database Users

OTA update in update.zip format with root options

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.

[Q] Rom Manager- Not able to verify whole-file signature

Hey guys,
I am pretty new with the android OS but I am trying my hardest to read up on it and wrap my head around it. so please bear with me.
I have a verizon fascinate that was purchased a week ago and I rooted it.
I have the Rom Manager installed and the OS is running smoothly. I was going to install a custom Rom on my phone but when I tried to back up the current Rom using the Rom manager. it will boot into the Android system recover (2e) and this is what shows up on my phone:
-- Install from Package...
Finding update package...
Opening update package...
verifying update package...
E:faield to verify whole-file signature
E:signature verification failed
Installation aborted.
with that massage I dont think that I have my current Rom backed up any where...
does any one know how I can get passed this step?
I dont have much knowledge about the android operating system so if some one can help me out with this it would be freaking awesome!
---
I have not installed anything crazy, Rooted with the One click root. and Used the Titanium back up software.

You have to flash the Clockwork kernel/recovery onto it to run the update.zip that activates the backup stuff. See here.
MAKE SURE YOU FLASH INTO THE "PDA" SECTION OF ODIN AND NOT THE "PHONE" PART. "Phone" will brick your device.

Works perfect now!
Thank you very much!

i'm having the same problem, but i've already flashed clockwork? did i miss something?

fail fail
E:faield to verify whole-file signature
E:signature verification failed
Installation aborted.
Runing pt Litening_Rom_v1-5.rar tried Litening_Rom_v3-2.rar same isue .
Rom Manager (pro) fails to backup every time. When useing CWM (comeing with Litening_Rom no probelem at all)
And today I tried Litening_Rom_v4.1 same problem

jesterdallas said:
i'm having the same problem, but i've already flashed clockwork? did i miss something?
Click to expand...
Click to collapse
Which version of cwm are you using, and what are you trying to flash?

[Q] CM MOD on SGS

Hey guys,
so, a lot of my quetstions will be already posted, but i can´t find them all.
So i hope i annoy no one here ;-).
Ok, now to the important:
I have a SGS until 6 month. over the time i learnd a lot of android and i´m very lucky with them.
Then i heard from cyanogenmod. and all i read about it is great.
i have knowledges about root of linux an so of android.
So, during my research i have a lot of question before i flash my sgs:
- i found only one forum enty where i read i have to format all partitions.
So, how do i flash a sgs?
i have a modded boot rom with root and clockwork mod.
I tried a backup of the system.
the rom manager don´t show ne the cm7 mod for my device.
Do anyone know why? because the RC status?
When i get an error, how can i rollback my firmware with the backup?
Which pc software i need?
my plan ist to flash the sgs with the experimental version, no nightly build.
CWM makes al lot if IMG files. the cm7 zip has only one IMG.
So, i hope anyone can tell some or send my some nice links.
thanks a lot :-D
ravn

Use this

Boom, that's how it's done folks.
Sent from my I9000m running Cyanogen Mod Nightly

Hey,
thanks guys.
So, can anyone explain me how i can go back to the original rom if i got any probs or even i want?
So, i made a backup with Titanium Backup (premium user) and secondly with CWM.
So, i copied them to my PC.
CWM makes some IMG files. So, how can i rollback them to my device?
Also if i try to create a rom image with the rom manager the recovery manager makes a error.
:-D
So, i get by saving my rom the following error:
-- Installing package ...
Finding update package...
Opening update package...
Verifying update package...
E: failed to verify whole-file signature
E:signature verification failed
Installation aborted.
Why do the rom manager want to install a package by making an backup?
PS: i have the rooted bootloader: PDA_XXJVK_Sbl.tar installed.

to revert back to you need to revert to a stock rom. using odin and a full PDA froyo will do the job.

Hey,
so u mean, i have to download the offical rom and install them over odin.
then i have to root them and install CWM and reverse the backup.
is that right?

ravn83 said:
Hey,
so u mean, i have to download the offical rom and install them over odin.
then i have to root them and install CWM and reverse the backup.
is that right?
Click to expand...
Click to collapse
yes.. that will be the proper way to do it.

Flash Cyanogen over CWM

Hello,
i got a problem, i want to flash cyanogen over CWM. At first i flashed my phone to another Firmware, i used the tutorial.
The flash worked and now i want to flash cyanogen over CWM, but all time i got this Message in the recovery:
E: Failed to verify whole-file signature
E: signature verification failed
Installation aborted.
Someone can help me please??
I got the following building on my Samsung Galaxy S
Firmware-Version: 2.3.6
Basisbandversion: I9000XXJVU
Kernel-Version: [email protected] #2
Buildnummer: GINGERBREAD.XXJVU
It was my first time, that i flashed my phone, i wish someone can help me.
P.S.: my english is not so good

Redownload cm and try again

I did, but it still not work and show me all time the same fail :-(

Try removing your external sdcard and then going into CWM

you are trying to flash an unsigned zip in stock recovery. the stock recovery checks if the zip is signed. if it is, the recovery applies the update. but the zip you are flashing is not signed, so it checks the zip and cannot find a signature. then it aborts the installation.
your solution is to flash a custom kernel, for example Galaxian. after flashing install the zip again, it will work like a charm
if you have any more problems, don't hesitate to send me a PM in German

I wrote you a message Noobproof, hope you understand

[Q] Installation of CyanogenMod 7.2.0-RC1 aborts with (Status 7)

Hi all,
I am having difficulty installing CM 7.2.0-RC1 on my Droid 2. I have been using the official CyanogenMod wiki guide at
wiki.cyanogenmod. com/wiki/Motorola_Droid_2:_Full_Update_Guide
-phone was originally v2.3.3
-as per guide, downgraded to 2.3.2
-verified phone ok running android version 2.2
-successfully rooted with rageagainstthecage
-installed Droid 2 recovery bootstrap & ClockwordMod recovery
-verifed ClockworkMod recovery working - booted into CWM recovery and created backup
Then I tried to apply the CM7.2.0-RC1 zip update:
-put the .zips (CM7.2.0... and gapps) on my sdcard
-bootstrapped into clockworkmod via droid 2 bootstrapper
-apply update from .zip > choose zip on sdcard > chose update-cm-7.2.0-RC1-droid2-signed.zip
everything seems to go fine, then it pops the status 7 error:
Checking kernel version...
If install aborts here
make sure you are on
the OTA and not the
original GB leak!
assert failed: run_program("/tmp/check_kernel") == 0
E:Error in /sdcard/update-cm-7.2.0-RC1-droid2-signed.zip
(Status 7)
Installation aborted.
The part of the error message where it says "make sure you are on the OTA and not the original GB leak" has me confused... I was on the OTA as far as I knew, but then the wiki guide had me downgrade to 2.3.2. I assume that downgrade is a stock OTA update - am I right?
I've done quite a bit of searching, but can't figure out where I've gone wrong. Is there something else I've missed?

So are you on 2.2 or 2.3.3?

Where did you get your release candidate .zip? I would like to check the integrity of the file.
Sent from my DROID2 using xda premium

I keep banging my head against the exact same set of circumstances. I downloaded all of my files directly from the cyanogen wiki. I rooted my device first with SuperOneClick. Assuming that this might be the problem, I then SBFed it back to stock, and rerooted it verbatim per the instructions on the wiki and the cyano build... and continue to get the same results.

It took a bit of digging around in the CyanogenMod forums, but you have to be on the latest .sbf (2.3.3?). CyanogenMod 7.2 is based on the Gingerbread kernel and won't work over the top of a Froyo installation. Though I hear that you can't just flash nightlies (or any update, for that matter) over the top of it. You'll have to .sbf either way. This really sucks for me because I've got to re-flash my phone back to cricKet wireless (an hour process; manual flashing sucks) every time I .sbf as it sets everything back to the VZW defaults.
Sent from my DROID2 using xda premium