• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[APP] Android Market patched to skip self-update and remove device restrictions

Search This thread

Tsjoklat

Senior Member
Apr 5, 2010
1,705
2,386
All versions of the Android Market (Play Store) above version 3.0 will self-update automatically (even if you freeze/rename/delete the Market Updater application). The following version of the Android Market has been patched to ignore the self-update check.

Note: Android Market (Google Play Store) v3.4.7 is the last available version that allows Titanium Backup to control the Market links in the application.

Note: Using the command "pm disable com.android.vending.updater" does NOT stop the Android Market 3.0+ from self-updating. Other methods of preventing the market from self-updating, such as creating a read-only file that blocks the installation procedure, are also not recommended because the market will still download market updates and use up precious internal memory and extra cpu cycles.

Code:
diff -ru Vending.3.4.7/smali/com/google/android/finsky/utils/SelfUpdateScheduler.smali Vending.3.4.7-noupdate/smali/com/google/android/finsky/utils/SelfUpdateScheduler.smali
--- Vending.3.4.7/smali/com/google/android/finsky/utils/SelfUpdateScheduler.smali	2012-04-04 02:21:11.729877751 +0200
+++ Vending.3.4.7-noupdate/smali/com/google/android/finsky/utils/SelfUpdateScheduler.smali	2012-04-04 02:33:51.870385096 +0200
@@ -29,7 +29,7 @@
     invoke-direct {p0}, Ljava/lang/Object;-><init>()V
 
     .line 42
-    const/4 v0, 0x0
+    const/4 v0, 0x1
 
     iput-boolean v0, p0, Lcom/google/android/finsky/utils/SelfUpdateScheduler;->mUpdateInProgress:Z


Logcat of Android Market with "noupdate" patch applied:

Code:
D/Finsky  ( 4890): [1] SelfUpdateScheduler.checkForSelfUpdate: Skipping self-update check as there is an update already queued.

Note: Also provided below is an additional variation of the Android Market that includes an additional "no restrictions" patch applied. The additional patch removes restrictions on certain applications in the market placed by specific countries. If the country you live in has blocked the application you are looking for, this patch will allow you to see it in the market. There are still server side restrictions in place when you download an application that is blocked within your country and the use of a proxy or VPN might also be necessary. The "no restrictions" patch also removes the device application compatibility check, so every application should be visible in the Android Market (even if they "say" it is not compatible with your device). Credits to L.D.B. for the "no restrictions" patch.

Code:
diff -ru Vending.3.4.7/smali/com/google/android/finsky/api/model/Document.smali Vending.3.4.7.mod/smali/com/google/android/finsky/api/model/Document.smali
--- Vending.3.4.7/smali/com/google/android/finsky/api/model/Document.smali	2012-04-05 21:49:58.647890272 +0200
+++ Vending.3.4.7.mod/smali/com/google/android/finsky/api/model/Document.smali	2012-04-05 21:49:20.751889471 +0200
@@ -3236,6 +3236,8 @@
     .line 674
     :cond_0
     :goto_0
+    const/4 v2, 0x1
+
     return v2
 
     .line 662

Note: A third patch for the Android Market is the "DPI 160" patch. If you change the default DPI settings on your device, the Android Market might not detect the required DPI settings and specific applications will then not be visible in the Android Market. The "DPI 160" patch forces the Android Market to think you are using a DPI of 160, which makes specific applications in the Android Market visible.

Code:
diff -ru Vending.3.4.7.orig/smali/com/google/android/finsky/utils/DeviceConfigurationHelper.smali Vending.3.4.7/smali/com/google/android/finsky/utils/DeviceConfigurationHelper.smali
--- Vending.3.4.7.orig/smali/com/google/android/finsky/utils/DeviceConfigurationHelper.smali	2012-04-10 23:06:45.156379816 +0200
+++ Vending.3.4.7/smali/com/google/android/finsky/utils/DeviceConfigurationHelper.smali	2012-04-10 23:06:55.795879255 +0200
@@ -257,7 +257,7 @@
 
     move-result-object v15
 
-    iget v0, v12, Landroid/util/DisplayMetrics;->densityDpi:I
+    const/16 v0, 0xa0
 
     move/from16 v17, v0

Note: A "DPI 240" patch is also posted below. Some high resolution devices (ie; HTC Desire and Samsung Galaxy SII) require a 240 DPI in order for certain applications to be visible in the Android Market. The "DPI 240" patch forces the Android Market to think the device is using a DPI of 240.

Code:
diff -ru Vending.3.4.7.orig/smali/com/google/android/finsky/utils/DeviceConfigurationHelper.smali Vending.3.4.7/smali/com/google/android/finsky/utils/DeviceConfigurationHelper.smali
--- Vending.3.4.7.orig/smali/com/google/android/finsky/utils/DeviceConfigurationHelper.smali	2012-04-10 23:06:45.156379816 +0200
+++ Vending.3.4.7/smali/com/google/android/finsky/utils/DeviceConfigurationHelper.smali	2012-04-10 23:06:55.795879255 +0200
@@ -257,7 +257,7 @@
 
     move-result-object v15
 
-    iget v0, v12, Landroid/util/DisplayMetrics;->densityDpi:I
+    const/16 v0, 0xf0
 
     move/from16 v17, v0

