[REQUEST] Make sideloaded APKs appear as if they were installed from Google Play - Magisk

I came across this guide that explained how to get a sideloaded apk to work with Android Auto.
It got me thinking, there are always some apps that don't respond well to integrations due to the getInstallerPackageName() method of checking the install source.
Would someone be kind enough to create a module that does this so we do not need to connect our phones to the PC every time we update the APK just for a few apps?

There's no need to connect to your computer (and neither for a Magisk module, really). You should be ably to simply run the command in a Terminal emulator instead (without the ADB shell part).

As Didgeridoohan said and you could try as
Code:
pm set-installer "PACKAGE" "com.android.vending"
Replacing PACKAGE with the package name of app installed already you want to change its installer to Google Play.

Can't you do this in titanium backup by clicking on the app and going to special features tab and clicking attach to market?

This pm set-installer didn't work for me. What did was just installing the package (as root , not sure it's needed) with:
pm install -i "com.android.vending" <apk>

Related

SuperSu 2.67 missing icon in launcher

I installed SuperSu v2.67 on a Nexus 5 running stock Marshmallow 6.0.1, and SuperSu works great for me so far!
The only (minor) issue I've encountered thus far is that the SuperSu icon seems to be missing from the Google Now launcher home screen and app drawer.
I can still launch SuperSu by searching for it in the Google Play store and clicking "Open", and it still pops up when an unauthorized app is requesting root access.
I've tried to do a complete unroot + reinstall, change the SuperSu icon from the app's settings etc. - without success.
Has anyone else encountered this? Is there any way to get SuperSu icon to show up?
Thanks in advance.
Try this with your computer:
adb uninstall eu.chainfire.supersu
Reboot back into Android, then reboot into recovery and reflash, or extract the APK from the zip and "adb install" it.
Edit:
Correction! Found the icon. It was buried in the app drawer all along. What threw me off was that for some reason, when I write "SuperSu" or any prefix of the name in the search box at the top, it doesn't find SuperSu, like it does pretty much any other app. Weird.
Anyway, thanks for the help and sorry about the false alarm.
Chainfire said:
Try this with your computer:
adb uninstall eu.chainfire.supersu
Reboot back into Android, then reboot into recovery and reflash, or extract the APK from the zip and "adb install" it.
Click to expand...
Click to collapse
I'm having a similar problem as the OP except that 2.6.7 binaries don't install on a T-Mobile Note 4 (SM-910T3) in either Lollipop or Marshmallow using either the Normal or TWRP methods. 2.6.5 and 2.6.6 binaries install properly, however.
I tried the command in recovery and got the following error:
In other words, you have a completely different problem that isn't even vaguely related. Not enough info, wrong thread.
Also, adb uninstall doesn't work from recovery, only full Android.
Chainfire said:
In other words, you have a completely different problem that isn't even vaguely related. Not enough info, wrong thread.
Also, adb uninstall doesn't work from recovery, only full Android.
Click to expand...
Click to collapse
You're right I didn't explain things right. My ROM comes preinstalled with SuperSU 2.6.6 and I have the same issue as the OP as the app doesn't appear in either app drawer and I can't launch it from the Play Store either. I'll try adb uninstall properly.
The 2.6.7 failed install is a separate issue. Do I start another thread here in the same forum? What info do you need?
Mate if adb shell not working then use this as i got same issues before anyway go to setting/application manger then roll down to find this
eu.chainfire.supersu
Then uninstall it & reboot then re install supersu app extracted from supersu zip it should work for u ok
thereassaad said:
Mate if adb shell not working then use this as i got same issues before anyway go to setting/application manger then roll down to find this
eu.chainfire.supersu
Then uninstall it & reboot then re install supersu app extracted from supersu zip it should work for u ok
Click to expand...
Click to collapse
Thanks. I got it to uninstall and was able to reinstall, but it still wouldn't show up in app drawer or open from the Play Store.

MIUI 9 systemless magisk, xposed possible?

