yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] mohitrocks:
Oh god. Do you guys think I should return my Galaxy Nexus and get a new one now? Just a note: In my area (Canada) Google Wallet will officially be released early 2012 so will it start working again when it's officially released? Couldn't I just complain to Google (or whatever service) saying that I went to USA for Christmas vacation and when I came back, it stopped working?

By "ties your phone to the current ROM" I assume you mean the specific version of the rom as well? So basically, if I wipe and update to a higher version of the rom running a new version e.g. 4.0.2 > 4.0.3 will I be locked out as well? :( I should have read the thread before trying it. Hopefully Bell will exchange mine, experiencing wifi issues anyway.

EDIT: If I do upgrade to a new rom, but do not activate Google Wallet on the new rom, then nandroid back to the rom with Google Wallet installed will it work?
[Samsung Galaxy Nexus] SS2006:
Support 4.03 please
[Samsung Galaxy Nexus] Royal2000H:
Please note I'm just interpreting Ryands991's experience. I have yet to install the APK, and I'll probably hold off on it based on this information.
[Samsung Galaxy Nexus] mobilehavoc:
It's it fair to say that this secure element issue won't affect people who don't flash ROMS? I have the apk working fine on a stock GSM Nexus so I'm assuming I won't have any issues in the future. Thoughts?
[Samsung Galaxy Nexus] jburnette87:
Was on android rev hd 2.1,switched to gummy .3 and secure element pops up. Got no help in the rom thread. I made a nandroid,would it work if I restored that?
[Samsung Galaxy Nexus] biggiephat:
Ummm... ive flashed about 7 roms so far and everytime I have restored my titanium backup of google wallet and it has never locked me out...
[Samsung Galaxy Nexus] jburnette87:
Damn man. I'm depressed now. I only installed the apk. Guess I'll restore and see what happens.
[Samsung Galaxy Nexus] biggiephat:
ive yet to try it though. Did it once and it just kept looping "Sending..." "Sent" "No terminal dectected"

pretty sure i just did it wrong. It beeped once and i pulled it away and i should of waited until it was done cycling through its procedure.
[Samsung Galaxy Nexus] jburnette87:
Ive done it twice, felt like a badass. Lol. Now I don't have it :(
[Samsung Galaxy Nexus] NPuter:
My GN should be arriving tomorrow, and I was going to install wallet right away.

However, now I am going to hold back....

Can anyone further explain what is happening?
[Samsung Galaxy Nexus] jburnette87:
Nandroid restore didn't resolve it :(
[Samsung Galaxy Nexus] mohitrocks:
Did you make a titanium backup? Also, on a side note, if I flashed a new rom, didn't install Google Wallet, and then I restore my nandroid backup with Google Wallet installed, will I get the secure element issue?
[Samsung Galaxy Nexus] tim-atl:
I'm pretty sure you cannot add funds from a debit or any other card that requires a PIN. I just can't find the link at the moment..
[Samsung Galaxy Nexus] :
I believe Gummy comes with wallet pre-installed. Did you open it up, and get locked out?

What I am doing now is simply not even playing around with Wallet anymore, if a ROM that I install has it, I immediately delete the .apk via root explorer. Should this be okay? Or simply having the .apk on my phone can get me locked out?

---------- Post added at 12:44 PM ---------- Previous post was at 12:38 PM ----------

Sorry to bump this, but can anyone clarify?
[Samsung Galaxy Nexus] jetrii:
For those restoring it with titanium backup, do you simply restore Google Wallet or the nfc application also?
[Samsung Galaxy Nexus] mohitrocks:
I actually have the exact same concern. I think what I'll end up doing is exchanging the phone from Bell because I'm experiencing wifi issues as it is, and I can always fake another issue.
[Samsung Galaxy Nexus] carrot34:
I'm wondering about this too ... I've got a GSM Galaxy Nexus running 4.0.1, and I'm wondering if the OTA update to 4.0.2 (whenever it finally comes!) will break Google Wallet. Does anyone know?
[Samsung Galaxy Nexus] biggiephat:
Just went to Mcdonalds to test this thing out finally after my failed attempt at Burger King (I did it wrong).

The old lady was pissed at me trying to make it work but i held it there for a solid 10 seconds and it never accepted the payment. Google wallet opened and it said sending and then Sent! but then threw an error saying ask cashier if it went through or tap again.

This thing has not worked for me, maybe im doing it wrong? lol
[Samsung Galaxy Nexus] devlp1213:
anyone find a work around for 4.0.3 yet? tried a couple things but still learning my way around app development n such
[Samsung Galaxy Nexus] biggiephat:
workaround? ive been running it on a 4.0.3 ROM for awhile
[Samsung Galaxy Nexus] zilaitis817:
It turns out my credit card works i just couldnt use my dept card for adding funds
[Samsung Galaxy Nexus] biggiephat:
Just tried to disable my pre-paid card after my failed attempt at mcdonalds, and it told me it couldn't and I have to reset google wallet data because it was an "unrecoverable error"

Seems to be when I use it, it needs to be reset everytime and does not work.
[Samsung Galaxy Nexus] civicsisedan:
Wrong.

I add funds with my debit card. Have done it 4 times already. Make sure your billing address is correct and all other info
[Samsung Galaxy Nexus] devlp1213:
ive tried it on bugless beast and can't get it to stop fc-ing after installing it. tried regular and pushing it to the system with no go
[Samsung Galaxy Nexus] chandlerweb:
Ok, so it seems no one really knows exactly what steps cause a secure element lockout and which steps guarantee you don't get a lockout / can recover from a lockout. There must, however, be a common thread. One piece of detail missing from most people's accounts of successful or failed attempts is what rom they flashed from and to. Could the key be in this but of detail? Perhaps any future accounts of experiences could include this to help us all out?
[Samsung Galaxy Nexus] mohitrocks:
@lukegb can you please bold the insecure element issue on your thread or at least make it abundantly visible for the next user walking into this mess.

Edit: Also, as of this point in time, there is no possible way to bypass the insecure element error? Can someone explain what this error is? Thanks.
[Samsung Galaxy Nexus] drPheta:
Some easy to read info on how GW fails with the secure element.

http://pocketnow.com/android/secure-element-not-responding-in-google-wallet

I'm curious what will happen when GW is officially released for the Google Nexus. What will happen to those of us who installed and setup the current GW apk?

I also wanted to ask: Why does GW ask you to add the prepaid card after you reinstall it and enter your Gmail info? Shouldn't it realize that you have already exhausted the $10 prepaid gift and just update the app that you in fact have a $10 (or however much) prepaid cash card?
[Samsung Galaxy Nexus] bplewis24:
Doesn't seem to be anything there that hasn't been said in this thread. There's still no definitive information on what causes this thing, what doesn't cause it, and what can be done to undo it.

Brandon
[Samsung Galaxy Nexus] shominy:
UPDATE 4 - 12/28/2011 - Got a message from Google Wallet Helpdesk. They still can't figure out what the problem is. Now they're escalating it up to the development department for further investigation. It was only a courtesy call to keep me informed. I never called Google only Money Network.

For those just reading. I was locked, stocked and unrooted. Installed GW.apk. Everything worked fine. Used it at CVS and added $50. Decided to root using superboot. Unlocked bootloader. Flash with superboot. Installed GW.apk. Launch GW and was greeted with a friendly "Secure Element not responding." App closes. Uninstall and reinstall. Same error. Flash back to stock and lock the bootloader. Install GW.apk. Same error. Flashed back to superboot and staying.
[Samsung Galaxy Nexus] ebe3692:
has anyone flashed a new ROM and re-installed Wallet successfully? or will this happen anytime GW is reinstalled?

I'm a little worried about flashing a new ROM now that Ive side loaded the GW apk
[Samsung Galaxy Nexus] JayBeezy802:
Yes. People have flashed new roms and "re-installed" wallet and have had it working. However, when i say "Re-install" what I actually mean is they reinstalled the BACKUP DATA/.apk they made from titanium back-up or similar apps. SOME people have flashed never made a back up and reinstalled wallet just fine. However, most of the people who flashed new roms and are still using wallet, are using back ups that they made when they first installed wallet (i.e. when it was first activated, working and linked with the secure element).
[Samsung Galaxy Nexus] papstar:
After first installing the apk on the stock ROM, I flash AOKP which has wallet.apk as a system app. Setup just fine.
[Samsung Galaxy Nexus] ebe3692:
awesome.

I read a thought on another forum which was to reset google wallet via the settings menu which would remove all credential data and hopefully remove the link to the secure element and then do a new setup after re-install.

not sure if this would erase your balance but I would expect that the data is stored on google's servers and not just locally
[Samsung Galaxy Nexus] jtambis6:
Grrrrr..... I hate to read bad news just when I transferred $50 to my Google Wallet and I'm ready to root my phone. Maybe I should put the rooting on the back burner until Google Wallet Secure loop hole has been solved. I just love showing off paying with my phone in my local McDs outlet.
[Samsung Galaxy Nexus] andrew53517:
So if I go from ARHD (I had the .zip installed and it worked fine) to droidtheory (which comes with the .apk already with the ROM) I should restore my titanium backup and everything will work fine? Or just start fresh with the app since it is a new ROM?
[Samsung Galaxy Nexus] mohitrocks:
I doubt you could restore your titanium if you already have the app pre-installed in the phone. I think you would have to get root explorer, navigate to /system/app and then delete the google wallet apk, and finally install it through titanium backup.

Note: I don't provide any guarantee with this method. It may work, or may not work. You have been warned. However, if you do decide to go through with it and restore the titanium backup, please let us know how it goes :)
[Samsung Galaxy Nexus] drPheta:
Didn't see an answer to this question in the entire thread, so I wanted to ask again.

Why does GW ask you to add the prepaid card after you reinstall it and enter your Gmail info? Shouldn't it realize that you have already exhausted the $10 prepaid gift and just update the app that you in fact have a $10 (or however much) prepaid cash card? I ask this because I had to exchange a Gnex due to busted speaker. Loaded up GW in the new phone and I had to activate a new card and all... even after loading up the gmail info.

(NOTE: someone mentioned GW may be tied to the ESN of the phone rather than your GMail info)
[Samsung Galaxy Nexus] mobilehavoc:
Sooooo it does seem this is specific to people flashing ROMS because they do a factory wipe in the process. Doesn't look like this will be an issue if you stay stock and just follow the stock updates because the app data will be preserved.
[Samsung Galaxy Nexus] lukegb:
Except I have never once had the SE error despite having swapped between several different roms - notably modaco and stock - and not having restored backups at all.

Something to think about.
[Samsung Galaxy Nexus] biggiephat:
it was def. the zip file you had witht he mistake in it that killed a few people's phone (honest mistake though, this is why we test these things).

or people installing on 4.01 or 4.0.2, then going to 4.0.3 and restoring backups.
[Samsung Galaxy Nexus] lukegb:
It can't really have been the zip, and because I used that too...
[Samsung Galaxy Nexus] beng2k:
So i had stock 4.0.2 rooted with CWM. Flashed the original FLASH version, had been working fine, no problems except FC after the transaction. No biggie.

Upgraded to 4.0.3 AOKP last night, starting getting the infamous Secure Element error. restored my TiBackup copy, no luck except the error chaneged to the Insufficient Priviledges error. Wierd.

Restored my nandroid of my working 4.0.2 with Wallet, get secure element. Tried with my TiBackup and still got the secure element.

Reinstalled the AOKP zip for CWM and TiBackup and get the insufficient Priviledges again.

Stuck and lost $25 bucks trying to upgrade. Wish I hadnt now I dont have my google wallet anymore. Everything was done with wipes in between

EDIT: I did have to delete the wallet.apk in the sys/app folder as it was already installed with AOKP...maybe thats the reason it botched?
[Samsung Galaxy Nexus] :
When you installed AOKP , did you open Google Wallet? Or did you just install ROM, and started seeing Secure element error?
[Samsung Galaxy Nexus] mohitrocks:
First things first, thanks so much for going through with this, and sorry for your loss :(

Second, did you use the apk already installed with the rom? Or did you remove the apk from system and then re-install the titanium backup?
[Samsung Galaxy Nexus] :
I'm hoping someone can chime in.

I do not have the secure element issue, and I never did install the zip version. I once installed the .apk on a rooted stock 4.0.2 rom. It worked great

Lately, I've been trying 4.0.3 roms (AOKP), and I notice it was pre-installed. I personally don't want anything to do with Wallet so I've just been deleting the apk from system/app as soon as the rom boots.

My question is, can my secure element get locked out somehow even if I don't launch the app?
[Samsung Galaxy Nexus] drPheta:
No, as long as you're not accessing the secure element (currently, I only know of GW doing this) you should be fine. Especially since you're deleting the GW apk off the bat.
[Samsung Galaxy Nexus] mohitrocks:
Are you sure? So basically, if I make a nandroid backup + titanium backup on a 4.0.2 rom running wallet, then install a new rom, delete wallet before I even open it, and then restore back to the old nandroid with wallet installed, I wont get the Secure Element issue?

Secondly, if I make a nandroid backup + titanium backup on a 4.0.2 rom running wallet, then install a new rom, delete wallet before I even open it, and then restore back to the backup I made via titanium backup, will I get locked out?

EDIT: If someone is willing to, could you make a nandroid + titanium backup of rom with wallet installed, then wipe data + cache, then install a 4.0.3 rom (preferably aokp), remove the app via root explorer and finally restore the app + data via titanium backup and see what happens? Also, can someone make a nandroid + titanium backup with wallet, then install a new rom, delete the apk via root explorer (/system/app) and finally restore to the nandroid backup and see what happens?

Thanks.
[Samsung Galaxy Nexus] :
I think he's right in my situation. For someone who installs ROMS with Wallet pre-installed who don't have a single intention on even opening Wallet.

I really enjoy AOKP, but after all this secure element stuff, I'm done with wallet. I'll let you guys do the testing, I just wanted to make sure I can't get locked out if I don't open the app.
[Samsung Galaxy Nexus] drPheta:
No, I'm referring to this scenario....

As for Nandroids and Titanium Backups being restored on new ROMs, YMMV. I have no idea what to do with GW when upgrading to a 4.0.3 ROM. The leaked/modded apk was intended fro 4.0.2, still people ended up with secure element errors on 4.0.2. So, I'm really trying to figure this one out like everyone else.
[Samsung Galaxy Nexus] mohitrocks:
I'll probably end up getting 4.0.3 since the battery drain is fixed in Francisco Franco's Kernel (available here) and when I do, I'll delete the Wallet APK right away and either I'll restore it via titanium backup or restore the nandroid and see what happens.
[Samsung Galaxy Nexus] chantheman525:
issue with apk

so i have an unrooted lte galaxy nexus 4.0.2. I downloaded the apk and installed as instructions said. I got signed up and received the $10 on my google prepaid card which was great. However when i went to use GW at my local gas station to buy a drink, GW did not work correctly. I held it to the NFC receiver and the payment on my phone said "sent". but the credit card receiver then declined my card.. I tried it again and the same thing happened. I ended up having to pay with cash. Also, after exiting the app and opening it again GW never came up and my phone said "google wallet is not responding. Do you want to close?" The same thing happened when I tried to open the settings on my phone. Neither apps would open until i restarted my phone. Do any of you know what is going on, or if I made a mistake with the apk? I really appreciate your help!
[Samsung Galaxy Nexus] mellen_hed:
Here is my scenario for those interested.

Got my VZW GNex launch day.

On Dec 19 I apparently initialized GW for the first time (this is the first confirmation email i still have) - cannot remember if i flashed zip, sideloaded, or if I just used the one that came installed with AOKP build 7 (probably the baked-in, but can't remember)

I have flashed every update to AOKP since then (5 or 6) with wipes of data, cache, and dalvik between, plus probably a couple other roms, too.

I have initialized GW on at least 2 other dates (as per emails), and topped up once, too, for $50.

I have never backed up or restored anything related to GW.

The only things I have kept the same are:

1) Only initializing in the AOKP ROM

2) Account PIN for signing in to GW.

Hope this helps somebody, as I would think I should have been locked out already.
[Samsung Galaxy Nexus] mohitrocks:
Thanks so much for the info. To find the true culprit of this issue, could people post exactly what steps they took to either get the issue or what they did to not get the issue after switching roms?

Thanks,

Mosh

---------- Post added at 03:40 AM ---------- Previous post was at 03:05 AM ----------

To confirm, when you switched to AOKP, you deleted the wallet apk right of the bat and then restored your backup of wallet? Thanks, and please answer ASAP.

EDIT2: Okay guys I've created a Google Doc for this issue which can be found here: https://docs.google.com/spreadsheet...FZ3b21aVnluX1RwLVc4QV8xc0dTSEE&hl=en_US#gid=0

Please tell me your scenario so I can add it to the doc. Also, if you guys would like to add additional info, please pm me your email

@lukegb This is the second time I'm requesting this: Please let users be aware of the Secure Element Issue and put it in the OP. Also, can you include a link to my doc in the OP so that more users can submit their errors? Thanks.
[Samsung Galaxy Nexus] drPheta:
Three Gnexii:

First: Stock Rooted 4.0.2. Installed APK. No issue. Returned/exchanged due to busted external speaker (unrelated to GW).

Second: Android Revolution HD 4.0.2. Installed APK. No issue. Have not tried to use GW, but have $10 card activated.

Third: Stock Rooted 4.0.2. Installed APK. No issue. Wiped/Installed Android Revolution HD 4.0.2. Restored using Titanium Backup. No issue. Have not tried to use GW, but have $10 card activated. Will likely test it tomorrow or Saturday.
[Samsung Galaxy Nexus] mohitrocks:
Thanks so much! Since you have 3, do you mind flashing AOKP on one of them, removing the wallet.apk without ever opening it, restoring a titanium backup of the apk and seeing what happens? Or can you make a nandroid of Android Revolution HD, wipe data + cache, install AOKP, then go back to the nandroid backup and see if wallet works? (I guess it should be the same as flashing ARHD again and then restoring to nandroid)

EDIT: I'm still waiting for beng2ks reply (see post http://xdaforums.com/showpost.php?p=20809721&postcount=1036 ) because I think he already went from 4.0.2 to 4.0.3, restored apk and it didn't work. Just confirming with him if he removed the apk before ever using it, already pm'ed him. So if you are uncomfortable with trying it, it's fine :) Also, beng2ks if you are reading this, did you try it on the built in apk for AOKP? Or did you remove it without ever using it, then restore a titanium backup?
[Samsung Galaxy Nexus] beng2k:
No I did not remove the APK intially as I had seen that the OP had no issues switching roms, its acutally the only reason I switched. I did just launch Wallet once AOKP was installed from 4.0.2 to 4.0.3. Didnt think to restore or anything as OP said there were no issues. Kinda pissed now as I really enjoyed the Wallet features.