Note: Similar to the previous DPI patches, a "DPI 320" patch is also posted below. Some of the higher WXGA resolution devices (ie; Galaxy Nexus) require a 320 DPI in order for certain applications to be visible in the Android Market. The "DPI 320" patch forces the Android Market to think the device is using a DPI of 320.

Code:
diff -ru Vending.3.4.7.orig/smali/com/google/android/finsky/utils/DeviceConfigurationHelper.smali Vending.3.4.7/smali/com/google/android/finsky/utils/DeviceConfigurationHelper.smali
--- Vending.3.4.7.orig/smali/com/google/android/finsky/utils/DeviceConfigurationHelper.smali	2012-04-10 23:06:45.156379816 +0200
+++ Vending.3.4.7/smali/com/google/android/finsky/utils/DeviceConfigurationHelper.smali	2012-04-10 23:06:55.795879255 +0200
@@ -257,7 +257,7 @@
 
     move-result-object v15
 
-    iget v0, v12, Landroid/util/DisplayMetrics;->densityDpi:I
+    const/16 v0, 0x140
 
     move/from16 v17, v0

If your device is using a custom DPI setting, then you will need a version of the Android Market that includes one of the three "DPI Hacks" mentioned above (dpi160, dpi240, or dpi320). Without the "DPI Hack" applied, updates might not be visible in the Market.

The default DPI value for your device can be determined by looking it up in it's device specifications. When you change the default DPI setting on your device, it may cause compatibility problems for the Android Market. Therefore, we want the Android Market to think we are still using the same default value that is found in the specs.

For example, the Samsung Galaxy SII has a default DPI of 240 in it's device specifications, so we want to make the Android Market think we are still using that setting (if the default value has been modified).

For most devices, the standard default DPI values are 160, 240, and 320.

All modified versions of the Android Market that are signed by another key are unable to make purchases from within the Android Market application itself because the signing key does not match Google's signing key. Because the new signing key of the modified Android Market no longer matches with Google's signing key, the modified version of the Android Market is unable to connect with GoogleServicesFramework. There are also modified versions of the Android Market available (in post #132 of this thread) that are made using the original Google signature which makes it possible to purchase applications again within the modified Android Market.
http://forum.xda-developers.com/showpost.php?p=26102810&postcount=132

All applications can still be purchased via the web browser.

How to install:

Rename file to "Vending.apk" and copy to /system/app/Vending.apk. Make sure to uninstall any updates of previous versions first. Root Required. If you are running ICS 4.0.4, "Vending.apk" might be substituted for "Phonesky.apk".

NOTE: If you are testing a "DPI Hacked" version of the Android Market and you are still experiencing incompatibilities with certain applications or the changes are not "sticking", see post #92 in this thread for further solutions. The following link explains what additional patches may be needed: http://forum.xda-developers.com/showpost.php?p=25720539&postcount=92

Additionally, the following links contain modified versions of GSF uploaded to this thread:
http://forum.xda-developers.com/showpost.php?p=29401924&postcount=334
http://forum.xda-developers.com/showpost.php?p=30074336&postcount=390
http://forum.xda-developers.com/showthread.php?t=1631070
http://forum.xda-developers.com/showpost.php?p=26423837&postcount=161

** Google Play 3.4.4 with "market purchase fix and dpi120" has been added to the following link: http://forum.xda-developers.com/showpost.php?p=31027248&postcount=460

** Google Play 3.4.7/3.5.19 with "market purchase fix" has been added to the following link:: http://forum.xda-developers.com/showpost.php?p=26102810&postcount=132

** Google Play 3.7.11 has been added to the following link: http://forum.xda-developers.com/showpost.php?p=28029688&postcount=222

** Google Play 3.7.13 has been added to the following link: http://forum.xda-developers.com/showpost.php?p=28207664&postcount=243

** Google Play 3.7.15 has been added to the following link: http://forum.xda-developers.com/showpost.php?p=29466370&postcount=344

** Google Play 3.8.15 has been added to the following link: http://forum.xda-developers.com/showpost.php?p=30317127&postcount=399

** Google Play 3.8.16 has been added to the following link: http://forum.xda-developers.com/showpost.php?p=30387825&postcount=409

** Google Play 3.8.17 has been added to the following link: http://forum.xda-developers.com/showpost.php?p=30563737&postcount=436

** Google Play 3.9.16 has been added to the following link: http://forum.xda-developers.com/showpost.php?p=32768509&postcount=505

** Google Play 3.9.17 has been added to the following link: http://forum.xda-developers.com/showpost.php?p=33747629&postcount=544

** Google Play 3.10.9 has been added to the following link: http://forum.xda-developers.com/showpost.php?p=34774989&postcount=566

** Google Play 3.10.10 has been added to the following link: http://forum.xda-developers.com/showpost.php?p=35741543&postcount=599

** Google Play 3.10.14 has been added to the following link: http://forum.xda-developers.com/showpost.php?p=38633857&postcount=660

** Google Play 4.0.25 has been added to the following link: http://forum.xda-developers.com/showpost.php?p=40237365&postcount=694

** Google Play 4.0.26 has been added to the following link: http://forum.xda-developers.com/showpost.php?p=40822664&postcount=705

** Google Play 4.0.27 has been added to the following link: http://forum.xda-developers.com/showpost.php?p=40823085&postcount=706

** Google Play 4.3.10 has been added to the following link: http://forum.xda-developers.com/showpost.php?p=44365806&postcount=769
 
Last edited:

Tsjoklat

Senior Member
Apr 5, 2010
1,705
2,386
I think my browser did not upload the file properly the first time. I have re-uploaded it and verified it this time. Thanks for letting me know.
 
Last edited:
  • Like
Reactions: fitz420

haggardh

Senior Member
Feb 1, 2011
122
11
Memphis, TN
What browser are you using? Chrome on the phone has problems with downloading apks

Sent from my HTC PH39100 using xda premium
 

Tsjoklat

Senior Member
Apr 5, 2010
1,705
2,386
I added an additional version of the market that includes a patch to remove restrictions placed on applications by the market.

1) Removes device compatibility check so all applications are visible to your device
2) Removes restrictions places on certain applications by specific countries. If the country you live in blocks a specific application in your market, then it should now be visible.

