[GUIDE] Make Google Play think you have a device feature you don't actually have... - Android Software/Hacking General [Developers Only]

So, I was looking around my ROM and I discovered this neat little trick.
You know when you power on the device after a factory reset, and that setup comes up? When it says it is communicating with the server, it is actually getting the features of your device and sending it to Google Play.
How does it get the features of the device you may be asking. Well, it parses the XML files located in the /system/etc/permissions directory!
So, how can we use this to our advantage? Well, we can add features to our device/ROM!
How to do this? Simple!
Step 1: Copy a file in that directory and paste it in the same directory. I recommend you use the Root Explorer app.
Step 2: Rename the new file with the feature you want - if you want the android.hardware.telephony feature, rename the file to android.hardware.telephony.xml
Step 3: Open the file in a text editor. Remove the <text> part of the name="<text>" tags, and replace the <text> with the feature name (the same as the file name, without the .xml extension)
Step 4: Save the file!
Step 4.5: Delete the backup file if using Root Explorer
Step 5: Open your System Settings menu and clear the app data and cache for the following apps:
Google Play Store
Google Services Framework
Package Installer
Setup Wizard
com.android.provision
Step 6: Reboot the device:
Step 7: Open the Google Talk app, and sign in to your account(s), sign out, then sign in again. Open Google Play, and see if you can install an app that needs the feature you just added!
List Of Features
No matter how hard you try, this wont add telephony to your wifi only tablet It only spoofs the features for Google Play - it doesn't actually add them, and some apps will force close if they really did need the feature you 'added'!

Related

[GUIDE] Merging updated system apps with old one, GET MORE FREE MEMORY!!