Dear fellow mixers,
I try to achieve the combination of:
MIUI 9 Android 7.0 either from EpicROM or xiaomi.eu
Installing Magisk systemless root
Installing Xposed for magisk
3 Questions:
Anyone achieved this already? If yes, can you tell us which version/release of MIUI, which variant of Magisk & Exposed did you use?
If someone didn't do it, but knows which combination of MIUI, Magisk and Xposed (especially which versions and mods) should work in theory, can you say so?
To my understanding this should help to *not* trip safetynet and allow us to run Snapchat?
My research so far:
According to this post, Unofficial Xposed 88.1 for MIUI9 SDK24 should work
According to this post, 88.1 works and xmiui also has a magisk zip
Another guide that seems to be written before 88.1 was released with MIUI 9 compatibility. So I'm confused which guide to follow, which combination of systemless xposed/magisk will work?
Edit:
I'll use my experiences and document them here to later create another how-to for systemless magisk/xposed on miui9 and another guide how to properly backup second space apps.
Second space backup:
Using Titanium Backup installed and started in First Space will only backup first space apps. Installing Titanium Backup in Second space also didn't work properly for me for some apps like LINE messenger.
Actually there are two (somethimes three) places that need to be backed up:
1. App APK (the installation files itself)
/data/app/<appname>
for both spaces, because they use the same app installation, as no user data is saved here, so it's in a single location, no matter how many android user accounts or MIUI spaces you have.
2. App's user data (like LINE Messenger database etc. normally not visible to you but important):
First space: /data/user/0/<appname>
Second space: /data/user/10/<appname>
This is unique for every user account (or miui space), here individual data is being saved, like two different LINE messenger accounts, or FB accounts.
3. User's accessible app data (where your app stores things that you produce in your apps and are visible to you when connecting your phone to your PC or checking your sdcard/internal storage):
First Space: /storage/emulated/0/<folder>
Second Space: /storage/emulated/10/<folder>
the folder names can be a mess here, whatsapp names their user data folder simply Whatsapp. Here they store your chat history DB, your downloaded pictures, videos and audio. Other apps can basically name their folder however they want and sometimes it's difficult to find out what folder your app stores files in. The app "Magix Pro Screen Recorder" as a fictional example could store your screen recordings in /storage/emulated/0/Movies/recordings/
To properly backup whatsapp in second space:
copy /storage/emulated/10/whatsapp folder to your PC
in new rom/phone create second space, then copy the backup form your PC to the same location as above in your new rom/phone
install whatsapp from play store, open it and it should recognize the backup and ask you to directly restore it
To properly backup a more complex app that uses all three folder types described above I take Naver LINE Messenger as an example:
backup /data/user/10/jp.naver.line.android/ *
backup /data/app/jp.naver.line.android-1 *
in new rom/phone create second space, then copy the backups to the same locations as above
don't open line app yet
install terminal emulator and delete the previous LINE settings by using the following commands:
su
sqlite3
/data/user/10/jp.naver.line.android/databases/naver_line
delete from setting;
.quit
if you don't have the sqlite3 binary, you can try to find it online for android (arm64 binary), paste it to your /bin folder and try again, or open the file on your computer with an sqlite explorer
if available, delete the following xml:
/data/user/10/jp.naver.line.android/shared_prefs/jp.naver.line.android.settings.xml
open the Line app and it will ask you to enter your user and password
Alternative method:
backup /data/user/10/jp.naver.line.android/
backup /data/app/jp.naver.line.android-1
in new rom/phone create second space, then copy the backups to the same locations as above
don't open line app yet
use an sqlite editor on your phone or on your pc to empty the following database:
/data/user/10/jp.naver.line.android/databases/naver_line
start line
My preferred method:
on old phone, install device id changer pro in second space and open it
note down device ID
backup /data/user/10/jp.naver.line.android/
backup /data/app/jp.naver.line.android-1
in new rom/phone create second space, then copy the backups to the same locations as above
don't open line app yet
install device id changer pro in second space and open it
enter the previously noted down device ID and set it
start line
* creating proper backups of the two LINE folders is a whole procedure again, we need to use tar gz to preserve permissions when copying and pasting:
- enable developer mode and usb debugging
- connect to pc
- install minimal adb & fastboot on your PC
- start cmd, execute:
adb shell
- accept popup on device, then type into cmd:
su
- accept supersu on device
- type:
cd /data/user/10/jp.naver.line.android
tar -cvpzf /storage/emulated/0/user-10-jp.naver.line.android.tar.gz .
cd /data/user/0/jp.naver.line.android
tar -cvpzf /storage/emulated/0/user-0-jp.naver.line.android.tar.gz .
cd /data/app/jp.naver.line.android-1
tar -cvpzf /storage/emulated/0/app-jp.naver.line.android-1.tar.gz .
- copy the 3 backup tar.gz files into your first space internal storage, and type:
cd /storage/emulated/0/
tar xpvzf user-10-jp.naver.line.android.tar.gz /data/user/10/
tar xpvzf user-0-jp.naver.line.android.tar.gz /data/user/0/
tar xpvzf app-jp.naver.line.android-1.tar.gz /data/app/
Reported Psyman version seems work and sometimes... latest build officialy released by Rovo works... then u need made a backup and try to flash a magisk version, lastest will have more chance to work because include all report from git...
And a lot of xposed module need to be updated....
cheers
I wasn't unable to make xposed 88.0 or 88.1 to work with the latest N MIUI 9 Epic rom using magisk. the only version that worked for me was V87 xposed but somehow gravity box didn't seen to work well when enabling setting and applying theme, that is gravity older version not the newest the newest version require xposed 88 and newer which didn't activated on N MIUI 9 Epic newest rom, exMIUI did work though
Ok, some news...
Lastest stable from Xiaomi.eu (9.1 - 7.0 - SDK 24) works with magisk and xposed... only need good version and right apk...
Cheers

