Related
First this is a guide from the Verizon Note 2 forums, for those who don't know about it.
All Credit to WarlockLord, ogdobber, and tpmwr, and everyone else involved in this.
Visit the original thread here
Follow these steps, I have done this 3 times already and every time it works, IF you follow these steps.
I HIGHLY suggest using root explorer for this
1. Download the attached zip file, you must extract it, and place everything in their respective folders, backup your current files, rename with .bak on the end, paste the files in their respective folders from the zip. Set the correct permissions as the other files in the folder. Under the "Read" check, owner, group, others. Under "Write", check owner, and press ok.
2. Next, navigate to your build.prop in your /system and edit it to mirror the Galaxy Nexus.
ro.product.model=Galaxy Nexus
ro.product.name=yakju
ro.product.device=maguro
3. Reboot
4. Open your app drawer, find the wallet app, from there, set it up, it will say Setting up this will take 5 minutes, you WILL get a force close.
5. From this point navigate to your /system/app and delete the wallet app.
6. Reboot.
7 Open the play store, download wallet, now set everything up, and add a card, once you have registered a card, it will say the app needs to reset. Reset it, and wait. Once you get back to the screen where you can select your account, close the app.
8. Navigate to your /data/app and delete the wallet.apk in there. DO NOT UN-INSTALL IT!!, This is crutial, ONLY DELETE IT
9. Now head back to your downloaded files from this post and paste the modaco R87 wallet apk back into your /system/app, and set the correct permissions, under the "Read" check, owner, group, others. Under "Write", check owner, and press ok.
10. Reboot.
11. Now open wallet again from the app drawer and set everything up. It should proceed with no errors if you did everything correct.
12. Once setup, reboot again and open the app again to make sure its still working, and your cards are still there.
13. If its still working, you can now change your build.prop back to
ro.product.model=SGH-I317 or SGH-I317M(which ever variant you have)
ro.product.name=t0lteatt
ro.product.device=t0lteatt
If you do not change your build.prop back to stock values, it wll probably break SNote
14. Save the build.prop and exit.
15. Profit.
Everything you need to know is in this post, if its not working, you didn't do something correctly, or you missed a step.
VIDEO HOW TO - THANKS TO YELLOWGTO
YellowGTO said:
Here you guys go
Click to expand...
Click to collapse
I did this thursday night, works perfect
Sent from my GT-N7105 using xda premium
I was one of those who tested this out for warlocklord. Weird thing is, I re-did everything last night again just to see(going back to stock) without all those steps. I used the flashable zip(r87), replaced the build prop warlocklord uploaded when he first started it(attached). I load up wallet without crashing, everything loads and then I place back the original build.prop.
cmjkxa said:
I was one of those who tested this out for warlocklord. Weird thing is, I re-did everything last night again just to see(going back to stock) without all those steps. I used the flashable zip(r87), replaced the build prop warlocklord uploaded when he first started it(attached). I load up wallet without crashing, everything loads and then I place back the original build.prop.
Click to expand...
Click to collapse
Yea I did the same, you already had the folder in your data with saved stuff is why it worked.
However that is the verizon build.prop - I dont suggest people using it. Won't hurt, but verizon likes to block app's from the makret.
This is my first chance to use google wallet, lol its awsome.gas stations, cvs, gas stations, toys r us, mcdonalds.love using it
Sent from my GT-N7105 using xda premium
This going to be a really stupid and probably self-explanatory question... but I don't want to take any chance: Do you have to be ROOTED to perform this complicated procedure or can you be fully stock??
Dr. Evo said:
This going to be a really stupid and probably self-explanatory question... but I don't want to take any chance: Do you have to be ROOTED to perform this complicated procedure or can you be fully stock??
Click to expand...
Click to collapse
Rooted of course you have to copy files to the system directory.
Sent from my SCH-I605 using Tapatalk 2
Was holding off, but now must root! Damn you,XDA!
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
srtpusher said:
Was holding off, but now must root! Damn you,XDA!
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Click to expand...
Click to collapse
Root it. Its not "your" phone unless you root it.
Im on tmobile and still no luck it fails when it tries to finish the transaction
Sent from my SGH-T889 using xda app-developers app
Did this thursday night and it works flawlessly, glad to have Wallet back after I lost my Secure Element on my GS3
revemou ear
I am on step 7 now, and I think I am stuck. How long does the reset take? The progress bar is stuck on 98%, on "Removing payment cards," for about 15 minutes now.
Roundabouts said:
I am on step 7 now, and I think I am stuck. How long does the reset take? The progress bar is stuck on 98%, on "Removing payment cards," for about 15 minutes now.
Click to expand...
Click to collapse
That is very normal. Try to back out of the app.
malinois16 said:
That is very normal. Try to back out of the app.
Click to expand...
Click to collapse
Yeah, I finally gathered my courage and backed out. I finished everything and now my wallet seems to be working. Time to give it a go at a store!
Is this something that would be able to be cooked into a rom- a working version of Wallet, or would this procedure have to be done after every flash?
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
I originally used the original link that you posted. Those directions were a bit lacking so I ended up using the GS3 thread in combination with the original GN2 thread. It said to remove the APK. I was like, what APK, I am starting new, i don't ahve anything installed. So I assumed this person started off using the GS3 thread. So I went to the GS3 thread and flash modaco patched r87 and the GS3 NFC fix (I know, that was mistake). I then removed the APK. Then changed my build.prop. I installed the legit APK from play store. Then I opened it and activated my cards. It claimed that the app would restart on it's own, but it never did. I then just deleted the APK and then moved the modaco patched r87 into the system/app directory. Everything appeared to go well. I tried to make a payment and got a declined message at a 7-11. I then tried it at a CVS and but this time the NFC didn't even register. I then realized, I had the wrong NFC fix. So I flashed the NOTE2 NFC fix and was able to make my first successful wallet payment. Well everything ended up well so I'm happy. It seems that your directions are a little bit clearer than he original. Good luck to everyone else. I feel a little uncomfortable because my method was little dirty cuz I flashed the GS3 NFC fix first by accident. Once the new Cleanrom comes out with the multiwindow, I will try this process again from scratch and hopefully get a cleaner install.
Why am I getting the message Android is Upgrading everytime I reboot my phone? Is there anyway to get rid of it?
homegeek said:
Why am I getting the message Android is Upgrading everytime I reboot my phone? Is there anyway to get rid of it?
Click to expand...
Click to collapse
I can't speak for sure, but I've only seen that after clearing out dalvik, when it starts having its odexing fun.
-----
I would love to help you, but help yourself first: ask a better question
http://www.catb.org/~esr/faqs/smart-questions.html
Except I did not clear out the Cache and it happens everytime I reboot the device.
mastermindx85 said:
Im on tmobile and still no luck it fails when it tries to finish the transaction
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
Go back and repeat the process.
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.
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?
OK, so this may not even be the result of running a custom rom because it hasn't worked with any of them. When I click on Voicemail which isn't setup yet by the way, all it does is send me to my messaging app. It gives me no options to set it up, or check voicemail.
Sent from my HTC6500LVW using XDA Premium 4 mobile app
Running bonestock 1.0a
tygray6 said:
OK, so this may not even be the result of running a custom rom because it hasn't worked with any of them. When I click on Voicemail which isn't setup yet by the way, all it does is send me to my messaging app. It gives me no options to set it up, or check voicemail.
Sent from my HTC6500LVW using XDA Premium 4 mobile app
Running bonestock 1.0a
Click to expand...
Click to collapse
I removed the Visual Voicemail application. It can be added back.
The icon for Visual Voice mail is tied to the Messaging app.
I need to edit the messaging app to rid that icon. for now just use the feature to "hide" it in the app drawer.
of it you want the app, pull it outta the bloat.zip
Okay, thanks
Sent from my HTC6500LVW using XDA Premium 4 mobile app
OK, so I downloaded the bloat zip and extracted the vvm.apk it gives me the install option but says install failed every time. Any ideas?
Sent from my HTC6500LVW using XDA Premium 4 mobile app
tygray6 said:
OK, so I downloaded the bloat zip and extracted the vvm.apk it gives me the install option but says install failed every time. Any ideas?
Sent from my HTC6500LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
are you using my empty flashable.zip..?
just pull vvm.apk and put in system/app
Once I get my phone back, and or you have S-OFF this won't be an issue.
Aroma will solve a lot of these types of issues as well.
Okay, I put it in place of the null file in the app folder in your flashable zip and after re zipping it it failed when flashing
Sent from my HTC6500LVW using XDA Premium 4 mobile app
Don't unzip then rezip. Use a tool like 7zip and drop it into the zip. It failed because by unzipping, you broke the signature
Sent from my HTC6500LVW using Tapatalk 4
If I've helped, please hit the thanks button
tylerlawhon said:
Don't unzip then rezip. Use a tool like 7zip and drop it into the zip. It failed because by unzipping, you broke the signature
Click to expand...
Click to collapse
exactly what Ty said.
I am expecting my phone back today, and my first project is Aroma..
so bare with me.. (not you Ty)
I will be getting the ROM to where I am comfortable with calling it a full non beta release.
Only reason it's beta is because I don't have Aroma set up yet, once that is set up, it's game on.
you will be able to re-flash the ROM.zip pick "MOD only" and then select JUST the .apk you want (NO you can't remove apps, use root explorer for that, I think S-OFF takes away write protection but I have no idea yet, if not, then, well, we will need to get used to that .zip that deletes files (it's quite easy, once you try it out and everything)
andybones said:
exactly what Ty said.
I am expecting my phone back today, and my first project is Aroma..
so bare with me.. (not you Ty)
I will be getting the ROM to where I am comfortable with calling it a full non beta release.
Only reason it's beta is because I don't have Aroma set up yet, once that is set up, it's game on.
you will be able to re-flash the ROM.zip pick "MOD only" and then select JUST the .apk you want (NO you can't remove apps, use root explorer for that, I think S-OFF takes away write protection but I have no idea yet, if not, then, well, we will need to get used to that .zip that deletes files (it's quite easy, once you try it out and everything)
Click to expand...
Click to collapse
I forgot to come back and post a thank you, it worked great after I placed the apk into the zip and flashed. By the way, I've run every rom available now for the phone and keep coming back to yours, I appreciate your work.
Sent from my One using XDA Premium 4 mobile app
tygray6 said:
I forgot to come back and post a thank you, it worked great after I placed the apk into the zip and flashed. By the way, I've run every rom available now for the phone and keep coming back to yours, I appreciate your work.
Sent from my One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hey man thank you very much, it really does mean a lot to me!
and you're very welcome
andybones said:
I removed the Visual Voicemail application. It can be added back.
The icon for Visual Voice mail is tied to the Messaging app.
I need to edit the messaging app to rid that icon. for now just use the feature to "hide" it in the app drawer.
of it you want the app, pull it outta the bloat.zip
Click to expand...
Click to collapse
Have you had any luck ridding the VVM icon and whatever else from the messaging app yet. I had a nasty issue related to the new VVM.
I will spell it out here in case anyone else has this issue.
So i like always update my phone when updates come out.
The new VVM has some addition network elements tied to it on the back-end.
Long story short this 443 update has created randomly dropping my mobile connection. I tried re flashing the radios, the stock rom, going back one radio version, etc. I mentioned this in a post in this thread:
http://forum.xda-developers.com/verizon-htc-one/help/wifi-bluetooth-mobile-data-wont-off-t2883253
I don't believe it is anything we have done in here, but the issue was with exclusively mobile data where it would disconnect but still show 4g, anyways back to the VVM
I had to revert to 442 stock rom as it didn't have the disconnecting issue
Since i already ran the newest 443 VVM app with those additional features, the 442 VVM fails with error code 2004 when on a 442 ROM
So i had to be coy when calling VZW to get them to reset this. Lucky they didn't ask SW/HW versions, so basically they had ' reset the network elements ' associated with the newest version. WORKED!
So if this happens to you , all i said was it came down as an update, i didn't like it, and reverted back and now it does not work, etc.... I tried to find the newest update again but cant find it.
I was wondering how the VVM icon still there after removing the APK, that answers that. I tried to load the newest VVM on 442, and epic fail lolz
Just providing some info for everyone
carm01 said:
Have you had any luck ridding the VVM icon and whatever else from the messaging app yet. I had a nasty issue related to the new VVM.
I will spell it out here in case anyone else has this issue.
So i like always update my phone when updates come out.
The new VVM has some addition network elements tied to it on the back-end.
Long story short this 443 update has created randomly dropping my mobile connection. I tried re flashing the radios, the stock rom, going back one radio version, etc. I mentioned this in a post in this thread:
http://forum.xda-developers.com/verizon-htc-one/help/wifi-bluetooth-mobile-data-wont-off-t2883253
I don't believe it is anything we have done in here, but the issue was with exclusively mobile data where it would disconnect but still show 4g, anyways back to the VVM
I had to revert to 442 stock rom as it didn't have the disconnecting issue
Since i already ran the newest 443 VVM app with those additional features, the 442 VVM fails with error code 2004 when on a 442 ROM
So i had to be coy when calling VZW to get them to reset this. Lucky they didn't ask SW/HW versions, so basically they had ' reset the network elements ' associated with the newest version. WORKED!
So if this happens to you , all i said was it came down as an update, i didn't like it, and reverted back and now it does not work, etc.... I tried to find the newest update again but cant find it.
I was wondering how the VVM icon still there after removing the APK, that answers that. I tried to load the newest VVM on 442, and epic fail lolz
Just providing some info for everyone
Click to expand...
Click to collapse
Foolish me, this is so very simple, I just forgot that you have to do it on a 100% clean flash, you can't use a flashable.zip as it is an .xml system edit.
system/customize/resource/allapplication.xml
basically you edit this .xml just search for "voicemail"
you will find this line of code
Code:
<item type="application" packageName="com.htc.sense.mms" className="com.htc.sense.mms.ui.VoiceMailTabActivity" display_order="200" display_hide="[B][COLOR="Red"]0[/COLOR][/B]" />
change it to
Code:
<item type="application" packageName="com.htc.sense.mms" className="com.htc.sense.mms.ui.VoiceMailTabActivity" display_order="200" display_hide="[B][COLOR="Red"]1[/COLOR][/B]" />
to be quite honest though to save yourself A LOT of time, just hit the menu button in app drawer click hide apps and hide it, that is what this MOD does anyway...
andybones said:
Foolish me, this is so very simple, I just forgot that you have to do it on a 100% clean flash, you can't use a flashable.zip as it is an .xml system edit.
system/customize/resource/allapplication.xml
basically you edit this .xml just search for "voicemail"
you will find this line of code
Code:
<item type="application" packageName="com.htc.sense.mms" className="com.htc.sense.mms.ui.VoiceMailTabActivity" display_order="200" display_hide="[B][COLOR="Red"]0[/COLOR][/B]" />
change it to
Code:
<item type="application" packageName="com.htc.sense.mms" className="com.htc.sense.mms.ui.VoiceMailTabActivity" display_order="200" display_hide="[B][COLOR="Red"]1[/COLOR][/B]" />
to be quite honest though to save yourself A LOT of time, just hit the menu button in app drawer click hide apps and hide it, that is what this MOD does anyway...
Click to expand...
Click to collapse
I will give this a try sometime; kudos
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...