(Preface for noobs : /system and /data are two different partitions. Freeying up /system won't get you more intrenal memory, but /data does. Old apks rest in /system and updated versions placed in /data. You can replace the old apks using newer versions)
I heared Titanium Backup PRO does something like, but you can do this with any File Explorer with ROOT access. Its works 100% for Android Gingerbread 2.3.x , try on other versions.
### Do it on your own risk, I am not responsible for anything ###
1. Update the desired app to the latest version from Google Play Store
2. Open File Manager, Enable ROOT_ACCESS, remount /System as writable
3. Goto /system/app and backup the desired apk to sdcard
4. Goto /data/app and copy updated apk
5. Paste into /System/app
6. Note down the filename of old apk and delete the old apk
7. Rename the new apk into the old filename
8. You may encounter a FORCE CLOSE if the app was running in background
9. The updated apk in /data/app will be removed automatically
10.Restart your device, Done!
I replaced Playstore, Maps, Google Search ect..
Example: For PlayStore, updated apk will be com.android.vending-1.apk, and old apk is vending.apk
Hit thanks it it works, Thanks
thanks, nice guide! All is ok (PlayStore, Terminal Emulator), but if I merge last version of "Google Play Service", then Gmail or Maps shows the message "Unknown issue with Google Play services" when I open them... do you know how to solve? thanks in advance
p.s. configuration in signature
Better use Link2SD. It makes the integration of updates into system seamless. Rebooting the device is optional (restart only if you encounter errors).
thank you for your suggestion! I tried TitaniumBackup but it gives me the same error, then now I'm trying with Link2sd and it works well, BUT the new apk file is in system/app instead of system/priv-app, and its name is "com.google.android.gms-1.apk" instead of "PrebuiltGmsCore.apk"... can this create some problems in future?
EDIT: I tried moving to the priv-app folder and renaming the apk to be identical as before and it seems to work... for now...
It's the package name, it won't create any problems. There is no need to rename the app to match the old one. Default location when converting to system app is in /system/app. I don't know if you can change the location, but you can move it manually to /system/priv-app thru root explorer. Just restart the device afterwards to eliminate FC errors.

Guide To Get Google Voice Search Offline On Any Android Device

Hi, Friends Today I'm Going to show you how to get offline google voice search offline
1. First download Google Voice Search.
2.Open Google Voice Search and close it.Make sure data connection is off.
3. Download the file from attachments.
4.Extract the files.
5.Install Root Browser.
6.Open Root Browser and go to /data/data/com.google.android.googlequicksearchbox then open app_g3models.In the Folder If a folder en-us exsists, then delete it.And, create a new folder en-US and paste the files which you obtained from the attached files.After pasting close the root browser.
7. Open Google Settings , then go to search , then voice ,then change the language to English(US).After that , reboot the phone and its all done.

how to find apks on my device

Hi everyone,
There is a way to find the .apk of apps downloaded from playstore. ull need root and root browser, we will use here esfile explorer. open esfile explorer and press top left-->tools enable root explorer and show hidden files, then go to local-->device now go to file data-->app and thats it, to find system apps u can go to device-->system-->app.
Wiked dudes production
Pull Apk in Non-Rooted Device.
There is no need of a rooted device,
you can pull the apk by using following techniques.
//_______________________________________________________
A) Using ADB
1) Determine the package name of the app, e.g. "com.whatsapp" (WhatsApp).
if you don't know the package name, you have 2 options to get the package name
i) Visit play store and search for the desired application, The link of the app contains the package name. "https://play.google.com/store/apps/details?id=com.whatsapp" (WhatsApp) where com.whatsapp is the package name
ii) use command "adb shell pm list packages" , this will list the package name of all application installed.
2) Once you know the package name, get the apk installed path by using command "adb shell pm path com.whatsapp"
it will return the apk path of the application, like this
package:/data/app/com.whatsapp-2/base.apk
3) Now to pull apk, by using command "adb pull /data/app/com.whatsapp-2/base.apk"
Apk will be extracted to the same folder where adb is present
//_______________________________________________________
B) Using ESFileExplorer
1) Open ESFileExplorer and navigate to User Apps either by (swiping left to right twice) or (goto APP under Library in Navigation Drawer)
2) Select App you want to pull, and click on Share.
3) Share the Apk to another device via Bluetooth or to desktop via AirDroid,
shanrais said:
There is no need of a rooted device,
you can pull the apk by using following techniques.
//_______________________________________________________
A) Using ADB
1) Determine the package name of the app, e.g. "com.whatsapp" (WhatsApp).
if you don't know the package name, you have 2 options to get the package name
i) Visit play store and search for the desired application, The link of the app contains the package name. "https://play.google.com/store/apps/details?id=com.whatsapp" (WhatsApp) where com.whatsapp is the package name
ii) use command "adb shell pm list packages" , this will list the package name of all application installed.
2) Once you know the package name, get the apk installed path by using command "adb shell pm path com.whatsapp"
it will return the apk path of the application, like this
package:/data/app/com.whatsapp-2/base.apk
3) Now to pull apk, by using command "adb pull /data/app/com.whatsapp-2/base.apk"
Apk will be extracted to the same folder where adb is present
//_______________________________________________________
B) Using ESFileExplorer
1) Open ESFileExplorer and navigate to User Apps either by (swiping left to right twice) or (goto APP under Library in Navigation Drawer)
2) Select App you want to pull, and click on Share.
3) Share the Apk to another device via Bluetooth or to desktop via AirDroid,
Click to expand...
Click to collapse
ur right however, not all system apps are present using the second way, and first way is complicated for some people and might confuse them. if someone would want to change something he saw on google, that is connected to system apps or other stuff"like systemui" i think rooting and copying the apk from its directory is best. btw thanks for ur concern about this, believe it or not for the first 7 month i posted this it posted in android wear, and no one was commenting, i made it with the xda app, i think it has alot of bugs.
Lord_of_Death said:
ur right however, not all system apps are present using the second way, and first way is complicated for some people and might confuse them. if someone would want to change something he saw on google, that is connected to system apps or other stuff"like systemui" i think rooting and copying the apk from its directory is best. btw thanks for ur concern about this, believe it or not for the first 7 month i posted this it posted in android wear, and no one was commenting, i made it with the xda app, i think it has alot of bugs.
Click to expand...
Click to collapse
IMO, if one is able to root the phone, then he will certainly not find any complication in pulling apk using first way.
shanrais said:
IMO, if one is able to root the phone, then he will certainly not find any complication in pulling apk using first way.
Click to expand...
Click to collapse
u might be right bro but rooting is only downloading a file and flashing it through odin.