I did try wiping several times and reinstalling both my nandroid backup and my AOKP zip file. I also tried restoring my titanium backup to both my nandroid and AOKP with no success either. Im pretty much down to trying fastboot with ICL53F yakju build to get a stock level 4.0.2 and try again.

I am gettin mixed errors depending on rom i use and whether or not i restore my titanium backup. I have had both Secure element not responding and insufficient priviledges r/t release keys error. I did try "reverting" from zip to APK with no success either.

How do the original zip file differ? I hope someone can figure this out as this was one of the major features I was planning on using. I dont feel like ebaying it and buying another one off contract at 599.99CAD
[Samsung Galaxy Nexus] AndyCr15:
This is what I've got the last two times I've tried. Last week it worked though... so it's a little confusing and annoying.
[Samsung Galaxy Nexus] beng2k:
Opened it first and thats when it gave my the Secure Element no responding.

When Id flash the titanium backup, I believe thats when it switched to Insufficient Privildeges.
[Samsung Galaxy Nexus] mohitrocks:
Thanks so much for your reply! I'll add it to the document asap

Edit: I know I've asked this before, but if anyone has went from a 4.0.2 rom (whether stock or custom, doesn't matter), made a titanium + nandroid backup of the rom and apk then flashed a 4.0.3 rom (e.g. AOKP), never opened the Google Wallet app, deleted it from /system/app and restored the titanium backup of the app please let me know.

