Database Info

[Q] Downgrade To 2.3.2

Before the 2.3.3 update the screen on my Nexus S was actually fairly accurate. I did not have any of the blue color tint problems reported by some, with the new update the color temperature is visibly yellow. It seems that a lot of the SuperOMOLED screens are different sadly even when running the Star Field live wallpaper I can see a yellow tint. Is there any way to downgrade back to Gingerbread 2.3.2
Thanks

http://android.clients.google.com/p...9e.signed-soju-GRI40-from-GRH78C.98f3836c.zip Or download a nandroid backup of 2.3.2 or download a ROM thats using 2.3.2 (CM7, GingerS, etc)

so i only have to install this update.zip to downgrade?
is this really working?
thx
bernd

bgrimm said:
so i only have to install this update.zip to downgrade?
is this really working?
thx
bernd
Click to expand...
Click to collapse
yes
10char

zephiK said:
http://android.clients.google.com/p...9e.signed-soju-GRI40-from-GRH78C.98f3836c.zip Or download a nandroid backup of 2.3.2 or download a ROM thats using 2.3.2 (CM7, GingerS, etc)
Click to expand...
Click to collapse
zephiK I downloaded the link and installed the update from the SD Card and everything installed fine. But I rebooted and its still stuck on 2.3.3
Should I follow these instructions?
http://forum.xda-developers.com/showthread.php?t=965686
Thanks

brnagi said:
zephiK I downloaded the link and installed the update from the SD Card and everything installed fine. But I rebooted and its still stuck on 2.3.3
Should I follow these instructions?
http://forum.xda-developers.com/showthread.php?t=965686
Thanks
Click to expand...
Click to collapse
yes that is another way of reverting back to 2.3.2, but that update SHOULD work.
What recovery do you have? If you're using clockwork, MAKE SURE you are flashing
98f3836cef9e.signed-soju-GRI40-from-GRH78C.98f3836c.zip not update.zip.
to do this.. install .zip from sdcard -- just make sure it isnt update.zip
It's very possible that you renamed the 2.3.3 .zip to update.zip and you just simply reflashed update.zip which is 2.3.3
if you're on stock recovery, then mount the USB and delete update.zip and rename 98f3836cef9e.signed-soju-GRI40-from-GRH78C.98f3836c.zip to update.zip then flash

I'm running a stock Nexus S not rooted yet. I did delete the old update.zip and replaced it with your link but I'm still having getting the same results. In recovery the update installs everything and I still reboot back into 2.3.3
Kernal Version is: 2.6.35.7-g1d030a7
Build: GRI40

The other alternative step is to 'fastboot oem unlock' and go through the rooting process. (or do the process of not unlocking and rooting)
- Install Clockwork Recovery
- Download Nandroid backup of 2.3.2
- Restore from the 2.3.2 backup
| OR |
Flash a 2.3.2 based ROM such as CyanogenMod7 RC1 (or Nightlies), GingerS, Bionix, MoDaCo, and so forth.
Stickies in Dev forum will help you get started with tutorials.

zephiK said:
The other alternative step is to 'fastboot oem unlock' and go through the rooting process. (or do the process of not unlocking and rooting)
- Install Clockwork Recovery
- Download Nandroid backup of 2.3.2
- Restore from the 2.3.2 backup
Stickies in Dev forum will help you get started with tutorials.
Click to expand...
Click to collapse
Thanks zephiK I'm going to give this a shot

brnagi said:
Thanks zephiK I'm going to give this a shot
Click to expand...
Click to collapse
no problem. sorry that the 2.3.2 update didnt work out.
I would highly recommend buying Titanium Backup pro or using MyBackUp (Never used this) to backup your apps as you become a flashaholic.
Whenever you flash new ROMs and wipe.. you'll lose your apps but those two apps I mentioned above will save them.
BTW. when you do fastboot oem unlock, your stuff are going to be wiped so make sure you back them up!

zephiK said:
no problem. sorry that the 2.3.2 update didnt work out.
I would highly recommend buying Titanium Backup pro or using MyBackUp (Never used this) to backup your apps as you become a flashaholic.
Whenever you flash new ROMs and wipe.. you'll lose your apps but those two apps I mentioned above will save them.
BTW. when you do fastboot oem unlock, your stuff are going to be wiped so make sure you back them up!
Click to expand...
Click to collapse
I just did a quick Google search on the file you posted and I think its for the 2.3.3 update

