Database Info

2.3.4 Google Nexus One Rom Only 6.7MB, something wrong??? can't install???

I am trying to remove cyanogen ROMs from my Google Nexus One phone and I am following How To: Update Nexus One to Android 2.3.4 gadgetfeel.com/how-to-update-nexus-one-to-android-2-3-4/ to install the 2.3.4 update.
When I do a trackball/power start and select bootloader and then recovery I am put in the ClockworkMod Recovery v3.0.0.5 app, from there when I do an "apply update from sdcard" or install zip from sdcard" it gives me the cyanogen logo with a hat on it and does nothing.
I downloaded the renamed to update.zip 2.3.4 ROM to my sdcard and moved it to the top directory in the sdcard.
What am I doing wrong. The 2.3.4 ROM is only 6.7MB that seems very small. Perhaps that is the problem

you have to flash nexus one 2.3.3 rom first then flash v2.3.4 over it
here is a guide for 2.3.3
http://www.redmondpie.com/install-android-2.3.3-gingerbread-on-nexus-one-how-to-guide/
after doing that follow your 2.3.4 guide

This is what I am getting when I try to install the new update.zip I copied to the root of the microSD card.
ClockworkMod Recovery v3.0.0.5
-- Install from sdcard...
Finding update package...
opening update package...
installing update...
assert failed: blah blah blab
E:error in /sdcard/update.zip
(Status 7)
Installation aborted.
Should I try to reformat the sdcard and recopy and try again?
EDIT:
I deleted the file and retried it again. Same thing.
So I dl the 7.0.3.0-NI and it installed just fine.
So must be a problem with the file?
bob.

ok have you tried from this guide?
http://www.gottabemobile.com/2011/05/03/nexus-one-android-2-3-4-update-can-be-manually-installed/
and you have to have 2.3.3 thats manatory

UPDATE
it should be only a update file, so you first flash the android 2.3.3 first and then go back into your app for flashing or clockmmod and flash the update, then you should be able to get it done

The 2.3.3 from this file will not load it gives the above posted errors.
http://www.redmondpie.com/install-android-2.3.3-gingerbread-on-nexus-one-how-to-guide/
So its not me and its not the phone as far as I can tell, I just updated to 7.0.3-N1 cyanogen mod7. works fine. So where do I get the 2.3.3 from if this one doesn't work?

I think I need an original recovery image. These ones I am downloading don't want to go over top of Cyanogen Mod7?

I still can't get the original ROMs back on this phone. every file I download is corrupt except for the cyanogen files which I can dl and install no problem. Can some one give me a link to a file that is good and that they have downloaded and it is not corrupt. and yes I rebooted my winXP box.

Actually, it IS possible to flash from an older Android version to 2.3.4. I did exactly that on my Nexus One, going straight from 2.2 to MIUI 2.3.4. I needed to unlock my bootloader and flash Amon Ra's recovery, I experienced no problems whatsoever.

please help with my phone: can't update ROM, keep getting error msgs!

Hi all, I recently rooted my NS4G and flashed my rom to the Brainmaster's MIUI 10.14.11. It worked great for a while and then I started having issues with it so I tried to update it to the 10.28.11 version and it wouldn't let me. I was finally able to reflash to GRJ06D, but no other custom rom would work. I'm using CWM 5.0.2.0. ROM Manager won't work either after it gets into recovery. I get the error message...
assert failed: getprop("ro.product.device") == "crespo4g" || getprop("ro.build.product") == "crespo 4g"
E: Error in /sdcard/
(Status 7)
Even trying to do an OTA system update via Sprint freezes and gives me the Android error message (triangle with exclamation). I've tried many many times to reflash and no success.
What do I need to do?

This issue has been reported a few times and there are a few ways to fix it;
1) Make sure you downloaded the right ROM; ie, the ROMs from the Nexus 4G Development section
2) If you're installing ROMs through ROM Manager, don't. Reboot into recovery mode, do a full data, cache and dalvik wipe and then flash the ROM zip while still in the CWM recovery mode
3) Else; try a different version of CWM, make sure it's compatible with your device and then do step 2 again.
Good luck.
Greetz

