Originally Posted by LiquidSolstice
The new Google Wallet builds don't use the Secure Element anymore. All the encryption happens in the cloud. I have repeatedly flashed without clearing the data and never have any problem activating it.
This thread is no longer valid. Google fixed this problem and it's not coming back. If I was to guess, even if it says your secure element is bricked, you could use the newer builds just fine.
If you're worried about this at all, stop worrying. I'll say it again; as long as you're using the newer builds of Google Wallet, there is NO interaction with the Secure Element period. You can wipe as much as you want, even RUU for all it matters, Google Wallet will work and activate just fine.
Completely dead wrong. The secure element is still in use - if it weren't, then GW would be working on the GT-I9100P and SGH-I777. GW wouldn't cause piles of SE spam in logcat when you use it. GW wouldn't REPORT A DAMNED SECURE ELEMENT VERSION IN THE ABOUT SETTINGS. GW wouldn't bomb if nfcee_access.xml is missing.
The only thing that changed with the "cards stored in the cloud" update is that instead of directly storing the info for an added Citi PayPass card, the SE now stores a "proxy" PayPass card that is funded from whatever card you added in the cloud.
However, Google has made SE management significantly more robust. Previously, if GW lost its credentials, it would just keep retrying until the SE bricked. Now, if it can't authenticate with the SE, it commands the SE to wipe its data and start from scratch. It's pretty much impossible to brick SEs with GW these days.
(Why the thread necromancy? People are still linking to this thread from elsewhere.)