Hi everyone,
So straight into the problem: I got my phone around the end of November 2018, which was when the Security Patch for that month came out. After that last update, I checked manually every month to see if there was another one. But after 12/14/2018, which was the last time I was able to check for updates, the phone would keep saying that it failed to download update, and a network or server error has occurred. I desperately need help.
View attachment 4685945
NahteT said:
So straight into the problem: I got my phone around the end of November 2018, which was when the Security Patch for that month came out. After that last update, I checked manually every month to see if there was another one. But after 12/14/2018, which was the last time I was able to check for updates, the phone would keep saying that it failed to download update, and a network or server error has occurred. I desperately need help.
View attachment 4685945
Click to expand...
Click to collapse
Boot into recovery & wipe the cache partition,reboot to system & then try again.
If that doesn't help,try using Samsung Smart Switch on your PC to update.
https://www.samsung.com/us/support/owners/app/smart-switch
KOLIOSIS said:
Boot into recovery & wipe the cache partition,reboot to system & then try again.
If that doesn't help,try using Samsung Smart Switch on your PC to update.
https://www.samsung.com/us/support/owners/app/smart-switch
Click to expand...
Click to collapse
Sadly, none of the two options worked for me. I have also tried booting into Safe mode, but the same problem would occur again. What else can I do, other than a factory reset?
NahteT said:
Sadly, none of the two options worked for me. I have also tried booting into Safe mode, but the same problem would occur again. What else can I do, other than a factory reset?
Click to expand...
Click to collapse
The only thing I can think of ATM is find the system apps responsible for system updates (two,I believe) wipe the cache & data ,if possible,from both,& try again.
If you are running an unadulterated version of the firmware that shipped with the phone,I'm stumped as to why you cannot update.
If you have any disabled apps perhaps enable them to rule out anything that might be causing this.
KOLIOSIS said:
The only thing I can think of ATM is find the system apps responsible for system updates (two,I believe) wipe the cache & data ,if possible,from both,& try again.
If you are running an unadulterated version of the firmware that shipped with the phone,I'm stumped as to why you cannot update.
If you have any disabled apps perhaps enable them to rule out anything that might be causing this.
Click to expand...
Click to collapse
Do you have to rely on ADB to wipe the cache and data? I found the two system apps that are used for Software Update (com.sec.android.soagent , com.wssyncmldm), but I can't seem to find the command code to do that.
NahteT said:
Do you have to rely on ADB to wipe the cache and data? I found the two system apps that are used for Software Update (com.sec.android.soagent , com.wssyncmldm), but I can't seem to find the command code to do that.
Click to expand...
Click to collapse
No,just navigate to Settings > Apps & tap on the 3-dot menu in the corner,select to view all/system apps & wipe each software update app.
If the buttons are greyed-out,then of course that can't be done.
KOLIOSIS said:
No,just navigate to Settings > Apps & tap on the 3-dot menu in the corner,select to view all/system apps & wipe each software update app.
If the buttons are greyed-out,then of course that can't be done.
Click to expand...
Click to collapse
I have just tried wiping the cache and data for the system apps, and also wipe the cache partition of the phone, yet nothing changes. I think what happened was that I accidentally disabled the two system packages for Software Update through ADB before this problem occurs, and now re-enabling them would have no effect.
NahteT said:
I have just tried wiping the cache and data for the system apps, and also wipe the cache partition of the phone, yet nothing changes. I think what happened was that I accidentally disabled the two system packages for Software Update through ADB before this problem occurs, and now re-enabling them would have no effect.
Click to expand...
Click to collapse
You can't re-enable apps that have been disabled by ADB w/o a factory reset.
In the future, you may want to consider using one of the Package Disabling apps that are available to avoid situations like this.
KOLIOSIS said:
You can't re-enable apps that have been disabled by ADB w/o a factory reset.
In the future, you may want to consider using one of the Package Disabling apps that are available to avoid situations like this.
Click to expand...
Click to collapse
If that's the case, then it wouldn't make sense that I were able to re-enable quite a lot of apps disabled by ADB. Or is this a special case where the crucial system apps that when disabled, they can't be re-enabled again?
NahteT said:
If that's the case, then it wouldn't make sense that I were able to re-enable quite a lot of apps disabled by ADB. Or is this a special case where the crucial system apps that when disabled, they can't be re-enabled again?
Click to expand...
Click to collapse
That would be my guess, otherwise, you should be able to update.
KOLIOSIS said:
That would be my guess, otherwise, you should be able to update.
Click to expand...
Click to collapse
Okay, I'll do a factory reset to see if this would solve the problem. Thanks for your help.
NahteT said:
Okay, I'll do a factory reset to see if this would solve the problem. Thanks for your help.
Click to expand...
Click to collapse
Please keep us posted on your outcome.
KOLIOSIS said:
Please keep us posted on your outcome.
Click to expand...
Click to collapse
So problem is solved: I did a factory reset, and the software update works just fine. I guess that the assumption about disabling crucial system apps caused them to not become re-enabled again must be right. Well I learned my lesson now - not to abuse ADB too much when it comes to bloatware. Thank you once again, I appreciate your help a lot.
NahteT said:
So problem is solved: I did a factory reset, and the software update works just fine. I guess that the assumption about disabling crucial system apps caused them to not become re-enabled again must be right. Well I learned my lesson now - not to abuse ADB too much when it comes to bloatware. Thank you once again, I appreciate your help a lot.
Click to expand...
Click to collapse
No problem, glad to be of help.
As for the ADB Removal & re-install of apps, I 1st heard about it from this XDA article/how-to:
https://www.xda-developers.com/uninstall-carrier-oem-bloatware-without-root-access/amp/
As it mentions the inability to re-install/re-enable apks, I just took their word for it & never uninstalled anything that I might need at some point.
That's why I like using package disablers, it's easily reversible without a reset.
Regardless, a factory reset isn't the end of the world, just a PITA at most.
Glad you got things going again.
Sorry to bother you again, but now I have problems with package disablers. I'm currently using a package disabler app, and it requires Device Owner App permission in order to disable bloatware apps, which can easily be done through ADB.
adb shell dpm set-device-owner com.pdp.deviceowner/.receivers.AdminReceiver
However, upon doing this, the lock screen of the phone will now show "This device is managed by your organization" at the bottom of the screen, and I don't feel comfortable about it. I have tried to uninstall the package disabler after done removing bloatware, but it wouldn't let me because the app is now a device administrator. I kind of screwed up myself after using the uninstall option inside the app, without knowing that it has completely uninstalled all the bloatware I disabled (instead of uninstalling the app itself), and caused my phone to stuck in boot loop, but I managed to fix that by another factory reset.
What kind of ADB command do I need so I can remove Device Owner App from the package disabler after I'm done disabling the bloatware?? (this is so ironic: disable a package disabler). Very sorry to disturb you again.
NahteT said:
Well I learned my lesson now - not to abuse ADB too much when it comes to bloatware..
Click to expand...
Click to collapse
Glad the problem was solved. My view is that concern with bloatware is a vestige of the past. On present-day phones, I'd guess that less than 0.1% of storage, memory, processor time, or battery charge are tied up with bloatware apps. So trying to identify and disable them won't have any noticeable benefit, and may well break things.
NahteT said:
Sorry to bother you again, but now I have problems with package disablers. I'm currently using a package disabler app, and it requires Device Owner App permission in order to disable bloatware apps, which can easily be done through ADB.
adb shell dpm set-device-owner com.pdp.deviceowner/.receivers.AdminReceiver
However, upon doing this, the lock screen of the phone will now show "This device is managed by your organization" at the bottom of the screen, and I don't feel comfortable about it. I have tried to uninstall the package disabler after done removing bloatware, but it wouldn't let me because the app is now a device administrator. I kind of screwed up myself after using the uninstall option inside the app, without knowing that it has completely uninstalled all the bloatware I disabled (instead of uninstalling the app itself), and caused my phone to stuck in boot loop, but I managed to fix that by another factory reset.
What kind of ADB command do I need so I can remove Device Owner App from the package disabler after I'm done disabling the bloatware?? (this is so ironic: disable a package disabler). Very sorry to disturb you again.
Click to expand...
Click to collapse
The message is just a generic one (as used when you grant admin rights for work e-mail,for example).
What it comes down to is if you trust the package disabler app & its developer,as I don't think there is any way to revoke the permission as long as you are using it to disable any apps at all.
I may be wrong on that,but,it seems like that's what's going on here.
If this still bothers you,then the next best solution is to continue using the disabling app long enough to determine which apps you are 100% certain are not needed/wanted.
Make a list & then switch to the ADB method.
That way,you get the admin rights to the disabler app off of your phone,but,you do give up the flexibility of the app as well.
The only way I see around your predicament is gaining root access & using the disabler app w/o admin rights,or,another app such as SD Maid Pro or Titanium Backup Pro.
Related
Device info:
Oneplus 3T, OOS 5.0.1 (Android 8.0), rooted with Magisk v15.3
Recently, my phone has been giving me an error message "Files has stopped " whenever I do anything that requires me to pick a file. and sometimes for no reason. Some examples include selecting a module to install in Magisk Manager, or selecting a file to attach in Gmail.
I highly doubt my root is involved, as I even reflashed the OOS 5.0.1 OTA to try to fix it. I've also tried wiping the cache of the apps File Manager, Files, and all caches in TWRP recovery.
The problem disappears if I reboot into safe mode, meaning it might be due to a rogue app. The problem also seemed to start after I used a USB OTG thumbdrive if it helps, that's the only major thing I remember doing.
Any ideas? Is there any info I can find in logcat to diagnose the problem?
Emeraldscorpion said:
...
I've also tried wiping the cache of the apps File Manager, Files, and all caches in TWRP recovery.
...
Click to expand...
Click to collapse
Try clearing the apps' data in Settings>Apps.
Also, have you installed a theme using Substratum? If so, try disabling it for the File* apps.
Sent from my OnePlus3T using XDA Labs
BillGoss said:
Try clearing the apps' data in Settings>Apps.
Click to expand...
Click to collapse
Yup, already tried clearing data in Settings.
BillGoss said:
Also, have you installed a theme using Substratum? If so, try disabling it for the File* apps.
Click to expand...
Click to collapse
Not using Substratum. I think it's safe to rule out any modifications to /system or any that require root, as the problem persisted even after I reflashed the 5.0.1 OTA.
If you're by chance using Xposed, then Scoop app might be helpful. But if not, you would have to connect your phone to PC, run logcat from there and pause when crash occurs.
With logs it will be easier to debug
przemcio510 said:
If you're by chance using Xposed, then Scoop app might be helpful. But if not, you would have to connect your phone to PC, run logcat from there and pause when crash occurs.
With logs it will be easier to debug
Click to expand...
Click to collapse
I've tried to browse it on-device using the app CatLog, but I have no idea what I'm supposed to be looking for! Any tips on what I should be focusing on?
Emeraldscorpion said:
I've tried to browse it on-device using the app CatLog, but I have no idea what I'm supposed to be looking for! Any tips on what I should be focusing on?
Click to expand...
Click to collapse
Maybe do it another way - start logging in an app, make Files crash and then stop. Paste the log at pastebin.com and link it here, we will see what's wrong
Been MIA due to exams.
I was trying the adb logcat method when I realised that the problem disappeared! Weird. Maybe the app causing it update again. Anyway, thanks for the help!
I used an application to hide my navbar, however, it was glitching and flickering forcing me to stop and uninstall the app.
Doing so permanently removed my navbar. Issue is any other replacent navbar I am not able to use. I must enable access in the accessibility option, however, when trying to do so I keep getting ''settings has stopped working'' error. How can I fix this?
Bump. Anyone? Even when trying other third party apps such as power toggles, I am unable to use the back, go home or recent apps menu....
Any way of restoring the soft navbar keys?? I am unable to do anything without them. The last resort would be to factory/data reset, wipe or re-flash rom. Please advise.
Try clearing cache in recovery mode.
Or
On PC with adb command uninstall the app but with the com.xxx.xxx name of the app.
Or
You can try to flash the stock rom 3 files + home-csc file (won't wipe data).
Or as you said factory reset.
BluePhnx said:
Try clearing cache in recovery mode.
Or
On PC with adb command uninstall the app but with the com.xxx.xxx name of the app.
Or
You can try to flash the stock rom 3 files + home-csc file (won't wipe data).
Or as you said factory reset.
Click to expand...
Click to collapse
I will try the second option, using adb command. I believe the name of the app that caused me this issue is ''Navigation Gestures''
This one - ''https://play.google.com/store/apps/details?id=com.xda.nobar
However, it was uninstalled yet my navbar is still missing. Ever since I tried other ones without success. How do I remove all the ones using adb?
Hi,
In the future, please contact us directly via email. If you uninstall the app without reverting the pill like we warned, this situation will happen. If you have access to ADB, you can manually re-enable the nav bar by running the following command:
adb shell wm overscan reset
The "glitching" and "flickering" by the way, happens if you use Samsung's nav bar hider and not ours. Version 1.2.0 of the app has much better compatibility with Samsung phones (tested personally on a Note 8.)
MishaalRahman said:
Hi,
In the future, please contact us directly via email. If you uninstall the app without reverting the pill like we warned, this situation will happen. If you have access to ADB, you can manually re-enable the nav bar by running the following command:
adb shell wm overscan reset
The "glitching" and "flickering" by the way, happens if you use Samsung's nav bar hider and not ours. Version 1.2.0 of the app has much better compatibility with Samsung phones (tested personally on a Note 8.)
Click to expand...
Click to collapse
Really worked the command. thanks
MishaalRahman said:
Hi,
In the future, please contact us directly via email. If you uninstall the app without reverting the pill like we warned, this situation will happen. If you have access to ADB, you can manually re-enable the nav bar by running the following command:
adb shell wm overscan reset
The "glitching" and "flickering" by the way, happens if you use Samsung's nav bar hider and not ours. Version 1.2.0 of the app has much better compatibility with Samsung phones (tested personally on a Note 8.)
Click to expand...
Click to collapse
I re-flashed my rom 2-3 times due to bootloop/not booting due to messing about with several navbar hiders, VERY surprised that messing with the navbar can prevent the phone from booting!
Even when trying Substratum with the paid addon, even this caused a bootloop/unable to boot.
I may of even tried your version, cannot remember, what is the latest version YOU have that has been tested and works with Note 8? I'll give that a try.
First of all i highly recommend you update your phone to latest version of Flyme as of day i write this guide newest stable version is 7.0.0.0G. It brings various bug fixes as well as security update and new functions. It fixed the weather problem too when it would not appear on secondary screen. This is my experience based on the standard model with Helio P25 chip.
JUST IN CASE BACKUP ALL OF YOUR DATA FIRST
Grab it at http://www.flymeos.com/firmwarelist?modelId=88&type=1
Installation is pretty straightforward:
-switch off your phone
-now press volume up button and power button at same time, then release power button when meizu logo appears
-phone now will enter update mode, connect it to pc and it should show up as removable drive named recovery, copy the update.zip over it
-once copied tap the start button to begin. the process itself and first boot will take a while
-when done and phone boots up just log in to your accounts and set up everything as normal or whatever
ta-dah ! you should be running latest software now.
Next problem i've encountered was big number of unwanted apps and you will need working ADB for that. I've always used custom roms which did not contain bloatware. Now im giving you one of the way of disabling them (not permanent removal).
For this to be done you need to activate developer mode and usb debugging, simply go to settings->about phone->and now tap on your build number several times
After you activate it it will be available in accessibility options under developer settings. just check the usb debugging and you're good to go
DISCLAIMER: dont ask me about adb drivers for your phone, since i had issues installing them under win 10 x64 build 1803 i thought "aw f*ck it" and just did it on linux where everything worked out of the box.
The application you will need is called Ice Box (you will find it here https://play.google.com/store/apps/details?id=com.catchingnow.icebox&hl=en_US) and install it.
After you install the app its necessary that you remove ALL of your accounts including your Google account. We will need to grant the app device owner permission. Also if multi-user or guest mode has been set on your device, it need to be closed or deleted.
When you have that done just type in your command line , terminal or whatever "adb shell dpm set-device-owner com.catchingnow.icebox/.receiver.DPMReceiver "
Now reboot and add your accounts back, and disable/freeze uwanted apps.
Last - the night mode. As its no longer availble in Flyme 7 if you want to use it you need to manually bring it back by installing Flyme Lab and enabling it trough quickshortcutmanager. Install both apps, then open quickshortcutmanager and search for Flyme Lab. expand it and choose the activity named com.meizu.flymelab/com.meizu.flymelab.component.nightmode.NightModeSettingsActivity .Create shortcut and open it. You should be able to enter the night mode.
Nice guides, thanks.
It's also nice that Flyme 7 still supports rooting, therefore I'm using Titanium Backup to freeze unwanted apps. I bought it when I was using another phone so, for me, it's still worth it. Altough, for uninstalling system apps I'm using separate ADB commands for each app.
cris2d2 said:
Nice guides, thanks.
It's also nice that Flyme 7 still supports rooting, therefore I'm using Titanium Backup to freeze unwanted apps. I bought it when I was using another phone so, for me, it's still worth it. Altough, for uninstalling system apps I'm using separate ADB commands for each app.
Click to expand...
Click to collapse
Its first time for me writing a guide so good word is always appreciated. What im trying to show here is the no root way of getting rid of apps for ppl like me who dont want to root their phone. As i bought it literally two days ago and i dont want to mess with it too much and loose warranty or/and OTA updates.
I also been considering posting a root guide once i tried it myself to confirm it working.
non.verbal said:
Its first time for me writing a guide so good word is always appreciated. What im trying to show here is the no root way of getting rid of apps for ppl like me who dont want to root their phone. As i bought it literally two days ago and i dont want to mess with it too much and loose warranty or/and OTA updates.
I also been considering posting a root guide once i tried it myself to confirm it working.
Click to expand...
Click to collapse
Well, before I discovered a rooting method for Flyme 7, I used to uninstall apps by using ADB commands. So, yes, it is possible to remove unwanted system apps without root. But now, after rooting Flyme 7, I'm only using Titanium Backup to freeze unwanted system apps, not removing them.
As far as I know, rooting Meizu phones by the official method (from Settings) does not lead to losing warranty. Only OTA updates are lost, but this is not important, at least to me, because I can always check Flyme website for new updates and, if I want to update, I just download the file and flash it through standard Flyme recovery. There is no need, for me, to maintain OTA capability. Anyhow, Flyme updates are slow to non-existent, so we can't really complain about losing an update.
Thank you all. I'm happy with this phone at all, but software has few shortcomings and design flaws, in my opinion. Especially related to the integration with "flyme login" and Touchpal. This last one is very annoying because although I try to stop it, at each software update it comes back, more annoying than ever. So, I have some questions: which is the adb command to stop and freeze bloatware without rooting? Which is the official way to root the phone? Once rooted, is it possible to revert to the unrooted state? Some apps, actually, do not work on rooted phones. Thanks
pask876 said:
Thank you all. I'm happy with this phone at all, but software has few shortcomings and design flaws, in my opinion. Especially related to the integration with "flyme login" and Touchpal. This last one is very annoying because although I try to stop it, at each software update it comes back, more annoying than ever. So, I have some questions: which is the adb command to stop and freeze bloatware without rooting? Which is the official way to root the phone? Once rooted, is it possible to revert to the unrooted state? Some apps, actually, do not work on rooted phones. Thanks
Click to expand...
Click to collapse
I can't freeze (or disable) apps with ADB commands, only uninstall.
You need [email protected], App Inspector or similar (to find exact name of package for an app) and these commands:
adb devices
adb shell
pm uninstall -k --user 0 name_of_package
Example, for gmail:
pm uninstall -k --user 0 com.google.android.gm
Regarding rooting, as far as I know, the only method that works on Pro 7 / Pro 7 Plus is also supported by Meizu (but it breaks OTA updates).
The method is described in this video (in russian) but it's quite easy.
If you want to remove root (or if root breaks functionality) you have to reflash the same ROM from Recovery (without wipe).
Any air update coming soon? Or manually installation single option?
com.miui.securitycenter
This thing along with 3-4 other security components , pretends to securize
But it does just the opposite. It's a legitimized spyware from Xiaomi in every MI UI ROM .
So I opened up the APK components - services broadcast receivers etc.
Here is what I am find ( see more in screenshot )
-
Code:
AdsProcessPriorityService
com.facebook.ads.internal.ipc.AdsProcess
PriorityService
AdsMessengerService
com.facebook.ads.internal.ipc.AdsMessen
gerService
On disabling these specific components - it will not let me change them my modifications are reset to their default
- Being rooted -I do a magisk hide on all non essential components. Here too certain components of Xiaomi including this one are forcibly unhidden from magisk
-try and disable this using pm disable and that will not work
-tried to use a third party tool To fine grain it's permissions and remove them.
Here I get a warning
Code:
"This is a system application, change
A
settings may cause serious problems.
The Shared user ID for this application is
android.uid.system, and applications with
the same Shared user ID share most of the
permissions.
"
I am opening up this thread so we can collaborate and think of how to MOD this app possibly or any other solutions where all these so called security components of Xiaomi can be thrown out without boot looping.
One approach would be model security component is loaded after booting and original one is thrown out through a magisk module.
Can someone please give Me an approach how to go about doing this
Thanks for sharing this information.
This is annoying and I would never have noticed since I regularly use the cleaning tool (it is my first time using a Xiaomi phone). I just checked the Security Center's data usage and it's been consuming a little bit of my mobile data and WiFi. It's only now I know where's that supposedly going to
What about removing authorization for the app?
What ROM is it on? I'm on the EU and there is nothing called this in the apps, even system apps. Closest app below as attached.
MIUI 11.0.3 Android version 9
xNAPx said:
What about removing authorization for the app?
Click to expand...
Click to collapse
Yeah there's an option to revoke Authorization but that is just window dressing. It is switched off and whether you switch it on or off it will behave exactly the same way it has absolutely no impact I I try to disable individual service components and those to remain as they are
did you try magisk debloater module? Bootloop? I am interested
xNAPx said:
did you try magisk debloater module? Bootloop? I am interested
Click to expand...
Click to collapse
xNAPx said:
did you try magisk debloater module? Bootloop? I am interested
Click to expand...
Click to collapse
you mean this right here nah thx I will give it a shot. My biggest concern is if there is some kind of APK checking going on for the system to boot then it will get stuck in bootloop and I had to restore /system once again -though the terminal apps says that it creates a dummy file
let me know because I have it on my phone and looking for newer ways to debloat my phone, I might give it a shot tomorrow as I plan to reflash my firmware from scratch with the latest fastboot global stable, the thing is we need to understand what dependencies has this app and what triggers them
By the way I already a jar debloater file that brought an applet which will let you enable disable install uninstall. Even after I disable a lot of bloatware or uninstall it - un-installing in redmi isn't permanent , that crap is still out there - dunno where its stored. And you can always reinstall after you have uninstalled. So that uninstall is just a lollipop. Hopefully magisk mod will trick it.
did you try the magisk module?
Nandroided /system and ran the debloat --> boot looped.
restored /system and I am still in boot loop
I had 2 Nandrois of system still got stuck . Finally got it to boot after restoring /vendor from an old backup.
Dunno why /vendor was affected at all.
sieger007 said:
Nandroided /system and ran the debloat --> boot looped.
restored /system and I am still in boot loop
I had 2 Nandrois of system still got stuck . Finally got it to boot after restoring /vendor from an old backup.
Dunno why /vendor was affected at all.
Click to expand...
Click to collapse
BTW boot loop was AFTER that Redmi logo @ Powered by android . I moved a week ago from Havoc to MIUI due to some limitations in the former. Even then a simple full Nandroid restore would''nt work & it got stuck the same spot (@ Powered by android .)
what d'e do now?
We should understand what dependencies this app has, because for sure once we delete it something is looking for it. What did you debloat safely so far?
Hey fellas ...'y dope on this?
Did you find the dependencies? I don't think there are alternatives otherwise. If it is a spy software xiaomi made this by purpose
xNAPx said:
Did you find the dependencies? I don't think there are alternatives otherwise. If it is a spy software xiaomi made this by purpose
Click to expand...
Click to collapse
ty . looking for dependencies ... yes obvious analysis. got any code or something hand that I can test out or work with to develop something ?.
Do you mean the package com.miui.analytics?
Did you try to debloat both? As well as MIUI daemon?
I don't have any code I'm afraid and I would know anyway I'm not a developer
xNAPx said:
Do you mean the package com.miui.analytics?
Did you try to debloat both? As well as MIUI daemon?
I don't have any code I'm afraid and I would know anyway I'm not a developer
Click to expand...
Click to collapse
Dad is no issue with De bloating analytics. Problem is security center
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