Go Back   Android Forums > Android Phones > Nexus S

test: Reply
 
LinkBack Thread Tools
Old April 2nd, 2012, 05:52 AM   #1 (permalink)
New Member
Thread Author (OP)
 
Join Date: Nov 2011
Posts: 8
 
Device(s): Nexus S
Carrier: Not Provided

Thanks: 1
Thanked 0 Times in 0 Posts
rahulc13
Question Issue in Updating ICS from 4.0.3 to 4.0.4 after reaching the recovery screen

Hi

I earlier received the OTA for 4.0.3 but when 4.0.4 update was released I didn't received the same, so tried getting it manually done.

Followed the steps mentioned here: How To Manually Update Android 4.0.4 ICS On Nexus S | ValueWalk

Everything is going fine till Step No. 5... but after that I am facing an issue.
  1. When I select 'recovery' this is what happens:
  2. The screen goes blank
  3. The 'Google' logo appears
  4. for a second the 'yellow exclamation mark appears'
  5. The next second I see a 'red exclamation mark' over the android logo.
  6. The screen goes blank with menu buttons lights on.
  7. The phone restarts after a while.

I am having a rooted 4.0.3 with stock firmware.

Requesting assistance for the same.

Advertisements
rahulc13 is offline  
Reply With Quote
sponsored links
Old April 2nd, 2012, 07:11 AM   #2 (permalink)
Senior Member
 
Join Date: Dec 2010
Location: Birmingham, UK
Posts: 730
 
Device(s): HTC ONE, Galaxy SIII retired, Note 2 (Ditto DN 5.2 KK 4.4.2) , ASUS TF300 (JB 4.2.1 stock roo
Carrier: 3 UK

Thanks: 44
Thanked 309 Times in 240 Posts
Default

The reason you are "stuck" at this point is because your device is looking for the recovery. Easiest way is to flash a custom recovery as you did when you rooted. Well if you are/were rooted you will have used the adb method for communication with and subsequently the flashing of your device. You are obviously halfway there. Go to the bootloader again (from off with vol up + power on) at that point connect to your PC via USB (if you already have the ADB drivers installed properly your PC should recognise the device.
Open the command prompt from where your adb command files are located by holding the shift button and right clicking the folder. You now have the command prompt > type fastboot devices - this should return a long text and numerical string (youir device S/N > your device is recognised by Windows OS > now you need to reflash your custom recovery (I assume it's CWM - I'd recommend the Touch version 5.8.0.2) > after it has flashed the custom recovery reboot the bootloader and choose recovery followed by selecting to install from sd-card and choose the zip file you want to flash. That should do it.
heat57 is offline  
Reply With Quote
The Following User Says Thank You to heat57 For This Useful Post:
rahulc13 (April 2nd, 2012)
Old April 2nd, 2012, 11:34 PM   #3 (permalink)
New Member
Thread Author (OP)
 
Join Date: Nov 2011
Posts: 8
 
Device(s): Nexus S
Carrier: Not Provided

Thanks: 1
Thanked 0 Times in 0 Posts
rahulc13
Default

Quote:
Originally Posted by heat57 View Post
....your custom recovery (I assume it's CWM - I'd recommend the Touch version 5.8.0.2) > after it has flashed the custom recovery reboot the bootloader and choose recovery followed by selecting to install from sd-card and choose the zip file you want to flash. That should do it.
Thanks a lot...

issue resolved...

@Mods... request you to close the thread..
rahulc13 is offline  
Reply With Quote
Reply

Nexus S
Current Rating:
Rate this Phone:

The Nexus S is the second generation in a line of smartphones that are in direct collaboration with Google. This time, it's made by Samsung as opposed to the Nexus One from HTC. Google's Nexus line of phones are always a stock, vanilla Andr... Read More



Go Back   Android Forums > Android Phones > Nexus S
Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On



All times are GMT -5. The time now is 10:07 PM.
Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2014, vBulletin Solutions, Inc.