Database Info

[App]GMail from Android 4.2

This is a leaked version from Android 4.2
There are new features and seems to be working on Android 4.0+
Enjoy! Not my work, I take no credit, just passing it along

Hows everyone liking it? Swipe to delete is great! Any bugs out there?

The link in that thread was removed but here it is
Installation Option 1:
]
Uninstalled old apk with Titanium -> Reboot -> Installed new Gmail apk with explorer -> Reboot - Done
Click to expand...
Click to collapse
Installation Option 2:
The Gmail 4.2 APK is signed by Google, but with a different key than the one in the Play Store (we checked the signatures - they differ). One is probably the test key and the other the production key. For this reason, you can't simply install it as an update and therefore need to be rooted with the ability to mount the /system directory for writing in order to remove the existing Gmail APK.
OK, let's get down to it. You'll probably need ADB installed on your computer (here's an easy way that doesn't require downloading the Android SDK). There is a chance that this might work without ADB by just removing the APKs mentioned below and installing the new one, but it didn't seem to work reliably for everyone. This should, though:
1. Download Gmail 4.2 from one of the mirrors above.
2. Rename it to Gmail2.apk.
3. Make a Nandroid backup in case something goes wrong (this is always a good thing to do before messing with your device).
4. Delete (or move if you want to save the APKs) all other versions of Gmail. Usually there are 2 or 3 copies. One will be in /system/app (that's the original Gmail that was pre-installed on the device) and there may be a few in /data/app (these are the updates installed from the Play Store). They'll be called "Gmail.apk," or "com.google.android.gm-[number].apk," An easy way to tell is to look for the Gmail icon.
5. You may need to delete the .odex files matching the APKs in step 4 too, if you have them. Neither I nor Artem had to do this, but there are many different ROMs out there, and we're trying to cover all bases. Ignore this step and only come back to it if something doesn't work later.
6. Reboot. Once you do, you should have no Gmail as far as Android is concerned.
7. You can try to install the Gmail 4.2 APK you downloaded at this point by tapping it in your favorite file explorer (move the APK to your device first, of course). If that doesn't work, or if you prefer ADB, fire up a command line and type adb install Gmail2.apk.
If you get an error message, you probably didn't delete all copies of Gmail. If you don't feel like playing with ADB for Step 7, I've also gotten it to work by just copying the APK to /data/app, but that's not as fool proof as "ADB install".
Click to expand...
Click to collapse
All instructions taken from the original post, just posting them here to help you guys

Neverendingxsin said:
The link in that thread was removed but here it is
Click to expand...
Click to collapse
Thanks!

speedybishi said:
Thanks!
Click to expand...
Click to collapse
No problem

I like it. Pinch to zoom is nice and swipe is also. Hope to start seeing this in a few roms.
Sent from my SCH-I535 using Xparent Blue Tapatalk 2

Is it just me...or can we only access our inbox with this gmail. No outbox/sent items...trash or anything?
Sent from my SCH-I535 using xda app-developers app

duarian said:
Is it just me...or can we only access our inbox with this gmail. No outbox/sent items...trash or anything?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
It's working fine for me. Just now checked. You have to hit the label looking icon to change sections. Thats on the bottom right corner.

Neverendingxsin said:
It's working fine for me. Just now checked. You have to hit the label looking icon to change sections. Thats on the bottom right corner.
Click to expand...
Click to collapse
Ah! That's it. Alright I take that back. Works great. Refresh animation doesn't work for me but it does refresh either way. Thanks!
Sent from my SCH-I535 using xda app-developers app

It won't let me install?
Sent from my SCH-I535 using xda app-developers app

kichard said:
It won't let me install?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
great, did the same for me, so i used titanium to un-install gmail and then tried to install it, still get an error. Now ti is not restoring my gmail.

Uninstall Gmail with TB.
REBOOT.
Install 4.2 Gmail
I had that same error at first too. You have to Reboot after uninstalling with TB before you install the new one

TokedUp said:
Uninstall Gmail with TB.
REBOOT.
Install 4.2 Gmail
I had that same error at first too. You have to Reboot after uninstalling with TB before you install the new one
Click to expand...
Click to collapse
Ok, I may try that. After it hung re-installing gmail, I rebooted and my screen said updating and then I had gmail again. I'm on stock. Is that an issue?

kichard said:
It won't let me install?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I personally used root explorer and changed the original gmail apk to Gmail2.bak (yours may either be in system/app or data/app) mine was in data/app because im using AOSP, for stock touchwiz it might be in system/app. For AOSP its probably going to be named com.gmail.apk or something along the lines of that. Anyways after you delete/rename your original one move the 4.2 Gmail2.apk to system/app, set the permissions and reboot. It MUST be in system/app and you have to set the permissions and reboot for it to work
---------- Post added at 12:25 PM ---------- Previous post was at 12:22 PM ----------
Installation Option 1:
Originally Posted by uwdus
Uninstalled old apk with Titanium -> Reboot -> Installed new Gmail apk with explorer -> Reboot - Done
Click to expand...
Click to collapse
Installation Option 2:
The Gmail 4.2 APK is signed by Google, but with a different key than the one in the Play Store (we checked the signatures - they differ). One is probably the test key and the other the production key. For this reason, you can't simply install it as an update and therefore need to be rooted with the ability to mount the /system directory for writing in order to remove the existing Gmail APK.
OK, let's get down to it. You'll probably need ADB installed on your computer (here's an easy way that doesn't require downloading the Android SDK). There is a chance that this might work without ADB by just removing the APKs mentioned below and installing the new one, but it didn't seem to work reliably for everyone. This should, though:
1. Download Gmail 4.2 from one of the mirrors above.
2. Rename it to Gmail2.apk.
3. Make a Nandroid backup in case something goes wrong (this is always a good thing to do before messing with your device).
4. Delete (or move if you want to save the APKs) all other versions of Gmail. Usually there are 2 or 3 copies. One will be in /system/app (that's the original Gmail that was pre-installed on the device) and there may be a few in /data/app (these are the updates installed from the Play Store). They'll be called "Gmail.apk," or "com.google.android.gm-[number].apk," An easy way to tell is to look for the Gmail icon.
5. You may need to delete the .odex files matching the APKs in step 4 too, if you have them. Neither I nor Artem had to do this, but there are many different ROMs out there, and we're trying to cover all bases. Ignore this step and only come back to it if something doesn't work later.
6. Reboot. Once you do, you should have no Gmail as far as Android is concerned.
7. You can try to install the Gmail 4.2 APK you downloaded at this point by tapping it in your favorite file explorer (move the APK to your device first, of course). If that doesn't work, or if you prefer ADB, fire up a command line and type adb install Gmail2.apk.
If you get an error message, you probably didn't delete all copies of Gmail. If you don't feel like playing with ADB for Step 7, I've also gotten it to work by just copying the APK to /data/app, but that's not as fool proof as "ADB install".
Click to expand...
Click to collapse
All instructions taken from the original post, just posting them here to help you guys

The TI method worked wonderfully, thanks boys and girls.

Thank yo:thumbup:

TokedUp said:
Uninstall Gmail with TB.
REBOOT.
Install 4.2 Gmail
I had that same error at first too. You have to Reboot after uninstalling with TB before you install the new one
Click to expand...
Click to collapse
Yep, worked now too. Thanks

Gotta lock this up,the new app is considered warez. Google doesn't want this being distributed.

PocketTV Rooted

PocketTV Rooted
Looking to root that PocketTV you just received (or should be receiving in a few days)? Well, here you go, it's quite simple:
1) Download the root zip: http://bit.ly/U0QrvS
2) Place it on to the sdcard you're using
3) Start up your PocketTV, go to the "Upgrade" app
4) Select the zip you just downloaded, and install it
5) Upon reboot, make sure to update both the su binary and Superuser.apk
6) If you wish to install busybox, there are apps on the Play Store
WARNING: there are no stock images for this device, if you break your /system or boot.img there may be no way to recover (ie bricked); I am not responsible for this happening, so be careful.
Source: https://plus.google.com/u/0/113601948978986762347/posts/T5VfLcfJ1Q2