Gear LIve TWRP, Rooted With Magisk - General/Questions 2019

So I just recently came across this watch and have been fiddling with it. I managed to twrp it, unpack the 5.1.1 boot img other day and patch it with magisk and flashed it successfully. There was a little error in magisk manager you could slide by when you first opened it but it showed installed could grant superuser permissions.
The newest updates (6.0.1) and above I guess are using this squashfs scheme for system so it's not mountable. I noticed on the lg watch there was a squashfs doryimg, does anyone have squashfs sprat compatible twrp already anywhere, or can create one quicker than me? Or lead me in the right direction to compile it myself? An update installed on me unrooted me and failed to install, ideas on easiest way to freeze them prefferably adb shell pm uninstall -0 type command? Managed to also magisk patch 6.0.1boot img and flash it successfully get superuser permissions but its not proper doesnt have system permission to change anything much because of squashfs.
Tried DPI Changer is nice. Google Keyboard is good but wish it had an enter button so I can fiully type in jackpal terminal spaces that require an enter key. Will maybe try hackers keyboard(tried swype, gboard, minuum on 5.1.1 no dice). Google Analog draw keyboard zip kind of nice but annoying to type with. Es File Explorer pro size render disallowed looking at others app menu beside users. Es File Explorer worked to uninstall on 6.0.1 but not 5.1.1 had to go to go to data/ app to uninstall on 5.1.1. Could not install apk from device. Have been having to use adb install and push commands to get most files on the watch. Chrome apk latest works. I'd like to stay at 5.1.1 to maintain proper magisk/ twrp solely because of lack of squashfs support. Anyway to update google play service (1.1 to android 1.3 or 1.5) without updating version or install real playstore? Tried remote desktop/ gmail but only thing stopping me was I am unable to login to a google account on device because there is no account section in settings. Tried several app versions, shortcuts, workarounds no luck but lmk if you were able to.
Used rootjunky restore tool v2 to restore stock 4.4 it works well. V3 wouldn't recognize my almost bricked device but V2 would. OTA back from 4.4 is super annoying tho adb doesnt work says unauthorized until 5.1.1 doesnt give key doesnt pop up. Adb sideload is friend. There is not another boot img until 6.0.1 so had to apply patch updates then unpack/ repack. Had issues with backups not restoring root somehow. https://forum.xda-developers.com/wiki/Samsung_Gear_Live couldnt find anything newer besides one reddit post. first 6.0.1 update is twrp flashable.
well thats about all for now when I reupgrade I'll try and upload 5.1.1 magisk root if nothing changes. Thank you kindly Feel free to chime in if you still have this device, what worked for you., any tips, :good:
Still looking??
Sorry, I can't help you....... The gear live support just keeps getting less..... Well, it IS five years old after all...
Anyhow, I still have mine an love it. I read you were able to get TWRP on it successfully.
I can flash TWRP to the Gear Live just fine, but as soon as I reboot normally, the stock software replaces TWRP with the original recovery.
Supposedly, TWRP has a patching feature built in, but I've not been able to make it work.
SO....... Do you have any ideas why mine would not be working??
Thanks
Boowho??

