After returning 4 HDs that developed charging and other problems following the setting of the "allow unknown sources" flag, we decided not to tempt fate with the 5th Nook HD and then I discovered that apks can be installed via ADB, bypassing the Android setting. There is a drawback, of course--the apps cannot self-update.
I did this with a copy of an apk that's no longer available in the PlayStore and which I had already installed on my NT/CM10. What I forgot was that this package came with an Aptoide Store app attached. The desired app installed on the Nook HD and runs fine, but we now get periodic random messages like "this app cannot be installed" blah, blah, blah. I'm assuming this is because the Aptoide store is trying to install itself, but of course is blocked by the Android setting that won't allow unknown sources.
My question: where do you suppose this uninstalled package is hiding? If I try to use the ADB uninstall command as if it were already installed, will that expunge it?
Hey all. Running the next-to-latest version of Chroma (3/15 I think; the one that can be clean flashed and not 3/18 though I might just flash the new version and hope for the best if I can't figure this out). I've successfully granted root access since installing the ROM (doubletap to wake app), but now when apps ask for su I get the prompt and can't tap any of the options. I tried to open the SuperSU app but it doesn't exist in my drawer. It shows that it's installed under "All Apps" in settings>apps, and on the play store it says "Installed" but won't allow me to open/uninstall. I flashed a package called "UPDATE-SuperSU-v2.46.zip" through TWRP right after flashing Chroma.
Edit: Running Franco Kernel nightly r20, gapps-L-3-17-15, most recent thing I installed was FDroid marketplace which I haven't even opened yet and vomertweaks which is the first app to try and get permissions and fail.
Update: Turns out that SuperSU was in my system apps (I hadn't installed it that way before; my bad). I still couldn't get it to cooperate, even with reinstallations. Flashed the new version of Chroma and the same SuperSu package, working so far.
Phone: HTC One M8 HK modelid: 0P6B70000, cidnum: SPCS_004; S-ON; Bootloader 3.19; Rooted; TWRP 3.2
ROM: Stock, updated 6.20.654.3
I wanted to utilize Titanium Backup but I discovered that I need to have BusyBox installed. I have TWRP and root. So I went to install BusyBox and ran into all kinds of problems.
First, there are several busybox installer apps out there. I tried a few and although the app would install, the install busybox function wouldn't work. I'd click "install" and then it would sit there doing nothing. In a few moments, a cascade of Google and HTC service apps would start to crash. A real mess. I would reboot and try again... same thing. Cleared cache of Google and HTC services... no difference.
During the process and chaos of notification messages popping up about this service or that service stopping, I caught notice of a SuperSU receiving a request to grant permissions from BusyBox. But by the time I could get access to grant it (clearing away other notifications), the busybox installation would have already aborted.
Older posts about this problem claimed "busybox on rails" would fix this. I tried and it didn't. I then tried the Stericson busybox. Same service crashes started happening once again. So the problem appeared to be some peculiar delay, where the SU request from an app is not getting to SuperSU in time for being granted permission. With Stericson busybox, I was able to finally grant access in SuperSU, although it had aborted. With the grant already done, restarting the Stericson busybox install allowed it to proceed to the next step of getting the Smart Installer loaded. During that process, I kept having to clear away notifications of services and apps crashing. That kept continuing as busybox actually installed. So I kept closing notifications until busybox finished installing. The Root# app verified busybox is installed correctly. The service crashes stopped. Opening the busybox installer app works fine now.
I eventually discovered the install issue... the SuperSU app has a "tapjacking" feature, whereby an su permission request dialog won't respond to input while obscured by other window/overlay. I found that Titanium Backup Pro wouldn't recognize busybox being installed, as SuperSU hadn't received any request from Titanium. I'm guessing that this caused a clash at a fundamental level, to cause services to crash? I unchecked the tapjacking option and finally I could grant Titanium Backup su permission. And now I'm able to use TBP (Titanium Backup Pro). However... it's not working quite right. When I attempt to backup user apps, some will be backed up but others are extremely slow or fail. Busybox Free 55 (Stericson) causes TBP to completely crash. OK, so I went to skip backing up that app. I then started to do one app at a time. Some apps would backup quickly, while others take an extraordinarily long period of time. Cardboard 1.8 was extremely, painfully slow (which is 456Mb). I hadn't used that app in a long while, so I just deleted it. But then when attempting to backup Excel (220mb), TBP stalled on that app... eventually completed it. Backup just seems very slow. But I can live with that as long as backups have integrity.
So I'm feeling like something might not be quite right with my system. Everything generally seems to be fine. With tapjacking disabled, SuperSU is fielding requests without services crashing. The only really bizarre thing is that TBP is simply unable to backup busybox. Anytime I try to do it, TBP crashes. Very strange. Do I need to stop and disable it first?
Device: SM-N950F
Android version: 9
Magisk version name: com.topjohnwu.magisk
Magisk version code: 22,1 (22100)
Well I believe this is an alien thing going on.
Magisk was working fine.
I just had a notification to update Magisk in the notifications bar.
I simply accepted, something showed downloading and then nothing happened.
So I just then went to check Magisk. I opened it and I chose to install latest 22.1 (22100) (20) App.
Well it downloads, I install it succesfully but then Magisk manager (already hidden and renamed) doesn't open.
It just shows a message "Magisk Manager: Upgrade to full Magisk Manager to finish the setup. Download and install?" I press OK , it downloads for some seconds something and then it shows a toast message "Please manually re-launch the app".
I re-launch Magisk Manager and get again "Magisk Manager: Upgrade to full Magisk Manager to finish the setup. Download and install?"...
A continuous loop in other words with no successful outcome.
Now:
Some apps that require root still work
A banking app is still working, another sees rooted and stops
Rootchecker app shows "root access is not properly installed"
Root check app shows "rooted"
In other words a big fat mess!
I strongly fear that If I reboot the device I will lose all remaning root capabilities. Correct???
I think of flashing with TWRP "Magick 22.zip" but then this may mean fresh rooting and ALL data will be lost. Correct???
Thank you all in advance, God bless you!
No reply! Smells bad!!
Can you uninstall magisk?
Then try to use TWRP to install Magick 22.zip
sammiev said:
Can you uninstall magisk?
Then try to use TWRP to install Magick 22.zip
Click to expand...
Click to collapse
I can uninstall only through Titanium Backup since Magisk Manager isn't working.
I also wonder if I will lose data after uninstalling and flashing Magisk 22.zip
awarexda said:
I can uninstall only through Titanium Backup since Magisk Manager isn't working.
I also wonder if I will lose data after uninstalling and flashing Magisk 22.z
Click to expand...
Click to collapse
You should always backup your data before doing anything.
https://magiskmanager.com/uninstall-magisk
sammiev said:
You should always backup your data before doing anything.
https://magiskmanager.com/uninstall-magisk
Click to expand...
Click to collapse
I know that it is always safe to backup data but I also know how time consuming is to bring phone to earlier state...
sammiev said:
You should always backup your data before doing anything.
https://magiskmanager.com/uninstall-magisk
Click to expand...
Click to collapse
that's not official Magisk website the only official is the github page https://www.xda-developers.com/psa-magiskmanager-com-not-official-website-magisk/
Today I will restart device.
Fingers crossed (nandroid backup + all data of SD card to PC + TitaniumBackup)!
I restarted it today.
It loaded OK and some banking app that was seeing root now just works fine.
Magisk Manager still doesn't open and I am worried to flash Magisk22.zip because I may lose data and can't handle the hassle to restore all settings etc.
Very weird situation.
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