Does anyone know if its possible to reset google wallet without being able to sign into the app?
I accidently flashed another rom without resetting GW
But I restored my previous rom where it was working before I tried to actually set up GW on the new rom
Im not getting any secure element errors the app just stays on activating account forever..
If anyone knows a way to safely clear out all the data so I can try it out on a new rom id appreciate it..
lilwing said:
Does anyone know if its possible to reset google wallet without being able to sign into the app?
I accidently flashed another rom without resetting GW
But I restored my previous rom where it was working before I tried to actually set up GW on the new rom
Im not getting any secure element errors the app just stays on activating account forever..
If anyone knows a way to safely clear out all the data so I can try it out on a new rom id appreciate it..
Click to expand...
Click to collapse
Well your kind of lucky right now but who knows what will happen when account activates. Dude i just backed a rom up on my gnex (didnt erase no data or nothing) and when i went into wallet as soon as i got in before even activating accnt i got the secure element error. If u get the " secure element not responding " error u need a new device to use wallet or a new motherboard. when u go into the app and hit menu on your phone then go to settings. See if u can reset there
Edit...and also resetting app data will not do anything it has to be reset from inside app
What would be proper procedure before you flash a new rom at all??
From what I understand first you remove all the cards in your Google Wallet than in Settings -> Reset wallet??
Would it be smart to clear cache (etc) through the settings -> Applications??
What I did was Delete The Google Wallet APK from /system/app folder then reinstalled it. Worked fine after that. Good Luck..
DSlick said:
What I did was Delete The Google Wallet APK from /system/app folder then reinstalled it. Worked fine after that. Good Luck..
Click to expand...
Click to collapse
Yes but u got lucky you are playing with fire the way your supposed to do it is go into google wallet then hit menu on your phone. Go to settings then scroll down to reset google wallet. This will take down all your cards and every other piece of data in the money network. Thn after its done u will see the app is totally reset like how it looks when u first downloaded it. Now is when u can flash a new rom
I have been searching and i havent found anything
so i have the ATT s3, i rooted before and got wallet working. Even purchased many thing with it. Today I decide to unroot my phone to take in the OTA update from ATT. i did that and then i rooted again. I was trying to see if all my app works, so without thinking i open up wallet. It gave me some errors. so i went and reflash wallet to the newest file. And now the wallet icon is grayed, and it has a sd card mini logo next to it. when i click on it, it said " application not installed." I installed it many times over and still the same. i am not sure what to do.. i have been looking, seems like no one is having this problem.
please help
i got the icon back working but still say "insufficient secure element privileges for this system image (release-keys)"
any way around it?
darkmist2k1 said:
I have been searching and i havent found anything
i got the icon back working but still say "insufficient secure element privileges for this system image (release-keys)"
any way around it?
Click to expand...
Click to collapse
You need to install the nfc libraries, there is a link somewhere, search for wallet threads.
OP - YMMV. You can wipe data/system/cache/dalvik and then install your rom and everything should be fine. I did the same thing before and hunted around and it seems that not resetting wallet does not lead to secure element breaking. Again YMMV.
i just fixed it. ( for the insufficient error)
so i flashed to stock, ota updated, then restore to factory.
Root the device, installed super user, updated super user
installed root manager
change you build.prop
flash newest hacked google wallet
activate google wallet account
change you build.prop back to factory.. all my cards are there except for the prepaid.
i dont if it works.. so i will update if it would.
http://forum.xda-developers.com/showthread.php?t=1872161
nullredvector said:
You need to install the nfc libraries, there is a link somewhere, search for wallet threads.
OP - YMMV. You can wipe data/system/cache/dalvik and then install your rom and everything should be fine. I did the same thing before and hunted around and it seems that not resetting wallet does not lead to secure element breaking. Again YMMV.
Click to expand...
Click to collapse
yea thats exactly what i did... the information is there..
so this is for those who just got updated ota on the rooted stock rom, and got the error on the google wallet( if you forgot to reset it)
ingenious247 said:
http://forum.xda-developers.com/showthread.php?t=1872161
Click to expand...
Click to collapse
search those words, and never that thread came up.. weird.. sighhh im fail! sorry
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?
Ok, so I went to my Play Store and saw that Google Wallet has an update so I proceed to update it. However after it updates and installs a dialogue box pops up saying Google Wallet is requesting Superuser Permissions...Now I'm kinda concerned as to why it would request such a thing...
Sent from my Galaxy Nexus using XDA
I updtated GW too...
but didn't get the SU permissions request. I am 100% stock though and not yet unlocked the boot loader
Guy that's weird. Maybe a reboot will fix but also please remember when doing anything like rooting unlocking bootloader,backups data wipes anything! Go into the app hit settings and reset. Just trying to help out because once secure element notification pops up your screwed for that device and google wallet. I had it working great and backed up my rom. When I rebooted I got the secure element not responding window and have been locked out ever since. I only thought this happened when wiping data but obviously not. So be careful and when doing anything just reset app from inside google wallet settings and u will be OK......and yes I tryed everything to get it to work. I reset google framework uninstalled app wiped data, new rom, dead stock not rooted and locked bootloader.... nada don't let it happen guys
sarni84 said:
Guy that's weird. Maybe a reboot will fix but also please remember when doing anything like rooting unlocking bootloader,backups data wipes anything! Go into the app hit settings and reset. Just trying to help out because once secure element notification pops up your screwed for that device and google wallet. I had it working great and backed up my rom. When I rebooted I got the secure element not responding window and have been locked out ever since. I only thought this happened when wiping data but obviously not. So be careful and when doing anything just reset app from inside google wallet settings and u will be OK......and yes I tryed everything to get it to work. I reset google framework uninstalled app wiped data, new rom, dead stock not rooted and locked bootloader.... nada don't let it happen guys
Click to expand...
Click to collapse
Thanks and the moment I got the notification, after it updated, I reset Google Wallet from within the app itself I hope everything will be ok and that I won't have to come across the Secure Element bug.
Sent from my Galaxy Nexus using XDA
Please continue this in the other Google Wallet thread
http://forum.xda-developers.com/showthread.php?t=1657935
Thanks
FNM
Today Google Play Store was giving me the message of app incompatible with device. I changed to DPI to the Nexus Setting (I think its 320 or something) and as soon as I hit reboot I realized the mistake I have just committed. I have a pin unlock and now the screen DPI is so off that I cannot enter my pin and get my device unlocked. I've looked at bypassing apps on the play store but I cant install onto my device since the google play store wont let me install many apps since they are incompatible. Is there anything else I can do to save me the trouble of wiping my phone?
bxboogie said:
Today Google Play Store was giving me the message of app incompatible with device. I changed to DPI to the Nexus Setting (I think its 320 or something) and as soon as I hit reboot I realized the mistake I have just committed. I have a pin unlock and now the screen DPI is so off that I cannot enter my pin and get my device unlocked. I've looked at bypassing apps on the play store but I cant install onto my device since the google play store wont let me install many apps since they are incompatible. Is there anything else I can do to save me the trouble of wiping my phone?
Click to expand...
Click to collapse
why dont you just flash over the rom again and it will load up stock dpi settings and preserve your data and settings. The most you will have is apps back that you may have deleted... It will refash your build.prop
playya said:
why dont you just flash over the rom again and it will load up stock dpi settings and preserve your data and settings. The most you will have is apps back that you may have deleted... It will refash your build.prop
Click to expand...
Click to collapse
I never loaded a ROM without wiping before but this did the trick for me. I had to re-install GAPPS also but thats not a major problem. Thanks for the help. I didnt think it was gonna be this easy.
bxboogie said:
I never loaded a ROM without wiping before but this did the trick for me. I had to re-install GAPPS also but thats not a major problem. Thanks for the help. I didnt think it was gonna be this easy.
Click to expand...
Click to collapse
Glad it worked
Please see the 'generic' Note 3 CF-Auto-Root thread here:
http://forum.xda-developers.com/showthread.php?t=2466423
This actual thread will become a proper CF-Auto-Root thread once I'm finished tying up all the lose ends. Please comment in this thread, but read the instructions and grab the file from the thread linked above.
--- reserved #1 ---
--- reserved #2 ---
Thanks
Has anyone else been getting RPC:S-5:AEC-0 errors?
I tired wiping both caches and data from app manager. nothing
Tried wiping cache from recovery. nothing.
tried wiping cache and factory restore. nothing.
After I rooted apps were installing fine but then it just stopped.
Any suggestions? Im gonna try to see if I can find an odin file of it stock.
EDIT: So I used a odin stock image. Still getting error. Any suggestions?
Do tmobile employees check to see if it has been flashed?
Gonna try to go back to store and see if can get it replaced with another. But cant till later. This sucks....
FIX looks like it was on googles servers. Back to normal but this is on stock after I odin, Ill wait on the root to see if others are still getting problems.
transitoyspace said:
Has anyone else been getting RPC:S-5:AEC-0 errors?
Click to expand...
Click to collapse
I was getting the above error too even after performing a device reset. I reflashed the root a second time and it is working. The only difference is I enabled USB debugging in the Developer options the second time, not sure if that really made a difference though.
transitoyspace said:
Has anyone else been getting RPC:S-5:AEC-0 errors?
I tired wiping both caches and data from app manager. nothing
Tried wiping cache from recovery. nothing.
tried wiping cache and factory restore. nothing.
After I rooted apps were installing fine but then it just stopped.
Any suggestions? Im gonna try to see if I can find an odin file of it stock.
EDIT: So I used a odin stock image. Still getting error. Any suggestions?
Do tmobile employees check to see if it has been flashed?
Gonna try to go back to store and see if can get it replaced with another. But cant till later. This sucks....
Click to expand...
Click to collapse
Me too I p m chain fire like 15 min ago. It could be a Google issue
Sent from my SM-N900T using Tapatalk 4
transitoyspace said:
Has anyone else been getting RPC:S-5:AEC-0 errors?
I tired wiping both caches and data from app manager. nothing
Tried wiping cache from recovery. nothing.
tried wiping cache and factory restore. nothing.
After I rooted apps were installing fine but then it just stopped.
Any suggestions? Im gonna try to see if I can find an odin file of it stock.
EDIT: So I used a odin stock image. Still getting error. Any suggestions?
Do tmobile employees check to see if it has been flashed?
Gonna try to go back to store and see if can get it replaced with another. But cant till later. This sucks....
Click to expand...
Click to collapse
I have been getting it (wasn't up until I rooted!). Was driving me insane.............. Tried all the tricks I found on the internet with absolutely zero luck.... until I came across this dude's video: http://www.youtube.com/watch?v=uv8d-nl04qI. It worked but I followed it to the t! So delete your Google account. Force close and erase Data for the 3 services he's mentioning. Turn it off. Turn it back on. Go to Play, it asks for your Google Account; add it.... Enjoy!
XooLoo said:
I have been getting it (wasn't up until I rooted!). Was driving me insane.............. Tried all the tricks I found on the internet with absolutely zero luck.... until I came across this dude's video: http://www.youtube.com/watch?v=uv8d-nl04qI. It worked but I followed it to the t! So delete your Google account. Force close and erase Data for the 3 services he's mentioning. Turn it off. Turn it back on. Go to Play, it asks for your Google Account; add it.... Enjoy!
Click to expand...
Click to collapse
Thanks I will give it a try
Edit: it worked Thanks a million
Sent from my SM-N900T using Tapatalk 4
Ah wow, I was getting these errors too. Thought it was unrelated and a server side issue (still might be, account specific?)
I'm writing this without reading the suggestions above but, what eventually worked for me (after removing accounts, factory reset, clearing play store data & play framework whether necessary or not)..
Went to Google dashboard (all on PC), made sure device was there, went to play.google.com (computer)-- it errored and froze, logged out, back in, worked eventually, viewed my installed apps (took like 5 minutes to load), started installing apps from there. Once that was working, it worked on my device.
The curious part was, initially, when I'd search for ANY app on play.google.com, it would show no results. Opening in incognito (not signed in), it worked fine.
XooLoo said:
I have been getting it (wasn't up until I rooted!). Was driving me insane.............. Tried all the tricks I found on the internet with absolutely zero luck.... until I came across this dude's video: http://www.youtube.com/watch?v=uv8d-nl04qI. It worked but I followed it to the t! So delete your Google account. Force close and erase Data for the 3 services he's mentioning. Turn it off. Turn it back on. Go to Play, it asks for your Google Account; add it.... Enjoy!
Click to expand...
Click to collapse
Yes, had the same problem on my SM-N900T, not on either of the other two [N900/A], it took creating a new google account and also clearing the cache for google services framework, google play and uninstalling the play store update. I had to do this a couple of times, seemed to work better for me without a reboot, but this is the right path for fixing this problem.
Hope this helps,
Bob
Can someone with a rooted note 3 confirm this doesn't t change Knox to 0x1 ?
bob_beringer said:
Yes, had the same problem on my SM-N900T, not on either of the other two [N900/A], it took creating a new google account and also clearing the cache for google services framework, google play and uninstalling the play store update. I had to do this a couple of times, seemed to work better for me without a reboot, but this is the right path for fixing this problem.
Hope this helps,
Bob
Click to expand...
Click to collapse
I just force stopped play store and cleared data and it worked after that.
unlockingsky said:
Can someone with a rooted note 3 confirm this doesn't t change Knox to 0x1 ?
Click to expand...
Click to collapse
How do we se our Knox status and also....does it do anything to the phone when its like that? Should we wait for a method of root that doesnt trip knox
bdorr1105 said:
How do we se our Knox status and also....
Click to expand...
Click to collapse
go to download mode .
unlockingsky said:
go to download mode .
Click to expand...
Click to collapse
If you have both Kies and Android SDK installed, go to command prompt (cmd) and go to where adb.exe is, and type:
adb reboot download
---------- Post added at 11:43 PM ---------- Previous post was at 11:43 PM ----------
unlockingsky said:
Can someone with a rooted note 3 confirm this doesn't t change Knox to 0x1 ?
Click to expand...
Click to collapse
Mine is 0x1
unlockingsky said:
Can someone with a rooted note 3 confirm this doesn't t change Knox to 0x1 ?
Click to expand...
Click to collapse
it changes it. what does knox do for the normal user? i
transitoyspace said:
it changes it. what does knox do for the normal user? i
Click to expand...
Click to collapse
None, basically it detects flash so that they can void your warranty.
zoth said:
None, basically it detects flash so that they can void your warranty.
Click to expand...
Click to collapse
it voids your samsung warranty to be exact. if you take it back to tmobile with tmobile warranty, they will still fix/replace hardware issues.
About to root for the simple fact I can not stand the headphones auto adjusting. I need it louder then normal and tired of playing music at maxed settings just to hear music and then a few songs later it acts like its supposed to. (work in a factory)
Anywho: Does this method still give you the option of having auto updates from Tmobile for bug fixes and stuff or do we need to manually keep an eye open for updates?
(coming from Rooted Stock Note 2 thats why im asking. Not big on romming)
Thank you