Jump to content

21/Oct Stock ROMs - ERD79 -> FRG83 images / zip / online kitchen (optional root / insecure)


Guest PaulOBrien

Recommended Posts

OK, here is my situation:

I have unlocked bootloader and rooted my N1. I installed the RA recovery image and backed up NAND. I also had installed the wireless tether app with required me to update my kernel. Awesome app btw.

I tried to update using the 'Main Update' download, which I renamed to Update, through the recovery process. I get an error:

-------

...

Verifying update package...

E:Corrupt file:

system/app/Mms.odex

E:Verification failed

Installation aborted.

---

Any help would be appreciated....I am pretty much a n00b here, sorry.... Do I need to wipe first? Is there a better way to do this? Should I cook up an update using the kitchen so I can keep my phone rooted with wireless tether and save some steps?

Thanks for any suggestions...

Link to comment
Share on other sites

EDIT: It looks like it works now....I tried again but without renaming the zip file, and it worked. multitouch! looks like I lost superuser, but i expected that.

Also, I am using the stock ROM, and I installed cyanogen's multitouch browser hack, which is why i think i can't push the standard update...

OK, here is my situation:

I have unlocked bootloader and rooted my N1. I installed the RA recovery image and backed up NAND. I also had installed the wireless tether app with required me to update my kernel. Awesome app btw.

I tried to update using the 'Main Update' download, which I renamed to Update, through the recovery process. I get an error:

-------

...

Verifying update package...

E:Corrupt file:

system/app/Mms.odex

E:Verification failed

Installation aborted.

---

Any help would be appreciated....I am pretty much a n00b here, sorry.... Do I need to wipe first? Is there a better way to do this? Should I cook up an update using the kitchen so I can keep my phone rooted with wireless tether and save some steps?

Thanks for any suggestions...

Edited by pwnvds
Link to comment
Share on other sites

I just dl the lastest beta5.0 rom, but i found that the "boot.ERE27.superboot.himem.img" didn't included netfilter kernel. It made the "wireless tether for root users" can't work. online kitchen baked is the same.

But when I load "nexusone-zimage å’Œnexusone-2.1-update.zip" into N1 in order to add netfilter kernel separately, the "himen" disappeared. The remain memory just down to 100MB below.

Can u just release the "himem.img"??

I have this problem too... how can we use both himem and wireless tether? is this possible right now? I noticed that's Paul's cyanogen mod-kitchen has the wireless tether option to bake in, but I don't really want to get a custom ROM - I just want to use the wireless tether app... for now, i'm installing the nexusone zimage which I guess will eliminate himem, but it would be nice to have both. BTW thanks Paul, Cyanogen, and all of the rest who post on here to help make all this possible.

Link to comment
Share on other sites

Guest ReGGaEt0N

I bought a Nexus One from someone and could not install the OTA update from google.

it appeared it has been flash to a custom modaco rom

I would like to restore it to stock

I downloaded the stock rom in image format two times and it appears to be corrupt (not unzipping)

Any other host I can download it from?

Please help

Edited by ReGGaEt0N
Link to comment
Share on other sites

Hi,

I installed this update, rooted, with superboot and new radio version.

I have an issue copying files to my sdcard, when i mount the sd card in my pc, using the nexus and I try to copy some files to the sd card the device reboots aleatory.

I can't copy files to sd card connecting the phone to my PC by USB, the device reboots when I am copying files to the sd card.

Someone with this issue? some suggestion?

Thanks!

EDIT: I tryed mounting the sd card from the recovery and it works perfectly, only reboots when i am in android system.

Edited by Ozius
Link to comment
Share on other sites

Guest nethium

Getting this behavior when trying to apply a cooked rom OR even if I try to apply the packaged update.zip from step 1.

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.

My device has an unlocked bootloader, it's been rooted, and it's got the mod for the multitouch from cryogen, I also added a mod to allow for wirless tether (new kernel).

I tried fastbooting and loading the superboot with himem which returned no errors, then tried applying the update.zip again, still the same error.

What am I doing wrong? To get into the recovery I am using 'adb reboot recover'

Thanks in advance, really scratching my head here.

Link to comment
Share on other sites

Getting this behavior when trying to apply a cooked rom OR even if I try to apply the packaged update.zip from step 1.

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.

My device has an unlocked bootloader, it's been rooted, and it's got the mod for the multitouch from cryogen, I also added a mod to allow for wirless tether (new kernel).

I tried fastbooting and loading the superboot with himem which returned no errors, then tried applying the update.zip again, still the same error.

What am I doing wrong? To get into the recovery I am using 'adb reboot recover'

Thanks in advance, really scratching my head here.

Same fault here, really starting to bug me i cant use the standard or non standard upgrade ;)

