I have been working on this Google Wallet thing with no luck.......maybe I am just retarded.
I gave in an rooted my phone. I have SuperSU, ROM Toolbox Lite, Root Browser Lite, and Root Explorer installed.
Ok, so it started as unsupported.....rooted and that fixed that problem. Now, it just goes to add account. I select my email address, then it goes to an error "insufficient secure element privileges for this system image (release-keys).
I the rooted ROM. I changed the build.prop to Galaxy Nexus thing.....and I download a new APK com.google.android.apps.walletnfcrel.magn2o.1.5-r75-v6.apk and copied that to the system/apps folder.......still no luck......what am I doing wrong? Does Google just hate me? I just don't get this....can someone please suggest my best opinion......I have dug through all the posts and tried 100 different things and can't figure this out.
PLEASE HELP....
ericu571 said:
I have been working on this Google Wallet thing with no luck.......maybe I am just retarded.
I gave in an rooted my phone. I have SuperSU, ROM Toolbox Lite, Root Browser Lite, and Root Explorer installed.
Ok, so it started as unsupported.....rooted and that fixed that problem. Now, it just goes to add account. I select my email address, then it goes to an error "insufficient secure element privileges for this system image (release-keys).
I the rooted ROM. I changed the build.prop to Galaxy Nexus thing.....and I download a new APK com.google.android.apps.walletnfcrel.magn2o.1.5-r75-v6.apk and copied that to the system/apps folder.......still no luck......what am I doing wrong? Does Google just hate me? I just don't get this....can someone please suggest my best opinion......I have dug through all the posts and tried 100 different things and can't figure this out.
PLEASE HELP....
Click to expand...
Click to collapse
You missing one step:
4-boot to recovery and flash SGS3-TW-US_variants-lib&nfc-fix.zip for ics touchwiz roms or SGS3-TW-US_variants-lib_nfc-fix-jellybean_4.1-1.zip for jellybean touchwiz roms and then wallet version com.google.android.apps.walletnfcrel.modaco.1.5-r87-v15.zip
(for CM9/10, I9300, aokp, aosp roms just flash the wallet zip)
Orginal Post is here
norbarb said:
You missing one step:
4-boot to recovery and flash SGS3-TW-US_variants-lib&nfc-fix.zip for ics touchwiz roms or SGS3-TW-US_variants-lib_nfc-fix-jellybean_4.1-1.zip for jellybean touchwiz roms and then wallet version com.google.android.apps.walletnfcrel.modaco.1.5-r87-v15.zip
(for CM9/10, I9300, aokp, aosp roms just flash the wallet zip)
Orginal Post is here
Click to expand...
Click to collapse
What does that mean "Flash"......how do I do that?
Not a tech person.........psychologist
ericu571 said:
What does that mean "Flash"......how do I do that?
Not a tech person.........psychologist
Click to expand...
Click to collapse
You need to install custom recovery via Rom Manager from play store.
Here is great guide , READ READ READ
Here is video how to flash rom on Galxy S3. This is way how to flash anything else.
Here is another exelent guide
Ok, so I did everything I had to do......I got to the point of adding the card.....I added my card.
When I go online I see the Galaxy Nexus showing on my Google Wallet account.
I then went to steps 9 and 10 and I returned my settings to the old Galaxy S3 ATT settings....now my Google Wallet is saying unsupported device.
ericu571 said:
Ok, so I did everything I had to do......I got to the point of adding the card.....I added my card.
When I go online I see the Galaxy Nexus showing on my Google Wallet account.
I then went to steps 9 and 10 and I returned my settings to the old Galaxy S3 ATT settings....now my Google Wallet is saying unsupported device.
Click to expand...
Click to collapse
Google Wallet is supposed to say unsupported device if your device is unsupported. This is unavoidable. You can still use Google Wallet just fine, though.
No, I mean I cant even open the app because it has a popup that say unsupported on your device and network, I click ok, and it kicks me out.......as if I never rooted my phone and installed.
I went back to the Galaxy Nexus build.prop and it works fine when I leave that alone. But the minute I change it back to the original build.prop.....it starts the unsupported thing again and not able to open app.
ericu571 said:
I have been working on this Google Wallet thing with no luck.......maybe I am just retarded.
I gave in an rooted my phone. I have SuperSU, ROM Toolbox Lite, Root Browser Lite, and Root Explorer installed.
Ok, so it started as unsupported.....rooted and that fixed that problem. Now, it just goes to add account. I select my email address, then it goes to an error "insufficient secure element privileges for this system image (release-keys).
I the rooted ROM. I changed the build.prop to Galaxy Nexus thing.....and I download a new APK com.google.android.apps.walletnfcrel.magn2o.1.5-r75-v6.apk and copied that to the system/apps folder.......still no luck......what am I doing wrong? Does Google just hate me? I just don't get this....can someone please suggest my best opinion......I have dug through all the posts and tried 100 different things and can't figure this out.
PLEASE HELP....
Click to expand...
Click to collapse
ericu571 said:
What does that mean "Flash"......how do I do that?
Not a tech person.........psychologist
Click to expand...
Click to collapse
How does your phone make you feel when it does this?....
WickR1 said:
How does your phone make you feel when it does this?....
Click to expand...
Click to collapse
it makes me feel like taking some Xanax......lol......not funny.....lol
ericu571 said:
Ok, so I did everything I had to do......I got to the point of adding the card.....I added my card.
When I go online I see the Galaxy Nexus showing on my Google Wallet account.
I then went to steps 9 and 10 and I returned my settings to the old Galaxy S3 ATT settings....now my Google Wallet is saying unsupported device.
Click to expand...
Click to collapse
Samsung Galaxy S3 on ATT is not supporting Google wallet. That why we using diffrend one by changing build.prop to make wallet work.
Do not restore you nandroid after your wallet is working just restore your build.prop
In my google Wallet account my phone is showing as Nexus too but wallet is working.
I left wallet open, then restored my build.prop. everything has worked great. I dont even have the unsupported device notice
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
WickR1 said:
How does your phone make you feel when it does this?....
Click to expand...
Click to collapse
Lmao....
Galaxy S III I747
norbarb said:
Samsung Galaxy S3 on ATT is not supporting Google wallet. That why we using diffrend one by changing build.prop to make wallet work.
Do not restore you nandroid after your wallet is working just restore your build.prop
In my google Wallet account my phone is showing as Nexus too but wallet is working.
Click to expand...
Click to collapse
That is the issue...all I did was go back into build.prop and changed the values back. I don't believe I even made a nandroid. Actually I am not even really sure what a nandroid is.
ericu571 said:
That is the issue...all I did was go back into build.prop and changed the values back. I don't believe I even made a nandroid. Actually I am not even really sure what a nandroid is.
Click to expand...
Click to collapse
How did you install your Google Wallet? Did you follow instruction in post i give it to you or did you install Google Wallet from Play Store?
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.
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
I've managed to extract an apk of a (free) application that is restricted to the Galaxy S3. Unfortunately, when I try to install this apk on my Galaxy Nexus, it says 'application not installed'. I'm assuming this is because the S3's device ID is integrated into the apk file, which is why the apk installs fine onto the S3 that it was extracted from.
How does one get around this? Surely it's possible, as applications such as Google Wallet are extracted and shared for all devices on the internet within hours of an update. Could somebody give me a guide on how to do this?
Just a thought, install on your s3, titium back up , copy the backup to your GN and install
Sent from my Galaxy Nexus using xda premium
qtwrk said:
Just a thought, install on your s3, titium back up , copy the backup to your GN and install
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
It's my mother's S3; I can't root it.
Add her email account then go to play store menu and click her email under accounts and her play suite will be on there. Just make sure you don't sync when setting it up or will get all her emails. Then remove her account. app will still be installed and will update. If you flash you'll have to do it again
LoveNFC said:
It's my mother's S3; I can't root it.
Click to expand...
Click to collapse
Is yours rooted? If so, did you try adding into the system apps folder? Make sure you make a backup too
Swyped on my Galaxy Nexus running AOKP with Franco Kernel, overclocked to 1.4GHz
Don't need root. Just add her under accounts on phone. I did it once. My friend had tmobile. I'm sprint. Apps are tied to email account. All you do is switch user in the store and hers will be there and yours won't until you switch back. Get app. Switch back to yours. Go back to phone settings and remove her account.
JediNinjafication said:
Don't need root. Just add her under accounts on phone. I did it once. My friend had tmobile. I'm sprint. Apps are tied to email account. All you do is switch user in the store and hers will be there and yours won't until you switch back. Get app. Switch back to yours. Go back to phone settings and remove her account.
Click to expand...
Click to collapse
Thanks for the suggestion, I've just tried it now. Unfortunately, even though the app did show up in the list, I'm getting "your device is not compatible with this version".
What app? just curious.
LoveNFC said:
Thanks for the suggestion, I've just tried it now. Unfortunately, even though the app did show up in the list, I'm getting "your device is not compatible with this version".
Click to expand...
Click to collapse
Lame. I don't know how they Decompile either.
Mach3.2 said:
What app? just curious.
Click to expand...
Click to collapse
It's an NFC payment application for my country.
Any new ideas?
Is it even possible to pull files from system folders via ADB command without root?
Isn't there some Apps that can temporary root your device withou actually touch system to root it?
Or why don't you root it and then afterwards unroot it?
Sent from my Galaxy Nexus using xda premium
I think you will be able to pull this off in a custom recovery.
Beamed from my Maguro
OK, so I've realised that the apk that I've pulled from the S3 works fine. I had an online friend install it on his phone and it installs perfectly. I then tried installing it on a Galaxy Note and Galaxy S2. Both of those threw up the same error: 'application not installed'. This has lead me to conclude that the apk, and the application, have device checks built-in. It won't install on anything other than an S3.
Does anyone know how to decompile apks to remove these device checks? I know it's possible, but how complicated is it?
This brief guide is to help others get Google Wallet working on AOSP based ROMs. There are guides already by Dafoxs and Antiochasylum but they are apparently for Samsung based ROMs and the lib files, etc are incompatible with AOSP based ROMs. Personally, I tried several times and the NFC setting kept getting wiped out so I had to do restores. These instructions are what ManelScout4Life posted and the thread is at his request. All the credit goes to the DEVs that made this possible - I am NOT a developer - Seriously... Lastly, the typical disclaimer applies - I take no responsibility for bricking your phone, etc. I highly recommend making a nandroid backup before any mod like this. These instructions worked on JellyBAM 3.2 compiled by ManeelScout4Life - http://forum.xda-developers.com/showthread.php?t=2069164
1) The lib files should not be modified like the posts for the SamSung based ROMs. However, you will need the modified Google Wallet .apk that is included in the zip you can download from their threads. I used the attached file that I downloaded from this thread - http://forum.xda-developers.com/showthread.php?t=2037372&highlight=google+wallet
2) I already had NFC enabled so ensure it is on in settings if you haven't already.
3) You need to modify /system/build.prop. I used Root Explorer (remember to change to RW) and you have to modify three lines. I made a copy of the existing build.prop before editing because you will revert to the existing file once complete to match your actual device.
3a) ro.product.model=Galaxy Nexus
3b) ro.product.name=yakju
3c) ro.product.device=maguro
4) I then rebooted before installing Google Wallet from the Play store. I then opened the app and performed the setup. The other guides mention getting FCs on NFC and to continue on but I never had any and the setup completed. YMMV.
5) Once the setup is complete with the version of the app from the store, you need to replace the app with the modified version that you downloaded in step 1. I used TB to force stop the app before I deleted it from /data/app.
6) I then use Root Explorer again to place the attached apk in /system/app (remember RW). I checked permissions and removed the group write check but again am not certain if that was necessary.
7) I then changed the build.prop.bak file to build.prop so it is back to before you started.
8) Reboot and hopefully it will work.
Hopefully, this helps and is clear.
Note: I see a prompt in the app shown in the attached pic but it will still work. It is really just a warning about a rooted device.
I pretty much did this, and it didn't work until I fixed permissions on the modded file that I moved to system/apps at the last step, like I saw in the YouTube video
Sent from my SGH-I317 using xda premium
capite said:
I pretty much did this, and it didn't work until I fixed permissions on the modded file that I moved to system/apps at the last step, like I saw in the YouTube video
Sent from my SGH-I317 using xda premium
Click to expand...
Click to collapse
So, I assume you removed the group write permission like I mentioned in step 6 and that fixed it for you? I assume it is the same video referenced in the link I have in step 1. The person checked permissions and removed that one check but he didn't say you had to. I did it anyway and maybe that is why it worked for me the first time that I followed the instructions I listed - from ManelScout4Life.
Thanks for this!
Sent from my Samsung Galaxy Note II
Yes
Sent from my SGH-I317 using xda premium
So, I assume you removed the group write permission like I mentioned in step 6 and that fixed it for you? I assume it is the same video referenced in the link I have in step 1. The person checked permissions and removed that one check but he didn't say you had to. I did it anyway and maybe that is why it worked for me the first time that I followed the instructions I listed - from ManelScout4Life.
told me to reset the app...and its hanging at 98%...thoughts?
If you reboot and check the "about device", does it show Galaxy Nexus before you even download the app?
Have you double checked the spelling on the other two lines?
What ROM and version are you on?
Sent from my SAMSUNG-SGH-I317 using xda premium
All I did was change name, model and device in build prop let me download and install and runs flawless no need for modified app
Sent from my Galaxy Nexus using xda premium
crisis187 said:
All I did was change name, model and device in build prop let me download and install and runs flawless no need for modified app
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I assume the reason for the modified app is for it to continue working after you change the build.prop back to an unsupported device. I guess on AOSP ROMs where S-pen apps don't work, then the proper build.prop isn't as important. You will lose access to external sd card possibly and other issues possibly.
Sent from my SAMSUNG-SGH-I317 using xda premium
I switched back the info seems to work still haven't fully tested yet
**EDIT
After installing multi window support to jelly bear ROM wallet force closes when trying to add account
Sent from my SGH-I317 using xda premium
How about if you complete the instructions above - adding the modded app, changing permissions, deleting the downloaded app, etc?
Sent from my SAMSUNG-SGH-I317 using xda premium
RichMD said:
If you reboot and check the "about device", does it show Galaxy Nexus before you even download the app?
Have you double checked the spelling on the other two lines?
What ROM and version are you on?
Sent from my SAMSUNG-SGH-I317 using xda premium
Click to expand...
Click to collapse
sorry for the delay...yes everything was spelled correctly, said Galaxy Nexus etc etc...I'm running CM10 by madmack...with it hanging i forced out, deleted pushed modded apk fixed perm and rebooted...opened the app and it hung on "setting up google wallet" for a good 15min...so i forced out and left it at that.
MonsterBandit said:
sorry for the delay...yes everything was spelled correctly, said Galaxy Nexus etc etc...I'm running CM10 by madmack...with it hanging i forced out, deleted pushed modded apk fixed perm and rebooted...opened the app and it hung on "setting up google wallet" for a good 15min...so i forced out and left it at that.
Click to expand...
Click to collapse
With the Galaxy Nexus build.Prop and Google wallet downloaded from the store, the setup needs to complete before you move to the next steps of reverting the build.prop and pushing the modded app. Those steps are to keep the app working without having issues due to a Galaxy Nexus build.prop. I would delete the app, and start over. I assume you never got an email stating you activated wallet.
Sent from my SAMSUNG-SGH-I317 using xda premium
Also, did you ever use the steps/zip posted by dafoxs or the other thread (forgot the name)? If so, your NFC setting might be gone or you have incompatible lib files, etc. I would revert to the nandroid backup if you made one before following those procedures which are for Samsung based ROMs rather than AOSP/CM10
Sent from my SAMSUNG-SGH-I317 using xda premium
crisis187 said:
I switched back the info seems to work still haven't fully tested yet
**EDIT
After installing multi window support to jelly bear ROM wallet force closes when trying to add account
Sent from my SGH-I317 using xda premium
Click to expand...
Click to collapse
Wait. You installed multi window support on jelly beer!?
ManelScout4Life said:
Wait. You installed multi window support on jelly beer!?
Click to expand...
Click to collapse
LOL!
Modified build.prop and now my phone won't turn on. Any help?
---------- Post added at 02:37 PM ---------- Previous post was at 02:30 PM ----------
Took out battery, replaced it. Boot to recovery and restored Nandroid. Not sure what went wrong but I think I'll give up hopes of Google Wallet. Made me a little skiddish now.
This method of getting Google Wallet appears to break both Google Now and video output on cm10.1 variants that are running the open source audio hal.
Google Now goes into the 'Didn't catch that, retry?' Loop.
Steps to reproduce:
Install cm10.1 later than 01/26/2013
Allow it to boot and stabilize.
Setup Google Now.
Modify build.props to reflect Galaxy Nexus, yakju, maguro as dictated in OP.
Reboot.
Google Now will now have the 'Didn't catch that' error if you attempt voice recognition.
Sent from my "berry", spelling may vary.
bofhemeritus said:
This method of getting Google Wallet appears to break both Google Now and video output on cm10.1 variants that are running the open source audio hal.
Google Now goes into the 'Didn't catch that, retry?' Loop.
Steps to reproduce:
Install cm10.1 later than 01/26/2013
Allow it to boot and stabilize.
Setup Google Now.
Modify build.props to reflect Galaxy Nexus, yakju, maguro as dictated in OP.
Reboot.
Google Now will now have the 'Didn't catch that' error if you attempt voice recognition.
Sent from my "berry", spelling may vary.
Click to expand...
Click to collapse
Thanks,
I can't confirm this works on 10.1 (Android 4.2.x) - only confirmed on 4.1.x even though I expect Google Now, etc will be fine after reverting your build.prop. I'm "assuming" Google Wallet will work as indicated in these steps but Google Now, etc may have problems while the bulld.prop stilll indicates the wrong device - temporary until your wallet is working.
However, were you able to get Google Wallet to setup properly?
If you did get it working, did you try changing the build.prop back to original? I don't know if that would solve the Google Now but your steps listed don't indicate that you finished reverting the build.prop.
Please reply with your results for others.
Hello -
I did actually revert the build.props file to the original settings, and Google Now continued to give the same error. I'm about to test it without opening Google now until after the revert and reboot.
Thanks for your help!
If you like my work, donate to the Juvenile Diabetes Research Fund.
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...