I think you should flash CWM again then wipe data, cache, dalvik, boot, then flash rom again and report your findings back to us.

I had this issue last week.. You've probably tried to flash the incorrect ROM originally or something..
The only way I could fix it was to boot into download mode, and flash the PDA, phone and modem via Odin. You can get the firmware from samfirmware.com

Thanks for the responses, its funny because I flashed the 4.0.1.0 CWM, which was for the GSM version and then reflashed to 5.0.2.0 (NS4G) in order for the MIUI rom to work. It was after flashing that and running MIUI for a while that I started having issues so I reflashed a new 5.0.2.0 and its still the same.
I haven't been able to flash back to the CWM 3 that it originally came with because I lost my micro USB cable. I hope to get this fixed soon! Thanks again, will keep you guys posted.

Galaxy SII Issues with CWM Ultra toxic rom 8.0

Gday. I'm having this issues trying to update to the latest 8.01 version of the ultra toxic rom. I cant post as im below 10 post so this was the only place i could find for some help.
I have rom manager installed. and i also flash clockworkmod recovery then reboot into recovery. For what ever reason it will not work and im at a loss, tried uninstall it and go from there but no go.
Once it reboots it says at the top Android system recovery <3e>.
Down a little it says this.
E:failed to verify whole-file signature.
E:signature verification failed.
Installation aborted.
Basically i have searched the net and cant work it out myself. I've used it before for a backup when going from lightning rom to toxic rom. but I've never used it since.

[Q] Problems with flashing!!

I am currently on CM10 Alpha 3.
I tried flashing 2 ROMS (JellyBam and PacMan latest ones).
I followed the normal procedure(Backup,Wipe data,cache,dalvik) and install the ZIP.
While flashing Jellybam, the aroma installer got stuck on "Extract: /system/update_me.xml"
I had to take out the battery and restore the bakup.
Then again i tried installing Pacman (same Procedure) and while"Installing update" step , recovery rebooted.
It gave me errors: "
E:can't mount /cache/recovery/command
E:can't mount /cache/recovery/log
E:can't mount /cache/recovery/last_log
E:can't open /cache/recovery/last_log"
I tried restoring but it got stuck on "Restoring System".
Then i removed my battery for a few minutes and booted into recovery and restored successfully. The phone is working fine but my problem is why cant I flash other roms?
Any developers who would help?
Thanks.

I guess that's because the latest version might be built for cm10alpha4. Read flashing instructions for alpha4 on cm10 thread ... read the last few pages as well.

Hetalk said:
I guess that's because the latest version might be built for cm10alpha4. Read flashing instructions for alpha4 on cm10 thread ... read the last few pages as well.
Click to expand...
Click to collapse
I am on Cm10 Alpha 4 but i also am uable to flash any roms

Pratikpathare said:
I am on Cm10 Alpha 4 but i also am uable to flash any roms
Click to expand...
Click to collapse
Odd case, mate. I just update my phone with A4, then I flash JellyBam v.1.30 with scrolling and build.prop mod make by Top Droid. And so far my phone is alive and still working. Try flash stock ROM again and flash A4 after that.
Sent from my Galaxy SL Powered by JellyBam.

[Q] Trying to Install CM10.1 (unofficial), Only Boots into CWM Recovery

