__
__
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.
__
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.
RC 1 can now be found HERE
Here is a mirror
How to get back to stock if you are having issues:
1. You will need to flash a sbf, you can find guides here for Windows and here for Linux.
2. Reboot recovery by pressing X on the keyboard and turning it on
3. Press the search key so a menu pops up
4. Navigate to wipe data with the volume keys. Select with the camera button.
5. Then navigate to reboot with the volume keys and select with the camera key.
You are back to stock and you can root!
The File Manager was included in this rom so you are able to install the Bootstrap application so you can restore a back up or flash a different rom. Wipe your data after this.
Bugs
Bugs go here
Sweet, i am so excited for this. Gonna install it as soon as I get a chance, downloading now. I can't wait to see if you guys figure out custom kernels
Sent from my DROID2 using XDA App
I'm real curious to hear what you guys found that will allow custom kernels on this phone. I already read over what birdman and nenolod were trying and it seems they threw in the towel. I read some other posts on droidforums about initiating essentially a second boot second to trick the phone into loading a custom kernel, but nothing more on that topic. Really curious to see how you might be able to implement this
Nice work guys. I will probably give this a try this weekend.
I too would like to hear your theory on how to get a new kernel on the phone. Not in a hurry to see it happen, but just curious to hear the underlying theory.
Though, I do understand if you are waiting to get it released before sharing. Just don't forget to let the community know when/if you get it worked out. It will open a lot of doors for some of these rom cookers around here, and rom cookers of the future.
and just installed it, sans computer intervention (thank god nothing went wrong or I'd be SOL for 5 hours lol, im at work)
mounted, wiped cache/data, remounted, installed, remounted, and wiped cache/data again just to be safe
now I'm waiting for it to restore all my apps and stuff so I can get everything reconfigured and have a glorious blur free phone! thank you so much devs, this is fantastic
Hey guys, awesome ROM! Very stable so far!
One thing I noticed: The "Car Home" application shows up in Android Market, but the update fails when attempting to apply it. Not sure what the cause of this is just yet. If I can glean more information from my own testing, will let you know.
Thanks again for the work you've put into this!
- Andy
AndyRoss said:
Hey guys, awesome ROM! Very stable so far!
One thing I noticed: The "Car Home" application shows up in Android Market, but the update fails when attempting to apply it. Not sure what the cause of this is just yet. If I can glean more information from my own testing, will let you know.
Thanks again for the work you've put into this!
- Andy
Click to expand...
Click to collapse
I am not sure why that happens, but if you really want the new one from market, you can just remove it from /system/app and then it will install fine from market. I have had that issue with other apps before. Honestly, with a lot of these apps in the market now, there really isn't much need to include them in the rom.
Seems to work pretty well. Got stuck in a boot loop because I didn't wipe my data, so I rebooted recovery and wiped it. Problem solved.
The only problem I'm having is that I can't get Backup Assistant to work, so I can't restore my phone numbers.
I downloaded the stock app rar, and tried doing an ADB install for BackupAssistanceClient and BuaContactAdapter, but I get "Failure [INSTALL_FAILED_DEXOPT]".
I tried copying over BuaContactAdapter.apk and BackupAssistanceClient.apk manually (to /system/app) and setting permissions, but that doesn't seem to do anything.
Any ideas?
Phoible said:
Any ideas?
Click to expand...
Click to collapse
Export your contacts from the verizon website and then take that file and import it into gmail and sync your contatcs with gmail. Then, it doesn't matter which rom you install you'll have your contacts.
Sent from my DROID2 using XDA App
Phoible said:
Seems to work pretty well. Got stuck in a boot loop because I didn't wipe my data, so I rebooted recovery and wiped it. Problem solved.
The only problem I'm having is that I can't get Backup Assistant to work, so I can't restore my phone numbers.
I downloaded the stock app rar, and tried doing an ADB install for BackupAssistanceClient and BuaContactAdapter, but I get "Failure [INSTALL_FAILED_DEXOPT]".
I tried copying over BuaContactAdapter.apk and BackupAssistanceClient.apk manually (to /system/app) and setting permissions, but that doesn't seem to do anything.
Any ideas?
Click to expand...
Click to collapse
Here's what I did with another ROM. Go to VZW with your pc. Navigate to contacts. Export contact list as Outlook CSV. Go to your gmail acct and import the CSV. Sync phone contacts to gmail. Important to do the outlook export though. Regular CSV doesn't populate gmail contacts properly.
Just a quick question. If and when we flash this, are we still rooted? If so, can I just install bootstrap and reboot recovery and restore? Or do i have to do the whole root process again like if it was an original phone from store?
one thing with the bootloader i remember when i first got my eris was people on the fourms would keep emailing htc for the bootloader keys because it was hard to crack and htc gave them up ... maybe if we flood moto with emails and stuff they'll loosen up like htc
DL'ing now. If you guys want another mirror let me know.
When I get a phone call the sliders are messed up
RMcCall said:
When I get a phone call the sliders are messed up
Click to expand...
Click to collapse
x2 with this. If I'm not mistaken you already knew about that in the alpha build thread...but just saying.
also, still not getting the touchscreen dialer on the activation page.
Coderedpl said:
Just a quick question. If and when we flash this, are we still rooted? If so, can I just install bootstrap and reboot recovery and restore? Or do i have to do the whole root process again like if it was an original phone from store?
Click to expand...
Click to collapse
Yes, it comes with root. No, you do not want to restore. Restoring will bring you back to the backup you created. This rom comes with Superuser.apk (root) no need to re-root.
Sent from my DROID2 using XDA App
I seem to remember the alpha thread saying not to flash themes over this....but don't think it was mentioned this go round....still the case? (assume so). Figured it was worth noting in the first post if that's the case.
Also....I just installed this, and am also stuck unable to get it programmed.
First time it started the music and then got a failed message. Since then I don't even get the music, and after 20 seconds or so I just get a "Please enter the # you're calling about" message and if entered, it just tries to transfer me to cust service.
one. said:
I seem to remember the alpha thread saying not to flash themes over this....but don't think it was mentioned this go round....still the case? (assume so). Figured it was worth noting in the first post if that's the case.
Also....I just installed this, and am also stuck unable to get it programmed.
First time it started the music and then got a failed message. Since then I don't even get the music, and after 20 seconds or so I just get a "Please enter the # you're calling about" message and if entered, it just tries to transfer me to cust service.
Click to expand...
Click to collapse
Have you tried *22899 send? Should go straight into programing the phone
Problems with Titanium Backup's "Integrate system app updates into ROM" feature.
I searched, but didn't find any documentation on this feature, so I did the adventurous thing and tried it out. It's supposed to replace the system apps in the ROM with the updated apk, therefore saving space in the system memory. But after the batch finished, all of the updated apps were completely gone...the originals AND the updates were deleted. Since there isn't a way to "undo" this function, I had to reflash the ROM. Does anyone know more about this option? Does it work with any ROM?
Sent from my Evo with the xda app
deafcon5 said:
I searched, but didn't find any documentation on this feature, so I did the adventurous thing and tried it out. It's supposed to replace the system apps in the ROM with the updated apk, therefore saving space in the system memory. But after the batch finished, all of the updated apps were completely gone...the originals AND the updates were deleted. Since there isn't a way to "undo" this function, I had to reflash the ROM. Does anyone know more about this option? Does it work with any ROM?
Sent from my Evo with the xda app
Click to expand...
Click to collapse
If your rooted you can replace them yourself.
deafcon5 said:
I searched, but didn't find any documentation on this feature, so I did the adventurous thing and tried it out. It's supposed to replace the system apps in the ROM with the updated apk, therefore saving space in the system memory. But after the batch finished, all of the updated apps were completely gone...the originals AND the updates were deleted. Since there isn't a way to "undo" this function, I had to reflash the ROM. Does anyone know more about this option? Does it work with any ROM?
Sent from my Evo with the xda app
Click to expand...
Click to collapse
I faced the same probs. But here is a few tips to get back your app:
1. Use titanium backup, run Batch, uninstall those apps that you have moved to ROM (which already highlighted in Red)
2. Find install apks for those apps in Google, reinstall it
3. Reboot your device
4. All app icons have back
Have fun, mate!!
winbytrick said:
I faced the same probs. But here is a few tips to get back your app:
1. Use titanium backup, run Batch, uninstall those apps that you have moved to ROM (which already highlighted in Red)
2. Find install apks for those apps in Google, reinstall it
3. Reboot your device
4. All app icons have back
Have fun, mate!!
Click to expand...
Click to collapse
I had the same problem; with the Android Market app disappeared. I have tried to re-install it the way you suggest, but the app stops working when I start any download from the market. Even reset the phone to factory settings, but I have the same problem. Any clue?
Thanks!!!
I just did a hot restart and it was fine for me.
Sent from my PC36100 using XDA on Fresh 4.3.3
deafcon5 said:
I searched, but didn't find any documentation on this feature, so I did the adventurous thing and tried it out. It's supposed to replace the system apps in the ROM with the updated apk, therefore saving space in the system memory. But after the batch finished, all of the updated apps were completely gone...the originals AND the updates were deleted. Since there isn't a way to "undo" this function, I had to reflash the ROM. Does anyone know more about this option? Does it work with any ROM?
Sent from my Evo with the xda app
Click to expand...
Click to collapse
I was having a similar problem with my Galaxy Note on ICS 4.04.
Whenever I tried to integrate the Play Store it would delete both the update and the old app and I would have to reinstall the APK.
I also noticed recently that a few other updates that appeared to be integrated successfully reappeared in the list of available updates to integrate, like they reverted to user apps after a reboot?
What finally fixed it for me was selecting the option in Titanium Backup Pro *Menu; Preferences; Advanced Settings; Check the box "Auto-integrate sys Dalvik into"
I then did a backup of my launcher app, long pressed on the backup and selected "Convert to System App", then single pressed on the app backup, selected restore then selected app data only"
It prompted me to reboot, after reboot when I checked the"batch, integrate updates into system ROM" all the apps which I was having problems with had disappeared from the list, and appear to be integrated now.
I don't know if it was the reboot or enabling the option in Titanium Backup, but something changed.
I have some problems also
I used Titanium mainly to integrate the updates into rom in my previous htc sensation and in my galaxy s3 and it worked fine with them. Now it does not work properly with my galaxy s4. After the integration some apps crash, Chrome, Dropbox. Some of them only delete the update and leave the old one in rom. If I go to google play the update is there to be installed again or some apps just prompt for the update when opened. I sent an email to the developer but I have not response. I have used it successfully in my previous phones but it is not working in this one. Any help is appreciated.
rdefranx said:
I used Titanium mainly to integrate the updates into rom in my previous htc sensation and in my galaxy s3 and it worked fine with them. Now it does not work properly with my galaxy s4. After the integration some apps crash, Chrome, Dropbox. Some of them only delete the update and leave the old one in rom. If I go to google play the update is there to be installed again or some apps just prompt for the update when opened. I sent an email to the developer but I have not response. I have used it successfully in my previous phones but it is not working in this one. Any help is appreciated.
Click to expand...
Click to collapse
Yep, I'm having this exact problem. First the apps didn't show up, so I performed a hot restart. They're all back now, but Dropbox, Chrome, G+ and others that were integrated are all crashing now.
I imagine it's mostly to so with new security features with the S4. If you're using an S4 please stay away from this feature until it's officially recognised as an issue by the TitaniumBackup developer. I'll reflash PDA shortly and report back if that resolves the problem.
chrisfu said:
Yep, I'm having this exact problem. First the apps didn't show up, so I performed a hot restart. They're all back now, but Dropbox, Chrome, G+ and others that were integrated are all crashing now.
I imagine it's mostly to so with new security features with the S4. If you're using an S4 please stay away from this feature until it's officially recognised as an issue by the TitaniumBackup developer. I'll reflash PDA shortly and report back if that resolves the problem.
Click to expand...
Click to collapse
I did reflash the phone with the stock firmware and everithing is good. I have tried some apps but it did not work. I just leave them there until titanium backup is updated. This is the most used feature for me and now is not working.
rdefranx said:
I used Titanium mainly to integrate the updates into rom in my previous htc sensation and in my galaxy s3 and it worked fine with them. Now it does not work properly with my galaxy s4. After the integration some apps crash, Chrome, Dropbox. Some of them only delete the update and leave the old one in rom. If I go to google play the update is there to be installed again or some apps just prompt for the update when opened. I sent an email to the developer but I have not response. I have used it successfully in my previous phones but it is not working in this one. Any help is appreciated.
Click to expand...
Click to collapse
Titanium Backup's update this week supposedly fixed integrating on Android 4.2. Who's up to try it out?
M3wThr33 said:
Titanium Backup's update this week supposedly fixed integrating on Android 4.2. Who's up to try it out?
Click to expand...
Click to collapse
I will try one of the apps that did not work for me, when I get home. I already updated it today. Thanks
rdefranx said:
I will try one of the apps that did not work for me, when I get home. I already updated it today. Thanks
Click to expand...
Click to collapse
It's been a week. Tried it yet?
M3wThr33 said:
It's been a week. Tried it yet?
Click to expand...
Click to collapse
Sorry, I have been busy to come back. Well, some work, others no. Chrome did not work but I did google Maps, google play, and several other updates. I did not mess with ChatOn since if something goes wrong it could break S voice and S translator. I just did now Google music and Flipboard. Usually I have to reboot in order to have the shortcut in the apps or to fix the name of them. For example, after integrate flipboard is in the drawer with the name and no icon, it launched fine, google music was fine and worked fine. After reboot the icon came back. The only problem is that if does not work then I have to convert the system app to user in order to make it work. Yesterday I converted the jelly bean photosphere camera to system and it was converted but did not work. It force close, then I tried to converted to user app and it took a long time and just was frozen there. I stopped TB but the camera disapear from the drawer, since rebooting fix the icon or name problem, I did it. My phone did not pass the samsung galaxy logo on boot. It was just a black screen after the logo and pressing the power button did not power on or off when I pressed, only when I released. Lucky me that I did a NAND backup before this process and still I could access download mode and the CWM which I used to restore my phone with the backup in my external card. After everything was as before I started. Now I will be more careful when I do this doing a backup before starting.
Samsung Link update integration did not work, force close. Samsung Hub worked but when press the back button to close then force close. Group play seems to work since it opens and go to the start page and no problem when I press the back button.
Still having same problem
Several programs quit working after converting apps to rom. I couldn't get them to work and finally put the locked rom back in, then unlocked it again. I have a verizon galaxy s4 me7 sch-I545 and the update didn't help here.
i want to know if i do this method, does the phone memory will get smaller if i do this again if the system apps getting new update?
hey there,
i have to grab out this thread because i have problems too. almost every app i integrate into system rom force closes, when i try to start it.
even chmod a+x didn't make it better (but the other apps in /system/app are not executable, so this had no sense).
i'm using the latest cm11 nightly for the motorola photon q. is there a known solution?
I have the same issue with this function as rdefranx.
After the integrate process, all updates are fine and i have the old versions again which i have to update. Repeated the process with single apps with showing same results again.
I also sent an so to the developer, but that's a shame: You never ever get an answer if you have a problem with titanium backup.
The app is good and helped me a lot. But shame on the non existing support. Really disappointing and unprofessional. Oh yes: i paid for the app. Thank you.
Hi, I just quit using his feature. I don't know if will work with my note 3 because I don't want to have problems. I will be subscribing to this thread in case a solution is found.
Also happened to me 4 days ago using a Moto X. Except for me it also deleted the Google keyboard & play store among others.
So I was left with no keyboard to type with and no play store to download from. After a factory rest it meant that by having no keyboard I couldn't even type anything on my phone to create a google account to restore the aps & Keyboard with. I had to reflash the whole rom again, and will stay clear of integrating the apks. I did this 4 days ago, so i'm not sure if titanium has updated since then.
Same problem with me. LG G2 Mini Official KK4.4.2 rooted, after Integrating system apps in ROM almost all of them crashing. Don't think that has to do with titanium, but with the android version. I used tha feature on my old LG P350 (stock rom+cm) and worked perfectly. But now in kitkat is messing up. Btw i'm using the latest version of titanium pro
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
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...