Credits to L.D.B. for the "no restrictions" patch.
 
Last edited:
  • Like
Reactions: lazyb421 and MadJoe

Eddie1506

Senior Member
Feb 19, 2010
405
33
Zagreb
Google Nexus 5
OnePlus 9 Pro
Note: Also provided below is an additional version of the Android Market that includes an additional "no restrictions" patch applied. The additional patch removes restrictions on certain applications in the market placed by specific countries. If the country you live in has blocked the application you are looking for, this patch will allow you to see it in the market. The "no restrictions" patch also removes the device application compatibility check, so every application should be available to download (even if they "say" it is not compatible with your device). Credits to L.D.B. for the "no restrictions" patch.

This does not work. I already tested this exact patch, and while apps are visible in Market app, they cannot be downloaded, as additional checks are being done server side.
 

famewolf

Senior Member
Jul 14, 2006
5,246
1,348
OnePlus 7 Pro
I have a device that has not yet been rooted (without hardware modifications).....is there a way to install the google play store (it comes with old market) and still use the feature where it ignores device incompatiblity? I find it tells me alot of my apps are incompatible even if I know they work.

Hey google...here's a clue...if the app is already INSTALLED on the device odds are it works.
 

lohtse

Senior Member
Apr 1, 2009
1,679
139
Where ever they send Me!!
I have a device that has not yet been rooted (without hardware modifications).....is there a way to install the google play store (it comes with old market) and still use the feature where it ignores device incompatiblity? I find it tells me alot of my apps are incompatible even if I know they work.

Hey google...here's a clue...if the app is already INSTALLED on the device odds are it works.

Mines rooted and still get same incompat issue even when previous ver installed!

Anyway is there to be an updated market version?
 

famewolf

Senior Member
Jul 14, 2006
5,246
1,348
OnePlus 7 Pro
Mines rooted and still get same incompat issue even when previous ver installed!

Anyway is there to be an updated market version?

Did you uninstall updates to the app like the directions say? Did you remount the system partition to made it r/w instead of read only? It worked fine on all 4 of my rooted devices and I installed apps that previously failed except through sideloading.
 
Last edited:

Tsjoklat

Senior Member
Apr 5, 2010
1,705
2,386
Anyway is there to be an updated market version?

As of today, the latest version of the Android Market (Play Store) is v3.5.16. But, I had chosen v3.4.7 because I wanted a version that is fully functional with Titanium Backup. If you want to add the "no restriction" patch to the latest version of the Android Market (v3.5.16), then this is what the changes will look like (slightly different than with v3.4.7):

Code:
diff -ru Vending.3.5.16/smali/com/google/android/finsky/api/model/Document.smali Vending.3.5.16.mod/smali/com/google/android/finsky/api/model/Document.smali
--- Vending.3.5.16/smali/com/google/android/finsky/api/model/Document.smali	2012-04-05 21:35:12.551888812 +0200
+++ Vending.3.5.16.mod/smali/com/google/android/finsky/api/model/Document.smali	2012-04-05 21:54:49.299397643 +0200
@@ -3216,6 +3216,10 @@
     .parameter "library"
 
     .prologue
+    const/4 v0, 0x1
+
+    return v0
+
     const/4 v9, 0x2
 
     const/4 v5, 0x1

I have added Vending.3.5.16.noupdate.norestrictions-signed to the first page. A modified version of the Android market with this "no restrictions" patch can already be found on various other webpages, but the version found in this thread has also the self-update feature disabled. The modified versions can not self-update because the signing keys no longer match the original, so we might as well prevent it from trying and downloading the updates that will not apply anyway.
 
Last edited:

famewolf

Senior Member
Jul 14, 2006
5,246
1,348
OnePlus 7 Pro
As of today, the latest version of the Android Market (Play Store) is v3.5.16. But, I had chosen v3.4.7 because I wanted a version that is fully functional with Titanium Backup. If you want to add the "no restriction" patch to the latest version of the Android Market (v3.5.16), then this is what the changes will look like (slightly different than with v3.4.7):