Any way of unrooting my phone or it is stuck like this now

Someone please help :D

Link to comment
Share on other sites

I have this problem too... how can we use both himem and wireless tether? is this possible right now? I noticed that's Paul's cyanogen mod-kitchen has the wireless tether option to bake in, but I don't really want to get a custom ROM - I just want to use the wireless tether app... for now, i'm installing the nexusone zimage which I guess will eliminate himem, but it would be nice to have both. BTW thanks Paul, Cyanogen, and all of the rest who post on here to help make all this possible.

..hate to keep replying to myself, but it looks like I sorted this out...I installed Paul's 1.5 Beta 2 from

http://android.modaco.com/content/google-n...-mcr-for-ere27/

and wireless tethering is working, as well as over 200 MB of free memory. Haven't been using it long enough to try anything else out or determine stability, but it looks good to me. Thanks again Paul.

Link to comment
Share on other sites

Getting this behavior when trying to apply a cooked rom OR even if I try to apply the packaged update.zip from step 1.

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.

My device has an unlocked bootloader, it's been rooted, and it's got the mod for the multitouch from cryogen, I also added a mod to allow for wirless tether (new kernel).

I tried fastbooting and loading the superboot with himem which returned no errors, then tried applying the update.zip again, still the same error.

What am I doing wrong? To get into the recovery I am using 'adb reboot recover'

Thanks in advance, really scratching my head here.

Hi,

Had the same issue, rooted nexus one with stock recovery.

If you want to install the the "MAIN UPDATE ZIP", you will need to install the "1.5.3 - RA-nexus Recovery Image" first.

You can download it from here:

http://android.modaco.com/index.php?act=at...st&id=44651

It won't wipe your phone to install it (fastboot flash recovery <IMG FILE NAME>)

After you did that, try to install again.

When I did that, and installed again, I got the no space error. Although I didn't pursue that error since the MT seems to be working great.

Link to comment
Share on other sites

Guest jaredb03

Sorry if this has been asked or answered already. I read a few pages and didn't see the question.

I was rooted with modaco 1.2 rom flashed. My problem is i did step 1 by putting the update.zip on the SD booted to Bootloader went into recovery and flashed the zip. After that i rebooted and it just kept loading at the google X animation loading screen. So i thought maybe i needed to flash the radio to get it to boot the rest of the way so i went back to recovery and switched to ms-usb and copied that update.zip to the SD and flashed it. Again it just kept loading at the X google animation and never loaded up. Decided maybe i need to put the image on with superboot(Step 5 one). Went into CMD then fastboot flash boot boot.ERE27.... It said OK, and OK so i rebooted it again manually. Still same thing. So what do i need to do? This is my only phone so i need to get it going ASAP.

EDIT: Just to update I upgraded to modaco ad free to get the bake. Baked and still sticking on loading screen. Everything shows it completes fine but won't boot.

Edited by jaredb03
Link to comment
Share on other sites

Hi,

I installed this update, rooted, with superboot and new radio version.

I have an issue copying files to my sdcard, when i mount the sd card in my pc, using the nexus and I try to copy some files to the sd card the device reboots aleatory.

I can't copy files to sd card connecting the phone to my PC by USB, the device reboots when I am copying files to the sd card.

Someone with this issue? some suggestion?

Thanks!

EDIT: I tryed mounting the sd card from the recovery and it works perfectly, only reboots when i am in android system.

I have this same issue also. I think it has something to do with the superboot rooting. If I go full stock it seems stable but with a rooted system (cooked rom or otherwise) it crashes regularly when copying files over usb. I have "usb debugging" enabled if that matters.

Anyone found a fix or experiencing this also?

Link to comment
Share on other sites

I have this same issue also. I think it has something to do with the superboot rooting. If I go full stock it seems stable but with a rooted system (cooked rom or otherwise) it crashes regularly when copying files over usb. I have "usb debugging" enabled if that matters.

Anyone found a fix or experiencing this also?

MCR 1.5 Beta 2 fixes this! ;)

P

Link to comment
Share on other sites

Hi,

Had the same issue, rooted nexus one with stock recovery.

If you want to install the the "MAIN UPDATE ZIP", you will need to install the "1.5.3 - RA-nexus Recovery Image" first.

You can download it from here:

http://android.modaco.com/index.php?act=at...st&id=44651

It won't wipe your phone to install it (fastboot flash recovery <IMG FILE NAME>)

After you did that, try to install again.

When I did that, and installed again, I got the no space error. Although I didn't pursue that error since the MT seems to be working great.

Thank you it worked a treat on mine no errors ;)

Installed the extra ram image after also :D

Link to comment
Share on other sites

Works great on my N1. The highmem really makes the difference, the multitouch is really cool too ;)