Question Okay, I'm stupid...

So, I was going through and removing bloat from my phone and was trying to remove the Samsung Contacts app through `adb`, but apparently I removed the wrong thing and now the Phone, Messages, and Contacts app are crashing every time I try to open them. I removed "package:/system/priv-app/SamsungContactsProvider/SamsungContactsProvider.apk=com.samsung.android.providers.contacts" which is apparently a core service. I'm wondering if anyone might know how I could reinstall that APK?
install this apk should solve the problem
If worse comes to worse a factory reset will.
A lot of the bloatware is useful. I prefer to use a package disabler as I can easily toggle them on or off as needed real time.
rtd4 said:
install this apk should solve the problem
Click to expand...
Click to collapse
It sat for a minute trying to install and then came up with, "App not installed" and says that every time I retry.
Trying install via adb I get: "
Performing Streamed Install
adb: failed to install /home/mhicks/Downloads/SamsungContactsProvider.apk: Failure [INSTALL_FAILED_DUPLICATE_PERMISSION: Package com.samsung.android.providers.contacts attempting to redeclare permission android.permission.SEND_CALL_LOG_CHANGE already owned by com.android.providers.contacts]"
Hmmm, perhaps I should remove Google Contacts first...
Okay, that helped, but now I'm getting: "
Performing Streamed Install
adb: failed to install /home/mhicks/Downloads/SamsungContactsProvider.apk: Failure [INSTALL_FAILED_VERSION_DOWNGRADE]"
I thought deleting the "com.samsung.android.providers.contacts" might solve the problem, but trying gave me: "
./adb -d uninstall com.samsung.android.providers.contacts
Failure [DELETE_FAILED_INTERNAL_ERROR]"
darkfrog26 said:
It sat for a minute trying to install and then came up with, "App not installed" and says that every time I retry.
Click to expand...
Click to collapse
try these commands on pc
adb shell cmd package install-existing com.samsung.android.providers.contacts
adb shell pm install -r --user 0 /system/priv-app/SamsungContactsProvider/SamsungContactsProvider.apk
The first command returns: "Package com.samsung.android.providers.contacts installed for user: 0", but the second command returns: "Failure [-3001: INSTALL_FAILED_REJECTED_BY_BUILDTYPE]"
If you have deleted the apk with root you just have to paste it again in the folder /system/priv-app/SamsungContactsProvider
@rtd4, unfortunately, this device isn't rooted.
darkfrog26 said:
@rtd4, unfortunately, this device isn't rooted.
Click to expand...
Click to collapse
It is somewhat complicated to recover the device without wipe in the past I had these problems, it was solved with a higher version of the application
@rtd4, I suppose it's time for a wipe... Thanks for trying to help me.
If you had made a copy of all your apps including system apks with ApkExport you could now use that copy to restore it.
Now before you factory reset make a copy of your installed apps and any system updates then save it on the PC or SD card. After the reload you won't need Playstore. It speeds things up a lot...
APK Export (Backup & Share) - Apps on Google Play
Manage and extract your apps.
play.google.com
@blackhawk, thanks for the tip. Right now, I'm trying to set up a Telegram account so I can root my phone (US version) if I'm going to go through the trouble of wiping. Unfortunately, Telegram's SMS verification appears to be broken or at least doesn't like Mint Mobile... Fun day.
darkfrog26 said:
@blackhawk, thanks for the tip. Right now, I'm trying to set up a Telegram account so I can root my phone (US version) if I'm going to go through the trouble of wiping. Unfortunately, Telegram's SMS verification appears to be broken or at least doesn't like Mint Mobile... Fun day.
Click to expand...
Click to collapse
You're welcome.
You really don't need to root.
Consider the possible consequences carefully.
Package Disabler will easily block apks you don't want running.
Well, it would appear it's moot anyway since I'm at Baseband v4 and only v1 can be rooted apparently...
darkfrog26 said:
Well, it would appear it's moot anyway since I'm at Baseband v4 and only v1 can be rooted apparently...
Click to expand...
Click to collapse
This is the one I use:
Home - Package Disabler
The only NON-root solution that let’s you disable any unwanted packages that come pre-installed / installed with your phone / tablet.
www.packagedisabler.com
It has an interactive widget that allows you to toggle selected entries on/off. It runs even in Safe mode so be careful what you disable. I've never had to do a factory reset because of it but the potential is there.
Unfortunately it no longer disables Google play Services but will disable all carrier bloatware including OTA updates.
darkfrog26 said:
@rtd4, unfortunately, this device isn't rooted.
Click to expand...
Click to collapse
Then how come you have removed apk from system?
In case you have used command like
pm disable packageName . Then try pm enable packageName
Or
If you have used
pm hide packageName then try
pm unhide packageName
darkfrog26 said:
So, I was going through and removing bloat from my phone and was trying to remove the Samsung Contacts app through `adb`, but apparently I removed the wrong thing and now the Phone, Messages, and Contacts app are crashing every time I try to open them. I removed "package:/system/priv-app/SamsungContactsProvider/SamsungContactsProvider.apk=com.samsung.android.providers.contacts" which is apparently a core service. I'm wondering if anyone might know how I could reinstall that APK?
Click to expand...
Click to collapse
Next time use this, so you don't make mistakes:
[TOOL] ADB AppControl 1.8.0 🚀 Ultimate App Manager & Debloat Tool + Tweaks
ADB AppControl 🚀 Root is not required. Works with any Android device. Can do almost everything you dreamed about with applications. ADB AppControl - the desktop program, that will allow you to easily manage applications on your android device...
forum.xda-developers.com

