[Q] Stuck at Google Logo - Nexus S Q&A, Help & Troubleshooting

I flashed 2.3.4 and rooted fine. After I flashed Netarchy kernel 1.3.0.7 on CWM, I'm stuck at Google logo... what can I do? I can't reflash GRI22 because I already have Netarchy kernel installed.

johnkim0011 said:
I flashed 2.3.4 and rooted fine. After I flashed Netarchy kernel 1.3.0.7 on CWM, I'm stuck at Google logo... what can I do? I can't reflash GRI22 because I already have Netarchy kernel installed.
Click to expand...
Click to collapse
Assuming you don't have a nandroid you could always apply the full 2.3.3 update and then the 2.3.4 update over the top of that to get back to a fresh 2.3.4 and not wipe.
Full 2.3.3: http://android.clients.google.com/p...2cf141e6a.signed-soju-ota-102588.f182cf14.zip

krohnjw said:
Assuming you don't have a nandroid you could always apply the full 2.3.3 update and then the 2.3.4 update over the top of that to get back to a fresh 2.3.4 and not wipe.
Click to expand...
Click to collapse
I figured Netarchy 1.3.0.7 CFS is for 2.3.3 ROM... Why didn't I realize that?
Anyway, I was able to mount sdcard on CWM to copy full stock 2.3.3 ROM to the root of SNS and I flashed back to stock 2.3.3 ROM..
What a pain..
I have to re-root my phone

Help! I have the same problem. I'm stuck on the boot logo, but I'm a little more noobish. I added that stock file to my phone, but everytime I go to flash it, it says operation aborted! What am I doing wrong???

Related

[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

will updating to 2.3.4 break my root?

I am currently rooted on 2.3.3...will manually updating to 2.3.4 cause any issues? Will I need to re-root?
Sorry for the newb question
Sent from my Nexus S using XDA App
Yes you will have to re-root, but you can do it using the same method you used before, I believe.
after doing a bit of reading and having already experienced upgrading from 2.3.1 to 2.3.2 and 2.3.3, i just decided to go for it. here's what you need to do.
i'll give you what my setup was. 2.3.3 running stock with modified radio (kb3) and modified kernal (netarchy 1.3.0.7 bfs).
i got all the files i thought i would need.
1. kb1 radio
2. netarchy 1.3.0.8 bfs for 2.3.4
3. the 87mb 2.3.3 stock zip
4. the superuser.zip
5. the 2.3.4 zip
made a titanium backup of everything, and did a rom backup.
and then i just went for it. booted to clockwork recovery. tried flashing 2.3.4 and of course i got an error. i was expecting that.
updated to kb1 radio which is stock for 2.3.3 and then ran 2.3.4 update, and it errored again. was expecting that since my kernel was still different.
i didnt know how to flash stock kernel so i went ahead and ran the 87mb zip. it went very quickly and it flashed only the radio and the kernel.
tried 2.3.4 again and still no luck.
ran 2.3.3 again and this time it updated fully, taking approx 2 minutes.
NOW i ran 2.3.4 and it installed.
then i ran netarchy 1.3.0.8 cuz i just can't live without the voodoo color/sound enhancements.
i rebooted the phone and it loaded the OS up fine and dandy.
i also figured i would have lost recovery, but that wasnt the case. i rebooted into recovery and clockwork loaded. i then mounted everything and installed superuser.zip. that finished and i booted back into the phone.
all done. superuser back, colors great, radio kd1, stock 2.3.4. the one final thing i did was check system/etc to see if the recovery.sh file was renamed. it wasnt so i renamed it to recovery.sh.old using root explorer.
i rebooted to clockwork to make sure i still had recovery and i did.
done and done.
hope that helps.
Well crap....I'm not really up to speed on half this....had some serious trouble trying to root the first time...this list of what you went through makes me want to vomit just thinking about it lol...
Sent from my Nexus S using XDA App

[Q] Stock Recovery Nexus S 2.3.3

Is it possible that my 2.3.4 update isn't working because of my clockwork recovery image ? Because if that is the case I would like to revert to the stock recovery image.
With clockwork my update gets stuck in the android with the yellow triangle and I have to pull my battery to reboot.
I have build GRI54
Can anyone tell me where to find that recovery image ? And hope that that is the issue that my update won't install.
Thnx in advance.
Your probably trying to install the ota update file .. That will not work on your gri54 not even on stock recovery .. Go to the general section and downlaod the 2.3.4 full rom for gri54 . You can install that even with cwm ..
Thnx, after not booting anymore, googling a lot updating the CWM recovery it suddenly started to update my phone and also wiping it. But now I have 2.3.4 unrooted.
Had something strange a long the way of getting there. the boot partition couldn't be formated anymore. The latest version of clockwork fixed that i guess.
Jacob Nexus S 2.3.4

[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

[Q] Kernel Flash Help...

Currently running a SkyRocket i727 with GB 2.3.5. I have ROM Manager, Root Explorer and ROM Toolbox installed and the device is rooted. Also flashed CWM. I would like to flash my kernel to one that allows me to replace/modify the boot animation. I tried this one from Da_G:
ponack.net/TPC/dagnarf/cwm-ke...el-0.43-v2.zip
On reboot, I get a "Process system....." failure and the phone won't do anything. Pulled the battery, booted in CWM and restored from backup. Phone is working now.
Can someone help me with doing a kernel flash that will work? The ROM is the stock ROM. I was told that you can flash the kernel without having to flash a new ROM.
Thanks.
This is my favourite gb kernel
http://forum.xda-developers.com/showthread.php?t=1437563
Flash 010 mainline edition
If that doesn't work try Eugene's sgs2 streamline kernel

Categories

Resources