Although; I had an issue when installing a baked version : everything went fine for the install part; but I had no android keyboard in the "input device" anymore (it was working for sim unlock & all) but the virtual keyboard didn't show up when wanting to type a url, a text message, ...

The baked version contained the following items removed :

- car home

- gvoice

- voice search

- amazon mp3

-fbook

- voice dialer

+ radio update and superboot w/highmem.

Anyway, I baked another version with everything but amazon & fbook, without radio update this time (already set up); and now the keyboard's back :D

I didn't try to identify which of the removals made the keyboard go away. Is this a known bug?

Edited by foxof
Link to comment
Share on other sites

Guest phattyluver
I just upgraded to Modaco Premium.

My Nexus is Rooted with Factory Room

I baked one with SU root, trying to update the file (75mb) (renamed to update.zip

Geting this error "E: Signature verification failed"

Should I recovery first to non-root and them run this update?

i also rooted and unlocled the bootloader on mine and when i try to install update officially from google over the air or manually from sd card i get same error message. have u found out how to fix that to be able to apply update.

Link to comment
Share on other sites

Guest phattyluver

i also rooted and unlocled the bootloader on mine and when i try to install update officially from google over the air or manually from sd card i get same error message. have u found out how to fix that to be able to apply update. i would also like to keep everything stock with original os if its possible. and if not possible point me in the way to ware there is a site ware there is a good tutorial on how to install the fix the some of u guys r talking about on earlier post. im pretty new at this.

Link to comment
Share on other sites

Guest nethium
i also rooted and unlocled the bootloader on mine and when i try to install update officially from google over the air or manually from sd card i get same error message. have u found out how to fix that to be able to apply update. i would also like to keep everything stock with original os if its possible. and if not possible point me in the way to ware there is a site ware there is a good tutorial on how to install the fix the some of u guys r talking about on earlier post. im pretty new at this.

Phatty and everyone else frustrated with the "Verification Error". Go to this topic http://android.modaco.com/content/google-n...recovery-image/

Step by step:

1. Download the image for the ra nexus recovery image recovery-RA-nexus-v1.5.3.img , probably into the tools folder of your Android SDK where you have the adb and fastloader commands

2. Boot your phone into fastboot mode (power on while pressing the trackball)

Connect your phone via usb to your pc/mac/...

3. run the command from the console (command line or shell depending on OS)

fastboot flash recovery recovery-RA-nexus-v1.5.3.img

4. once this is done reboot the phone from the menu

5. decide whether you like Cyogen's Kitechen, or the ERE27 (paul's Kitchen)

6. If you like Cyogen's firmware, Bake yourself a rom there, if you like Paul's coolness Bake a rom here, copy the update.zip to your sdcard

7. run the command

adb reboot recovery

8. Notice that you have a sexy new recovery menu that is not only graphically superior to the stock recovery menu, it has the ability to be mounted in recovery mode, so you don't have to be scared and frustrated about bricking yoru phone, because you will always be able to go back to stock.... (as those of you who are reading this are probably totally annoyed by the fact that you're stuck in limbo, just do these steps and be happy)

9. On the sexy new recovery menu select update from sdcard

10. watch the sexy graphics, no verification error, by the time you've opened a beer the new 70+mb sd update is on your phone

11. Reboot the phone

12. The first boot might take a little while with a little box an arrow that points to an android guy.... don't worry, take a sip of your beer and relax, it will all be over soon

13. If you decided to go cyanogen... I think you can stop here

14. If you decided to go Paul's Kitchen from this thread, open another beer, goto the beta MCR thread, and download the Modaco Custom Rom Image, copy to your SD as update.zip and use your cool recovery menu again to apply it without any verification errors. (This will give you some of the stuff that is also in Cyanogen's custom ROM including busybox and the kernel for wireless tether).

That's it! Frustration over, enjoy the rest of your weekend.

Link to comment
Share on other sites

Hi I have rooted my phone and changed the boot loader and system images

as directed above for rooted phones.

I now have decided that I cant keep doing this every time Google has an update

How do I put it back to the way it was so that is is an unmodified Google phone.

and so that it will receive the normal Google updates from within the phone

and so that it will take the original Google update.zip file without having to used the modified one?

Many thanks

Tom

Link to comment
Share on other sites

Guest leemafox

When I use the Superboot img , my wifi doesn't work at all , it says unable to start Wi-Fi

when using the insecure one , same issue . Unable to start Wi-Fi

When I use the superboot.himem img , wifi can enable , but unable to obtain ip address ..

anyone experiencing this ?

Edited by leemafox
Link to comment
Share on other sites

That's because the himem superboot flashes a new wireless ko. Flash back to a non-himem main image (not just the superboot) and you'll be set.

Going forward i'll update the regular superboot to also include the regular wifi ko.

P

Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.