• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

2.3.3 Link

Search This thread

krohnjw

Inactive Recognized Developer
Jul 17, 2007
1,987
533
Plainfield
Full Rom link
http://android.clients.google.com/p...2cf141e6a.signed-soju-ota-102588.f182cf14.zip (89.9 MB)

Link for GRH78C
http://android.clients.google.com/p...9e.signed-soju-GRI40-from-GRH78C.98f3836c.zip

Link for GRH78 only

http://android.clients.google.com/p...2bf.signed-soju-GRI40-from-GRH78.e0b546c4.zip

As posted here by Matrik: http://forum.xda-developers.com/showpost.php?p=11616226&postcount=389

I figured I'd get this unburied for everyone interested (which is likely a lot of folks).




If you're stock and unrooted - download this and place it on the root of the SD card - named update.zip. Boot into recovery. Hold Pwr and then Vol up and then choose to apply update.zip.
 
Last edited:

moon-unit

Senior Member
Nov 24, 2009
126
12
Bristol

WOW - didn't think I'd see this so soon - thanks for digging it out man.

Guess I'll be the guinea pig
 

krohnjw

Inactive Recognized Developer
Jul 17, 2007
1,987
533
Plainfield
just got it on mine too.

does anyone know if this build is still rootable in the same method of 2.3.2? just curious

If your bootloader is unlocked then rooting is as easy as flashing CWM and flashing the SU binary.

If the bootloader is locked then the changelog indicates that you will not longer be able to use fastboot boot to load CWM and root that way.

With that said, I applied a lot of updates on my Nexus One without losing root and kept the boot loader locked the whole time. You'll need to pay attention, but you should be able to do the following.

Download the SU binary zip and place that on the SD card.

The OTA will not overwrite CWM until it actually boots. So, after you apply the OTA boot directly into recovery and apply the SU zip. This will give you root. (Just pay attention and hold vol up when it goes to reboot)

When you subsequently load up android CWM will be overwritten. At this point you can use the flash_image binary to manually flash CWM to recovery (or potentially ROM Manager).
 

moon-unit

Senior Member
Nov 24, 2009
126
12
Bristol
doesnt work for me - failed at file_getprop("/system/build.prop"

this update seems to be for build GRH78 - GRI40 ie 2.3.1 to 2.3.3

Im on 2.3.2 .......

any idea's???
 

hutzdani

Senior Member
May 9, 2010
1,222
357
London
If your bootloader is unlocked then rooting is as easy as flashing CWM and flashing the SU binary.

If the bootloader is locked then the changelog indicates that you will not longer be able to use fastboot boot to load CWM and root that way.

With that said, I applied a lot of updates on my Nexus One without losing root and kept the boot loader locked the whole time. You'll need to pay attention, but you should be able to do the following.

Download the SU binary zip and place that on the SD card.

The OTA will not overwrite CWM until it actually boots. So, after you apply the OTA boot directly into recovery and apply the SU zip. This will give you root. (Just pay attention and hold vol up when it goes to reboot)

When you subsequently load up android CWM will be overwritten. At this point you can use the flash_image binary to manually flash CWM to recovery (or potentially ROM Manager).

So what your saying is we can ( Possibly ) install 2.3.3 via the link with rooted devices with an unlocked bootloader ( if the 2.3.3 does not lock bootloader / root ) and then just re install superuser e.c.t and were away ?
 

krohnjw

Inactive Recognized Developer
Jul 17, 2007
1,987
533
Plainfield
So what your saying is we can ( Possibly ) install 2.3.3 via the link with rooted devices with an unlocked bootloader ( if the 2.3.3 does not lock bootloader / root ) and then just re install superuser e.c.t and were away ?

Yes - if you're unlocked then you'll only need to remove the isntall-recovery.sh and reflash CWM/su and you're golden.

It's a bit trickier for users who rooted without unlocking the boot loader and do not want to unlock at this point.

Looks like this is for GRH78, NOT GRH78C- we'll have to wait for that package still.
 

jaker.the.skater

Senior Member
Jul 19, 2010
396
7
Newport News
this really pisses me off. i was on 2.3.2 and i got the ota but when i tried to install it from cwm it didn't work. so then when i saw this one i gave up on the one i had and now its gone. turns out i should've just did a logcat and got the one for 2.3.2.:mad::mad:

oh well it'll be up soon
 

Top Liked Posts

  • There are no posts matching your filters.
  • 24
    Full Rom link
    http://android.clients.google.com/p...2cf141e6a.signed-soju-ota-102588.f182cf14.zip (89.9 MB)

    Link for GRH78C
    http://android.clients.google.com/p...9e.signed-soju-GRI40-from-GRH78C.98f3836c.zip

    Link for GRH78 only

    http://android.clients.google.com/p...2bf.signed-soju-GRI40-from-GRH78.e0b546c4.zip

    As posted here by Matrik: http://forum.xda-developers.com/showpost.php?p=11616226&postcount=389

    I figured I'd get this unburied for everyone interested (which is likely a lot of folks).




    If you're stock and unrooted - download this and place it on the root of the SD card - named update.zip. Boot into recovery. Hold Pwr and then Vol up and then choose to apply update.zip.
    2
    Here I got the 90MB FULL ROM version for those who are interested. Luckily I am still on 2.3.0 to grab it.

    h_t_t_p://android.clients.google.com/packages/ota/google_crespo/f182cf141e6a.signed-soju-ota-102588.f182cf14.zip

    P.S. sorry man I am not permitted to post external links.
    1
    just got it on mine too.

    does anyone know if this build is still rootable in the same method of 2.3.2? just curious
    1
    I've changed nothing at all. :-( The only thing I ever changed on my NS was just unlock the bootloader using superboot to root the phone. Everything else is stock.
    Language was english on the abort screen.

    I'm going to do this again tomorrow morning at work.
    It probably says the reason for aborting & I overlooked it. Will see on 2nd attempt.

    Sent from my Nexus S using XDA Premium App

    See what I bolded in your quote? I believe that's your problem.

    Like I said previously: If you've changed ANY file, including the kernel/boot.img that the update script wants to patch, the installation will abort.

    Superboot replaces your boot.img file with its own. The script in the OTA checks it and sees that it's been modded, so it can't proceed with the patches it needs to do to bring you to 2.3.3, so it aborts. It's for your own protection, so that the patches don't corrupt you.

    Several options for you at this point:

    1-Get a 2.3.2 stock boot.img file and fastboot flash it to the phone, then proceed with the update.

    2-Get the FULL OTA file (the 90mb one) and apply it. It OVERWRITES your /system, so it doesn't care what you've done previously.

    3-Get one of the nandroid images of 2.3.3 and apply it from clockwork recovery. You'll be updated and pre-rooted if you pick a rooted one.

    4-Edit the updater-script file to not check/flash the boot.img, then proceed with the update and then re-flash a superboot boot.img file that's been made for 2.3.3 (if there is one).

    Remember, all the update methods will break root (permissions on the su file are changed), so you'll have to reroot as part of the process unless you use a pre-rooted 2.3.3 nandroid image.

    Good luck.

    Get one of the 2.3.3 nandroid images in the