Code:
diff -ru Vending.3.5.16/smali/com/google/android/finsky/api/model/Document.smali Vending.3.5.16.mod/smali/com/google/android/finsky/api/model/Document.smali
--- Vending.3.5.16/smali/com/google/android/finsky/api/model/Document.smali	2012-04-05 21:35:12.551888812 +0200
+++ Vending.3.5.16.mod/smali/com/google/android/finsky/api/model/Document.smali	2012-04-05 21:54:49.299397643 +0200
@@ -3216,6 +3216,10 @@
     .parameter "library"
 
     .prologue
+    const/4 v0, 0x1
+
+    return v0
+
     const/4 v9, 0x2
 
     const/4 v5, 0x1

I have added Vending.3.5.16.noupdate.norestrictions-signed to the first page. A modified version of the Android market with this "no restrictions" patch can already be found on various other webpages, but the version found in this thread has also the self-update feature disabled. The modified versions can not self-update because the signing keys no longer match the original, so we might as well prevent it from trying and downloading the updates that will not apply anyway.

So should I assume my attempt to install a version of google play store where practically everything is NOT listed as incompatible on my NON rooted device is hopeless by your lack of response? The logitech revue runs on honeycomb 3.1 and originally comes with market...it was later upgraded to google play. Your versions of course fail to install. Is it possible to apply your fixes to the version I am attaching to this post while keeping signatures so it will work as an install? This is the apk of the version that it was upgraded to. Thank you for your time.
 

Tsjoklat

Senior Member
Apr 5, 2010
1,705
2,386
So should I assume my attempt to install a version of google play store where practically everything is NOT listed as incompatible on my NON rooted device is hopeless by your lack of response?

I'm afraid that root is going to be necessary. When I make changes to an apk, I have to resign it (but I don't have the original keys). Since the modified apk is now signed with a different signature than the original, it can not be installed on top of the original. Therefore, you will need to have root access to replace the original apk with the modified version (since the signature keys no longer match).

The file you uploaded is only 554 bytes in size. That seems to not be correct. There seems to be problems uploading files to XDA lately. Also, make sure the files are not odexed (the apk must contain a classes.dex in order to be modified).
 
Last edited:

famewolf

Senior Member
Jul 14, 2006
5,246
1,348
OnePlus 7 Pro
I'm afraid that root is going to be necessary. When I make changes to an apk, I have to resign it (but I don't have the original keys). Since the modified apk is now signed with a different signature than the original, it can not be installed on top of the original. Therefore, you will need to have root access to replace the original apk with the modified version (since the signature keys no longer match).

The file you uploaded is only 554 bytes in size. That seems to not be correct. There seems to be problems uploading files to XDA lately. Also, make sure the files are not odexed (the apk must contain a classes.dex in order to be modified).