I've spent a good 50 hours trying to install scott.hart.bti's unofficial CyanogenMod 10.1 (JellyBean 4.2.1) on my Samsung Infuse 4G (SGH-I997), and have come up against nearly every conceivable problem. Today's problem is the fact that, after going through the scores of steps to finally get to the point to install CM10.1, my phone only boots into ClockworkMod Recovery whenever I turn it on. I've scoured these and other forums for hours trying to solve this, and I've had no luck. Any help would be greeeeatly appreciated.
Here's what I've done so far, if I remember correctly. I started out with stock Froyo on the Infuse.
I successfully rooted my phone with SuperOneClick.
I found out I have to install Gingerbread first. After having no luck with Heimdall (not exactly "one click"), I installed jscott30's UCLB3, option D using ODIN. It comes with Entropy's Daily Driver kernel and red CWM Recovery. I installed the corresponding gapps too.
Before I could install a JellyBean ROM, I had to install an ICS one. Entropy512's unofficial CM9 was recommended, so I installed the latest build of that, following the instructions for installing from Gingerbread with red CWM. I installed the recommended gapps along with it. I also did the recommended wipes before this installation.
I ended up with the scrambled rainbow start screen or whatever people call it. Apparently I have to have Gingerbread bootloaders and those didn't come with the GB ROM, so I installed those via ODIN.
I got CM9 to work.
I transferred over the zip files for the CM10.1 ROM and put them in /sdcard/.
Lots of wipes: wipe data/factory reset, wipe cache partition, format /system, wipe dalvik.
I installed the CM10.1 ROM, and then scott.hart.bti's modified gapps, using CWM.
I tried to reboot the phone. It rebooted into CWM, the same CWM I used to supposedly install CM10.1. Now, whenever I reboot or turn the phone on (by whatever method - removing battery, USB cord, holding power button, selecting "reboot system now" in CWM), it goes directly to CWM.
One, of many, points of confusion is the different CWMs. How do I tell what's a red CWM and a blue CWM? When I Google that, all that comes up is posts from this and other forums of people yelling at the poster to Google it. See the problem here? The CWM Recovery that I used to install CM10.1, is titled "CWM-based Recovery v6.0.2.7". It has a blue menu with a grey background.
Where did I go wrong? Anything remotely applicable that I read seems to be for a different phone, so I'm unsure what to believe. Here are some of the explanations / solutions recommended for similar problems on other phones.
Install a different type of recovery (recommended here, as well as several other places). But everything I find about installing different recovery software involves using ROM Manager (which I can't access and which doesn't work anyway), using Heimdall (which I couldn't get to work), or installing one of the ROMs I already installed. TWRP was recommended, but not for my phone specifically, plus I read here that it doesn't work with MTD JellyBean, which I think is what CM10.1 is. Everything seems to require going back to stock Gingerbread, which is where I started, so I'd still end up having to then install CM9 and run into the same problems. Is it this? Which recovery should I install, and how?
Someone else said here that "The ICS ROMS were built for safestrap now bootstrap (CWM). It does that because it was flashed using CWM." Is this just referring to some other ROM? Everything/everyone else says to do everything with CWM.
A couple posts (here and here) recommend some shell commands involving /dev/block/mmcblk0p3 and /dev/block/mmcblk0p4, respectively. I'm hesitant to try these because they're for different phones, they themselves refer to different blocks, and it seems like the type of thing that could really mess up my phone.
I just flashed with a Heimdall One-Click ICS Recovery found here. My phone is still only booting into recovery, but this time it's "CWM-based Recovery v5.5.0.4" with a blue menu and a black background. At the bottom of the screen, it shows the following errors, which I suspect are just because I cleared the cache before, but I'll include for completeness:
Code:
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
I'm clearly quite the noob, especially in comparison to all of you, so please save me with your endless expertise! Do I install a new recovery? If so, how? I have a new recovery now (just a different version of CWM). Is there some problem with a boot file or bootloader? Is it a kernel issue? Insert other clueless jargon-filled question here? Endless thanks in advance.

Before you flash 10.1, flash CM 10. Sometimes the phones can be finicky. I solved a similar problem by using this method.
Sent from my SGH-I997 using xda app-developers app

What CM10?
trej3k said:
Before you flash 10.1, flash CM 10. Sometimes the phones can be finicky. I solved a similar problem by using this method.
Sent from my SGH-I997 using xda app-developers app
Click to expand...
Click to collapse
Okay, so I've started again from stock Gingerbread. What CM 10 are you talking about, though? I was only able to find CM 10.1 for Infuse. What CM 10 did you install? Are you referring to scott.hart.bti's BeanStalk build?

Fixed, I think
I think I have it working now. I have no idea what the problem was. I just started over again from the beginning. Jesus Christ was this complicated. I don't know how you guys make this stuff; it's hard enough to just install! Thanks for your help.

Glad you got it working. I try to always flash
In order ( stock, cm9, cm10, cm10.1) cm10 is right under the cm10.1 link in the 10.1 thread. Again, glad you got it up & running! :thumbup:
Sent from my SGH-I997 using xda app-developers app