After much trial and error, I'm happy to announce that I have gotten Google Wallet working 100% on the Photon Q! I tested it out tonight, successfully made NFC purchases at two different locations. This is the first phone I've had with NFC, and contactless payment is pretty darn cool! And one 'plus' of this method is that it uses an unmolested Wallet apk. Personally, I didn't want to risk using a modified apk (as some other workarounds do) with financial information. So without further ado, here's the process:
What you will need:
Root access
Custom recovery (I used TWRP)
Root capable file explorer (I used ES File Explorer)
Xposed framework installer
Xposed patcher to disable region/device checks for Wallet
Google Wallet apk
Modified build.prop (optional) ONLY FOR PHOTON Q w/ OFFICIAL JB UPDATE
The process is based on the instructions here with a few modifications. Big thanks to Entropy512 for the original write up and Xposed module that makes this possible!
1. Place the Xposed framework apk, Xposed patcher apk, Wallet apk, and modified build.prop on your SD card (internal or external.) I had to name the file build.prop.txt to upload it here, rename it so it's just build.prop either before copying it to SD or once it's on SD but before moving to the next steps.
2. Boot into recovery and make a nandroid backup. This is essential! Not only will it save you if something goes wrong, but you will need it later.
3. Install the Xposed framework installer apk, then open it and allow it to install the framework. You will need to give it root access.
4. Install the patcher apk to disable region and device checks for Wallet. It will prompt you to activate the module, go ahead and do so. Reboot.
5. Open your root explorer and mount the system partition with R/W permissions. On ES File Explorer, this is on the tool bar to the left. Copy the modified build.prop to /system/ and allow it to overwrite the existing file when prompted. (see note below) DO NOT REBOOT!
6. Install the Google Wallet apk. Open it and run through the setup (link to your Google account and add/select a payment method.)
7. After Wallet setup is complete, reboot into recovery. Use the restore option and bring up the backup you made before starting. Select ONLY the system partition, make sure all other partitions are deselected. Run the restore operation.
8. Wipe cache and dalvik cache (may not be necessary, but it can't hurt.) Reboot the phone and try it out!
Note about the build.prop: If you prefer to edit the original build.prop yourself rather than using the pre-modified one that I'm providing, here are the lines that need to be changed:
Code:
ro.product.model=Galaxy Nexus
ro.product.name=yakju
ro.product.device=maguro
ro.product.brand=Samsung
ro.product.manufacturer=Samsung
If you reboot after installing Wallet and don't go into recovery, the phone will show the "Bootloader unlocked" screen and then hang at a black screen with the backlight on. Just power off, boot into recovery, and proceed with the system partition restore. I have tried numerous times to just replace the build.prop with the original after setting up Wallet, and it always hangs at the black screen when I reboot. Don't waste your time with that, just go to recovery and restore the system partition.
This was tested on the official JB OTA update, though it should work on the stock ICS ROM as well, though you will need to edit your build.prop rather than using the one I've provided. I'm not sure if it will work on CM, Carbon, or any other ROM, test at your own risk and keep a backup.
I hope some of you find this useful! I have gotten a lot from this community and would like to give something back.
Interesting.
I think with adb you can save yourself a few steps - like restoring the system partition .
But regardless, that is cool. I always wanted to try Google Wallet, and was confused when this phone didn't offer it... but did have NFC.
Good to see my friend Entropy512 is still around as well! I will have to give this a shot, thanks for the detailed writeup.
arrrghhh said:
Interesting.
I think with adb you can save yourself a few steps - like restoring the system partition .
But regardless, that is cool. I always wanted to try Google Wallet, and was confused when this phone didn't offer it... but did have NFC.
Good to see my friend Entropy512 is still around as well! I will have to give this a shot, thanks for the detailed writeup.
Click to expand...
Click to collapse
Very possible. I'm not that well versed with adb beyond basic push/pull operations, figured I'd better not mess with what works! If you try this and are able to make it work in a more simplified way I'd be happy to amend the original post. :good:
How would you save time with ADB? Replacing the build.prop with the original one?
Any idea why the system doesn't boot after restoring it? Something with the framework?
Interesting
Great writeup, I went from bum to buying **** with my phone in about 10 minutes. Make sure to follow instructions carefully and you shouldnt have a problem, the writeup was spot on and I love the capability offered to me by my photon q now
so i followed the steps in the first post, but obviously i missed something. when finished i go to open wallet and i get the message stating "not yet available for your device......." I will try the process again tomorrow, but any suggestions?
Aaargh! said:
so i followed the steps in the first post, but obviously i missed something. when finished i go to open wallet and i get the message stating "not yet available for your device......." I will try the process again tomorrow, but any suggestions?
Click to expand...
Click to collapse
I got this after i rebooted my device, so it initiall did work and then it stopped after a soft reset due to battery loss. Trying again, then goign to the store before the phone resets. Dang it
so i have tried three times with no success. Wallet sets up, but after restoring system partition and booting back-up, wallet does not work. Same error as before.
So i re-ran Xposedinstaller and let it do its thing, rebooted and i can now open Wallet and access it. This was after following the Ops instructions completely. I have not tried to make a purchase, but at least it opens
I made an in store purchase today and it worked perfect. Pretty cool technology
Sent from my XT897 using xda app-developers app
I'm unable to get this to stick on CM 10.1 06/06 build. I was able to set it up and had a banner saying my device wasn't supported at the top, then the next time I ran the app it would close the app after displaying a notification about my device not being supported. Unfortunate because this area has a ton of support for Offers.
Solust said:
I'm unable to get this to stick on CM 10.1 06/06 build. I was able to set it up and had a banner saying my device wasn't supported at the top, then the next time I ran the app it would close the app after displaying a notification about my device not being supported. Unfortunate because this area has a ton of support for Offers.
Click to expand...
Click to collapse
After following install instructions, try running Xposedinstaller again. this is what i did and Google Wallet finally stuck. I am stock JB, but it is worth a try
Aaargh! said:
After following install instructions, try running Xposedinstaller again. this is what i did and Google Wallet finally stuck. I am stock JB, but it is worth a try
Click to expand...
Click to collapse
I can confirm that this made it "stick" for me as well. I'm on the 6-15 nightly of CM 10.1.
Sent from my XT897 using xda app-developers app
CM11?
Does anyone have google wallet tap and pay working on CM11 with this phone? If so, what method did you use to make it work? It seems what's described here is for JB/CM10...
Related
I hope this how to guide is helpful. Yes it is not all about the AT&T crap, it also removes the horrible touchwiz launcher.
NOTE THERE IS A MUCH MORE DETAILED GUIDE HERE
1. Install a launcher substitute.
Personally, I prefer launcher pro, so that is the one I will be talking about in this step. You can pick this app up for free from the android market.
This launcher completely replaces your home screens and your application drawer with something more stock android like. It has several improvements over the actual stock android launcher also, so I would recommend it for any phone, not just TouchWiz phones.
CAUTION FROM THIS POINT ON YOU THINGS COULD (although unlikely) GO WRONG. PROCEED WITH CAUTION. I AM NOT LIABLE FOR ANY DAMAGE CAUSED IN ANY PART OF THIS TUTORIAL.
2. Root your phone
Note that this does void your warrenty and prevent returning of your phone. All that aside it is relatively easy.
2a. Download the following root update at: mediafire.com/download.php?eilzbhfl73rij1v
2b. DO NOT UNZIP THIS FILE. Instead, rename it update.zip
2c. Mount your phones internal storage to you computer. If you are on a mac, that may require enable debugging mode in the application settings menu. If you are on a PC it requires the Samsung Captivate drivers forum.xdadevelopers.com/showthread.php?t=728929
2d. Copy the drivers to your phones internal storage and unmount and unplug your phone.
2e. Turn your phone off.
2f. Turn your phone on by pressing volume up and down while pressing the power button.
2g. Use volume up and down to select reinstall packages and then press the power button. Allow it to update.
2h. Once you reboot, your phone should be rooted.
3. Uninstall the bloatware.
3a.Download Titanium Backup from the Market
3b. Make sure your sd card is mounted to your phone (not your PC)
3c. Once it is installed install the busybox version they prompt you to.
3d. Press the Backup/Restore tab (if not already pressed).
3e. Find any of the following applications that you want to delete. If you don't know what it is, I recommend not deleting it. There are other bloatware apps, but I recommend keeping them.:
At&t Navigator
At&t Radio
At&t Maps
At&t Music
At&t Mobile Hotspots
Mobile Banking
Mobile Video
Where
YPmobile
At&t FamilyMap
Mini Diary
MobiTV
Write and Go
Media Hub
Daily Breifing
3f. Click on the app and press the red un-install button. NOTE UNINSTALL WILL REMAIN THROUGH FACTORY RESET ONLY UNINSTALL IF YOU ARE SURE YOU WANT TO.
4. Sideloading Apps
4a. If you are on a PC download this androidcentral.com/sideload-android-apps-all-you-want-sideload-wonder-machine
4b. If you are on a Mac (me) or Linux download this androidcentral.com/android-central-sideload-wonder-machine-linux-and-mac-talented-forum-member (note the mac and linux link is down atm but it should be back up soon.
4c. if neither of those options suit you and you want a more perminate (note it did not work for me) solution, then try this forum.xda-developers.com/showthread.php?t=728121
5. The service
You're screwed. (It works pretty nice where I live, but always manages to be dead when I need it the most.)
6. The Voicemail
While this is not carrier specific (all carrier voice-mails suck) , I thought I would include the fact that you can get visual voicemail from Google via its Google Voice voicemail service using your current number. For more information go to this link google.com/voice
note sorry my links are so weird, I am a new member and they do not let me post links.
If you have anything you would like to add, please add it in a reply
this is great thank you !
Thank you for taking your time I'm pretty sure it'll be really helpful to us users.
WE just need A FREAKEN MOD to sticky this. Well, first we need a mod.
_____
You should adddddd GPS fix.
also i wanted to know once rooted can you go back to factory defaults ? if yes how ? thanks !
accinfo said:
You should adddddd GPS fix.
Click to expand...
Click to collapse
Ill add it as soon as I figure out how to do it myself (sometime tomorrow)
nobi.sheikh said:
also i wanted to know once rooted can you go back to factory defaults ? if yes how ? thanks !
Click to expand...
Click to collapse
I'm pretty sure you can unroot, and from there do the factory restore, but any apps you uninstalled will still be gone forever.
nbs11 said:
I'm pretty sure you can unroot, and from there do the factory restore, but any apps you uninstalled will still be gone forever.
Click to expand...
Click to collapse
I heard (keyword, heard) you couldn't yet, any proof?
I hope this doesn't sound rude.
accinfo said:
I heard (keyword, heard) you couldn't yet, any proof?
I hope this doesn't sound rude.
Click to expand...
Click to collapse
The only sure way I know of to unroot is to flash the original ROM. As samsung does not provide this we need to wait for someone to pull it off the device.
the guide says it is recommended to DELETE or NOT to delete the listed AT&T apps? I'm confused at that part
Another guide: How To: Remove AT&T From Captivate
Includes: root, sideloading, remove market censorship, delete bloatware.
Thanks for this nbs!!
Do you know if the sideloading process listed above works on a mac?
I have I 9000 but same... rooting only puts a version of Su in system/xbin and busybox. It also installs supeuser.apk. any of this can be undone.
Sent from my GT-I9000 using XDA App
I can't get the market enabler to work. Can't parse file. Any ideas?
#nevermind. Got it from the google code page.
Sent from my SAMSUNG-SGH-I897 using XDA App
phlunkie said:
I can't get the market enabler to work. Can't parse file. Any ideas?
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
I ran into the same problem the first time. The file I downloaded from the Google site was around 40 KB and kept giving me that error message. So I did a Google search and downloaded the file from ithinkdiff.com which was around 80 KB. Also how are you installing the apk?
tcv14 said:
Do you know if the sideloading process listed above works on a mac?
Click to expand...
Click to collapse
Yes, I have a rooted captivate with side loaded apps (Asphalt 5, PDAnet, etc.) that I just threw on my SD and installed that way.
I have only used my mac for my Captivate.
This thread is dedicated to hacking and development of the Sharp SH7218u. This is an Android phone with a somewhat unique clamshell form-factor.
Before proceeding, please note that all of the usual warnings apply. The software and techniques described here have the potential to break your device and make it unusable. By using the software and following these techniques you run the risk of bricking your phone. I take no responsibility if this happens - proceed at your own risk.
First, some credits for the work of others:
Z4root:
Developed by xda member RyanZA.
http://forum.xda-developers.com/showthread.php?t=833953
SH7218u Clockworkmod Recovery:
Clockworkmod original developer is Koushik Dutta:
www.clockworkmod.com
Dialer2:
Original developer of now open source dialer is dnaq Productions:
http://dnaq.tumblr.com/
Initial hacking and development work:
Gigi Tse is credited for early and ongoing work for the SH7218u:
http://gigitse.com/
http://www.msharp.cn/forum/t390991/page1/
Now on the instructions....
-------------------
Rooting Your Phone, Installing Clockworkmod Recovery, and Installing Google Apps
Gather the Required Files:
1. Go to the z4root xda thread, login in and download z4root.1.3.0.apk:
http://forum.xda-developers.com/showthread.php?t=833953
2. Download SH7218u_recovery.apk:
(attached below)
3. Download the Clockworkmod recovery flashable Google Apps file from the following site:
http://goo-inside.me/gapps
In the table, you want to select the HDPI, CyanogenMod 6 version. The file that you download should be
called 'gapps-hdpi-20101114-signed.zip'
4. Place these three files on your micro-SD card and insert the card into your phone.
Root Your Phone
1. Boot up your phone and skip the system setup wizard. Go to the app drawer and run 'Settings'.
2. Select 'Applications', and enable 'Unknown sources'.
3. Select 'Development', and enable 'USB debugging'.
4. Exit back out to your home screen launcher, then go to the app drawer and run 'ES File Explorer'.
5. The file explorer should show you the contents of your sd card. Tap on the file 'z4root.1.3.0.apk'.
6. Confirm installation of z4root, and when this is complete select 'Open' to run the app.
7. From within z4root, press the 'Permanent Root' button.
8. Wait until this process is complete, and the phone will reboot by itself. It can take 30 seconds or so for this to happen, so be patient. You are now rooted.
Flash Clockworkmod Recovery Image
You must be rooted for this to work. Do this after you have successfully completed the rooting process above. Also please note that this is not the CWM recovery image developed by Gigi Tse. Her image contains CWM version 3.0.2.4. This is my recovery image and contains CWM version 5.0.2.8.
1. Open the app drawer and run 'ES File Explorer'.
2. Tap on the file 'SH7218u_recovery.apk'.
3. Confirm installation and run the application by selecting 'Open' once installation is complete.
4. On startup, the application will request Superuser privleges - press 'Accept' to allow this.
5. Press the 'Flash Clockworkmod Recovery' button.
6. Wait a few seconds until you see the confirmation message 'Recovery Flash Complete'.
7. Exit out of the application. You now have Clockworkmod as your recovery. You can uninstall the SH7218u_recovery app if you wish as you have no further use of it.
Note for users of Link2SD: This version of Clockworkmod recovery will perform backup and restore operations on the secondary SD card partition used by Link2SD. However, that partition must be formatted in the ext3 filesystem for this to work. Formatting the partition in any other filesystem (e.g. ext2, fat32, ext4, etc.), will result in failure to mount and backup the partition. An SD card can be prepared for use with Link2SD from within this version of Clockworkmod recovery by using the 'Partition SD Card' feature within the 'Advanced' menu.
Install Google Apps
1. Boot into Clockworkmod Recovery. This is done by powering down your phone, then turning it back on by pressing and holding down the number 3 and 6 buttons together, then pressing and releasing the power button. Continue to hold the number 3 and 6 buttons until you see the Clockworkmod screen.
2. Select 'install zip from sdcard' from the menu.
3. Select 'choose zip from sdcard' from the next menu.
4. The next menu will be the contents of your sdcard. Select the Google Apps file - 'gapps-hdpi-20101114-signed.zip'.
5. Confirm the installation and wait until it is complete.
6. Press the back button once to get back to the main screen and select 'reboot system now'. You now have Google Apps installed.
When you reboot the device, you will be taken through the Google account setup. Please note that in order for contacts applications to work with Google synchronization, you will need to install a modified contact editor. The stock firmware on this phone is not intended to sync with the Google servers as it was intended for Chinese users. The modified contact editor fixes this issue. It is free and available from the Market. Look for 'Contact Editor Free' by a developer named 'dmfs'.
Deleted
Deleted
Thank you! Very good job!
No ideas how to get the phone to answer a call when you open?
TabletGuru said:
Thank you! Very good job!
No ideas how to get the phone to answer a call when you open?
Click to expand...
Click to collapse
Hey someone read my thread!!
Sorry, no posts on this thread yet and it has been up for a while. I think most people who have this phone stick to Howard forums or other such sites that cater to the phone type and its region of origin.
As for your question, no...but I have tried. That would require a modification of the phone app or a change to the OS itself as the phone app is the active app when the phone is ringing and the device is opened. If I had the source code for the stock phone app, this would be a fairly easy thing to do. Unfortunately, I have been unable to find the source for the stock device firmware anywhere. I tried compiling a generic Froyo phone app from the Google source, but of course this did not work. This is a somewhat special app that needs to interface with several parts of the device's hardware, so a generic version just doesn't work. Unless Sharp releases the full source code for the stock firmware, I don't think this is going to be possible....at least not from someone with my somewhat limited development abilities.
Sent from my MB855 using xda premium
Google Play
Hey xdajunkman, amazing work you are doing here.
Have you considered adding Google Play to the mix? I was able to get the latest version working just fine on my SH7218u.
How hard would it be to hack the light notifications area of the phone, to make some of the notifications last for 1-2 seconds longer?
I should also add that my phone is giving some really flaky GPS information. It is putting me somewhere in the ocean near China unless I use wifi only. Do you have any experience with this?
EDIT: I don't know why, but the dialer is not working for me with regard to the long-press of the delete key and silent (#) key. No idea why...
EDIT2: It is because I had another keyboard installed; which must do something funky... switching back to a default keyboard and then trying seemed to work!
Thanks for your guide! Do you have got new version Rom? 2.3 or 2.3.5?
johnny8384 said:
Thanks for your guide! Do you have got new version Rom? 2.3 or 2.3.5?
Click to expand...
Click to collapse
Not likely to come. This would mean building something like CM7 for a new device from scratch. This kind of task takes dozens of man-hours for an expert developer, and that assumes that they have access to the original source for the release build. We do not have the original source, and there is no such developer working on this device. We will be stuck with Froyo.
Thank you so much for taking the time to write a guide xdajunkman!
I received my SH7218u today and did everything. The instructions were clear and the whole process took no more than 30 minutes.
Surprisingly, my SH7218u accepts 64 microsd card (after you format it).
Is it ok to have 2 partitions?
One is a ext2, and the other I just created using clockwork mod ext3...
I'm wanting to use that custom rom..
EDIT: clockwork mod Repartitioned my ext2 to ext3 now ಠ_ಠ
and all my apps are "installed"
Going to make a backup rom now.. and then Install xdajunkman's custom rom >__<
EDIT: Ok succesfully installed the Custom rom It looks great I might say awesome work xdajunkman
Ok the question is now.. how to I get back all my previous apps and stuff?
I followed the guide and made a backup already
My 7218u stuck at Sharp logo when boot because i've uninstalled a system apps ( don't remember exactly) what i've to do now? plz help me
P/S: My english sucks, sorry for that
delpan said:
My 7218u stuck at Sharp logo when boot because i've uninstalled a system apps ( don't remember exactly) what i've to do now? plz help me
P/S: My english sucks, sorry for that
Click to expand...
Click to collapse
Boot into clockwork mod by pressing 3and 6 and the power on button, (assuming you have that installed)
Reinstall the rom.. http://forum.xda-developers.com/showthread.php?p=22106340#post22106340
sirjoe1 said:
EDIT: Ok succesfully installed the Custom rom It looks great I might say awesome work xdajunkman
Ok the question is now.. how to I get back all my previous apps and stuff?
I followed the guide and made a backup already
Click to expand...
Click to collapse
It is usually just easier if you wait until you have the new ROM installed before you try and install your apps. There is no reliable way from within CWM to restore your installed apps.
However, because the new ROM is just a modified version of the stock ROM, it should be possible to flash the new ROM without wiping the existing user data and keeping your installed apps. Restore your backup that has all of your apps installed. Then, flash the modified ROM but skip the step in the instructions that tells you to wipe existing user data. Instead of wiping the user data, do the following:
1. In the 'mounts and storage' menu of CWM recovery, select to format both '/system' and '/cache'
2. In the 'advanced' menu of CWM, select 'Wipe Dalvik cache'
Now proceed with installing the ROM as per the instructions. This should result in the modified ROM being installed, but all of your installed apps should be protected.
If this does not work, then you will just have to re-installed the modified ROM according to the instructions (including wiping the existing user data), then re-install all of your apps. For future reference, a great app called Titanium Backup will allow you to backup your apps and restore them after changing the ROM.
sirjoe1 said:
-->My 7218u stuck at Sharp logo when boot because i've uninstalled a system apps
-->( don't remember exactly) what i've to do now? plz help me
Boot into clockwork mod by pressing 3and 6 and the power on button, (assuming you have that installed)
Reinstall the rom.. http://forum.xda-developers.com/showthread.php?p=22106340#post22106340
Click to expand...
Click to collapse
Agree with sirjoe1. Hopefully you flashed CWM as your recovery before you did this. However, if not then booting into recovery mode as described above should trigger a factory reset from the stock recovery partition. I have not attempted this myself with the stock recovery, but usually what this will do is simply return your device to it's stock state. You can then start over using the instructions in the OP....but without deleting critical system apps this time.
Hello again, I've a question, has anyone successfully Overclocked the cpu frequency on this phone using setcpu or similar apps?
Overclocking not possible without either a custom kernel or a kernel module of some sort. As the source for the stock kernel was never released, such a thing would be a HUGE undertaking. Very unlikely to ever happen.
xdajunkman said:
Overclocking not possible without either a custom kernel or a kernel module of some sort. As the source for the stock kernel was never released, such a thing would be a HUGE undertaking. Very unlikely to ever happen.
Click to expand...
Click to collapse
Oh darn, that's such a downer..
These sh7218u threads are so dead nowadays :/
I might have messed up my phone -_- (again)
I went into the /data/sdext2/dalvik-cache and deleted everything and now a few apps have gone missing, and some won't work, they just give me a force close error >___<
I also lost my go launcher ex settings..
and to make things worse.... my internal memory went to 0% free... deleted a few things to clear up 8mb..
Any Ideas how to fix this ? @[email protected]
[Can you guys play 480p videos?
I can't.. 360p runs fine though..]
I am hoping to get this device this week.
Thanks for your tutorial, and I will let you know if it runs out just fine
So for many people getting the galaxy S3 on verizon, you are without the praised app, google wallet. You can only get it on sprint. However, like many people who tinker, people have found ways to get it to work on their GS3's. I just got my phone yesterday. Had it rooted and romed in less then an hour of owning it of course. Then I set fourth onto getting google wallet to work.
Here is the problem I ran into. There are so many ways of doing it, and some don't always work. and it gets confusing. I went back to the beginning and worked out a way that works, and it is more simple.
First thing that I found. You do not have to mess with build properties at all. That was a pain.
Step 1: Reboot into recovery.
Step 2: Mount system
Step 3: Push the latest com.google.apps(ETC) file to system/app. For instance I used "com.google.android.apps.walletnfcrel.modaco.1.5-R79-v5.apk" because that was the latest I could find.
Step 4: Push nfcee_access.xml to /system/etc which I will include as a download on this thread.
Step 5: Reboot and run wallet. it will work.
Once you have pushed the nfcee_access.xml file, which give the app appropriate permission to work, when ever you have to update with a newer com.google.app(etc) file, all you have to do is this.
Stepv1: Using root explorer or other root file manager, copy the new com app file to system/app
Step 2: Copy the name of the existing file that is already in there then delete it.
Step 3: rename the new com app file to the old file.
Step 4: Reboot into recovery.
Step 5: Reboot normally.
The new version will now work.
You could very easily make a bat file to do this for you, but we are talking 2 adb commands.
I hope this helps other new S3 owners and people who have not yet tried to get google wallet working.
Will this work on beans town? K1 baseband
g1g said:
Will this work on beans town? K1 baseband
Click to expand...
Click to collapse
I'm wondering the same thing.
awalkerz said:
I'm wondering the same thing.
Click to expand...
Click to collapse
No it wont, this will only work on AOSP based roms. OP should note that, my guide has the information but I havent updated it in a while.
OP would you like to take over my work? Or merge information to one post we dont need two posts on a mod.
This is by far the easiest method for installing Wallet: http://forum.xda-developers.com/showthread.php?t=1810040
Use the automated script and it's as simple as... Setting script to edit, rebooting into flash, flashing the zip, rebooting, configuring wallet to your liking, setting script to stock.
It takes minutes maybe. Also, when flashing new roms, I just make a backup of wallet+app data in titanium, set script to edit, reboot, restore wallet from titanium and make sure it's configured, set script to stock and reboot.
Skrypt said:
This is by far the easiest method for installing Wallet: http://forum.xda-developers.com/showthread.php?t=1810040
Use the automated script and it's as simple as... Setting script to edit, rebooting into flash, flashing the zip, rebooting, configuring wallet to your liking, setting script to stock.
It takes minutes maybe. Also, when flashing new roms, I just make a backup of wallet+app data in titanium, set script to edit, reboot, restore wallet from titanium and make sure it's configured, set script to stock and reboot.
Click to expand...
Click to collapse
My guide has also been locked from a mod. Can be located here though http://rootzwiki.com/topic/37284-latest-google-wallet-112912/
Deleted post
__
__
ATT seems to work
Sweet idea! Just tried this on an ATT GS3 and it seems fine. I did not test other apps. I do get an unsupported device tag at the top in the app but I don't think that impedes the function. When I use the Nexus device device, name and model (maguro, yakju and Galaxy Nexus) I don't get the warning but probably more likely to end up with incompatible apps.
Do you reset Google Wallet prior to flashing a new rom or do you just have the build.prop update before you run wallet?
__
I'm confused. I have Wallet installed on my Verizon GS3 and I have no problems now. I am rooted and running Synergy ROM. When installed Wallet, I had to use a patched APK and edit my build.prop prior to installing Wallet to trick the phone similarly to what your script does (Galaxy Nexus, yakju, and maguro instead) After installing and setting up Wallet, I restored my original SCH-I535, d2vzw, d2vzw settings in build.prop and rebooted again. I am running Wallet no problems and it doesn't even tell me that I am using an unsupported device.
When I reboot my phone, it does not affect Wallet and my build.prop is not modified. I don't understand why someone would need your script to keep modifying the build.prop to say it is the pretend device? Please don't take my reply wrong, I'm simply trying to figure out what I am missing, not be a jerk.
I am always leary about leaving my build.prop modified because you trick other things into thinking your phone is something it is not. I feel this leaves you open to potential problems. I used Goo Manager the other day to see if there were any updates for my ROM and because of a modified build.prop it thought my phone was an AT&T GS3 and if I had downloaded and tried to flash an AT&T ROM I might have bricked it. I'm not sure, but I wouldn't want to take that chance. Also, isn't there a possibility of downloading an app from the Play Store that is only for the Sprint phone you're pretending to be and causing problems?
Jim
__
Hi Jeremiah,
Thanks for the info. Just so you know, I used that Google installer few weeks ago and it worked fine. I changed to a new ROM last week and forgot to reset wallet before switching which caused bunch of problems. I was able to fix them but the installer did not work for me anymore. I was however able to get wallet working by manually editing build.prop and installing a patched apk of wallet. After wallet was up and running, I reverted back to the d2vzw and SCH-I535 version of build.prop. So you know, I have my correct build prop AND a working Google wallet. I can send you the link but its the Verizon Google wallet thread in the mods and app forum under Verizon GS3. I understand if you switch ROMs it would need to be reset and build prop edited again, but I don't think the is a need to keep your build prop edited unless you are using the play version of wallet. Perhaps the link could get you the patched version and that might help.
Take care,
Jim
__
jeremiahmegel said:
As I recall, the patched APK isn't the newest version/update of Google Wallet, right? That's why I'm using the Play Store version: to receive updates to the app. If you don't care about updates, though, I suppose your way of doing things would be best. (I don't think it works throughout ROM updates, though. Let me know if I'm wrong about this.)
Click to expand...
Click to collapse
Oh OK... I'm not sure but that makes sense... You would know more than me! Thanks... Again I was just looking for clarification. Thanks for your work. Good luck.
Jim
jeremiahmegel said:
The "Unsupported device." error only shows up if you're running Google Wallet on a rooted device (unsurprisingly); you're right that it doesn't impede the function. And you don't need to do anything as the user before or after flashing a new ROM; once you update the ROM, your phone should reboot automatically within a minute or two of starting up to put the new build.prop into effect! Simply install this once and don't worry about it again! (Unless, of course, you uninstall Tasker or wipe your phone or something.)
Click to expand...
Click to collapse
So to clarify, when you say:
"And you don't need to do anything as the user before or after flashing a new ROM"
Do you really mean "you still have to reset Google Wallet before flashing a new ROM"?
Also, I'm wondering if it's possible that modifying build.prop might cause my Nfc.apk to stop functioning. I'm wondering this because it stopped functioning (after using 'Google Wallet Installer' - which does replace nfc.apk I believe, so that could be it, but not sure).
calaski8123 said:
Hi Jeremiah,
Thanks for the info. Just so you know, I used that Google installer few weeks ago and it worked fine. I changed to a new ROM last week and forgot to reset wallet before switching which caused bunch of problems. I was able to fix them but the installer did not work for me anymore. I was however able to get wallet working by manually editing build.prop and installing a patched apk of wallet. After wallet was up and running, I reverted back to the d2vzw and SCH-I535 version of build.prop. So you know, I have my correct build prop AND a working Google wallet. I can send you the link but its the Verizon Google wallet thread in the mods and app forum under Verizon GS3. I understand if you switch ROMs it would need to be reset and build prop edited again, but I don't think the is a need to keep your build prop edited unless you are using the play version of wallet. Perhaps the link could get you the patched version and that might help.
Take care,
Jim
Click to expand...
Click to collapse
Jim will you please tell me how you fixed it? I did not reset Wallet before installing a new ROM a couple months ago and unfortunately all my nandroids are bad due to a CWM bug involving partitions (I didn't do anything to my partition structure manually...).
Thanks a lot!
Hi,
I'll tell you what I did, but I was just trying anything so I'm not sure if I got lucky or if you have to do everything I say... First I went into application manager and I cleared all data and updates from wallet. Then I rebooted into recovery and did full wipe 3x. Then I went onto Google on my laptop and logged in. Go to wallet and then to your activated devices. Not sure what they are called but you will see all your devices that have wallet. Some might day deactivated. If there are any active then disable or remove them. I don't remember what the term is Google uses to Deactivate. Once you have no active wallet applications left on Google go back to your phone. Install the working ROM or good backup. I had a good backup with wallet working...i was able to restore that nandroid and reset wallet from within the app so that i could then install the new ROM. then After setup, reboot again and wipe dalvic cache in recovery. Then try to install wallet again. Thats pretty much how I got it fixed... The key was getting it deactivated online.
---------- Post added at 09:52 PM ---------- Previous post was at 09:28 PM ----------
Oh and I uninstalled wallet after clearing the cache and updates.. Forgot that part sorry.
Jim
I followed the instructions to the T and it worked perfectly. Thank you. But my question is, what happens to the Tasker Profile? After, I went back in to check out what you did. I am a relatively new Tasker user and was curious about what all was intailed. But when I went back the profile was gone and the only sign that I had imported the xml file was two variables. Is it supposed to disapear?
__
jeremiahmegel said:
As I recall, the patched APK isn't the newest version/update of Google Wallet, right? That's why I'm using the Play Store version: to receive updates to the app. If you don't care about updates, though, I suppose your way of doing things would be best. (I don't think it works throughout ROM updates, though. Let me know if I'm wrong about this.)
Click to expand...
Click to collapse
Correct, the patches lag behind the updates somewhat. You can only use Play Store Wallet if you build.prop matches Play Store Wallet accepted devices (d2spr being one of them). For this reason, I prefer to wait for the updated patched version - if you do that, you can keep d2vzw or whatever you want in your build.prop
As far as resetting when changing ROMs, back when everything was stored on the secure element resetting was a big pain in the ass. I don't even bother anymore - there's a separate "reset wallet" option in the menu of the actual app (different than clearing app data), but you don't need to use it. I just keep a version of Wallet Installer V3 in TiBu, and restore it after installing a new rom. After restoring Wallet Installer, just run it once and then reset build.prop - the installer downloads the latest patched Wallet.apk.
jeremiahmegel said:
No, it is not supposed to disappear. Since Tasker updated its UI, Step 4 ("Tap the green check-mark at the bottom-left of the screen to save the profile.") is no longer available. Instead, press the back button or home button on your phone (or just switch to another app) to save the profile, then continue to Step 5. Let me know if this works. Nice to know that I could help you get Google Wallet up and running!
Click to expand...
Click to collapse
I tried going through the steps again but I cant get Tasker to recognize the xml file when going through the import sequence. I downloaded and extracted (when extracrted its another file folder with the xml file in it), placed it on the root of my internal sd card. I go into tasker to import. It recognizes the file folder but when I select it, there isn't anything inside. Tasker wont recognize the basic xml file. I remeber when I first did this, the xml file was recognized without being in a folder. I can plainly see the xml file on the root of the sd card from Root Explorer in ROM toolbox. Would have it something to do with the permissions of the xml file? I show the permissions as rw-rw-r--.
I think I know why I am having to go this. I didn't follow the step to the T. I clicked "Run" before saving becasue I didn't see the green checkmark.
__
jeremiahmegel said:
What is the file name of your XML file?
Click to expand...
Click to collapse
I have the actually xml file on my sd card. It is named Replace_build.prop.prf.xml
When i go to the file through Root Browser in ROM Toolbox, its visible. I click it and it presents me with options to open it. I select Tasker and is says "Failed to move import to my sd directory"
08BajaBoy said:
I have the actually xml file on my sd card. It is named Replace_build.prop.prf.xml
When i go to the file through Root Browser in ROM Toolbox, its visible. I click it and it presents me with options to open it. I select Tasker and is says "Failed to move import to my sd directory"
Click to expand...
Click to collapse
I am not what was happening but I updated to CM10.1.0 RC2. I cleared anything I had tried previously with this tut. redownloaded the file and went though everthing again. It worked and the tasker profile stuck this time. Thanks for the help.
Great write up. Very simple to install. Google wallet was installed and running in less than 5 minutes. Thank you!
Galaxy S3 :good:
MOAR :BetteR:
Can anyone confirm this method works with 4.3? I made the jump to CM10.2 Nightly 8/27 (and tried 8/14, I think) and my phone goes into bootloop. It was working fine on CM10.1.2.
__
here's a dirty method for Pokemon DesperaGos. it can also help to fool Niantic's account monitoring algorithms if they recognize and distinguish accounts from others that only log in while there's known-working root hiding methods.
make a full backup of your daily rom. odds are we all have one anyways, so that's probably covered but I'll have to point out that if you play a lot of games that do NOT save progress online or to internal/external sd, then this "solution" is not for you!! why? because upon restoring, your progress will be a few hours to a few weeks behind depending when the backup was made.
this is also not for owners of devices with a locked bootloader.
A LOT OF WHAT I'LL HAVE YOU DOING STRONGLY DISCOURAGED UNDER NORMAL CIRCUMSTANCES
HIGH PROBABILITY OF LEAVING YOU WITH A SOFT BRICK IF YOU DO NOT MAINTAIN A SEPARATE BACKUP!
MUST HAVE TWRP OR A RECOVERY WITH FILE MANAGER
onto the fun part. pick any rom, preferably a very small one, that comes with SELINUX ENFORCING by default, else pair it with a kernel that can be switched to enforcing and remain that way indefinitely, across reboots, after UNROOTING.
install your victim of a rom, (if needed) kernel meeting the above standard, and if CM based, nano gapps. **if you do NOT use supersu** have a copy of a recovery-flashable supersu zip on your device for use later or if your choice rom comes without root, flash it right away.
do your initial boot, set up the bare essential settings (network, display, google account), and install Google Play Games from Google Play.
reboot to recovery, make a backup of this rom and give it a name along the lines of unrooted or Pokemon Go or both. for the sake of time, you can disable md5 generation.
boot back to system, and start debloating the living hell out of it. Browser? YouTube? gmail? widgets? it's a blow-out. everything that won't prevent the rom from functioning gets uninstalled. the more you uninstall, the less time it'll take to get your Pokemon Go shoes on.
do not uninstall anything needed for Google Play to function either!
this rom will serve no purpose but to play Pokemon Go. you can even scrap some language files (~100-250mb) for nations on other continents. you'll find them in various folders in the System folder but don't touch Chinese (zh / chn) had bad experiences. if your rom of choice was made available in the forums from a dev in a different nation that speaks your same language i.e. GB / EN or SPAIN / MEX, don't delete either.
during this very very thorough debloating process, feel free to renew the backup as you go, so if you do something that breaks the rom, you won't have to start over.
all done? uninstall any and all root tools related and unrelated to the debloating process.
supersu users, open supersu. go to Settings, scroll down to Full permanent unroot and hit it.
non supersu users, including CM, install supersu from Google Play and launch it. tap Expert. CANCEL THE PROMPT TO UPDATE BINARY. then do the same -- settings, and permanent unroot.
your device is NOT READY FOR POKEMON GO YET!
reboot to recovery, and verify that System is mounted. navigate to your recovery's built in file manager -- for TWRP it's in Advanced. in the root of the device you should see a folder called supersu. delete it. if it's not there, proceed.
go in the System folder and look inside bin and xbin for a file simply named "su" and if there, delete it as well.
now, one last time, re-make your backup of this rom.
congrats! you now have a rom that should be slim enough to quickly switch to, 4-8 minutes, when you're hitting the road or curb for some pokismans.
when switching to/from your main rom and Pokemon Go rom, you should always wipe cache and dalvik
Edit: you won't need to do this if you include Cache in your TWRP backups
use your recovery's Restore function as a make-shift multi-rom.
Sterist said:
here's a dirty method for Pokemon DesperaGos. it can also help to fool Niantic's account monitoring algorithms if they recognize and distinguish accounts from others that only log in while there's known-working root hiding methods.
make a full backup of your daily rom. odds are we all have one anyways, so that's probably covered but I'll have to point out that if you play a lot of games that do NOT save progress online or to internal/external sd, then this "solution" is not for you!! why? because upon restoring, your progress will be a few hours to a few weeks behind depending when the backup was made.
this is also not for owners of devices with a locked bootloader.
A LOT OF WHAT I'LL HAVE YOU DOING STRONGLYDISCOURAGED UNDER NORMALCIRCUMSTANCES
HIGH PROBABILITY OF LEAVING YOU WITH A SOFT BRICK IF YOU DO NOT MAINTAIN A SEPARATE BACKUP!
MUST HAVE TWRP OR A RECOVERY WITH FILE MANAGER
onto the fun part. pick any rom, preferably a very small one, that comes with SELINUX ENFORCING by default, else pair it with a kernel that can be switched to enforcing and remain that way indefinitely, across reboots, after UNROOTING.
install your victim of a rom, (if needed) kernel meeting the above standard, and if CM based, nano gapps. **if you do NOT use supersu** have a copy of a recovery-flashable supersu zip on your device for use later or if your choice rom comes without root, flash it right away.
do your initial boot, set up the bare essential settings (network, display, google account), and install Google Play Games from Google Play.
reboot to recovery, make a backup of this rom and give it a name along the lines of unrooted or Pokemon Go or both. for the sake of time, you can disable md5 generation.
boot back to system, and start debloating the living hell out of it. Browser? YouTube? gmail? widgets? it's a blow-out. everything that won't prevent the rom from functioning gets uninstalled. the more you uninstall, the less time it'll take to get your Pokemon Go shoes on.
do not uninstall anything needed for Google Play to function either!
this rom will serve no purpose but to play Pokemon Go. you can even scrap some language files (~100-250mb) for nations on other continents. you'll find them in various folders in the System folder but don't touch Chinese (zh / chn) had bad experiences. if your rom of choice was made available in the forums from a dev in a different nation that speaks your same language i.e. GB / EN or SPAIN / MEX, don't delete either.
during this very very thorough debloating process, feel free to renew the backup as you go, so if you do something that breaks the rom, you won't have to start over.
all done? uninstall any and all root tools related and unrelated to the debloating process.
supersu users, open supersu. go to Settings, scroll down to Full permanent unroot and hit it.
non supersu users, including CM, install supersu from Google Play and launch it. tap Expert. CANCEL THE PROMPT TO UPDATE BINARY. then do the same -- settings, and permanent unroot.
your device is NOT READY FOR POKEMON GO YET!
reboot to recovery, and verify that System is mounted. navigate to your recovery's built in file manager -- for TWRP it's in Advanced. in the root of the device you should see a folder called supersu. delete it. if it's not there, proceed.
go in the System folder and look inside bin and xbin for a file simply named "su" and if there, delete it as well.
now, one last time, re-make your backup of this rom.
congrats! you now have a rom that should be slim enough to quickly switch to, 4-8 minutes, when you're hitting the road or curb for some pokismans.
when switching to/from your main rom and Pokemon Go rom, you should always wipe cache and dalvik
use your recovery's Restore function as a make-shift multi-rom.
Click to expand...
Click to collapse
That's impressive! Im a newb, but I think I understand most of the concept. I wanted to ask- instead of having to try to successfully do all that, creating dual ROMS, do you know any other way for an unrooted phone with a custom ROM to acquire and use the google libraries necessary to trick SafetyNet and pass the CTS profile match?
davizzyus said:
That's impressive! Im a newb, but I think I understand most of the concept. I wanted to ask- instead of having to try to successfully do all that, creating dual ROMS, do you know any other way for an unrooted phone with a custom ROM to acquire and use the google libraries necessary to trick SafetyNet and pass the CTS profile match?
Click to expand...
Click to collapse
if an unrooted custom rom is not passing safetynet, then, to the extent of my knowledge, there are still remnant superuser (no specific kind, just in general) files. this also includes xposed framework, not sure if it's app (aka installer) will cause a fail