As of now, I can almost confirm two things.

1.)If you go from rom x to rom y with the same OS version (e.g. 4.0.2) where you have wallet installed on rom x as well as a nandroid + titanium backup of rom x to rom y which never had google wallet and then you restore back to rom x, you shouldn't get an error.

2.)If you are on one rom with Google Wallet installed, you switch to another rom with Wallet pre-installed and you open the app from within the rom, you will probably get the Secure Element issue, if not another issue. This will probably also occur if you go from one ROM with Wallet installed to another ROM which doesn't have Wallet installed but you install it via the zip or apk method. One potential method of bypassing this issue is to make a backup via Titanium backup of the app + data, and restoring it after flashing the new rom. Note: If there is wallet pre-installed into the ROM, delete it by going to /system/app via root explorer and clicking delete (Note you might have to click mount as R/W at the top right). After you've ensured that Wallet is not on your phone, restore the app + data via Titanium backup. This has not been tested by me as of yet, and if anyone is willing to risk their Google Wallet functionality to try this out, please pm me. Note: Probably will not work if you already had the Secure Element issue from before

The following remains unknown:

1.) If you go from rom x to rom y with different OS versions (e.g. 4.0.2 to 4.0.3), with the same circumstances as above, will there be an error? (I would say most likely not, simply because the OS version shouldn't play a huge factor in this scenario)

2.) If you go from rom x with wallet installed, to rom y and you restore the titanium backup (of app + data), will there be an error? (Note: if you go from Android Revolution HD to AOKP which already has wallet installed, do the following:

download an app such as root explorer, navigate to /system/app and remove the wallet apk before restoring the titanium backup. Then restore the backup and see if there is an error Make sure you do not open the pre-existing wallet app in the rom.)