Successfully rooted
This is working.. you are the man!!!

CEnnis91 said:
PocketTV Rooted
Looking to root that PocketTV you just received (or should be receiving in a few days)? Well, here you go, it's quite simple:
1) Download the root zip: http://bit.ly/U0QrvS
2) Place it on to the sdcard you're using
3) Start up your PocketTV, go to the "Upgrade" app
4) Select the zip you just downloaded, and install it
5) Upon reboot, make sure to update both the su binary and Superuser.apk
6) If you wish to install busybox, there are apps on the Play Store
WARNING: there are no stock images for this device, if you break your /system or boot.img there may be no way to recover (ie bricked); I am not responsible for this happening, so be careful.
Source: https://plus.google.com/u/0/113601948978986762347/posts/T5VfLcfJ1Q2
Click to expand...
Click to collapse
Cool as hell that you rooted it. But other than titanium backup, what else do you plan on doing with this ability? I have one as well, and I've been trying to figure out ways to get the ui to feel a bit smoother.

ghostknyght said:
Cool as hell that you rooted it. But other than titanium backup, what else do you plan on doing with this ability? I have one as well, and I've been trying to figure out ways to get the ui to feel a bit smoother.
Click to expand...
Click to collapse
Need root to use play station controller with it!!

Verizon Galaxy S III (d2vzw): Persistent Google Wallet [ROOT]