zephiK said:
yes that is another way of reverting back to 2.3.2, but that update SHOULD work.
What recovery do you have? If you're using clockwork, MAKE SURE you are flashing
98f3836cef9e.signed-soju-GRI40-from-GRH78C.98f3836c.zip not update.zip.
to do this.. install .zip from sdcard -- just make sure it isnt update.zip
It's very possible that you renamed the 2.3.3 .zip to update.zip and you just simply reflashed update.zip which is 2.3.3
if you're on stock recovery, then mount the USB and delete update.zip and rename 98f3836cef9e.signed-soju-GRI40-from-GRH78C.98f3836c.zip to update.zip then flash
Click to expand...
Click to collapse
Why would the file named "GRI40-from-GRH78C" downgrade you from 2.3.3 to 2.3.2? That's the update file that takes you TO 2.3.3 (aka GRI40) FROM 2.3.2 (aka GRH78C).
Is the one you're recommending modded in some way? If so, it should be renamed to avoid confusion. If not, it's not the right thing to do to accomplish a revert from 2.3.3 to 2.3.2 as requested from the OP.

I don't think it's the right file to downgrade. It is the one upgrade to 2.3.3 from 2.3.2.

kurtlou said:
I don't think it's the right file to downgrade. It is the one upgrade to 2.3.3 from 2.3.2.
Click to expand...
Click to collapse
It's not. He's confused. The "98f3836cef9e.signed-soju-GRI40-from-GRH78C.98f3836c.zip" is definitely the NEW OTA to take you to 2.3.3 from 2.3.3. It has the new bootloader in it and PATCHES from 2.3.2 to 2.3.3. It is 21mb in size and only includes patches.

hmm so how to downgrade to 2.3.2 if I don't have (and hopefully don't have to) unlock bootloader?
i'm planning to downgrade to 2.3.2, then boot into clockwork mode, and use my previous 2.3.2 nandroid backup..
my previous 2.3.2 works fine, no random reboot and at least the colour is pleasant to my eyes..

I'm pretty sure I've devised a method to revert back to 2.3.2 correctly, but I haven't tested it yet and you may or may not need to root your device, depending on what you want backed up.
If you're on 2.3.3 and would like to back everything up as best you can, I advise that you first root, install Titanium Backup, and run.
Next, use the info from this thread to use Odin to revert your Nexus S back to 2.3.1. That thread also includes instructions on how to flash the radio as well to get it truly back to 2.3.1.
After that, you can grab the manual update.zip for 2.3.2 from this link.
From there, if you had previously rooted and backed up your apps and data, you can root again and use Titanium Backup to restore everything.
Hope this helps.

