If you've downloaded or had the Android 2.3.6 update pushed to your AT&T, T-Mobile, or unlocked Nexus S recently without issue, consider yourself lucky. None of this applies to the Nexus S 4G on the Sprint network.

While we reported that the update was breaking Wi-Fi and USB tethering initially, it seems something much, much worse is happening to some users who have received 2.3.6 OTA.

If you check out this Google thread, you'll see a number of poor souls have had all cellular connectivity stripped from their devices after updating. The easiest solution so far? Roll back to Android 2.3.4 (or earlier), which almost inevitably requires a full wipe of the device. Yikes. There's similar threads over at XDA, here and here.

A new radio baseband version was included in the update, and this seems to be the root cause of the aforementioned connection woes. Some savvy folks over at XDA have come up with an alternative solution, but it requires a bit of hackery.

By rolling your phone back to an older radio baseband version (instead of the entire OS), you can save yourself from rolling back the OS or conducting a full wipe. However, you'll need to follow the instructions for "Method 2" over on this XDA thread very, very carefully. To do this, you need to figure out which model your Nexus S is (I9023 and I9020T are T-Mobile, I9020A is AT&T), backup your EFS folder, and then download one of the older radios and flash it via ADB (included in the files). For AT&T and GSM Unlocked phones, the UCKD1 radio is advisable. For T-Mobile, KD1 should do the trick. Other radios may work as well.

Once you've flashed, if you have no 3G connection, you'll have to reset it manually using the "Retrieve 3G Data Connection" fix located in the same XDA thread. Read everything carefully, and if you're not sure you can manage doing this: don't. Missteps could result in a bricked phone.

Again, the alternative option is go into ClockworkMod, make a nandroid backup, then wipe the whole phone and reflash it to something like CyanogenMod or an older Nexus S image. We recommend the former. Good luck.

XDA [2] [3], Google

David Ruddock
David's phone is whatever is currently sitting on his desk. He is an avid writer, and enjoys playing devil's advocate in editorials, and reviewing the latest phones and gadgets. He also doesn't usually write such boring sentences.

  • Gabriel

    So far so good here !

    Nexus S T-Mobile 2.3.6 version GRK39F !

    3G Working
    Wifi Working
    Tethering wifi + usb working

    Using in Brazil

    • Alex

      Just like Gabriel, my nexus s has received de update here in Brazil, and everything is ok, including 3G and tethering

      • alex

        Wtf. My 3g stoped working. Google is terrible with this updates.

        • Gabriel

          Maybe it's not the celphone ... maybe it's your carrier ...

        • bisto

          I'm also in Brazil and updated to 2.3.6 after insistent push messages. It worked fine for 3 days and now wifi at work is connected but not exchanging data. Don't know yet if at home is ok. Did someone try something? Some config or tweaking perhaps?

  • Craig Rachel

    Google has been aware of the i9020A's bevy of problems since April 2011 and they continue to get worse.
    This is another very long Google thread in which people discuss, amongst other things, their experiences updating to 2.3.6


    Rogers quit selling the Nexus S all together, presumably because all the pissed off users

  • http://www.AndroidPolice.com Artem Russakovskii
  • matt

    Correction : i9023 is not T-Mobile version, it is AT&T version.

    • Leonid

      i9023 is a T-Mobile version with S-LCD.
      Why would you post such a misinformed comment is beyond me.

  • http://donothaveone.com Ben

    I know that this said that is only affecting non Sprint (Nexus S 4g) phone but I just had to replace my wifes NS4g because she updated to 2.3.7 and about two days later her 3g data, cell, including SMS and MMS were no longer working. The Wimax and Wifi still worked but nothing else. The great people at the Sprint service center in my area, Greensboro, NC, were more than helpful getting everything working again. But in the end I had to get a new phone because they were unable to flash hers back.

  • Duffin

    Weird. I received the update OTA and installed it with zero issues. My phone is still stock and I haven't rooted or anything. Maybe these other people changes something on their phones?

  • Evan

    I originally updated when it got pushed to me a month ago and could not tether. I put up with this for 4 days and gave up and rolled back to 2.3.4. NOW, for the last 2 days, I've been getting the push notification every 30 freakin' minutes to update to 2.3.6. HELLLLLL NOOOO!! I tether ALOT! This is the sole reason I pay for a 6 gig package. Really wish I could turn off the OTA push notification.

  • Luckbuckets

    i havent had a problem with 2.3.6, hopefully saying that isnt jynxing it, but all good with my Nexus S on T-mobile

  • http://techupdate.prayas.info Prem Kumar

    Updated today with 2.3.6 from 2.34 via OTA

    EVERY things seems to be working fine. Following things I noticed.

    Its solved the yellow screen problem (not fully) which 2.3.4 introduced.
    I m now not able to turn off the NFC hardware. Its a bug introduced.

    My configurations :
    Nexsus S unlocked
    Purchased from Best buy with T-Mobile 2 years contract (but unlocked)
    Using in Georgia,USA

    • Gabriel

      Hey Prem !

      I have experienced the problem with NFC too but after a simple reboot I was able to turn it off again !

      • http://techupdate.prayas.info Prem Kumar

        Thanks Gabriel.
        Since morning, I was not able to turn off the NFC hardware.
        But in the evening, I was easily able to turn it off, though I did not restarted the Nexsus S.
        But I remember that I did do some thing like starting stopping 3G, Wifi several time while travelling accross the city.

        So don't know how NFC harwared is now able to stop by using the menu option.

        As I am software engineer in microsoft domain, I can guess that there must exist some bug in the code which is related to 3G/WiFi and NFC. deep within the OS codes.
        I will update this chain, if I find something else.

  • scott

    Mine seems fine. I updated yesterday and am able to use both Sufi and 3g. I'm in Canada using wind mobile with a factory unlocked nexus s.

  • Ryan Griffin

    My at&t nexus s is still on 2.3.4. I'm still waiting for the OTA.

    • http://techupdate.prayas.info Prem Kumar

      You may not be lucky enough today the one like me.

      You should wait for next few days.

  • http://andresschulz.com andyux

    Fixed. Update messed up tmobile network settings, i used these:
    Settings>wifi and networks>Mobile Netoworks
    Access Point Names (epn.tmobile.com)

    APN: epc.tmobile.com
    Proxy: not set
    Port: not set
    Username: none
    Password: ****
    Server: *
    MMSC: http://mms.msg.eng.t-mobile.com/mms/wapenc
    MMS Proxy:
    MMS port: 8080
    MCC: 310
    Authentication Type: Not set
    APN Type: not set


    3G is back, faster than before the update. Hotspot works.


  • greg

    My phone discharges at DOUBLE speed after 2.3.6... omg.

    • http://www.metaksan.com Wire mesh Cable Trays

      Dobule? Incredible..