the logitech revue has not yet been rooted without some rather drastic hardware modifications so I guess for now I'm stuck. Thanks for the reply.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 184
    All versions of the Android Market (Play Store) above version 3.0 will self-update automatically (even if you freeze/rename/delete the Market Updater application). The following version of the Android Market has been patched to ignore the self-update check.

    Note: Android Market (Google Play Store) v3.4.7 is the last available version that allows Titanium Backup to control the Market links in the application.

    Note: Using the command "pm disable com.android.vending.updater" does NOT stop the Android Market 3.0+ from self-updating. Other methods of preventing the market from self-updating, such as creating a read-only file that blocks the installation procedure, are also not recommended because the market will still download market updates and use up precious internal memory and extra cpu cycles.

    Code:
    diff -ru Vending.3.4.7/smali/com/google/android/finsky/utils/SelfUpdateScheduler.smali Vending.3.4.7-noupdate/smali/com/google/android/finsky/utils/SelfUpdateScheduler.smali
    --- Vending.3.4.7/smali/com/google/android/finsky/utils/SelfUpdateScheduler.smali	2012-04-04 02:21:11.729877751 +0200
    +++ Vending.3.4.7-noupdate/smali/com/google/android/finsky/utils/SelfUpdateScheduler.smali	2012-04-04 02:33:51.870385096 +0200
    @@ -29,7 +29,7 @@
         invoke-direct {p0}, Ljava/lang/Object;-><init>()V
     
         .line 42
    -    const/4 v0, 0x0
    +    const/4 v0, 0x1
     
         iput-boolean v0, p0, Lcom/google/android/finsky/utils/SelfUpdateScheduler;->mUpdateInProgress:Z


    Logcat of Android Market with "noupdate" patch applied:

    Code:
    D/Finsky  ( 4890): [1] SelfUpdateScheduler.checkForSelfUpdate: Skipping self-update check as there is an update already queued.

    Note: Also provided below is an additional variation of the Android Market that includes an additional "no restrictions" patch applied. The additional patch removes restrictions on certain applications in the market placed by specific countries. If the country you live in has blocked the application you are looking for, this patch will allow you to see it in the market. There are still server side restrictions in place when you download an application that is blocked within your country and the use of a proxy or VPN might also be necessary. The "no restrictions" patch also removes the device application compatibility check, so every application should be visible in the Android Market (even if they "say" it is not compatible with your device). Credits to L.D.B. for the "no restrictions" patch.

    Code:
    diff -ru Vending.3.4.7/smali/com/google/android/finsky/api/model/Document.smali Vending.3.4.7.mod/smali/com/google/android/finsky/api/model/Document.smali
    --- Vending.3.4.7/smali/com/google/android/finsky/api/model/Document.smali	2012-04-05 21:49:58.647890272 +0200
    +++ Vending.3.4.7.mod/smali/com/google/android/finsky/api/model/Document.smali	2012-04-05 21:49:20.751889471 +0200
    @@ -3236,6 +3236,8 @@
         .line 674
         :cond_0
         :goto_0
    +    const/4 v2, 0x1
    +
         return v2
     
         .line 662

    Note: A third patch for the Android Market is the "DPI 160" patch. If you change the default DPI settings on your device, the Android Market might not detect the required DPI settings and specific applications will then not be visible in the Android Market. The "DPI 160" patch forces the Android Market to think you are using a DPI of 160, which makes specific applications in the Android Market visible.

    Code:
    diff -ru Vending.3.4.7.orig/smali/com/google/android/finsky/utils/DeviceConfigurationHelper.smali Vending.3.4.7/smali/com/google/android/finsky/utils/DeviceConfigurationHelper.smali
    --- Vending.3.4.7.orig/smali/com/google/android/finsky/utils/DeviceConfigurationHelper.smali	2012-04-10 23:06:45.156379816 +0200
    +++ Vending.3.4.7/smali/com/google/android/finsky/utils/DeviceConfigurationHelper.smali	2012-04-10 23:06:55.795879255 +0200
    @@ -257,7 +257,7 @@
     
         move-result-object v15
     
    -    iget v0, v12, Landroid/util/DisplayMetrics;->densityDpi:I
    +    const/16 v0, 0xa0
     
         move/from16 v17, v0

    Note: A "DPI 240" patch is also posted below. Some high resolution devices (ie; HTC Desire and Samsung Galaxy SII) require a 240 DPI in order for certain applications to be visible in the Android Market. The "DPI 240" patch forces the Android Market to think the device is using a DPI of 240.

    Code:
    diff -ru Vending.3.4.7.orig/smali/com/google/android/finsky/utils/DeviceConfigurationHelper.smali Vending.3.4.7/smali/com/google/android/finsky/utils/DeviceConfigurationHelper.smali
    --- Vending.3.4.7.orig/smali/com/google/android/finsky/utils/DeviceConfigurationHelper.smali	2012-04-10 23:06:45.156379816 +0200
    +++ Vending.3.4.7/smali/com/google/android/finsky/utils/DeviceConfigurationHelper.smali	2012-04-10 23:06:55.795879255 +0200
    @@ -257,7 +257,7 @@
     
         move-result-object v15
     
    -    iget v0, v12, Landroid/util/DisplayMetrics;->densityDpi:I
    +    const/16 v0, 0xf0
     
         move/from16 v17, v0

    Note: Similar to the previous DPI patches, a "DPI 320" patch is also posted below. Some of the higher WXGA resolution devices (ie; Galaxy Nexus) require a 320 DPI in order for certain applications to be visible in the Android Market. The "DPI 320" patch forces the Android Market to think the device is using a DPI of 320.

    Code:
    diff -ru Vending.3.4.7.orig/smali/com/google/android/finsky/utils/DeviceConfigurationHelper.smali Vending.3.4.7/smali/com/google/android/finsky/utils/DeviceConfigurationHelper.smali
    --- Vending.3.4.7.orig/smali/com/google/android/finsky/utils/DeviceConfigurationHelper.smali	2012-04-10 23:06:45.156379816 +0200
    +++ Vending.3.4.7/smali/com/google/android/finsky/utils/DeviceConfigurationHelper.smali	2012-04-10 23:06:55.795879255 +0200
    @@ -257,7 +257,7 @@
     
         move-result-object v15
     
    -    iget v0, v12, Landroid/util/DisplayMetrics;->densityDpi:I
    +    const/16 v0, 0x140
     
         move/from16 v17, v0

    If your device is using a custom DPI setting, then you will need a version of the Android Market that includes one of the three "DPI Hacks" mentioned above (dpi160, dpi240, or dpi320). Without the "DPI Hack" applied, updates might not be visible in the Market.

    The default DPI value for your device can be determined by looking it up in it's device specifications. When you change the default DPI setting on your device, it may cause compatibility problems for the Android Market. Therefore, we want the Android Market to think we are still using the same default value that is found in the specs.

    For example, the Samsung Galaxy SII has a default DPI of 240 in it's device specifications, so we want to make the Android Market think we are still using that setting (if the default value has been modified).

    For most devices, the standard default DPI values are 160, 240, and 320.

    All modified versions of the Android Market that are signed by another key are unable to make purchases from within the Android Market application itself because the signing key does not match Google's signing key. Because the new signing key of the modified Android Market no longer matches with Google's signing key, the modified version of the Android Market is unable to connect with GoogleServicesFramework. There are also modified versions of the Android Market available (in post #132 of this thread) that are made using the original Google signature which makes it possible to purchase applications again within the modified Android Market.
    http://forum.xda-developers.com/showpost.php?p=26102810&postcount=132

    All applications can still be purchased via the web browser.

    How to install:

    Rename file to "Vending.apk" and copy to /system/app/Vending.apk. Make sure to uninstall any updates of previous versions first. Root Required. If you are running ICS 4.0.4, "Vending.apk" might be substituted for "Phonesky.apk".

    NOTE: If you are testing a "DPI Hacked" version of the Android Market and you are still experiencing incompatibilities with certain applications or the changes are not "sticking", see post #92 in this thread for further solutions. The following link explains what additional patches may be needed: http://forum.xda-developers.com/showpost.php?p=25720539&postcount=92

    Additionally, the following links contain modified versions of GSF uploaded to this thread:
    http://forum.xda-developers.com/showpost.php?p=29401924&postcount=334
    http://forum.xda-developers.com/showpost.php?p=30074336&postcount=390
    http://forum.xda-developers.com/showthread.php?t=1631070
    http://forum.xda-developers.com/showpost.php?p=26423837&postcount=161

    ** Google Play 3.4.4 with "market purchase fix and dpi120" has been added to the following link: http://forum.xda-developers.com/showpost.php?p=31027248&postcount=460

    ** Google Play 3.4.7/3.5.19 with "market purchase fix" has been added to the following link:: http://forum.xda-developers.com/showpost.php?p=26102810&postcount=132

    ** Google Play 3.7.11 has been added to the following link: http://forum.xda-developers.com/showpost.php?p=28029688&postcount=222

    ** Google Play 3.7.13 has been added to the following link: http://forum.xda-developers.com/showpost.php?p=28207664&postcount=243

    ** Google Play 3.7.15 has been added to the following link: http://forum.xda-developers.com/showpost.php?p=29466370&postcount=344

    ** Google Play 3.8.15 has been added to the following link: http://forum.xda-developers.com/showpost.php?p=30317127&postcount=399

    ** Google Play 3.8.16 has been added to the following link: http://forum.xda-developers.com/showpost.php?p=30387825&postcount=409

    ** Google Play 3.8.17 has been added to the following link: http://forum.xda-developers.com/showpost.php?p=30563737&postcount=436

    ** Google Play 3.9.16 has been added to the following link: http://forum.xda-developers.com/showpost.php?p=32768509&postcount=505

    ** Google Play 3.9.17 has been added to the following link: http://forum.xda-developers.com/showpost.php?p=33747629&postcount=544

    ** Google Play 3.10.9 has been added to the following link: http://forum.xda-developers.com/showpost.php?p=34774989&postcount=566

    ** Google Play 3.10.10 has been added to the following link: http://forum.xda-developers.com/showpost.php?p=35741543&postcount=599

    ** Google Play 3.10.14 has been added to the following link: http://forum.xda-developers.com/showpost.php?p=38633857&postcount=660

    ** Google Play 4.0.25 has been added to the following link: http://forum.xda-developers.com/showpost.php?p=40237365&postcount=694

    ** Google Play 4.0.26 has been added to the following link: http://forum.xda-developers.com/showpost.php?p=40822664&postcount=705

    ** Google Play 4.0.27 has been added to the following link: http://forum.xda-developers.com/showpost.php?p=40823085&postcount=706

    ** Google Play 4.3.10 has been added to the following link: http://forum.xda-developers.com/showpost.php?p=44365806&postcount=769
    24
    Google Play 3.7.13

    Google Play 3.7.13 with various patch combos.


    Code:
    78b10a63081ddf392f7aaf1f902ee5ba  Vending.3.7.13.noupdate.nosig-aligned.apk
    64bd83662b12e622ee09df7bf3b5a8f1  Vending.3.7.13.noupdate.norestrictions.nosig-aligned.apk
    b44154ad69a5015902b4283ef805f054  Vending.3.7.13.noupdate.dpi160.nosig-aligned.apk
    f3e3f6594c671f0aefbf1f5812ae9742  Vending.3.7.13.noupdate.dpi240.nosig-aligned.apk
    9918e6663975413add96331a1b613ee8  Vending.3.7.13.noupdate.dpi320.nosig-aligned.apk
    824e025563eb3f316929537394d8f0b7  Vending.3.7.13.noupdate.norestrictions.dpi160.nosig-aligned.apk
    fd6744da15f131430259873fdf8560cf  Vending.3.7.13.noupdate.norestrictions.dpi240.nosig-aligned.apk
    c168f468d34ebf1416fe39fbe975a5e6  Vending.3.7.13.noupdate.norestrictions.dpi320.nosig-aligned.apk
    23
    Vending 3.10.9

    Code:
    9f36f556017f59a623c9531bce2406e9  Vending-3.10.9.noupdate.nosig-aligned.apk
    f8c7c97a7636b6637f71ed0a59832078  Vending-3.10.9.noupdate.norestrictions.nosig-aligned.apk
    e2b9f40a4b02d11949477e3e1561a6b1  Vending-3.10.9.noupdate.dpi160.nosig-aligned.apk
    5919d74f934429e61b68eb4803de4408  Vending-3.10.9.noupdate.dpi213.nosig-aligned.apk
    7ac2c995f109c1101509088240de47e0  Vending-3.10.9.noupdate.dpi240.nosig-aligned.apk
    1aa0919d7288eb9976754f34af25fdfc  Vending-3.10.9.noupdate.dpi320.nosig-aligned.apk
    bc8a8a2d389c581e12b143e6c1fc1504  Vending-3.10.9.noupdate.norestrictions.dpi160.nosig-aligned.apk
    e3714983735558ff3efea5e92341b23f  Vending-3.10.9.noupdate.norestrictions.dpi213.nosig-aligned.apk
    8afef0e941441ed6ae0a9a5341ff6d14  Vending-3.10.9.noupdate.norestrictions.dpi240.nosig-aligned.apk
    16fc3e84284f6c0bae2d0a05f76c988c  Vending-3.10.9.noupdate.norestrictions.dpi320.nosig-aligned.apk
    21
    I just noticed that 3.9.16 has additional new code in "LegacyDeviceConfigurationHelper.smali" which might also need to be changed for older devices to work properly. The "DPI" patches for 3.9.16 have now changed to the following (the patch used to be only a one line change in the code and now it is two lines):

    DPI 160 patch:
    Code:
    diff -ru Vending-3.9.16.orig/smali/com/google/android/finsky/utils/DeviceConfigurationHelper.smali Vending-3.9.16/smali/com/google/android/finsky/utils/DeviceConfigurationHelper.smali
    --- Vending-3.9.16.orig/smali/com/google/android/finsky/utils/DeviceConfigurationHelper.smali	2012-10-14 00:42:17.855438171 +0200
    +++ Vending-3.9.16/smali/com/google/android/finsky/utils/DeviceConfigurationHelper.smali	2012-10-14 00:50:43.251448825 +0200
    @@ -257,7 +257,7 @@
     
         move-result-object v15
     
    -    iget v0, v12, Landroid/util/DisplayMetrics;->densityDpi:I
    +    const/16 v0, 0xa0
     
         move/from16 v17, v0
     
    diff -ru Vending-3.9.16.orig/smali/com/google/android/finsky/utils/LegacyDeviceConfigurationHelper.smali Vending-3.9.16/smali/com/google/android/finsky/utils/LegacyDeviceConfigurationHelper.smali
    --- Vending-3.9.16.orig/smali/com/google/android/finsky/utils/LegacyDeviceConfigurationHelper.smali	2012-10-14 00:42:17.863438351 +0200
    +++ Vending-3.9.16/smali/com/google/android/finsky/utils/LegacyDeviceConfigurationHelper.smali	2012-10-14 00:52:12.595449873 +0200
    @@ -257,7 +257,7 @@
     
         move-result-object v15
     
    -    iget v0, v12, Landroid/util/DisplayMetrics;->densityDpi:I
    +    const/16 v0, 0xa0
     
         move/from16 v17, v0

    DPI 213 patch:
    Code:
    diff -ru Vending-3.9.16.orig/smali/com/google/android/finsky/utils/DeviceConfigurationHelper.smali Vending-3.9.16/smali/com/google/android/finsky/utils/DeviceConfigurationHelper.smali
    --- Vending-3.9.16.orig/smali/com/google/android/finsky/utils/DeviceConfigurationHelper.smali	2012-10-14 00:42:17.855438171 +0200
    +++ Vending-3.9.16/smali/com/google/android/finsky/utils/DeviceConfigurationHelper.smali	2012-10-14 00:50:43.251448825 +0200
    @@ -257,7 +257,7 @@
     
         move-result-object v15
     
    -    iget v0, v12, Landroid/util/DisplayMetrics;->densityDpi:I
    +    const/16 v0, 0xd5
     
         move/from16 v17, v0
     
    diff -ru Vending-3.9.16.orig/smali/com/google/android/finsky/utils/LegacyDeviceConfigurationHelper.smali Vending-3.9.16/smali/com/google/android/finsky/utils/LegacyDeviceConfigurationHelper.smali
    --- Vending-3.9.16.orig/smali/com/google/android/finsky/utils/LegacyDeviceConfigurationHelper.smali	2012-10-14 00:42:17.863438351 +0200
    +++ Vending-3.9.16/smali/com/google/android/finsky/utils/LegacyDeviceConfigurationHelper.smali	2012-10-14 00:52:12.595449873 +0200
    @@ -257,7 +257,7 @@
     
         move-result-object v15
     
    -    iget v0, v12, Landroid/util/DisplayMetrics;->densityDpi:I
    +    const/16 v0, 0xd5
     
         move/from16 v17, v0

    DPI 240 patch:
    Code:
    diff -ru Vending-3.9.16.orig/smali/com/google/android/finsky/utils/DeviceConfigurationHelper.smali Vending-3.9.16/smali/com/google/android/finsky/utils/DeviceConfigurationHelper.smali
    --- Vending-3.9.16.orig/smali/com/google/android/finsky/utils/DeviceConfigurationHelper.smali	2012-10-14 00:42:17.855438171 +0200
    +++ Vending-3.9.16/smali/com/google/android/finsky/utils/DeviceConfigurationHelper.smali	2012-10-14 00:50:43.251448825 +0200
    @@ -257,7 +257,7 @@
     
         move-result-object v15
     
    -    iget v0, v12, Landroid/util/DisplayMetrics;->densityDpi:I
    +    const/16 v0, 0xf0
     
         move/from16 v17, v0
     
    diff -ru Vending-3.9.16.orig/smali/com/google/android/finsky/utils/LegacyDeviceConfigurationHelper.smali Vending-3.9.16/smali/com/google/android/finsky/utils/LegacyDeviceConfigurationHelper.smali
    --- Vending-3.9.16.orig/smali/com/google/android/finsky/utils/LegacyDeviceConfigurationHelper.smali	2012-10-14 00:42:17.863438351 +0200
    +++ Vending-3.9.16/smali/com/google/android/finsky/utils/LegacyDeviceConfigurationHelper.smali	2012-10-14 00:52:12.595449873 +0200
    @@ -257,7 +257,7 @@
     
         move-result-object v15
     
    -    iget v0, v12, Landroid/util/DisplayMetrics;->densityDpi:I
    +    const/16 v0, 0xf0
     
         move/from16 v17, v0

    DPI 320 patch:
    Code:
    diff -ru Vending-3.9.16.orig/smali/com/google/android/finsky/utils/DeviceConfigurationHelper.smali Vending-3.9.16/smali/com/google/android/finsky/utils/DeviceConfigurationHelper.smali
    --- Vending-3.9.16.orig/smali/com/google/android/finsky/utils/DeviceConfigurationHelper.smali	2012-10-14 00:42:17.855438171 +0200
    +++ Vending-3.9.16/smali/com/google/android/finsky/utils/DeviceConfigurationHelper.smali	2012-10-14 00:50:43.251448825 +0200
    @@ -257,7 +257,7 @@
     
         move-result-object v15
     
    -    iget v0, v12, Landroid/util/DisplayMetrics;->densityDpi:I
    +    const/16 v0, 0x140
     
         move/from16 v17, v0
     
    diff -ru Vending-3.9.16.orig/smali/com/google/android/finsky/utils/LegacyDeviceConfigurationHelper.smali Vending-3.9.16/smali/com/google/android/finsky/utils/LegacyDeviceConfigurationHelper.smali
    --- Vending-3.9.16.orig/smali/com/google/android/finsky/utils/LegacyDeviceConfigurationHelper.smali	2012-10-14 00:42:17.863438351 +0200
    +++ Vending-3.9.16/smali/com/google/android/finsky/utils/LegacyDeviceConfigurationHelper.smali	2012-10-14 00:52:12.595449873 +0200
    @@ -257,7 +257,7 @@
     
         move-result-object v15
     
    -    iget v0, v12, Landroid/util/DisplayMetrics;->densityDpi:I
    +    const/16 v0, 0x140
     
         move/from16 v17, v0

    If the previous version of 3.9.16 that I posted did not work, perhaps these changes will help.

    Code:
    17909b5fdbd7aa43e0a179d9e932a775  Vending-3.9.16.noupdate.nosig-aligned.apk
    6a0aa7c308004fbca74ca17f9c46ed4f  Vending-3.9.16.noupdate.norestrictions.nosig-aligned.apk
    399773420f334cfee1d40c427a05ff82  Vending-3.9.16.noupdate.dpi160.nosig-aligned.apk
    36cead47a46454356f07461698bd89a1  Vending-3.9.16.noupdate.dpi213.nosig-aligned.apk
    9d721f53db2ea90fac8798b014ec18d7  Vending-3.9.16.noupdate.dpi240.nosig-aligned.apk
    0070f71fe3e436745f581dc058a9ec6d  Vending-3.9.16.noupdate.dpi320.nosig-aligned.apk
    6e14221f7c623e3c3a9d335ab2dc72f2  Vending-3.9.16.noupdate.norestrictions.dpi160.nosig-aligned.apk
    584468ba944002cf36dba982ea704dc6  Vending-3.9.16.noupdate.norestrictions.dpi213.nosig-aligned.apk
    d9d876c953ed861618fde2f3a8c67ead  Vending-3.9.16.noupdate.norestrictions.dpi240.nosig-aligned.apk
    40dee1545ba5bf4dd96f7493b202a206  Vending-3.9.16.noupdate.norestrictions.dpi320.nosig-aligned.apk
    20
    3.9.16

    Code:
    cf895a511eb3f5a15840b1f24a9fba4d  Vending-3.9.16.noupdate.nosig-aligned.apk
    323e53ef8d134756390590f681572f66  Vending-3.9.16.noupdate.norestrictions.nosig-aligned.apk
    d67dd37c0fe0c0abb4b3daf0e0471cab  Vending-3.9.16.noupdate.dpi160.nosig-aligned.apk
    28b4cafeffad07b1a765bf747169e676  Vending-3.9.16.noupdate.dpi213.nosig-aligned.apk
    758945d1f2691b543e2b1a6b63351d6f  Vending-3.9.16.noupdate.dpi240.nosig-aligned.apk
    6c2ef0f8ee46aa05e13b4f094a1cd3c8  Vending-3.9.16.noupdate.dpi320.nosig-aligned.apk
    4b8260620a269790eab15f330a17b5f4  Vending-3.9.16.noupdate.norestrictions.dpi160.nosig-aligned.apk
    5ec536bc6e0d8837cb21ecb2202eca0c  Vending-3.9.16.noupdate.norestrictions.dpi213.nosig-aligned.apk
    dab9604b5a5a97b0894cf5ef59e354e3  Vending-3.9.16.noupdate.norestrictions.dpi240.nosig-aligned.apk
    005dc699282dbd87bacd671d8dd18e83  Vending-3.9.16.noupdate.norestrictions.dpi320.nosig-aligned.apk