It does sound like the update posted is 2.3.3 from 2.3.2 if you ask me, i guess there may be other revisions too, or will be (from 2.3.1 to 2.3.3 etc..)
For you colour issues (not something i have i guess i jsut have a good LED screen, but i did have the reboots (now fixed) i would suggest:
Keep 2.3.3 (its very smooth)
Install Netarchy cfs 2.3.3 compat kernel
Install Voodoo App from Market
Choose Voodoo's colour profile in the app
I think with that you may be able to keep your update and have the colours you want?
Well i hope so

[Q][GT-i9020a] How do I reflash back to factory?

Hi, new Android user here.
I was trying to root my Nexus S phone yesterday and I'm having problems. There is a lot of rooting guides out there and I used one from xda and also one from unlockr.com. Managed to root the phone ok (I think), but everytime I flash a custom ROM, the phone won't start at all, it just sits at the boot up screen and repeats itself.
So I'm thinking, I should just start over again. So I flash the stock ROM from xda back to 2.3.1. Everything seems ok, the phone starts up... but it's always stuck on airplane mode and the phone itself doesn't even show stuff like IMEI, mac address anymore.
So now I figure I've probably messed the phone up enough and need help lol. How do I go about reflashing the stock ROM and getting my Nexus back to out of the box condition (Stock ROM and no custom bootloader)?? Any guides or step by step instructions would be very helpful.
Thanks

Did you wipe before flashing roms?
Sent from my Nexus S c",)

Maybe flashing the KB2 modem would help that but the 9020a came stock with 2.3.3 and not 2.3.1 so that could be it...I'm not sure but that software wasn't meant at all for ours so it could be part of the problem. But if I was you I'd take a look at this thread wich has all the stock software for your phone. Make sure you wipe everything in clockework and then flash the stock rom. http://forum.xda-developers.com/showpost.php?p=13123996&postcount=39
dsixda uploaded the stock backup and the stock recovery, you can read more at that link, good luck hope it helps

You can download the full stock ROM from the link below:
http://goo.gl/8P8vl
Move the zip file to sdcard. Boot into recovery and flash the ROM. It should get you back to stock 2.3.4 ROM, all locked.

jungbum said:
You can download the full stock ROM from the link below:
Move the zip file to sdcard. Boot into recovery and flash the ROM. It should get you back to stock 2.3.4 ROM, all locked.
Click to expand...
Click to collapse
that did the trick. thanks everyone, now time to try rooting and flashing ROM again!
hrm lol now trying to update it to 2.3.4, it downloaded the update, but on reboot i get the white triangle with ! in it :\
this phone is so messed now
edit: well now everything is ok again, wiped data, flashed with CM7 and now it says 2.3.4, go figure.

[Q] CWM and stock recovery

Hello -- I'm new to the Charge but have a little experience rooting/flashing ROMS with Motorola devices. At this point all I want is a rooted device and everything else stock (2.2.1 firmware / EE4). To achieve this I placed the Superuser app zipfile onto my sd card, flashed CWM with Odin, booted into recovery and applied the zip update. Everything went smoothly, my device is now rooted and works fine. However, when I boot back into recovery I find that CWM is still installed, I was under the impression that this procedure would overwrite CWM with stock recovery when I rebooted. I don't really mind having CWM, just wondering if the fact that it wasn't overwritten is indicative of some other problem that is likely to bite me in the a** down the road.
Also, if all I have done is rooted and kept the kernel untouched, will I be able to receive the gingerbread OTA when it is released (if ever)? Or will I have to flash back to a stock Froyo ROM?
Thank you thank you thank you in advance.

talbot27 said:
Hello -- I'm new to the Charge but have a little experience rooting/flashing ROMS with Motorola devices. At this point all I want is a rooted device and everything else stock (2.2.1 firmware / EE4). To achieve this I placed the Superuser app zipfile onto my sd card, flashed CWM with Odin, booted into recovery and applied the zip update. Everything went smoothly, my device is now rooted and works fine. However, when I boot back into recovery I find that CWM is still installed, I was under the impression that this procedure would overwrite CWM with stock recovery when I rebooted. I don't really mind having CWM, just wondering if the fact that it wasn't overwritten is indicative of some other problem that is likely to bite me in the a** down the road.
Also, if all I have done is rooted and kept the kernel untouched, will I be able to receive the gingerbread OTA when it is released (if ever)? Or will I have to flash back to a stock Froyo ROM?
Thank you thank you thank you in advance.
Click to expand...
Click to collapse
What zip did you apply IN CWM?
Sounds like you applied a kernel too. Having CWM is not normal if you just flashed the superuser zip.
You will likely need to flash back to stock prior to updating with the GB OTA whenever it comes out.
_____________________________
Bloat frozen EE4 / Stock Kernel
V6 SuperCharger / Loopy Smoothness Tweak

Thank you for the reply.
The only zip I applied was the su-2.3.6.3-efgh-signed file downloaded here.
For CWM I flashed 0817_charge_recovery.tar.md5 found here.
Again I am now rooted but can still boot into CWM. After flashing the CWM file and disconnecting my phone, I initially fat-fingered it trying to boot into recovery and it rebooted. I then powered off and booted successfully into CWM to apply the zip file.
Any thoughts?

Ok, the main difference I see between my config and yours is that I may have used a different version of the superuser package.
The one at the link that you provided is superuser/su-3.0-d-signed.zip.
The one that I used is the su-2.3.6.3-efgh-signed.zip from here
You did start out from stock correct?
What is the kernel version in Settings->About phone->Kernel version?

Actually when I downloaded the Superuser zip file from the site I referenced it was su-2.3.6.3-efgh-signed.zip. This was a few weeks ago -- before version 3.0 was added.
My phone was absolutely stock when I got it 2 weeks ago and I have done no other messing with it. The Kernel version as it reads right now is:
2.6.32.9
[email protected] #1

talbot27 said:
Actually when I downloaded the Superuser zip file from the site I referenced it was su-2.3.6.3-efgh-signed.zip. This was a few weeks ago -- before version 3.0 was added.
My phone was absolutely stock when I got it 2 weeks ago and I have done no other messing with it. The Kernel version as it reads right now is:
2.6.32.9
[email protected] #1
Click to expand...
Click to collapse
Looks like you did the same steps that I did other than your extra boot into CWM. Usually, the stock init will check for the proper recovery, file systems, etc and then "fix" that which isn't right.
I have never seen it not do that before (I have had to reflash CWM several times before due to botching the 3 button bit)
_____________________________
Bloat frozen EE4 / PBJT Voodoo 0730
V6 SuperCharger / Loopy Smoothness Tweak

You cannot apply the OTA if you have CWM recovery. It will fail. Usually you need to have a fully bloated stock rom w/ stock recovery. Root is ok but you will lose it w/ the update

hoppermi said:
You cannot apply the OTA if you have CWM recovery. It will fail. Usually you need to have a fully bloated stock rom w/ stock recovery. Root is ok but you will lose it w/ the update
Click to expand...
Click to collapse
That's kind of why I chose this method to root, thinking that CWM would get overwritten when I rebooted -- but it didn't. Oh well.

talbot27 said:
That's kind of why I chose this method to root, thinking that CWM would get overwritten when I rebooted -- but it didn't. Oh well.
Click to expand...
Click to collapse
Enjoy it. I like CWM much better than stock recovery ;-)
_____________________________
Rooted and Bloat frozen Stock EE4
V6 SuperCharger