BYD Multimedia - Install APK

Hi everyone
I got my new BYD car
I dont have AA or AC and i try to install APK
I stack at passions the i copy APK files from USB to Multimedia
But i cant install them
I get a message like "For your driving safety and system stability, please do not install third party apps"
Any idea ?
Amir
BYD the Chinese car? Where r u from?
Yes, BYD is Chinese car
Someone, any idea ?
I too am interested in any developments on this front.
Hi, can this help you youtube
As of now, this is where we're up to:
1. we can now enable and use USB ADB to sideload apps
2. we can now re-enable Wireless ADB via sideloading a an wireless ADB enabling package
3. we can now replace the system Package Manager with an alternate unrestricted Package Manager
4. we can now install apps via native (or alternate) file manager using alternate-unrestricted Package Manager
Are people aware of this? or are instructions of this yet to be published on XDA?
insinc said:
As of now, this is where we're up to:
1. we can now enable and use USB ADB to sideload apps
2. we can now re-enable Wireless ADB via sideloading a an wireless ADB enabling package
3. we can now replace the system Package Manager with an alternate unrestricted Package Manager
4. we can now install apps via native (or alternate) file manager using alternate-unrestricted Package Manager
Are people aware of this? or are instructions of this yet to be published on XDA?
Click to expand...
Click to collapse
I can't find that infor online, can you please instruct us, I would be very greatfull
@insinc
Is this possible with every Android OEM head unit, like GM Mylink?
Thank you.
Bro, you need to open the box under the console on the passenger side. and you will see Android head just like SOFO888 said.
then you need to remove the thick black sticker and you will see a micro USB slot. with that slot, you can adb sideload apk. that is.
From a friend:
How to install applications on locked yuan/atto3​​On a USB drive (formatted in FAT32) create a folder called "third party apps" (WITHOUT the quotes)​​Inside that folder copy the apks you want to install​​Connect the USB drive to the USB data port of the car.​​You will see the screen to set a password​​Enter the password 20211231​
No need to sideload via ADB anymore.
Although I haven't tested this, you might be able to
1. install the unrestricted BYD package manager here: https://workupload.com/file/EgYhyaba92E
2. install app manager via here: https://github.com/MuntashirAkon/AppManager/releases
3. install Aurora OSS here: https://auroraoss.com/
4. install wireless adb switch from here: https://workupload.com/file/RsgTzvRKe6S
5. enable wireless adb via developer menu: Settings > tap on "restore" several times to show menu
6. launch app manager and grant permissions to aurora OSS to install packages
7. use Aurora OSS to install firefox and other non-google-drm apps
8. use firefox to install gbox and gbox apps via: www.gboxlab.com
insinc said:
From a friend:
How to install applications on locked yuan/atto3​​On a USB drive (formatted in FAT32) create a folder called "third party apps" (WITHOUT the quotes)​​Inside that folder copy the apks you want to install​​Connect the USB drive to the USB data port of the car.​​You will see the screen to set a password​​Enter the password 20211231​
No need to sideload via ADB anymore.
Although I haven't tested this, you might be able to
1. install the unrestricted BYD package manager here: https://workupload.com/file/EgYhyaba92E
2. install app manager via here: https://github.com/MuntashirAkon/AppManager/releases
3. install Aurora OSS here: https://auroraoss.com/
4. install wireless adb switch from here: https://workupload.com/file/RsgTzvRKe6S
5. enable wireless adb via developer menu: Settings > tap on "restore" several times to show menu
6. launch app manager and grant permissions to aurora OSS to install packages
7. use Aurora OSS to install firefox and other non-google-drm apps
8. use firefox to install gbox and gbox apps via: www.gboxlab.com
Click to expand...
Click to collapse
Good stuff bro, I'll test this weekend and will feedback here.
works in Thailand
SOFO888 said:
@insinc
Is this possible with every Android OEM head unit, like GM Mylink?
Thank you.
Click to expand...
Click to collapse
I do it on my GM head unit stock and install apks
Great to here that it is working on GM head units. Did you make it to install Google Maps?
Works like a charm for me in Japan too!! BUT the screen has dimmed alot even on full brightness, when on dash cam no problem but everything else is dimmed a lot now, anyone got any ideas?
@jollyboy1995
Can you PM me some pics of apps and how you did it? Thanks.
SOFO888 said:
@jollyboy1995
Can you PM me some pics of apps and how you did it? Thanks.
Click to expand...
Click to collapse
Harmon os -Gwm Haval -Range Rover -jaguar
Hey everyone just seeing if anyone could help currently have a stock unit which runs android 8.1 just looking for tips and tricks to make better experience Only website I have found so far is this for these headunits I have already installed...
forum.xda-developers.com
insinc said:
From a friend:
How to install applications on locked yuan/atto3​​On a USB drive (formatted in FAT32) create a folder called "third party apps" (WITHOUT the quotes)​​Inside that folder copy the apks you want to install​​Connect the USB drive to the USB data port of the car.​​You will see the screen to set a password​​Enter the password 20211231​
No need to sideload via ADB anymore.
Although I haven't tested this, you might be able to
1. install the unrestricted BYD package manager here: https://workupload.com/file/EgYhyaba92E
2. install app manager via here: https://github.com/MuntashirAkon/AppManager/releases
3. install Aurora OSS here: https://auroraoss.com/
4. install wireless adb switch from here: https://workupload.com/file/RsgTzvRKe6S
5. enable wireless adb via developer menu: Settings > tap on "restore" several times to show menu
6. launch app manager and grant permissions to aurora OSS to install packages
7. use Aurora OSS to install firefox and other non-google-drm apps
8. use firefox to install gbox and gbox apps via: www.gboxlab.com
Click to expand...
Click to collapse
this worked for me on byd atto 3 after softwer update. TNX
revy106 said:
Works like a charm for me in Japan too!! BUT the screen has dimmed alot even on full brightness, when on dash cam no problem but everything else is dimmed a lot now, anyone got any ideas?
Click to expand...
Click to collapse
yeah, your headlights are on. so the screen will only go to "night time" brightness. Day time brightness is so bright at night it's a safety hazard! Because during the day, the screen has to be bright enough it can beat the SUN!
so check if your headlights are set to "on" and change it to "auto" or "off" to get the android screen brighter.

Categories

Resources