• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Jellybean Upgrade = Secure Element Error

M

Mide

Guest
So this is just a warning to some peeps out there...perhaps it is only me but you never know whom it may help.

I got my Galaxy Nexus from the Play store about a month or so ago. Everything has been quite nice with the phone. No problems what-so-ever.

Jellybean got pushed a few days ago and I went ahead and updated. Afterwards I was trying everything out when I noticed that Google Wallet would error out with a "Secure Element not Responding" error. Called Wallet support they said that they have heard about it before and that it is a hardware issue. Got xfered to Google hardware support and they also have seen it before but that it was in Samsung's territory. Called Samsung and yeah my phone is hosed in this NFC regard and I have to send it in for repair.

The support guy from Samsung wasn't too helpful on giving out any other information but from what I read, I should've wiped my phone a few times prior to the OS upgrade.

I don't recall reading a warning about needing to do this first. I upgraded a Transformer Tablet to ICS with no wipe and that device functioned fine...

Sigh either way 2-3 weeks without a real phone; great.
 
Yeah, this was a problem for some root users when flashing roms. But it's quite concerning that it's rearing itself as an issue when accepting a standard OTA update. This is unacceptable. There is no prerequisite to wipe anything PRIOR TO accepting an OTA update. This is sad news and if it becomes widespread, a needless oversight by Google. Root users have already surfaced this issue in the past, there is no exuse for this sort of thing for folks who are playing by the rules and are upgrading stock phones. :thumbdown:
 
Yeah it's quite frustrating. I kept this phone 100% Vanilla Google and didn't touch anything yet this still happened.
 
Yeah, this was a problem for some root users when flashing roms. But it's quite concerning that it's rearing itself as an issue when accepting a standard OTA update. This is unacceptable. There is no prerequisite to wipe anything PRIOR TO accepting an OTA update. This is sad news and if it becomes widespread, a needless oversight by Google. Root users have already surfaced this issue in the past, there is no exuse for this sort of thing for folks who are playing by the rules and are upgrading stock phones. :thumbdown:

I have to wonder if something happened unrelated to the upgrade. I only suggest this because of the large number of people on the forum who have successfully upgraded to JB OTA, but this is the first case of Wallet not working, after the upgrade, that I've seen reported.

Though I am curious, if I understand the OP, you were simply trying to get into Wallet and got the error (since you say you were trying things out)? Or was this when you actually tried to use Wallet to pay for something?
 
I have to wonder if something happened unrelated to the upgrade. I only suggest this because of the large number of people on the forum who have successfully upgraded to JB OTA, but this is the first case of Wallet not working, after the upgrade, that I've seen reported.

Though I am curious, if I understand the OP, you were simply trying to get into Wallet and got the error (since you say you were trying things out)? Or was this when you actually tried to use Wallet to pay for something?

It's very good to question and wonder. I hope for everyone else' sake that I am an isolated case, but yeah if there are others Google should know.

As far as I know I didn't do anything out of the ordinary. I was trying things out by going into every app and seeing what was different in each. Google Wallet was one of the last apps. The second I clicked it, I got the error that looked exactly like this.

Next it booted me back to the main screen. I then powercycled the phone. No change. I then went into the Apps Info area and cleared out cache, and forced stopped the program. Then I tried to load it up again. It gave me the "intro" screen of Google Wallet. After clicking through some screens it asked if I wanted to use my main gmail account. I clicked on the bubble and clicked next. Then the error re-appeared again. I then went into Privacy and wiped it. Phone came back up, I put in my gmail credentials and tried out Wallet, same error. I then fully powered off the phone, removed the battery, and held down both volume buttons and powered it back on with the battery to get it into recovery mode and deleted the cache then wiped it again. Wallet still gave the same errors.

Yeah I never flashed anything on this phone (Not like my previous Captivate). I actually never plugged it into a computer either now that I think of it. All transfers were done through WiFi. So yeah I guess I'm just unlucky? I know that most people don't use Google Wallet but if people who have upgraded can try it out and see...perhaps they'll get the error. I honestly barely even use the program but on a whim I tried this afternoon...
 
It's very good to question and wonder. I hope for everyone else' sake that I am an isolated case, but yeah if there are others Google should know.

As far as I know I didn't do anything out of the ordinary. I was trying things out by going into every app and seeing what was different in each. Google Wallet was one of the last apps. The second I clicked it, I got the error that looked exactly like this.

Next it booted me back to the main screen. I then powercycled the phone. No change. I then went into the Apps Info area and cleared out cache, and forced stopped the program. Then I tried to load it up again. It gave me the "intro" screen of Google Wallet. After clicking through some screens it asked if I wanted to use my main gmail account. I clicked on the bubble and clicked next. Then the error re-appeared again. I then went into Privacy and wiped it. Phone came back up, I put in my gmail credentials and tried out Wallet, same error. I then fully powered off the phone, removed the battery, and held down both volume buttons and powered it back on with the battery to get it into recovery mode and deleted the cache then wiped it again. Wallet still gave the same errors.

Yeah I never flashed anything on this phone (Not like my previous Captivate). I actually never plugged it into a computer either now that I think of it. All transfers were done through WiFi. So yeah I guess I'm just unlucky? I know that most people don't use Google Wallet but if people who have upgraded can try it out and see...perhaps they'll get the error. I honestly barely even use the program but on a whim I tried this afternoon...

Thanks. I had tried it out on my Nexus, like you checking things out after I had downloaded JB OTA, so that is why I wondered. My Wallet has, and is still, working fine; though I haven't tried using it to pay. I'm sorry to hear you had problems.
 
Back
Top Bottom