[Q] NFC killed with 2.3.6 update - Nexus S Q&A, Help & Troubleshooting

The NFC on my phone stopped working (2.3.6 Nexus S, no root, stock recovery) so I fastbooted the ghr78 files to take me back to a previous firmware and nfc worked like a charm, turned on and off with no problem whatsoever.
The system update notification came for 2.3.6 and i installed it, and upon reboot the NFC refuses to turn on (gives me "an error has occured") Any ideas on was is going on?

Ok even weirder. I installed the google wallet fix on xda through clockwork mod, and nfc goes back to working perfectly. I'm really curious now as to what's happening.

I guess they locked it on not 4g nexus, dunno. Mine is the same, working on 2.3.3 and 2.3.4 but not on 2.3.6
Sent from my Nexus S using Tapatalk

Just noticed myself - 2.3.3 - working, 2.3.6 -not working.

I'm waiting for the ICS OTA just to see if NFC works then but I rolled back from 2.3.6 to 2.3.4 and NFC worked great there. On 2.3.6 it just says an error occurred, weirdly enough when I tried out the ICS OTA the NFC worked

anishs said:
I'm waiting for the ICS OTA just to see if NFC works then but I rolled back from 2.3.6 to 2.3.4 and NFC worked great there. On 2.3.6 it just says an error occurred, weirdly enough when I tried out the ICS OTA the NFC worked
Click to expand...
Click to collapse
There is no ICS ota.
Sent from my Nexus S using xda premium

I was on CM7 and oxygen 2.3.1 which are 2.3.7 based roms , I wanted to go back to stock because of stability issues so i restored my backup. But NFC did not work,
But it works perfectly with CM7 and oxygen,
Guess is that if you restore apps from a newer android version to a older version then NFC gets screwed up.
So i formatted everything including the sdcard and then flashed 2.3.4 ROM and updated to 2.3.6, Now NFC is working properly.
Hope this helps.

=\ weird I just checked mine and it says the same error message... I'm on 2.3.6 and it used to work... always backed up my phone and I guess it started happening once I started flashing Drew Garens ICS =\
Sent From In between Your Moms Boobies

It's a bug. It's going to be fixed in ICS 4.0 - see bottom of thread.
http://208.65.154.218/support/forum/p/Google+Mobile/thread?tid=6b9bc174d2ce5651&hl=en

Related

Update connection failed

Usually when I've tried to update it would automatically say latest version etc. Now its saying checking on software update for about a minute then software update connection failed.I turned off my wi fi, and it still happens.any suggestions? Thanks
Also I'm running stock & not rooted.
i dunno I had the same issue. it would seem that the OTA is pushed out like in batches or something for it to say latest version and/or connection failed. Personally I got tired of waiting and just flashed the OTA gb rom in the dev section. Sure i dont have the new baseband but i honestly dont care lol.
Thank you uploader very much.
This was happening to me as well..called T-Mobile they tried pushing the update through but didn't work so I got a new phone sent out and the update went smooth after that...I just wanted the new baseband and now am running miui alpha 2 and couldn't be happier!
Sent from my LG-P999 using XDA App
They stopped sending out the updates. Call T-Mobile and ask them if you don't believe me.
Got my replacement G2X last night and it came with 2.2.2, checked for updates and it said i was up to day. Checked the LG updater, same as well. So, I just did the KDZ method and it worked.

HELP! Nexus can't connect to carrier after 2.3.6 OTA...

Hey guys, I decided to go back to stock 2.3.3 from cyanogen yesterday via recovery. Everything went fine and worked on the stock rom until I got the update from google to 2.3.6....
So then my signal bar started showing an X right after the update and the notification bar says Emergency Calls only. Im pretty sure the APN is right as I have re entered it multiple times. My cousins sim card also didnt work on my phone.
Did the 2.3.6 OTA bust my radio or something?
PS: I flashed my phone back to the Cyanogen recovery I've made before all this and it still didn't work.
Go here: http://forum.xda-developers.com/showthread.php?t=1281864
Sent from my Nexus S running NSCollab ROM and Mathkid's Supercalifragilisticexpialidocious Kernel!!!

[Q] Unable to get stable Working ROM