[ROOT] Enable Google Assistant in Phones with RAM < 1.5GB

If you have a device running Android MM+ and your phone has RAM < 1.5GB you can still be able to use Google Assistant without downgrading your google app.
[Method 1: Manually]
You only need a root explore and a file editor. I recommend Solid Explorer or ES file explorer
Go to /system/build.prop
Open the build.prop with note editor.
NOTE: First backup build.prop file just copy the file.
Add the below line to the bottom of the file.
Code:
ro.opa.eligible_device=true
Clear Google App data go to Settings>Apps>Google>Storage>MANAGE SPACE>CLEAR ALL DATA
Reboot
[Method 2:Using App]
Download Get Assistant Grant ROOT access within the app click Get assistant select new method then continue clear Google app data Reboot.
If this helps you just hit the Thanks button.
Having any trouble let me know in the comments.

[Tutorial] [Root] [Samsung] How to stop apps being closed automatically on Samsung devices

Hello,
I recently discovered a way to disable automatically closing apps on Samsung Galaxy devices. This is especially useful for apps such as battery monitoring or fake GPS location apps.
I tested this on my Samsung Galaxy A52 5G, it should work on other models, however I cannot guarantee this. Despite this, it doesn't hurt to try!
First off let's talk a little why this happens. If you have multiple apps open at once, the OS will attempt to close some to free up resource when not currently in use, especially if the apps have not been interacted with for a while since they were last opened. This is normal behaviour, however you may have something like a battery monitoring app (e.g. AccuBattery) that you never want to be terminated. So let's try achieve this.
There's two core parts to this process. You need root for both of these (Magisk).
Part 1
Requirements:
Root file explorer (e.g. Total Commander)
A text file editor (PC is easiest. If you decide to use PC, use a USB transfer cable)
Guide:
On the root file explorer, navigate to /system/etc
Make a copy of floating_feature.xml. Make a second copy to preserve original contents in case things go wrong. If this file doesn't exist, you can't use this method.
Open it in the text editor of your choice (transfer to PC if needed)
Search for this in the file: <SEC_FLOATING_FEATURE_DWB_CONFIG_UNSUSPENDABLE_PACKAGE_NAME>
If it doesn't exist, create it like this: <SEC_FLOATING_FEATURE_DWB_CONFIG_UNSUSPENDABLE_PACKAGE_NAME> </SEC_FLOATING_FEATURE_DWB_CONFIG_UNSUSPENDABLE_PACKAGE_NAME>
Add your app's Package Name inside this tag. For example AccuBattery would be 'com.digibites.accubattery' so the result value would be <SEC_FLOATING_FEATURE_DWB_CONFIG_UNSUSPENDABLE_PACKAGE_NAME>com.digibites.accubattery</SEC_FLOATING_FEATURE_DWB_CONFIG_UNSUSPENDABLE_PACKAGE_NAME> assuming it didn't already exist. If it does exist, add a semi colon ; to the last entry and append the value to the end
Save the file and use your root file explorer to replace the original floating_feature.xml file
Reboot your phone
Part 2
Requirements:
Magisk
Command line interface with root (e.g. Termux)
Guide:
Download and install the App Systemizer Magisk Module
Reboot your phone
Open your command line interface and enable Superuser mode (in Termux this is 'su')
Enter 'systemize' in your command line interface and follow the instructions to systemize the desired app
Reboot your phone
Summary
You'll need to reapply this process whenever you update your phone software. It's a relatively simple process though. I'll be interested to see how successful this is for others so feel free to provide feedback and findings.
Hope this helps!

Categories

Resources