__
__

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.

__

[HOW TO] Google Wallet working on Photon Q

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...

Your Phone is Locked Because the Payment Service was Uninstalled

If you ever lock Your Samsung because of disabling Samsung Payments or by debloating and You have TWRP installed here is a fix.
Boot to TWRP and using File Manager copy data/system/users/0/package-restrictions.xml to SD and then copy this file to PC to and open in notepad or any text editor.
Remove <pkg name="com.samsung.android.kgclient" ceDataInode="-4294836077" enabled="3" enabledCaller="0/" /> line from the file. It can have different values but package name must be the same. Remove whole line, save file and place it back to data/system/users/0/. I suggest to delete old package-restrictions.xml and package-restrictions.xml.bak before placing back edited file.
That's it, phone should be unlocked now.

Thank you! This saved me from several hours of tweaking this stupid samsung security.

Thank you @Chamelleon! I was about to get in to a full reflash stock, reroot, reinstall situation. Damn, I love xda!
BTW, the thing I did differently was to remove the three lines inclusive of
<disabled-components>
<item name="com.samsung.android.kgclient.receiver.KGAgentReceiver" />
</disabled-components>
...and changed enabled="3" to enabled="1" in this line
<pkg name="com.samsung.android.kgclient" ceDataInode="2643" enabled="1"
Probably not required, but thought I'd mention it.
Galaxy Tab S6
Android 9
Stock-Rooted

i cant find the line even if i search it

I tried attempted to debloat an S8 (running Pie), but I started receiving this message afterwards. There's no “com.samsung.android.kgclient” in the package-restrictions.xml file. Is there any other place this restriction could be enforced?

Found Another Way 2
in my case i copied the file package restrictions but did not found the line or the package in it.
What I Did
1. download the Samsung payment services apk from apkmirror.com
2. installed this app as a system app using lucky patcher.
Note: i guess we can use the adb tool too to install apps as system apps.
3. Nothing just restart and done.
Also this can be overcome in every restart without installing the above app. As you may have noticed device waits some time after the restart before pushing the notification and locking the device. What i found is that if we restart the SystemUI it disables the lock and does not show it up until next restart.
Enjoy and Keep Sharing.

I went in and deleted package-restrictions.xml and the bak file, I can reboot now and get in with the message, I initially uninstalled payment services, I tried flashing a zip of payment services apk couldn't get that going, now I'm getting android set up pop ups and my twrp won't boot to the recovery loader from within the app, and super su has lost all the settings for applications!?¿ rlly don't want to do a clean flash and re root ... bloody system packages arggghf help

Wow, this was easy. Thanks!

