Like the title says, I rooted and updated to a custom rom (Liquidsmooth) but I noticed that I lost tap and pay functionality despite being on Android KK. Any thoughts on what could be causing it? I've done a few searches but a lot of what I've found seems to point to that it should be working.
Thanks in advance
Probably a bad secure element which means it will not work anymore. Have you tried to restore your backup if you did backup your original rom? The recommended procedure before flashing roms was to wipe data on the wallet app to avoid that secure element issue...
Sent from my SPH-L900 using Tapatalk
jocarog said:
Probably a bad secure element which means it will not work anymore. Have you tried to restore your backup if you did backup your original rom? The recommended procedure before flashing roms was to wipe data on the wallet app to avoid that secure element issue...
Sent from my SPH-L900 using Tapatalk
Click to expand...
Click to collapse
Thank you for giving me a direction to look for more troubleshooting information. I will try restoring the backup and clearing the data. Though I'm not sure if it'll fix it since according to what I've read, ever since the update to Kitkat only Tap and Pay support, secure element is no longer checked. Do you know if Google Wallet checks for root or other possible "security breaches"?
ringoshu said:
Thank you for giving me a direction to look for more troubleshooting information. I will try restoring the backup and clearing the data. Though I'm not sure if it'll fix it since according to what I've read, ever since the update to Kitkat only Tap and Pay support, secure element is no longer checked. Do you know if Google Wallet checks for root or other possible "security breaches"?
Click to expand...
Click to collapse
I don't think it checks for root anymore, not sure... but I read somewhere else that on this device the secure element still being checked... have you tried any other apps that use tap and pay? Like PayPal?
Sent from my SPH-L900 using Tapatalk
The source for our NFC chip that would enable the secure element is missing from AOSP. The manufacture provided sources to cyanogenmod (it's somewhere in jira) which has helped other devices. That was months ago but it's still disabled for us. Not even sure if it was tested to work.
ProperNoun said:
The source for our NFC chip that would enable the secure element is missing from AOSP. The manufacture provided sources to cyanogenmod (it's somewhere in jira) which has helped other devices. That was months ago but it's still disabled for us. Not even sure if it was tested to work.
Click to expand...
Click to collapse
Wow, that makes a lot of sense. Guess it's also the price to pay of having an "older" device. This definitely my last non Google Android phone. Thanks for the reply!
Related
I've been fretting about this for far too long and I want my question laid to rest for once and for all.
I am running stock 4.0.2 rooted and boot loader unlocked. I want to install the google wallet apk without worrying about it messing up and giving me the secure element error. Can someone please aid a fellow ever-worrying flasher?
And yes, I have a backup to rely on.
Sent from my Galaxy Nexus using XDA App
There's no guarantees. Essentially to be absolutely safe you need to wait until Google releases something official.
The error occurs after installing another rom with a wipe or after a factory reset. The theory is to make sure to press reset within Google Wallet so that it deletes the info off the Secure Element's memory. This is still just a theory, no guarantee..
You should watch the main thread for the most up to date info http://forum.xda-developers.com/showthread.php?t=1365360
To add to Royal2000H:
Even if you reset Google Wallet from within the app, it will still re-initialise the secure element. There's an ADB shell command that will reset it properly.
David Horn said:
To add to Royal2000H:
Even if you reset Google Wallet from within the app, it will still re-initialise the secure element. There's an ADB shell command that will reset it properly.
Click to expand...
Click to collapse
I know how to use ADB. Can you link the command?
_AI_ said:
I know how to use ADB. Can you link the command?
Click to expand...
Click to collapse
You need to download and install the Android SDK (software development kit). The ADB (Android device bridge) drivers and software are included with it. Sorry I don't have a link handy for you, maybe in the morning if someone else hasn't posted one.
Sent from my X10i using xda premium
He said he does know how to use ADB.
The command is in the thread I linked.
Interesting...I didn't even know there was a problem with google wallet and I installed it on my 4.03 AOKP milestone 1 nova launcher LTE nexus without any problems, just had google pay for my mcdonalds lunch yesterday
Screwedupsmitty said:
Interesting...I didn't even know there was a problem with google wallet and I installed it on my 4.03 AOKP milestone 1 nova launcher LTE nexus without any problems, just had google pay for my mcdonalds lunch yesterday
Click to expand...
Click to collapse
perhaps make a backup then of your working ROM. cause i believe if you wipe or switch ROMs something happens that resets the NFC hardware and you may lose ability to use it again. i'm not totally sure of the details exactly though.
I have another experience to add to this thread.
Today my phone got stuck on the boot animation so I reloaded my current 4.03 ROM. When the device booted up after flashing the gapps.zip I tried using my NFC for a tag but it wouldn't work. Additionally, trying to access the "more..." settings menu froze the settings program.
At this point I tried multiple ROMS etc and had no luck getting my NFC to work until I restored my nandroid backup from long before wallet, the first day I got the phone.
I then flashed back to my 4.03 ROM and everything works fine until the Gapps.zip adds wallet which breaks the NFC again. Removing wallet from the .zip makes everything ok but there is apparently no way for me to get wallet working again. I tried the ADB command and everything, but whenever I reinstall wallet wallet itself just opens to a black screen that is frozen and it destroys my NFC(plus the settings freeze)
Is there anything else I can try? Is my secure element bricked forever(meaning I should exchange)? Or should I hold on until google releases an official .apk?
Thanks for posing the question
I actually, using a link from here, installed Google Wallet and It is working just fine for me but my phone is stock rom and unrooted (LTE Edition), So I'll be paying close attention to this thread because I might decide to root this phone in the future.
Like most of you I am a flashing addict. I'm always looking for a ROM that is a small step ahead of the rest. This Google Wallet Secure Element Hoopla going on with the Gnex right now is concerning. I don't use Wallet yet. There just aren't enough places yet that I can really use it but one day I might want to give it a try. For this reason i'm concerned about continuing to flashing ROMs as I normally would.
When I first got the phone, I loaded the Wallet apk on the stock image and launched it to see how it worked. To this date I have never used it to purchase anything. I flashed a few ROMs after that and I did launch the app once to see if the version that was built into that specific ROM still worked. I flashed a few more ROMs since and it sits unconfigured currently (I get the Welcome to Google Wallet screen that has the "Get Started" button).
I"m hoping someone can educate on the latest that we know on why this error occurs and if I should be concerned. What do I need to do to keep from bricking my Google Wallet?
1. Uninstall the app right after flashing?
2. Remove the app from the ROM prior to flashing?
3. Freeze the app with Titanium?
4. Hit the Get Started button, configure it then run through the deactivation process that I have read about in one of the forum posts.
5. Turn off NFC immediately after flash
6. Don't worry about it since I don't ever launch or use Google Wallet?
7. Any other options that I haven't thought of?
From what I can tell you are supposed to nandroid and probably backup the app with titanium while it is in its working state. Then open up wallet and reset wallet from within the app (not clear data from app manager). Then uninstall wallet and flash whatever rom you want. Keep your backup just in case. In your position I wouldn't sign into wallet until they understand more what is going on. It may or may not already have you locked out of the secure element when you sign in again, and a fix might come along in the mean time and save the secure element.
axion68 said:
From what I can tell you are supposed to nandroid and probably backup the app with titanium while it is in its working state. Then open up wallet and reset wallet from within the app (not clear data from app manager). Then uninstall wallet and flash whatever rom you want. Keep your backup just in case. In your position I wouldn't sign into wallet until they understand more what is going on. It may or may not already have you locked out of the secure element when you sign in again, and a fix might come along in the mean time and save the secure element.
Click to expand...
Click to collapse
What good does doing a nandroid and titanium backup of the app? Its not like the backup will help if you get the secure element error from what I hear.
I'm confused about the next part. You said I need to launch wallet, sign into it then reset it. Then in your next statement you say to not sign into google wallet. The two things seem to be contradictory. Did I misunderstand? How I know if I am already broke or not? At what point do you receive the secure element error? I don't suppose there is a way to know for sure without risking causing the error by launching wallet?
I don't have a problem not using wallet until this is resolved. I just want to make sure that not using it is sufficient to protect it from damage.
Come on Devs. Someone has to have some updated information on this issue and how it can be prevented?
The question is actually simpler than I made it.
1. If you don't launch Google Wallet after flashing a new ROM is there a possibility for damage or do you need to launch it then run the reset procedure?
Anyone? Is the Secure Element issue not a problem anymore. I've been sitting in this holding pattern for weeks. I really want to start flashing again. Any update?
Same concerns here, I've actually installed and activated Google Wallet. Haven't actually 'used it yet' but from what I can tell all is good. This looming issues is all that's preventing me from jumping back into the custom rom scene I enjoyed so much while having the OG Droid. I hope some more info comes of this. Really would like to try some custom roms to try and solve these random reboots... Getting old... and more frequent.
I've successfully changed roms after using google wallet. I was originally on Android Revolution when I first used it via the APK method. To update to a new rom you need to login and reset google wallet from inside the app. (from what I understand this erases all traces from the secure element)(There is also an adb command to release secure element or something but I didn't use it. That's all I did reset from inside google wallet then didn't login again until I was on a new rom. This has worked for many and I haven't read about anyone bricking the element doing it this way but I'm still not responsible if damage occurs. All this information is in the thread for installing google wallet if you would have used the search function.
420SYN said:
I've successfully changed roms after using google wallet. I was originally on Android Revolution when I first used it via the APK method. To update to a new rom you need to login and reset google wallet from inside the app. (from what I understand this erases all traces from the secure element)(There is also an adb command to release secure element or something but I didn't use it. That's all I did reset from inside google wallet then didn't login again until I was on a new rom. This has worked for many and I haven't read about anyone bricking the element doing it this way but I'm still not responsible if damage occurs. All this information is in the thread for installing google wallet if you would have used the search function.
Click to expand...
Click to collapse
This is helpful info for people that use Google Wallet but what about us that don't ever launch it. If we flash a new ROM Google Wallet is usually installed. If we don't launch and configure it do we risk any damange by flashing a new ROM or do we have to login, configure it then do the reset everytime we flash a ROM regardless?
Well the title is pretty self explanatory.
I forgot to reset google wallet before wiping my device from ICS 4.0.4 where it was working 100%
Wipe, flashed a JB based ROM with some mods (Made by ...Awesome...)
let Google Wallet update, been stuck at initializing
I tried force-restoring my Titanium Backup version
I tried force closing, wiping the app's data
Rebooting causes the wallet to open automatically and reinitialize forever.
What else can I start doing to get this to work?
Thanks!
Did you do a nandroid backup before flashing JB? If so, restore that, reset wallet, then reflash JB.
Sent from my Galaxy Nexus using Tapatalk 2
The same thing happened to me. I tried to reset wallet before flashing a new rom, but it hung at the 2nd to last progress step. After rebooting, it acted like it reset, so I flashed a new rom. Since then, it hasn't worked. I restored a Nandroid and tried resetting again, only to have it hang again. Not much I can do since I'm on Verizon and it's not supported. I've just given up at this point. It must be something with the secure element. I'm just glad I only had a dollar left on it lol.
efrant said:
Did you do a nandroid backup before flashing JB? If so, restore that, reset wallet, then reflash JB.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I'll give it a shot.. :/
mwalt2 said:
The same thing happened to me. I tried to reset wallet before flashing a new rom, but it hung at the 2nd to last progress step. After rebooting, it acted like it reset, so I flashed a new rom. Since then, it hasn't worked. I restored a Nandroid and tried resetting again, only to have it hang again. Not much I can do since I'm on Verizon and it's not supported. I've just given up at this point. It must be something with the secure element. I'm just glad I only had a dollar left on it lol.
Click to expand...
Click to collapse
I really hope the secure element didn't get screwed.
UPDATE:
Nandroid back to ICS Base with working wallet installation
Google wallet fired right up, but had to re-add my Pre-paid card.
mwalt2 said:
The same thing happened to me. I tried to reset wallet before flashing a new rom, but it hung at the 2nd to last progress step. After rebooting, it acted like it reset, so I flashed a new rom. Since then, it hasn't worked. I restored a Nandroid and tried resetting again, only to have it hang again. Not much I can do since I'm on Verizon and it's not supported. I've just given up at this point. It must be something with the secure element. I'm just glad I only had a dollar left on it lol.
Click to expand...
Click to collapse
Exact same thing happened to me when I reset the app. I now get force closes, and in error report it says secure element, so like you I just gave up on it.
Sent from my Galaxy Nexus using xda premium
kyoteqwik said:
Exact same thing happened to me when I reset the app. I now get force closes, and in error report it says secure element, so like you I just gave up on it.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
If you get a secure element, you're pretty much SOL. I don't recall a fix ever being released by devs nor Google as it seems to be a hardware problem (you've been locked out of it). To be able to reuse GW you'll have to buy a new phone.
Unlawful said:
If you get a secure element, you're pretty much SOL. I don't recall a fix ever being released by devs nor Google as it seems to be a hardware problem (you've been locked out of it). To be able to reuse GW you'll have to buy a new phone.
Click to expand...
Click to collapse
Yeah I was scared pantless when I started having GW issues, I was afraid it would be the secure element issue
How do you check for that anyway? Where do you find the error report?
Does the Nexus have a Full Wipe Script? Always works better than wiping manually
Sent from my Dark Unicorn Resurrected v.2.5 using Tapatalk 2
...Awesome... said:
Does the Nexus have a Full Wipe Script? Always works better than wiping manually
Sent from my Dark Unicorn Resurrected v.2.5 using Tapatalk 2
Click to expand...
Click to collapse
I've noticed a wipe zip package in the Android RevolutionHD Thread, "Super Wipe Lite"...
I personally don't like these as a result of a couple bad experiences where one wiped my recovery and semi-bricked a device. I'd just wipe through recovery.
Unlawful said:
If you get a secure element, you're pretty much SOL. I don't recall a fix ever being released by devs nor Google as it seems to be a hardware problem (you've been locked out of it). To be able to reuse GW you'll have to buy a new phone.
Click to expand...
Click to collapse
Yeah, I haven't seen a secure element error in a logcat or from the wallet app, but I'm guessing mines broke. The thing that makes me mad is I was trying to reset wallet, but the app froze and would not finish (phone was still responding). This was on a stock rooted ROM as well. I guess I'll just have to stick to the RFID in my credit cards if I really feel like using a tap to pay (or my Nexus 7 in a month ).
I do wonder what it means for other apps that may eventually utilize the secure element. Is it just locked out for google wallet or all apps?
How does google wallet work in JB? I'm in Canada and want to use the market enabler with google wallet, but after installing both apk from an explorer, the wallet app doesnt show up.
Same here. Wallet works with marketaccess (better than enabler IMO) on ICS but wallet wouldn't show up on Jellybean.
nfc still only available for sprint and us cellular. at least we finally got the app.
Edited...
If youre running the hacked method to get it to work (Tmobile users)then do not update the app.
I just finished installing the new Wallet app. This isnt directly downloaded from the PlayStore. Im testing a .zip from a developer.
The new Setup is kinda wierd and im not sure if tap and pay is the same as before or if I have to choose a default card for it to work. Will report results after I make a successful transaction.
Im sure the developet will create a thread when bugs are fixed.
Please merge.
Double0EK said:
I just finished installing the new Wallet app. This isnt directly downloaded from the PlayStore. Im testing a .zip from a developer.
The new Setup is kinda wierd and im not sure if tap and pay is the same as before or if I have to choose a default card for it to work. Will report results after I make a successful transaction.
Im sure the developet will create a thread when bugs are fixed.
Click to expand...
Click to collapse
thanks for guinea-pigging this for us. I hope the new .zip version works well. I'd really like to run the most current version and have the added functionality. at present, I have the old nfc enabled version on my note 2 and the current, but non nfc enabled version on my tablet and old phone. It would be nice to be able to run the current version with NFC.
shizenyasuya said:
thanks for guinea-pigging this for us. I hope the new .zip version works well. I'd really like to run the most current version and have the added functionality. at present, I have the old nfc enabled version on my note 2 and the current, but non nfc enabled version on my tablet and old phone. It would be nice to be able to run the current version with NFC.
Click to expand...
Click to collapse
Heres what happened. I tried to make a purchase earlier this morning at 7-11 and it didnt work. From what the developer and I briefly discussed is that the modified NFC files might be the culprit. What I suggest that you can do is restore the factory NFC files and install the Wallet app directly from the PlayStore and test that way.
I dont have a copy of my factory NFC files anymore and dont want to odin back so im just waiting. As of right now im using the previous Wallet app.
Double0EK said:
Heres what happened. I tried to make a purchase earlier this morning at 7-11 and it didnt work. From what the developer and I briefly discussed is that the modified NFC files might be the culprit. What I suggest that you can do is restore the factory NFC files and install the Wallet app directly from the PlayStore and test that way.
I dont have a copy of my factory NFC files anymore and dont want to odin back so im just waiting. As of right now im using the previous Wallet app.
Click to expand...
Click to collapse
I installed the new app on my note 2 after updating the rom so i didn't have the cracked version anymore (yes i reset google wallet app first) With the updated app loaded, i looked through settings and it said tap to pay wasn't available, so after configuring the rest of my new rom (jedi master 17) I reinstalled the cracked version and (i havent tried it yet, but it loos the same as ever) nfc tap to pay should work again, just still on that oudated GW app. Fingers crossed one of the brainiacs at modaco will release an updated cracked version.
Go to the Note2 Themes & Apps Section. There is a new flashable .zip .
Few things you should do first.
1. Turn Off NFC & S-Beam.
2. Clear Google Wallet Data and Cache
3. Flash the New .zip
4. Check to see if Tap and Pay is active.
Double0EK said:
Go to the Note2 Themes & Apps Section. There is a new flashable .zip .
Few things you should do first.
1. Turn Off NFC & S-Beam.
2. Clear Google Wallet Data and Cache
3. Flash the New .zip
4. Check to see if Tap and Pay is active.
Click to expand...
Click to collapse
IT work just fine:good: but if you're a heavy S-pen user like me then i say don't install as you will lose S-pen functionality. Because your Note-2 will show as the (Nexus)
thugmafia said:
IT work just fine:good: but if you're a heavy S-pen user like me then i say don't install as you will lose S-pen functionality. Because your Note-2 will show as the (Nexus)
Click to expand...
Click to collapse
Thats only in the app. My build.prop and About Phone shows the proper name. And my S-Pen functions fine.
Double0EK said:
Thats only in the app. My build.prop and About Phone shows the proper name. And my S-Pen functions fine.
Click to expand...
Click to collapse
same here no issues with S-Pen or anything else....
got tap & play to show it's working using the new zip on stock rom- just been leery of trying it out yet...
Having a constant "Security Notice" on phone since rooting. Everything else works fine. Is there anyway I can maybe deactivate this function?
freeze in titanium backup...
Y0sHii said:
Having a constant "Security Notice" on phone since rooting. Everything else works fine. Is there anyway I can maybe deactivate this function?
Click to expand...
Click to collapse
to get rid of the security notice you will get(because the system is now rooted) simply install root explorer(or any root browser) and go to /system/app and delete securitylogagent or go into the folder and rename it adding .bkp to the end of the file name and reboot.
per
http://forum.xda-developers.com/showpost.php?p=68675715&postcount=2
I began getting this, too, after rooting my Note7. I solved it the way others suggested, with Titanium Backup by freezing the Security Log Agent. That worked for me.
SkyPhone said:
I began getting this, too, after rooting my Note7. I solved it the way others suggested, with Titanium Backup by freezing the Security Log Agent. That worked for me.
Click to expand...
Click to collapse
do you still have knox? i use samsung pay and security folder
You used the sprint method root at the N930V PHE or PH1? Not really related to thread, but just out of curiosity.
Same problem....
I'm having this same problem with my rooted note 7.
I've searched everywhere for securityagent on my note 7 and it's not there. The only way I can remove this threat found/restart device, is to remove device maintenance.
But then I lose the app done function and the advanced setting power saving mode.
I have disabled all knox and security realated apps.
But still still get the threat while device maintenance is there.
Does anyone know what the equivalent to securitylogagent is on a note 7 ????
Any help would be much appreciated, I am a noob, until 3 days ago I knew nothing, but I managed to unlock frp and root my note 7, but its been stressfull. I need help now...thanks.
Kellya86 said:
I'm having this same problem with my rooted note 7.
I've searched everywhere for securityagent on my note 7 and it's not there. The only way I can remove this threat found/restart device, is to remove device maintenance.
But then I lose the app done function and the advanced setting power saving mode.
I have disabled all knox and security realated apps.
But still still get the threat while device maintenance is there.
Does anyone know what the equivalent to securitylogagent is on a note 7 ????
Any help would be much appreciated, I am a noob, until 3 days ago I knew nothing, but I managed to unlock frp and root my note 7, but its been stressfull. I need help now...thanks.
Click to expand...
Click to collapse
You should have a package named SecurityLogAgent. Disabling this will stop the security notifications due to rooting. If you're referring to the Samsung messages regarding the recall, then you need to disable the Samsung Push service or just the notifications.
8
I'm not referring to them notifications, I have disabled Samsung push.
There is no package with the name 'securitylogagent' on my note 7.
I have researched this alot before joining and posting here. Its simply not there, no matter what I use to look for it. Just not there..
I would really like device maintenance back.. that's how iv got it disabled at the moment.
I am referring to the 'that found/restart device" warning that flags up in device maintenance.
Kellya86 said:
I'm not referring to them notifications, I have disabled Samsung push.
There is no package with the name 'securitylogagent' on my note 7.
I have researched this alot before joining and posting here. Its simply not there, no matter what I use to look for it. Just not there..
I would really like device maintenance back.. that's how iv got it disabled at the moment.
I am referring to the 'that found/restart device" warning that flags up in device maintenance.
Click to expand...
Click to collapse
Strange, there should be a folder at system/app/SecurityLogAgent
What firmware version are you on? What have you used to look for it?
I'm on 6.0.1, that I rooted on Sunday after I accidentally updated package disabler. I am a complete noob and have managed to just about get to this point without help.
I have looked for it using titanium backup, root browser and device control. It doesn't show on any...
So I have disabled a load of other things including device maintenance, com.samsung.andoid.sm.devicesecurity, and security manager service...
I was hoping one of these was the equivalent of securitylogagent.
Does this information below help?
Kellya86 said:
I'm on 6.0.1, that I rooted on Sunday after I accidentally updated package disabler. I am a complete noob and have managed to just about get to this point without help.
I have looked for it using titanium backup, root browser and device control. It doesn't show on any...
So I have disabled a load of other things including device maintenance, com.samsung.andoid.sm.devicesecurity, and security manager service...
I was hoping one of these was the equivalent of securitylogagent.
Does this information below help?
Click to expand...
Click to collapse
So by the build number I see that you are not on a Verizon firmware so the app names may be different. It appears you have UK firmware so you will have to find what the app name is for that firmware.
What I can suggest is that the next time you get the notification, long press on the icon at the left. You should be taken to the notification options for that app and you should also see an app info button on the right. you may be able to track the actual app down using this info or at least disable notifications.
Thanks for your reply.
Oh crap, I'll never find it then...
Is there a way I could post an image of my system so as some experienced members on here may look at it.??
Thanks again.