Due to my previous wrong operation, I cannot manage su now.
I tried to download Magisk uninstall.zip in git tonight, uninstall and then install, install and uninstall, Magisk app is always there (because it was installed by me as a system application).
I have tried adb uninstall (adb uninstall com.topjohnwu.magisk), but I cannot get root privileges.
I tried both of the two uninstall methods in the app, but they didn't work. Every time I restarted, it was still the same.
I cannot use magisk to authorize other applications, nor can I uninstall it from the system software.
In addition, after every restart, it will say that the `su database is damaged, the database will be rebuilt`, and then I restarted again, opening magisk is still the same prompt.
Related
So, I updated the mobile banking to 2.0 and it force closes every single time. Then I read that everyone was uninstalling then reinstalling and it worked. Problem is I can't find the 1.0 apk to reinstall then uninstall. Uninstalling and reinstalling 2.0 doesn't help at all. I've done it at least 10 times. Any suggestions?
This happened to me last night, but I simply uninstalled the new 2.0 and reinstalled it and it worked fine. Maybe reboot?
This is what I had to do....
First, uninstall the program
Second, into terminal emulator and type in: rm -R /data/data/com.infonow.bofa
Third, reboot and reinstall
And Voila!
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>
Hi, hopefully this is a good place for this topic. I have note 9 and Facebook is pre installed. I would like to install dark Facebook but before I have to uninstall this pre installed Facebook. I try adb command method but it didn't work. I meant adb method was successful but apparently adb command method hide apk instead of uninstall. Is it any chance to uninstall pre installed Facebook without root?
It can't be removed without root
Hello.
I uninstalled Find Device (pm uninstall -k --user 0 com.xiaomi.finddevice) to avoid its periodic enabling reminders.
However now sometimes "find device has been destroyed" appears as a toast. Also the Security Status in the Settings now crashes.
After finding this message (despite it is other phone model) I'm frightened about a future reboot of my phone. Can my phone really enter in a boot loop the next time I reboot? I have the miui optimization disabled, though.
I have tried to install it back, downloading the 9.0 apk, but it says INSTALL_FAILED_ALREADY_EXISTS. Using the "-r" switch also doesn't works ("com.xiaomi.finddevice is a persistent app. Persistent apps are not updateable"). I assume that this is due to haven't erased the app data (uninstalled with -k) but "pm clean" doesn't seems to clean it. I also have tried the -p option for partial installation, but returns a null exception.
Ah, my device is not rooted. MIUI Global 10.2 stable.
I managed to restore the application with the following adb command:
Code:
pm install-existing com.xiaomi.finddevice
It also works with applications uninstalled without "-k 0".
By the way, I used to use "pm disable", but now it seems it is called "pm disable-user".
So, next time I'll preferably use it instead of uninstalling, if works as expected.
Note that it doesn't allows to disable finddevice:
Code:
$ pm disable-user com.xiaomi.finddevice
Package com.xiaomi.finddevice new state: default
The package still continues in default state, unlike when it actually works:
Code:
$ pm disable-user com.miui.player
Package com.miui.player new state: disabled-user
Credits for these great discoverings to this blog post (eskerahn.dk/wordpress/?p=2462) [add the https prefix, I can't yet post urls!]
is there a any way to uninstall this application without trouble (without bootloop)?
i have the same question is there a any way to uninstall this application without trouble (without bootloop)?
If it doesn't boot, it's awesome tho.
Without modifying the vendor ROM image there is no way to get rid of it.
So, an OTA caused a loss of root (pixel 6 pro, unlocked). Tried to go into a hidden magisk and disable modules, but everything greyed out, unable to. Tried to uninstall the manager (I was using an old MagiskAlpha build), and thought it worked, though it must have left something behind. Updating wouldn't work - would give me a failure.
Flashed new factory image, installed new magisk manager, patched boot.img in new magisk manager, loaded boot.img, and I have root; adb shell su works, all my old apps that worked with root work, but no magisk manager recognizing that I have root - and therefore no modules - working. So, no charging management, safetynet is borked, etc. Have uninstalled/reinstalled mm numerous times. No luck. Tried loading it from adb, etc.
I've dug through adb shell pm list packages and can't find anything that looks like an old version of magisk at all anywhere anymore. I think I had three different versions on the phone. They are all gone. But no luck with a freshly installed manager. Still can't see root even though it's there. Any ideas?
Of note: I have a work profile and two users on the phone. However, I can't find anything even using --user for all three users. Only thing even close I see is com.lsposed.manager still installed. That shouldn't be a factor, but I can't think of anything at this point.
TB checker, under "check root" gives pass for everything except SU binary, 2nd SU binary, root via native, and magisk specific.
Under Check xposed, I have fail for dual/work profile and xprivacyLua, and com.topjohnwu.magisk under PM Sundry APIs. Everything else is Pass.
I had never granted TB checker root before; Termux on the other hand works fine with su (as does adb shell), and Root Essentials shows root fine.
Magisk Manager was downloaded from topjohnwu's github, then I manually added the canary URL, and updated to canary. No luck.
Any other ideas?
One other thing... /data/adb/magisk was dated; all the other directories in /data/adb were new, but magisk was from my last update of MagiskAlpha, and when I looked at util_functions.sh it was aligned to my old (uninstalled) magisk alpha build
So, the /data/adb/magisk tipped me off. I pulled the hidden apk info from the magisk.db, and from there was able to (while rooted) manually delete all the references to the hidden apk string (just did a find /data/* | grep [hidden package name] ) and once they were all deleted, deleted everything from /data/adb - the magisk.db and everything - and then next time I went into magisk, it informed it was incorrectly configured, I pressed okay, it fixed itself, and full root in magisk was restored.
had to reinstall all modules, but that wasn't a very big price to pay. Safetynet fixed (google pay worked just fine at the store yesterday), xprivacylua, etc., all worked.
As of right now, other than a citi app *****ing that I'm possibly rooted (and then it still works fine anyway), haven't had any issues with leaving magisk unhidden, so not going to hide it again unless I need to. Wasn't worth the PITA to fix it if something like this happens again.