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
I recently put the newest ICS Lite'ning Rom onto my S2 having backed up everything onto my SD card using CWM. I was previously running Lite'ning V4.2.
The new Rom was successful but when I went to restore all my apps/layout etc from CWM the phone went back to how it was before (V4.2).
I realise that this probably sounds obvious but I had (wrongly) assumed that the CWM backup would restore everything but keep the new Rom.
I am quite new to this, but is there anyway I can download the new ICS Rom and then restore everything I used to have on it without going back to the old Rom.
Please don't flame the newbie!
Ohhh lol its fine. Everyone makes mistakes.
Let me cover the basics. Cwm will restore everything( system, SD card...etc)
OK just download a supported rom. Best to do a clean install. (Search that) . Flash the from, flash the gapps. Reboot once, flash kernel if you want only after the reboot. Sync your email and install the apps.
Unless you did a back up before you stuffed this up just re install back up.
Sent from my Nexus S using XDA
Thanks TigaTiger - great help. All done and very happy.
Question regarding going back to stock,
I installed CleanRom and feel like it's using more battery than stock bloated.
Can I use CWM recovery to go back to stock nandroid that I made?
So I followed the methods on this forum to install the ROM,
Root,
install CWM,
make nandroid backup
unlock bootloader,
flash Cleanrom
Can I use the nandroid that i made to go back to rooted stock rom? or do I have to go back completely?
You should be fine using the nandroid as long as you do a full wipe beforehand.... If you run into problems you'll just have to Odin back to stock.
i have installed cm10 on htc one v primo-u (india gsm ) and i wish to revert to the original image.
i tried to flash India_1567201recovery_signed.img file but no success.
can someone help me with a procedure how to revert to either 1.56.720 or 2.09.720 image of the phone
romah1 said:
i have installed cm10 on htc one v primo-u (india gsm ) and i wish to revert to the original image.
i tried to flash India_1567201recovery_signed.img file but no success.
can someone help me with a procedure how to revert to either 1.56.720 or 2.09.720 image of the phone
Click to expand...
Click to collapse
How did you try to flash the RUU? You can not flash it like a normal ROM
Also if you are looking for the RUU try HERE
I see what you're trying to do, that won't work...you can't flash a recovery to get to stock because stock phone won't flash from recovery, which is why once you get root the first thing you do is flash a custom recovery. Use the RUU to flash it back to shipped state stock, or if you are trying to keep root and just want to use a different ROM. More clarification on what you are trying to accomplish would be nice.
If you did a Nandroid prior to flashing CM10 I would wipe all partitions except SD and restore the Nandroid, if all you want to do is get CM10 off your phone. Remember Nandroid Backups are your friend do them before flashing anything and save them to your PC if you don't want the SD space taken. Doing this has made flashing pain free and hassle free. If I don't like how my phone is running after a flash I can always get it right back to how it was when I was happy with it. Lastly there was a time when I had a Nandroid backup of a Sense ROM and was on AOSP and wanted to flash back to Sense, well my Backup wouldn't flash. After spending hours raising hell I did a clean install of the ROM booted once, then rebooted into recovery and flashed the Nandroid backup that had the settings I was using (when I was on Sense, it won't restore data and apps used on AOSP)...sorry if its not much help but more details are needed. But you have a starting point.
ItzCrooK2UxD said:
How did you try to flash the RUU? You can not flash it like a normal ROM
Also if you are looking for the RUU try HERE
I see what you're trying to do, that won't work...you can't flash a recovery to get to stock because stock phone won't flash from recovery, which is why once you get root the first thing you do is flash a custom recovery. Use the RUU to flash it back to shipped state stock, or if you are trying to keep root and just want to use a different ROM. More clarification on what you are trying to accomplish would be nice.
If you did a Nandroid prior to flashing CM10 I would wipe all partitions except SD and restore the Nandroid, if all you want to do is get CM10 off your phone. Remember Nandroid Backups are your friend do them before flashing anything and save them to your PC if you don't want the SD space taken. Doing this has made flashing pain free and hassle free. If I don't like how my phone is running after a flash I can always get it right back to how it was when I was happy with it. Lastly there was a time when I had a Nandroid backup of a Sense ROM and was on AOSP and wanted to flash back to Sense, well my Backup wouldn't flash. After spending hours raising hell I did a clean install of the ROM booted once, then rebooted into recovery and flashed the Nandroid backup that had the settings I was using (when I was on Sense, it won't restore data and apps used on AOSP)...sorry if its not much help but more details are needed. But you have a starting point.
Click to expand...
Click to collapse
i have installed CM10 without backing up any image, therefore i cannot restore the orifginal vendor's rom. Nandroid back would have prevented this situation. the second problem is that I couldnt find any RUU for this phone. indeed the link you attached seems to have it bu unfortunately it is in chineese and after pushing all the buttons i couldn't download the file. so my options are
1- to pray that someone will be kind enough to publish it in a manner that it is accessible
2- I have a friend with a simillar phone , can i somehow back up hus rom and restore it in mine ????
thank
romah1
I made a backup on my phone in TWRP and wanted to restore it to get some contact info that I forgot to upload to my Google account. Anywho, I go into recovery and wipe me squeeky clean then restore the backup. It goes through like normal and I boot up but it doesn't get bassed the HTC splash screen. It turns to a black screen that occasionally has a white/grey bar at the top. I loaded a different backup I had and am running fine, but I still need that contact info.
Any ideas as to get the back up to work or if it is no use?
KungPow90 said:
I made a backup on my phone in TWRP and wanted to restore it to get some contact info that I forgot to upload to my Google account. Anywho, I go into recovery and wipe me squeeky clean then restore the backup. It goes through like normal and I boot up but it doesn't get bassed the HTC splash screen. It turns to a black screen that occasionally has a white/grey bar at the top. I loaded a different backup I had and am running fine, but I still need that contact info.
Any ideas as to get the back up to work or if it is no use?
Click to expand...
Click to collapse
What hboot do you have?
If its 1.14 and you're switching ROMS (your backup is of a different ROM to the last ROM you were using) you might have to fastboot flash the boot.img of the ROM you're recovering.
i think it is a kernel issue
I had to downgrade from jb to ics and I wiped clean, I run into the same problem, I realized jb uses a different kernel, wipe clean flash your choosen Rom kernel update first and then your Rom, it worked for me hopefully works for you
ilirium said:
I had to downgrade from jb to ics and I wiped clean, I run into the same problem, I realized jb uses a different kernel, wipe clean flash your choosen Rom kernel update first and then your Rom, it worked for me hopefully works for you
Click to expand...
Click to collapse
where can i get the stock boot.img or the stock one x 2.20 image to extract the boot.img?
thanks!
is this it?
would this work?
http://forum.xda-developers.com/showthread.php?t=1812459
if i download the odexed stock rooted rom and extract the boot.img, i can flash that to boot, and then run twrp restore to my backed up stock rooted rom, right?
my stock rooted rom was at&t 2.20 firmware.
Hoping I understood you correct, you basically need to flash a kernel first, so I am guessing you can use flar kernel,
http://forum.xda-developers.com/showthread.php?t=1967897
and that should be the stock kernel on steroids, however if that were not to work he has a kernel for jb phones, so I would start by these first.
I really had this issue where I could see my phone in a brick state mode then flashed the right kernel for the right rom, and boom it worked like a charm.
nespid said:
would this work?
http://forum.xda-developers.com/showthread.php?t=1812459
if i download the odexed stock rooted rom and extract the boot.img, i can flash that to boot, and then run twrp restore to my backed up stock rooted rom, right?
my stock rooted rom was at&t 2.20 firmware.
Click to expand...
Click to collapse