How to modify Android app so it thinks it was installed from Google Play

Does anyone know how to edit the information about which app is the installer? Recently Revolut joined the ranks of idiots and is checking whether the app was installed from Google Play and refuses to start if not.

Where is this information stored on SFOS? Can it be edited?

I got an app working by changing the installer method in aurora store from session installer to native installer

2 Likes

That didn’t work, sadly, the app refuses to install with native installer.

not sure if that helps, downgrade your Revolut app to an older version e.g. before 08/03 that should work for now, but it seems newer releases will have that problem unfortunately.

Figured this one myself. The method by @thigg works for some cases but if the app uses a bundle, native installer doesn’t work.

In that case it’s a little more complicated, you need terminal access and all that fun.

Before you start, you should stop the Android support, this shouldn’t be done on a phone with Android support running.

You need to edit the file /home/.android/data/system/packages.xml (for example by using the nano command). I strongly advise to backup this file before making any edits, if you do something wrong, you’ll break your Android installation and you’ll have to reinstall App Support and all Android apps.

There find a block with the app’s internal name (in my case it was com.revolut.revolut). There may be multiple results for this search term, find the one that has codePath, nativeLibraryPath and other such properties. On that exact line find this: installer="com.aurora.store" installInitiator="com.aurora.store" (it might be slightly different depending on what is the installer, this is an example for an app from Aurora Store). Replace the com.aurora.store (or whatever your entry says) with com.android.vending for both options.

Afterwards save the file and start the Android support, the app should now think it came from the Play Store.

22 Likes

Hello Rikudou_Sennin,

It did not work.I ask myself, if I am the only one just because I used unofficial app many weeks ago. Ist that being banned? I still can use WA on an Android device, verification doesn’t workon neither on another device. Strange…

Have you also cleared the cache and data of the Android app?

1 Like

Tested it. Doesn’t work

Does this method still work with the latest SFOS?

Funny enough, I needed to do it just two hours ago.

The path to the file changed, it’s /home/.appsupport/instance/defaultuser/data/system/packages.xml

Note that if your goal is Revolut, it no longer works because they added more checks than just the origin of the app.

9 Likes

Just a heads-up: This doesn’t work anymore on 5.0.0.73 because the packages.xml is no longer a raw XML file but Android’s custom ABX (Android Binary XML) format.

Possibly even on older versions if they got the update to Android 13 sooner.

2 Likes

Well, made an app for that: AAS Installer Patcher | OpenRepos.net — Community Repository System

4 Likes

Not working on first try w/ consors banking.
Installed AAS IP, installed Consors banking App, changed installation source to GPS, Error A00053 persists.

Some Apps seem to ckeck more than the installation source.

I got as far as this, though I don’t have an account with them nor do I speak German. Does the check appear further down the process?

But yeah, if it checks SafetyNet or something, it won’t pass, this only helps with one exact use case and that is when apps specifically check where they were installed from.

1 Like

Yes, I get to enter account and pw, after verification, it drops a message about the untrusted source.

Hmm, the comment says that it worked by faking the installer which is essentially what the app does: Banking app refuses to launch due to untrusted store - GrapheneOS Discussion Forum

If you open the AAS Installer Patcher, what do you see as the installer for the bank?

Edit: I added a new version of AAS Installer Patcher to OpenRepos, try setting the installer to Aurora (or something) and then back to Google Play. But if it doesn’t help, it’s not a simple check that can be circumvented like this.

Install with options android app can do that. But I guess @Rikudou_Sennin 's app achieves the same functionality.

I updatet to AAS IP 1.01
After initial install, I see Aurora, that is correct.
I switched to “GPS” and also to “package installer”, the same error appeared.