Related
The other day I did one really dumb taboo thing everyone knows not to do. I was messing with my phone at 1:30 am doing stupid unproductive things. and then bam, I deleted LG Home. without this I can't go to the homescreen. I backed the apk up but I don't know where to access this. using root unistaller.
Somehow by going to the factory reset screen I managed to make it possible for me to boot the phone back up, only still there is no home screen. I can use google voice to make calls and send texts and emails. But I have no app folder or settings and I am quite a noob.
could Someone either tell me how to reinstall LG Home or get a rom that works back onto my phone. Any solution would be great.
Mreff777 said:
The other day I did one really dumb taboo thing everyone knows not to do. I was messing with my phone at 1:30 am doing stupid unproductive things. and then bam, I deleted LG Home. without this I can't go to the homescreen. I backed the apk up but I don't know where to access this. using root unistaller.
Somehow by going to the factory reset screen I managed to make it possible for me to boot the phone back up, only still there is no home screen. I can use google voice to make calls and send texts and emails. But I have no app folder or settings and I am quite a noob.
could Someone either tell me how to reinstall LG Home or get a rom that works back onto my phone. Any solution would be great.
Click to expand...
Click to collapse
here same problem http://forum.xda-developers.com/showthread.php?t=1256627
You can try to flash this through cwm.
h t t p://w w w.android-files.de/P920/launcherLG.zip
It´s LGHome.apk and LGHome.odex from 21D
well I have the P925g, my brother has the same model. I was thinking I could simply copy the files from his phone into the appropriate folder. Would anyone be able to tell me where I could copy these files from/to? If i could do this I'm sure it would work.
Mreff777 said:
well I have the P925g, my brother has the same model. I was thinking I could simply copy the files from his phone into the appropriate folder. Would anyone be able to tell me where I could copy these files from/to? If i could do this I'm sure it would work.
Click to expand...
Click to collapse
System/app
If you're rooted
Sent from my CM7 Thrill
Well I'm not to sure If it is rooted anymore. I erased all my user data, but I did not factory reset. I'll be checking later if i can access those files. But I'll have to access them via USB connection to my computer. My brothers phone where I'll copy the files from is not rooted so I'm not sure if I can copy them from him or not. I'm going to see what more I can do for my phone tommorow. I hate when this happens. The last time I bricked my phone I couldn't even get to the factory reset screen.
Now that I can get to the factory reset screen I don't even see much use in it because the factory reset option doesn't work like I would have expected. If you can even factory reset through that screen is a mystery to me because I could not get it to work. Every time I tried to initiate factory reset it just went back in the menu and no other button seamed to initiate factory reset. I feel like I'm over looking a lot of options here that I just wouldn't think of trying because of my lack of knowledge here.
I'm very dissapointed in myself and in LG right now.
So I,ve found that I already have the lghome.apk backed up on my phone. but as I cannot go to the homescreen or view files and folders on my phone I'm wondering how I will even launch the apk.
I can still use google voice commands to to other tasks like read emails. is there a way I can access my file system or the market through this?
NVM I checked I don't think it's possible. I cannot use the apk to reinstall the apk because I do not have a home screen or any apps that could open this. even my settings aren't working. and clockwork mod only bricked my phone. so i cannot install rom manager and did not.
Mreff777 said:
So I,ve found that I already have the lghome.apk backed up on my phone. but as I cannot go to the homescreen or view files and folders on my phone I'm wondering how I will even launch the apk.
I can still use google voice commands to to other tasks like read emails. is there a way I can access my file system or the market through this?
Click to expand...
Click to collapse
If you can get into settings, enable USB Debugging Mode.
Then upload LGHome.apk to the forums.
If you could access your emails then you have data connectivity. Why not open market.android.com on your pc log into your google account and install some launcher through it...
Where is the problem to flash this file through cmd ?
h t t p://w w w.android-files.de/P920/launcherLG.zip
or build another update.zip with adwlauncher.apk in it.
I just flashed the first real version of my new rom, and it appears that the settings app is not installed?!?!?! I have no idea why, I can see it in /system/app with the file browser, but it does not show in my app drawer and if I try to install it it tells me I don't allow unknown sources. but if I click change settings it obviously force closes since settings doesn't exist. does anyone have any idea what could cause this?
The exact same thing just happened to me last night! Ironic...
I have not had time to dig into it again yet (hopefully tonight)... but I also had the setup issue and "this is not a blur device" when trying to use the stock home. I partially suspect the moto setup issue is related to cheescake... once i reinstalled cheesecake, switched to the default server, then setup worked fine...
I'll let you know what I find out about settings tonight... you likewise - let me know what you come up with..
Edit- to explain the cheesecake thing... i think I used a backup or some files from one after I had been checking different servers on cheesecake.. so i think the non-default server settings got transferred over.
Anyone know which files cheesecake affects?
Sent from my mind using XDA
So, I was just giving it another go, and for some reason or another, right after I hit build I decided to go back and change an apk - right before I started the zip-align process... and low and behold there was no Settings.apk in the working folder! Very strange.. i don't recall removing it... So, I tossed it back in.
We'll see what happens.. gotta finish up this draft.
Sent from my mind using XDA
I just had this happen to me last week. I flashed a ROM (don't remember the name) then decided I wanted to try Lithium. I didn't read the small print on the post that says you have to flash Lithium 1.2 first, do a full boot into OS, then reboot and flash 1.2.1. When I flashed directly to 1.2.1 I was missing my Settings just like you described.
Dude, I don't know if you figured it out, bricked your phone, or are furiously busy trying to crank out a new ROM... But, i've come to the conclusion that the mysterious missing Settings.apk has something to with the xml edits and/or recompiling the apk. Had another round of flashing, and I made a couple extra update.zips this time along with the full rom.
So, initially after flashing the rom, I went and checked with root explorer and the settings.apk was physically there.. but was not being recognized by the system (I think TB showed it as uninstalled). So, I flashed one of my settingsfix.zips that I made - first the one with my xml edits (that had previously been de/recompiled) - and it was a no go - still not seeing Settings. Then I flashed a version from a Stock set, and that fixed it.
I am still having the Accounts Setup issue though - that's my pain in the... But, I made another setupfix.zip and that helped me skip the Account Setup - I can add google accounts with no problem, but when I try to add a yahoo account I get a login failed... and when I check for software updates through settings and try to setup a moto account, I get connection failed...still suspecting cheesecake.
Edit - Yup. Cheesecake - I just reinstalled it - did not hit the top "install necessary files" button - just switched to the default production server, and then went back to settings to check for system update - and this time the moto account was setup no problem, and my device is up to date... What the heck does cheesecake modify?? Where are those servers listed?
still having the issue. the app is there, but will not be recognized, is it a permissions issue? any idea how to fix it?
Did you try just flashing the Settings.apk only? If that's a no go, then its the apk - if it goes, then it's a problem with the rom building...
I can't figure it out yet but I got all of my settings working, inverted.. I think I started from scratch again but flashed it separately.. I haven't had a chance to dig into it again recently.. but yea.. don't know..
Sent from my mind using XDA
alteredlikeness said:
Did you try just flashing the Settings.apk only? If that's a no go, then its the apk - if it goes, then it's a problem with the rom building...
I can't figure it out yet but I got all of my settings working, inverted.. I think I started from scratch again but flashed it separately.. I haven't had a chance to dig into it again recently.. but yea.. don't know..
Sent from my mind using XDA
Click to expand...
Click to collapse
I tried writing a zip to flash it again after install of the rom. next i guess I will try installing the rom by backup, as that will probably work better. I think flashable zips are much better though. I have been using JRW28's inverted settings app, so Maybe I'll grap a normal one from a stock rom and see how that works.
Try signing the Settings.apk - it worked for me. Here's what I figured out so far if you are decompiling apks... (no need for simple image editing/swapping...)
SIGN:
Settings
PerformanceManager
DON'T SIGN:
BatteryManager
DataManager
framework-res
moto-res
blur-res
SystemUI
Not certain about the **-res.apks and SystemUI since I did those so long ago, but.. I got all inverted settings/task manager/Battery&Data manager working!
alteredlikeness said:
Try signing the Settings.apk - it worked for me. Here's what I figured out so far if you are decompiling apks... (no need for simple image editing/swapping...)
SIGN:
Settings
PerformanceManager
DON'T SIGN:
BatteryManager
DataManager
framework-res
moto-res
blur-res
SystemUI
Not certain about the **-res.apks and SystemUI since I did those so long ago, but.. I got all inverted settings/task manager/Battery&Data manager working!
Click to expand...
Click to collapse
good idea, I'll have to try signing them, I hope this ends up being the problem.
The settings apk looks for a signature that matches the major system apks. If it doesn't match it will not run at boot.
Along with that (I think this helps with the signature check), I placed blur-res, framework-res, moto-res, and SystemUI apks in my \Apk_Manager_5.0.2\other folder, then opened the command line on that folder and set the framework dependees or whatever...
CODE:
apktool if framework-res.apk
(hit Enter)
apktool if blur-res.apk
(hit Enter)...
...for all of the apks
Then do your de/recompiling...
Well, I am baffled again.. I threw those new signed/unsigned apks in a rom build I was working on, flashed it, and Setting.apk was missing again... So, I flashed the small update zip with inverted Settings.apk and PerformanceManager.apk I made earlier that day and flashed successfully while on stock. And, Settings.apk came back (and was inverted), but Task Manager force closes - then I tried to flash a restore zip (with stock settings and task manager) - and it restores Settings, but doesn't fix the task manager - So, needless to say, I am back to square one in my understanding of all of this. I am assuming it is merely a signature check issue somehow??
Like I said, I had everything working yesterday on stock 2.3.6 after flashing a small update.zip with new signed Setting.apk and PerformanceManager.apk, and another one with unsigned battery and data manger apps.. Ended up restoring back to stock by the end of the day, and now today those same zip packages don't work like they did yesterday... Are new signatures created each time when the system is installed (or re-installed)? It was the exact same system restore on which I built the new inverted apks - so, I am very confused.
I will get to the bottom of this.. but, if anyone can shed some more light on the situation, that'd be great...
still no luck here either. I got my stuff working as a cwm backup, but it won't boot passed the boot logo (motorola M) now, so who knows. I am busy right now, but after next week I should have a lot more time to work on this.
Just tried another restore.zip, but nothing fixes Task Manager for me now.. Could it be that something is created in /data based on the apk in /system? So, when I flash older stock versions it doesn't fix it, since some link has been created outside of the apk?
Another thing possibly worth noting is that I am working with .apks and their .odex counterparts... but, that shouldn't be making a difference since I am not messing with the odex files.. plus, you've got similar problems, and I am assuming you are working with deodexed apks...
alteredlikeness said:
Just tried another restore.zip, but nothing fixes Task Manager for me now.. Could it be that something is created in /data based on the apk in /system? So, when I flash older stock versions it doesn't fix it, since some link has been created outside of the apk?
Another thing possibly worth noting is that I am working with .apks and their .odex counterparts... but, that shouldn't be making a difference since I am not messing with the odex files.. plus, you've got similar problems, and I am assuming you are working with deodexed apks...
Click to expand...
Click to collapse
yep, I'm using jrw28s inverted settings
Sent from my MB865 using XDA
OK.. Did a little more researching.. And, I think you need to resign all of the moto system apks with the same key.. then the signatures should match up, and apps shouldn't fail to be recognized...
I believe this is only if you are editing the AndroidManifest.xml, otherwise you can just copy the META-INF folder from the original apks with 7zip to retain the signature...
Not sure about the details and if it will actually work, also not sure exactly which apks to re-sign (probably the major 4), but that's my next game plan... trial and error... still trying to make sense of it all.
good idea, I'll have to try signing them, I hope this ends up being the problem.
What I discovered (through numerous trials and error) is that you can't mess with the AndroidManifest.xml... Something gets messed up with the signature (i.e. it doesn't match the framework signatures, or maybe it needs to match all of the moto apk sigs - not sure yet - because sometimes it worked when I pushed them separately), and the system doesn't recognize the apk.
But once I got re-did all of the apks without editing the AndroidManifest - all of my problems went away. I still was able to decompile the apks and edit /res/values xmls, just not that manifest..
So, as for the OP's problem, it looks like JRW's inverted Settings.apk (which were probably created by editing the AndroidManifest), is not matching the signatures of the other major apks in your ROM..
I will still try to figure out how to safely edit the manifest when I get around to it... any hints from JRW28 would be great! Is that the reason you had to originally make a separate update.zip for the inverted settings in Lithium?
Side note, I also figured out my setup issues... it was cheesecake related, along with my Settings.apk missing.
A couple of things finally clicked for me two nights ago...
alteredlikeness said:
What I discovered (through numerous trials and error) is that you can't mess with the AndroidManifest.xml... Something gets messed up with the signature (i.e. it doesn't match the framework signatures, or maybe it needs to match all of the moto apk sigs - not sure yet - because sometimes it worked when I pushed them separately), and the system doesn't recognize the apk.
But once I got re-did all of the apks without editing the AndroidManifest - all of my problems went away. I still was able to decompile the apks and edit /res/values xmls, just not that manifest..
So, as for the OP's problem, it looks like JRW's inverted Settings.apk (which were probably created by editing the AndroidManifest), is not matching the signatures of the other major apks in your ROM..
I will still try to figure out how to safely edit the manifest when I get around to it... any hints from JRW28 would be great! Is that the reason you had to originally make a separate update.zip for the inverted settings in Lithium?
Side note, I also figured out my setup issues... it was cheesecake related, along with my Settings.apk missing.
A couple of things finally clicked for me two nights ago...
Click to expand...
Click to collapse
Thanks, not sure whether I am even going to continue with this or not. With ics stuff starting to roll in I might save my time for that.
Did anyone try to backup the way suggested in this thread?
It'd be great, if it worked: a full backup (apps, settings, everything) without needing to root. I'm trying this right now, but when the phone prompts me to allow backup I tap on the "allow backup" button but it's if it weren't tapped (nothing happens, not even the tapping animation).
Someone tried this?
Edit: it would also allow access to some files that are unaccessible without root...
nor-ric said:
Did anyone try to backup the way suggested in this thread?
It'd be great, if it worked: a full backup (apps, settings, everything) without needing to root. I'm trying this right now, but when the phone prompts me to allow backup I tap on the "allow backup" button but it's if it weren't tapped (nothing happens, not even the tapping animation).
Someone tried this?
Edit: it would also allow access to some files that are unaccessible without root...
Click to expand...
Click to collapse
I've tried by running the various adb backup options manually on Stock 2.21, but haven't had much luck, although got further than you. It will get part of the way through the backup, but silently errors out after a few packages and shows backup complete (when I know it isn't). Removing a problem app just results in it failing on the next one. On my Nexus 7 it works as expected, so there may be a bug in the stock version. Would be interesting if someone with CM or anything non stock could comment.
will1987 said:
I've tried by running the various adb backup options manually on Stock 2.21, but haven't had much luck, although got further than you. It will get part of the way through the backup, but silently errors out after a few packages and shows backup complete (when I know it isn't). Removing a problem app just results in it failing on the next one. On my Nexus 7 it works as expected, so there may be a bug in the stock version. Would be interesting if someone with CM or anything non stock could comment.
Click to expand...
Click to collapse
Agree, would be interesting to see if the issue is related to HTC rom.
I've read on the Nexus 7 subforum that a user is stuck at my same point. I wonder what's causing this...
I had no luck either, although it has been awhile since I tried. I thought I read something on the original documention that made it sound like I wouldn't have any luck. Forget what it was now--
I was able to get this to work with my wifes stock unrooted one s (still on android 4.03 and sense 4.0).
in developer options you need to specify a password BEFORE you start the backup and enter that password on the "full backup" start screen.
i also couldnt get it to create a file for the backup in C:\ so i created a folder, and put it in there, but made sure to check permissions and that the folder was not read only.
I havent restored the data yet, but actually getting the backup file and it being an appropriate size (about 680mb), i would say i am optimistic about the results.
I will report back after i root and update the OS.
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.
__