need help with root.

I flash CWM and installed imoseyon repacked kernal 4.0.0. I installed su from the market. binary update fails and i have no root. binary updater says checking for busybox....not found downlading busybox...ok then checking current install path....fail. i have rooted adn flashed may times with no issues.
This is the first time rooting after gb update though. am i missing something?

Go back into CWM and try flashing this. It worked for me.

thanks but that didn't work. I try to run wifi tether and it says my kernel isn't supportive but its imoseyon's newest kernel. gb 4.0.0and im using imnuts newest cwm 5. something its light blue. think there is a problem with the kernel or cwm? also im using odin 1.82

The way I see it you have nothing to lose. Why don't you try this: http://forum.xda-developers.com/showthread.php?t=1406951 Use the Odin version. This is the Rom I am on and it is smooth.

thanks i might have no choice at this point. I have been trying to dl infinity rom w/tsm ext4 since yesterday but dl either stalls or get a fail dl error.
Have you tried infinity rom? i used it back when it was first released and really liked it. how does that compare to infinity rom?

I was on Infinity w/TSM_ext4 and was having issues. Went to Infinity_ext4 and it was ok. I like the work that Imnuts does. I believe he is stopping work on Infinity to work on ICS for the Charge so I decided to try this. I am completely happy with the TweakStock Rom. This guy did a great job.

thanks for your help

No problem.

Try going back into cwm and mounting the system, don't reboot. Now reflash the su package. Reboot and check for root.

Help! OTA Update on Rooted, Stock Rom, CWM Recovery

Hey guys,
I searched around and only found some old posts for this topic.
I just bought this phone, I rooted it, simunlocked it, and added two day old CWM recovery. Its a S4 Canadian (Bell) version in case that helps..
Is there a way to apply the OTA update WITHOUT having to wipe my data and settings and reflashing a rom?
Hlep will be greatly appreciated!
THANKS :good:

I got the same thing going on. I have a TMOUS HTC One S stock with CWM Rooted and such. I just changed it back to the Stock recovery, but doesn't seem to help. Is there something else I need to do? Maybe I need to flash a newer recovery version?
I have the stock recovery from a MoDaCo topic I can't list because I don't have 10 posts yet.
its topic/353006-interim-clockworkmod-touch-recovery-for-the-htc-one-s-stock-download/ though.

Are you sure your Rom is absolutely stock. For example if the rom is tweaked in any way or if bloatware has been deleted then you won't recieve the update

Ok so I got the update to work. This is what I did: in CWM I backed up a nandroid. I flashed a stock BACKUP for the HTC One S (I moved the zip to the clockwork > backups folder on the sd card). Rebooted into bootloader, flashed a stock recovery from modaco, rebooted, ran the update (I had to update twice, from 1.53 to 1.84 to 2.35). Then I restored my original nandroid. Problem is, the update didn't stick. And now I'm getting an error when I try to turn on wifi. Any ideas? I feel like I got so close...

Tough to see what went wrong.
I had a brand new stock rom with no modifications.
Then I flashed stock recovery,
Did a root keeper (play store app)
Then did the update
And restored root.
Worked out fine for me!
I think you should flash a stock rom and not a backup..