harismuntazir said:
in my case i copied the file package restrictions but did not found the line or the package in it.
What I Did
1. download the Samsung payment services apk from apkmirror.com
2. installed this app as a system app using lucky patcher.
Note: i guess we can use the adb tool too to install apps as system apps.
3. Nothing just restart and done.
Also this can be overcome in every restart without installing the above app. As you may have noticed device waits some time after the restart before pushing the notification and locking the device. What i found is that if we restart the SystemUI it disables the lock and does not show it up until next restart.
Enjoy and Keep Sharing.
Click to expand...
Click to collapse
Hi..how to restart system ui within so limited time

Chamelleon said:
If you ever lock Your Samsung because of disabling Samsung Payments or by debloating and You have TWRP installed here is a fix.
Boot to TWRP and using File Manager copy data/system/users/0/package-restrictions.xml to SD and then copy this file to PC to and open in notepad or any text editor.
Remove <pkg name="com.samsung.android.kgclient" ceDataInode="-4294836077" enabled="3" enabledCaller="0/" /> line from the file. It can have different values but package name must be the same. Remove whole line, save file and place it back to data/system/users/0/. I suggest to delete old package-restrictions.xml and package-restrictions.xml.bak before placing back edited file.
That's it, phone should be unlocked now.
Click to expand...
Click to collapse
i cant find this xml anywhere, please help

Any advice if twrp isn't yet installed but device is already rooted?

Solution is to reboot to Samsung recovery and factory reset. Worked for me.

JoshReuben said:
Solution is to reboot to Samsung recovery and factory reset. Worked for me.
Click to expand...
Click to collapse
luckily factory reset solves it. i was already getting anxious about paying "ransomware" to samsung service oof
thanks

but my TWRP doesnt mount data

CANDco said:
but my TWRP doesnt mount data
Click to expand...
Click to collapse
Only hard reset can fix Your phone then. If TWRP can't mount data it means that your phone is encrypted and without full wipe you won't be able to unlock it.

Thanks! I just fixed my m51 with this method. I was thinking about restoring full TWRP backup or flashing stock rom as last resort. So glad I found this thread.

I don't know what is wrong with my phone. I disabled the app, and got the message. I did what you suggested and rebooted. but the app re-enabled itself. I tried disabling again and the message came up again. I checked and that line is no longer in my package-restrictions.xml
Luckily for me, just rebooting unlocks my phone, but I think that defeats the purpose....
I kinda want to get rid of that app

adb shell pm enable com.samsung.android.kgclient
will solve the problem

jafferkhan said:
i cant find this xml anywhere, please help
Click to expand...
Click to collapse
Man, that was a trip to do, but on my unlocked S9+, it worked! I could only see the exact file when I opened the .xml file with wordpad on my Win. 10 to edit it, otherwise it's very hard to spot scrolling in TWRP on the device, particularly since the long package list can freeze up while you scroll down.
I should add, that I used an OTG USB Bridge with a type C connector to paste the copied .xml file to the connected flash drive I mounted in TWRP (just scroll up through the directories for "OTG USB' to find the drive to paste it), then put it on my PC, this made the process go even faster.
But it's better to proactively check what apps can be disabled, removed, or in my case frozen with Titanium Pro, before ever having to deal with such a scare as this!

Chamelleon said:
If you ever lock Your Samsung because of disabling Samsung Payments or by debloating and You have TWRP installed here is a fix.
Boot to TWRP and using File Manager copy data/system/users/0/package-restrictions.xml to SD and then copy this file to PC to and open in notepad or any text editor.
Remove <pkg name="com.samsung.android.kgclient" ceDataInode="-4294836077" enabled="3" enabledCaller="0/" />line from the file. It can have different values butIpackage name must be the same. Remove whole line, save file and place it back to data/system/users/0/. I suggest to delete old package-restrictions.xml and package-restrictions.xml.bak before placing back edited file.
That's it, phone should be unlocked now.
Click to expand...
Click to collapse
What are procedures on how to remove the file after disabling the package, my Samsung A03 CORE can't mount. So kindly assist me here..