Can someone please help me out. Ive been trying for days to install apps such as omnisketch, car home, zen brush, and the original samsung apps that came with the galaxy note.
I have a rooted galaxy note on the latest Saurom rom and i am using tmobile.
I have tried all of the following with no luck:
1) go back to stock rom and reinstall saurom
2) I backed up the original samsung apps that came preinstalled with my note through titanium backup i then restored it on the saurom rom and when i tried to open it, it takes me to the play store saying it is not compatible with my device.
3) I heard you have to change your build.prop. So i searched around and changed my build prop model, name , and device to the international galaxy note through root explorer.
Still no luck. I dont know what else to do. I have tried searching the fourms and google but i cant find how to make my note compatible. Like searching the play store for omnisketch, car home, samsungapps, zenbrush, those dont even show up. The only way i can get them to show up is if i google them and then link to the play store, but then it says device not compatible and i cannot install them.
Can anybody please help me out
This is an Xposed module (See http://forum.xda-developers.com/showthread.php?t=1574401 for more on Xposed) that allows disables region/device checks for Google Wallet r87 and above.
Source code for the module is at https://github.com/Entropy512/XposedWalletPatcher
To install:
Install the Xposed Installer APK from the thread linked above
Install the Xposed framework using Xposed Installer
Install the APK linked in this post
Reboot your device after enabling the module in Xposed Installer
Install Google Wallet from the Play Store - No more need for hacked APKs for a banking app. Complete source code for the module showing every method that is patched is provided above.
This will work even if Google Wallet gets updated through the Play Store, as long as method names used for checking don't change. (GW had major changes between r81 and r87 that required changing Xposed modules, however, no changes were necessary from r87 to the current Play Store version.)
NOTE: Initial setup of Google Wallet still requires a hacked build.prop, but you can restore build.prop once you've set it up. Thanks go to ogdobber for most of these settings from http://forum.xda-developers.com/showthread.php?t=1769083
Here are the modified values I use. SAVE YOUR build.prop before editing!!!
Code:
ro.product.model=Galaxy Nexus
ro.product.name=yakju
ro.product.device=maguro
ro.product.brand=Samsung
ro.product.manufacturer=Samsung
You'll see two differences here from ogdobber's settings: setting brand and manufacturer to Samsung. The reason for this is that his tutorial is for a Galaxy S III - e.g. faking out one Samsung product on a different Samsung product. On my Xperia T, I needed one or both of these additional changes (I have not yet had time to determine which one.)
Many of the tips and tricks in http://forum.xda-developers.com/showthread.php?t=1769083 are still valid - the only difference is you no longer have to install smali-hacked Wallet versions to /system, full source of the module is provided, AND you can update Wallet from the Play Store and it will continue working as long as the compatibility check methods/classes don't change names.
Change Log
Initial Release so far...
Technical Details and other observations
Reserved for Future Use
FAQ
Q: Why does this still require build.prop changes when initially setting up Wallet?
A: For unknown reasons, SOMETHING is directly parsing build.prop and sending it to a server somewhere during initial setup. I have not figured out what is doing it and how to fake it out with Xposed yet.
Q: If I need build.prop hacks, what's the point of this module?
A: Once you have initialized Google Wallet and set up a card, you can return build.prop to its normal state. If you do this without the module, Google Wallet will stop working.
Q: Resetting Google Wallet hangs with at N-3/N steps complete (e.g. 74/77)
A: Resetting GW also needs modified build.prop. DO NOT FEAR: You can safely modify build.prop and reboot even after reset has started. I have done this numerous times.
Confirmed Working Devices/Firmwares
Confirmed Working - build.prop hacks only for card setup/reset
Sony Xperia T
CyanogenMod 10
Sony Xperia Z
.350 Stock
CyanogenMod 10.1
Samsung Galaxy S3 (AT&T - SGH-I747)
CyanogenMod 10.1
Samsung Note 2 (Verizon - SCH-I605)
"Jedi XV13" - Not sure if this really belongs in the "hacked NFC libraries" or is an AOSP derivative.
Working - Requires hacked NFC libraries
TBD
Not Working
Samsung Galaxy S II (AT&T version, SGH-I777) - No Secure Element present
Non-Sprint HTC One units - Unknown, Wallet hangs on setup no matter what anyone does
Oppo Find5 - Same issue as the HTC One
Using the Wallet R96 apk, I was able to install and setup without modification to build.prop on my Sprint Galaxy Note 2, LJC firmware.
Note: The R96 apk will install on my GN2 without this mod, if I use the latest MA7 firmware.
Edit: Google Wallet R96 apk
Sent from my SPH-L900 using Tapatalk 2
on a tmobile sgs2 I get stuck at setting up... I don't know off hand and I'm no at my desktop but I imagine the 989 also doesn't have the secure enabled.
Sent from my Galaxy Nexus using Tapatalk 2
k3v0 said:
Using the Wallet R96 apk, I was able to install and setup without modification to build.prop on my Sprint Galaxy Note 2, LJC firmware.
Note: The R96 apk will install on my GN2 without this mod, if I use the latest MA7 firmware.
Edit: Google Wallet R96 apk
Sent from my SPH-L900 using Tapatalk 2
Click to expand...
Click to collapse
Doesn't surprise me since Sprint is the only carrier I'm aware of that cooperates with Google - many Sprint phones are officially supported by GW.
iamanalog said:
on a tmobile sgs2 I get stuck at setting up... I don't know off hand and I'm no at my desktop but I imagine the 989 also doesn't have the secure enabled.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I know none of the Exynos-based GS2s had an SE. Don't know about the Qcom variants.
If your NFC gets totally hosed when GW is installed, but then starts working perfectly as soon as you uninstall GW, that's a sign you're missing the SE.
Works on ATT Galaxy S 3 (i747) running CM 10.1 nightlies.
Temporarily made the build.prop edits for initial setup. Just re-install xposed hooks after flashing each nightly.
Thanks dude! I was tired of resetting my build.prop everytime I reboot my phone. :thumbup:
SeNT FRoM oVeR THeRe----->
Just curious, Im on a tmobile sgs3. I used the wallet installer to install wallet perfectly, the version that installs allows you to revert the build.prop changes afther the initial setup and it will still work perfectly. There is a version in the play store though and it prompts me to update. Once I update it says that it will not work with a rooted device. Will this module fix that issue and allow me to update? As of right now, I just unlinked it from the play store using rom toolbox so I dont even see the update anymore.
tp2215 said:
Just curious, Im on a tmobile sgs3. I used the wallet installer to install wallet perfectly, the version that installs allows you to revert the build.prop changes afther the initial setup and it will still work perfectly. There is a version in the play store though and it prompts me to update. Once I update it says that it will not work with a rooted device. Will this module fix that issue and allow me to update? As of right now, I just unlinked it from the play store using rom toolbox so I dont even see the update anymore.
Click to expand...
Click to collapse
It completely removed the root check because when I was using the Galaxy Nexus information in the build.prop file, every time I used wallet it says unsupported device but after I installed the module that unsupported device message went away and I was able to revert my build.prop file back to the note 2 with no issues whatsoever (and I'm on the latest version of google wallet)
On Xperia S i can install but it always says to exit and try again after restarting the device...
Sent from my Nexus 7 using xda app-developers app
This worked perfectly on my VZW Note 2.
Thanks!
Will not get past setting up for purchases note 2 n7100
Sent from my Galaxy Nexus using Tapatalk 2
Sir - Lancelot
Are you running stock rooted or a ROM on you VZW note 2?
Sent from my SCH-I605 using xda premium
areayetee said:
Sir - Lancelot
Are you running stock rooted or a ROM on you VZW note 2?
Sent from my SCH-I605 using xda premium
Click to expand...
Click to collapse
Hi.
I am on Jedi XV13. It has the exposed framework installer in the jedi rom tricks. So I just added this module then changed my build prop in rom toolbox pro.
Now I guess I should clarify worked perfectly. lol
I set up wallet when i made that post bit as of today I have not used it. It did however pull all my old cc info from my nexus and seems to be good to go.
I will get gas, a milkshake, or something to see if it does work tomorrow. I see no reason it shouldnt through.
tp2215 said:
Just curious, Im on a tmobile sgs3. I used the wallet installer to install wallet perfectly, the version that installs allows you to revert the build.prop changes afther the initial setup and it will still work perfectly. There is a version in the play store though and it prompts me to update. Once I update it says that it will not work with a rooted device. Will this module fix that issue and allow me to update? As of right now, I just unlinked it from the play store using rom toolbox so I dont even see the update anymore.
Click to expand...
Click to collapse
Yes - with this module, you can update from the market and it will USUALLY work unless Google changed method names.
They did that a few versions ago, but the past 2-3 Play Store updates have not required module changes. If they do I'll probably notice within a day or two and update the module.
dingokevin said:
Will not get past setting up for purchases note 2 n7100
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Need more details. Also refer to the thread that I linked - it has a LOT of useful info on various gotchas, the main difference being that this does not require putting a hacked APK into /system AND, as stated above, often (but not always) continues working after updating via the Play Store.
If you look at some of the other threads, sometimes other hacks are needed other than the hacked APK. This approach ONLY replaces the hacked APK, and not other things that may be necessary, such as hacked up NFC libraries on some devices.
Entropy512 said:
Yes - with this module, you can update from the market and it will USUALLY work unless Google changed method names.
They did that a few versions ago, but the past 2-3 Play Store updates have not required module changes. If they do I'll probably notice within a day or two and update the module.
Need more details. Also refer to the thread that I linked - it has a LOT of useful info on various gotchas, the main difference being that this does not require putting a hacked APK into /system AND, as stated above, often (but not always) continues working after updating via the Play Store.
If you look at some of the other threads, sometimes other hacks are needed other than the hacked APK. This approach ONLY replaces the hacked APK, and not other things that may be necessary, such as hacked up NFC libraries on some devices.
Click to expand...
Click to collapse
Tried that.. copied libs from Sprint GS3 which is known to work and nfc_access.xml certs and what not.. samething... you would NOT be able to pass setting up the payments. Always get Device setup failed.. Gave up on this.. Damn it google..
I have installed the exposed frame work and module, edited build prop like it says in first post. installed Google wallet Apk, but all im getting is
wallets unable to proceed until this device is fully initialized. Make sure the devices has network access and try rebooting if problem persists.
I can't get past this any ideas? I'm on jb stock Xperia s. In settings there is Google wallet or operator Wallet, what is operator wallet for? Thanks
Sent from my LT26i using xda premium
Hi all, first time post here.
I just switched from my 5-year obsession with the iPhone (due to loss of interest) and bought my first Android device, the Galaxy S4. Love it! Already updated to the latest OTA update, and then rooted via the SD card method. Just ran into my first (minimal) issue today.
Upon reading this article on Android Police, I decided to download the latest Google Play .apk to install the latest version of the app. Once downloaded, I opened the .apk for installation, but I see this (check attached image) after any attempt to install.
Any ideas?
Key Info: I have a rooted Verizon Galaxy S4 on the latest OTA update.
HEllo,
I am unable to download any application from samsung apps, when I open samsung apps it shows all softwares and all navigation works well but when I try to download anything the waiting circle comes and it stucks at waiting circle forever and then I have to exit samsung apps.
I tried uninstalling samsung apps by root uninstaller and then installing it back again from apk , I tried clear data/cache many times, I tried updating samsung apps too.Although google play is working fine.
please give a solution.
Device - Samsung galaxy note 1 , 4,1.2 Rooted.
thanks
Administr4tor said:
HEllo,
I am unable to download any application from samsung apps, when I open samsung apps it shows all softwares and all navigation works well but when I try to download anything the waiting circle comes and it stucks at waiting circle forever and then I have to exit samsung apps.
I tried uninstalling samsung apps by root uninstaller and then installing it back again from apk , I tried clear data/cache many times, I tried updating samsung apps too.Although google play is working fine.
please give a solution.
Device - Samsung galaxy note 1 , 4,1.2 Rooted.
thanks
Click to expand...
Click to collapse
I am not sure what is the problem, but let me tell you ,
"You can't install/Download apps from Samsung apps until your device is registered."
( You may have noticed a SMS is send to Samsung when you Factory format your device )
Make sure your device is registered at Samsung Servers.
Edit: Also there are chances that your device has updated its BUILT NUMBER or KERNEL version from Stock while Rooting or any other activity.
Dear All,
I ve tried to install the apk downoladed from Apk mirror of AOD, touchwiz and other Samsung system app but I got an error saying there was an exiting package installed on my phone and it is in conflict.
I'm on N935K with N935L firmware
Yes, i have the same by trying to install the european weather app from samsung.
N935L with L Firmware.
I tried this as soon as I got the phone (a few days after release) and I believe from some research that you would need root access in order to fully uninstall the original app and it's framework, I did read somewhere that adb could be used but again without root I'm doubtful. My solution to the weather app was to install xwidget from the app store and use the s8+ weather widget from within there, I also installed the accuweather app so that when you click on the widget it takes you to that.
From my understanding samsung pay will never be a think for anyone outside of korea (for the FE) because you'd need to uninstall it's root files again requiring root access which would trip knox therefore disabling samsung pay anyways, after doing some testing I found that installing a custom rom and then using the full unroot feature of SU it will allow you to use all the banking apps in the UK and the only thing that will not work (obviously) would be samsung pay due to knox.
I may have Rambled on a lot here but I just wanted to let anyone who reads this to know what I have tried
You needed to root your FE.
I've attempt to install Live Message apk into my unroot FE without success.
So, I root my FE and port a lot of Note 8 apps into my FE now. Very happy to have Live Message with my FE.
Also, fingerprint reader is working significantly faster too!
galaxy note fe
can no need root also can use live message