Hi All,
I own a Motorola Defy. I am kind of new to android developement. i had 2.2 on my phone and wanted to upgrade, followed all the steps available online for cyanogen 7.1, liquid arc, etc. with all the ROM's i had the same problem. Everything goes fine, until i reboot my phone. The moment i do that after installing new ROM. I loose network connectivity and a pop up msg comes up continously saying android.phone.com stopped responding. From there i have to do the complete wipe once again. i read in some forum about flashing radio, however i dont see this option in my recovery mode at all.
Anybody who knows how to resolve this????????
I looked this up in the forums. This applies to going from 2.1 to 2.2, but sounds like it may help you. http://forum.xda-developers.com/showthread.php?t=947578
Thank you for the reply.
However, I was already running Froyo on my defy. I can also go back to that via RSD or by restoring it to the ROM i backedup before i started this testing. My concern is why i am not able to Install this custom ROM and make it working when all others can do it without any issues. I am still running Cyanogen nightly ROM (2.3.7). I also know the moment i restart my phone it will loose network connectivity and will keep getting those pop msgs. Is there a way to curb that.
Appreciate the help...
You can look for MIUI for the defy. I have also MIUI on my Defy and it works perfect
Sent from my Galaxy Nexus using XDA App
Thanks for your reply....
I was missing the defy baseband update. Thank fully that fixed the network connectivity issue. Now i am running ICS 4.0.1 perfectly. Except the camera everything is working smooth. Had little issue with restore from Titanum backup. But an unregistered version of TB fixed it.

My stock 4.0.3 Xoom got update but didn't update

I am new to Xoom but not to Android. My new Xoom came shipped with ICS 4.0.3(IML77), told me there was an update and rebooted afterward, but the About Tablet page in settings still says 4.0.3 IML77 and NOT 4.0.4 IMM76. Now there is no update available. Is this common. I am tempted to just root it and put on EOS, but I thought I'd give it a few days on stock first.....
Always something different.....
Having same issue on stock unrooted US Xoom Wifi. Loaded w/ 4.0.3 from factory, 4.0.4 update downloads and ends up in green bot w/ red ! during install, then eventually reboots to 4.0.3. After that upadate is no longer found??
hammersfd said:
Having same issue on stock unrooted US Xoom Wifi. Loaded w/ 4.0.3 from factory, 4.0.4 update downloads and ends up in green bot w/ red ! during install, then eventually reboots to 4.0.3. After that upadate is no longer found??
Click to expand...
Click to collapse
Exactly the same! I thought I must have done something wrong! Got my Xoom from 1saleaday...Hope they didn't sell me a non-US wingray.....
bbshopper
same thing as you guys. im gonna try this guide here and see what happens.
http://www.xoomforums.com/forum/mot...es/2299-how-return-stock-wifi-only-hw169.html
Just install this stock rooted ics 4.0.4
http://forum.xda-developers.com/showthread.php?t=1575393
Sent from my Xoom using Tapatalk 2

How to disable stop OTA updates on ICS 4.0.4

How to disable stop OTA updates on ICS 4.0.4? It tries to do OTA install of jellybean 4.1 but i want to stick with current custom ROM?
stewie-droid said:
How to disable stop OTA updates on ICS 4.0.4? It tries to do OTA install of jellybean 4.1 but i want to stick with current custom ROM?
Click to expand...
Click to collapse
If you are on custom rom, you shouldn't be getting OTA.
Try renaming etc/security/otacerts.zip to otacerts.bak
Sent from my Nexus S using xda premium
Thank you guys. Renaming that file at first did not work but after while those annoying updates have stopped so i think it's working.
What's weird is that even after reboot they still were popping up but only after some time they stopped. Odd. Thank you guys.
Now i'm getting some weird message about:"there was an error while trying to download the data. Please try again later"
This is famous pixelrom 1.72 fully touched. I love this rom
Hmm, I've experienced this on Stock 2.3.6 ROM, the download still showing but stopped, It's annoying but, I'd try factory reset & after it completed I'm turning on the phone without sim card (to ensure there is no internet connection) & renaming the "otacerts" file. So download will not be showing & not started
Sent from my Nexus S using xda premium
So weird. Even the data message went away now. Many thanks guys. I'm keeping this rom.
no problem guys, glad to help
Sent from my Nexus S using xda premium
stewie-droid said:
How to disable stop OTA updates on ICS 4.0.4? It tries to do OTA install of jellybean 4.1 but i want to stick with current custom ROM?
Click to expand...
Click to collapse
I tried and removed ICS and JB. Went back to GB, it's faster less bloated and does the job for me. GB kept downloading ICS automatically and giving me nag messages to install it.
I found the following thread, which fixed the problem.
http://forum.xda-developers.com/showthread.php?t=1579154
The trick is to install FOTAKill immediately after you install another rom, before the phone connects to the network.
To install it, I used the "adb push" method from cwm recovery.

Categories

Resources