Database Users

Cannot re-enable apps that I've disabled.

I have a thing against having lots of apps in my app drawer that I never use. I always go through and disable ones that I won't need. Well, I disabled some of the ZTE apps like My Voice, and now I can't re-enable them. When I go to app info, it shows "disabled" on the list for the app, but when I tap it, there is an "enable" button that is grayed out.
I'd like to be able to do this without factory resetting the phone.

If you can get ADB running to connect the phone to the PC try this
adb shell pm list packages -d
adb shell pm unhide package.Name

peramikic said:
If you can get ADB running to connect the phone to the PC try this
adb shell pm list packages -d
adb shell pm unhide package.Name
Click to expand...
Click to collapse
:laugh: looks like we are all here , by the way wont work (unhide command) needs to be " pm enable " and requires system access (root) "Permission Denial" , i try with a disabled app(s), just hope we get that update soon to avoid all this problems
P.S. yeah i'm the guy from ZTE forum

Haha good to see you guys!

Too bad on the ADB pm cmd, i was 50/50 on it working
I need to find a way to auto-post to both forums through :laugh:

biglilsteve said:
Haha good to see you guys!
Click to expand...
Click to collapse
peramikic said:
Too bad on the ADB pm cmd, i was 50/50 on it working
I need to find a way to auto-post to both forums through :laugh:
Click to expand...
Click to collapse
LoL, good to see people from ZTE Forums here too hehehe and yeah this is what i get when trying to enable it back (using terminal app but is the with ADB)

DrakenFX said:
LoL, good to see people from ZTE Forums here too hehehe and yeah this is what i get when trying to enable it back (using terminal app but is the with ADB)
Click to expand...
Click to collapse
Technically i went there from here
Looks like you ran directly from terminal emulator. I'm not sure, but ADB shell might run under a different UID and have more permissions. This might have changed in MM, but you could use pm command to grand permission to Greenify package on non rooted devices

Was there ever a fix for this? I am running into the same issue and can't re-enable apps.

imp3r10 said:
Was there ever a fix for this? I am running into the same issue and can't re-enable apps.
Click to expand...
Click to collapse
Are you on software version B27?

xtermmin said:
Are you on software version B27?
Click to expand...
Click to collapse
B20

imp3r10 said:
B20
Click to expand...
Click to collapse
Update to B27 (and maybe factory reset). I'm pretty sure this was one of the things fixed in B27.

xtermmin said:
Update to B27 (and maybe factory reset). I'm pretty sure this was one of the things fixed in B27.
Click to expand...
Click to collapse
Oh. I was putting off upgrading until I got root and there was more development in the phone to recover corrupt devices.

xtermmin said:
Update to B27 (and maybe factory reset). I'm pretty sure this was one of the things fixed in B27.
Click to expand...
Click to collapse
Are you sure about this? I have seen posts on ZTE board saying that apps can no longer be enabled/disabled with B27. With B20 you can at least do disabling (I am not sure about enabling).

some you can some you can't. you can disable ZTE browser, but can't disable ZTE calendar or ZTE messanger for instance.

For disabling apps, are you using a different launcher?
Launch the Stock Android launcher and disable apps through the app drawer - I've successfully disabled ZTE calendar and messenger on my device.
Re-enabling seems another problem altogether though..

imp3r10 said:
Oh. I was putting off upgrading until I got root and there was more development in the phone to recover corrupt devices.
Click to expand...
Click to collapse
B27 can still be rooted and bootloader unlocked. No real reason not to update.

no such love for B27

mh127 said:
Are you sure about this? I have seen posts on ZTE board saying that apps can no longer be enabled/disabled with B27. With B20 you can at least do disabling (I am not sure about enabling).
Click to expand...
Click to collapse
That was something else that was changed.
On B20, if you disabled apps in Settings > Apps, sometimes you would not be able to re-enable them.
(What you're talking about) On B20, if you use the Stock Android theme, if you press and hold on an application icon, there's a "Disable" option at the top of the screen that you can drag the icon to. Using this method, you could disable apps that you couldn't via Settings > Apps, such as the ZTE Calendar and Messaging apps. However, this allowed you to disable things that could cause issues with the device, such as disabling Settings or the Dialer. If you disabled apps this way, you could not re-enable them via Settings > Apps.
On B27, you can still disable apps in Settings > Apps, and people haven't reported having issues re-enabling them.
On B27, the "Disable" option in the Stock Android theme has been removed. So while you're not able to disable some stock apps, you cannot accidentally disable something that could break the OS.

xtermmin said:
On B27, you can still disable apps in Settings > Apps, and people haven't reported having issues re-enabling them.
On B27, the "Disable" option in the Stock Android theme has been removed. So while you're not able to disable some stock apps, you cannot accidentally disable something that could break the OS.
Click to expand...
Click to collapse
Thanks - hadn't noticed that difference with B27 till now.
However, I've disabled the stock clock, and can no longer re-enable it through the App settings.
There does appear to be another solution (I haven't tried it though) - from the App settings, if you select the 3 dot menu on the top right, the option to reset app preferences should re-enable apps (and reset other settings as well).

An Droid said:
Thanks - hadn't noticed that difference with B27 till now.
However, I've disabled the stock clock, and can no longer re-enable it through the App settings.
There does appear to be another solution (I haven't tried it though) - from the App settings, if you select the 3 dot menu on the top right, the option to reset app preferences should re-enable apps (and reset other settings as well).
Click to expand...
Click to collapse
Did you disable it back in B20? Cause when I look at the stock clock in B27 on my device, the disable option is greyed out.

Use this command to get your root changes to persist after a reboot

Thanks and all credit to Nameless One for the heads-up!
As found here - run this adb command to get changes to survive a reboot:
Code:
adb shell reboot disemmcwp
It seems there's system write protection enabled. That command will disable it. I changed my DPI and emojis and can confirm that both changes stuck!

goalkeepr said:
Thanks and all credit to Nameless One for the heads-up!
As found here - run this adb command to get changes to survive a reboot:
Code:
adb shell reboot disemmcwp
It seems there's system write protection enabled. That command will disable it. I changed my DPI and emojis and can confirm that both changes stuck!
Click to expand...
Click to collapse
Nice find, I'll be adding this thread to my Guides / Info Thread....
Thank you dude

Cool Awsome!! Now my phone is working properly with ROOT.

Is this step still needed? Been following the links on DrakenFX's thread that lead me here.
Thanks guys. The dev is much appreciated as is the guide pulling everything together.

Barsky said:
Is this step still needed?
Click to expand...
Click to collapse
Whether it is done by a script (if so there should be clear indication that it does this so people know where they stand in the overall process) or by hand it still needs to be done, it is a completely separate issue from whether or not the boot-loader is unlocked or the phone rooted.

Already did it. :cyclops:

Is this only needed if your bootloader is locked but you still wanna root ?

Ugh, so this was the reason why I couldn't uninstall system apps even w/ a system app uninstaller....
So developer unfriendly :/

Haha needed to do this on the official root for EU as well.

Yay, thanks guys! got adaway running. Starting to feel like home again..now to backup it before I screw it up..

I'm not getting it to work on my Axon 7 rooted with terminal emulator
Sent from my ZTE A2017U using XDA-Developers mobile app

Tried using emulator. No go. Tried using adb shell. still no go...
Can one of you explain to me the exact method? Maybe im doing something wrong

nickcaper said:
Tried using emulator. No go. Tried using adb shell. still no go...
Can one of you explain to me the exact method? Maybe im doing something wrong
Click to expand...
Click to collapse
Boot into A7, enable developer options and enable USB Debugging, connect to computer, accept the computer's debugging signature on your A7 (if you've never gotten a pop-up that you've had to accept, it's not connected properly), type in "adb devices" in a command prompt to make sure that the device is showing up, and if it is, issue the OP's command.

xtermmin said:
Boot into A7, enable developer options and enable USB Debugging, connect to computer, accept the computer's debugging signature on your A7 (if you've never gotten a pop-up that you've had to accept, it's not connected properly), type in "adb devices" in a command prompt to make sure that the device is showing up, and if it is, issue the OP's command.
Click to expand...
Click to collapse
yes, tried that. phone rebooted and still.. cant delete/remove system apps... aggrivating. ill try again later.. im tired of messing with this nonsense...
---------- Post added at 02:50 AM ---------- Previous post was at 02:23 AM ----------
Tried it again, all it does is reboot.. I open RU uninstaller Pro and its still saying the same thing. That permissions are not granted.

nickcaper said:
yes, tried that. phone rebooted and still.. cant delete/remove system apps... aggrivating. ill try again later.. im tired of messing with this nonsense...
---------- Post added at 02:50 AM ---------- Previous post was at 02:23 AM ----------
Tried it again, all ti does is reboot.. I open RU uninstaller Pro and its still saying the same thing. That permissions are not granted.
Click to expand...
Click to collapse
Open the SuperSU app and make sure that you gave RU uninstaller root permissions.

xtermmin said:
Open the SuperSU app and make sure that you gave RU uninstaller root permissions.
Click to expand...
Click to collapse
tried that yo... aint happnin....
any other ideas?
When I plug the phone into the laptop, the phone has a popup that sks me which mode I want to use the phone.
I choose Media device MTP. I also tried the mode called connect to PC software. Both times, the phone is recognized by ADB.
yet it will not fix the permissions

nickcaper said:
tried that yo... aint happnin....
any other ideas?
When I plug the phone into the laptop, the phone has a popup that sks me which mode I want to use the phone.
I choose Media device MTP. I also tried the mode called connect to PC software. Both times, the phone is recognized by ADB.
yet it will not fix the permissions
Click to expand...
Click to collapse
Go into the app's permissions list and make sure that the Storage permissions is allowed.
If that doesn't work, then try using a different app all together.

xtermmin said:
Go into the app's permissions list and make sure that the Storage permissions is allowed.
If that doesn't work, then try using a different app all together.
Click to expand...
Click to collapse
Doesnt work..
I am thinking the problem is that ZTE put a lock on system files so no one can delete them or modify them.
There is suppose to be some kind of way to turn that off but I cant seem to do it on my phone.

nickcaper said:
Doesnt work..
I am thinking the problem is that ZTE put a lock on system files so no one can delete them or modify them.
There is suppose to be some kind of way to turn that off but I cant seem to do it on my phone.
Click to expand...
Click to collapse
/system has write protection enabled by default, but the command in the OP disables it. After turning it off by running that command, I'm able to uninstall apps via Titanium Backup fine.

xtermmin said:
/system has write protection enabled by default, but the command in the OP disables it. After turning it off by running that command, I'm able to uninstall apps via Titanium Backup fine.
Click to expand...
Click to collapse
Can you tell me if your phone is rooted? what update version si your phone? Mine is 27.
Did you do this permission fix before or after root? did you use an emulator to do the fix or adb?

Gsam on Nougat - how to grant permissions to see all battery usage on all processes

I just noticed this when I opened up Gsam , the latest version:
Use adb shell so plug in the cable to the PC/Mac/linux whatever:
execute this:
adb shell pm grant com.gsamlabs.bbm android.permission.BATTERY_STATS
Click to expand...
Click to collapse
That's it. No root necessary.

hachamacha said:
I just noticed this when I opened up Gsam , the latest version:
Use adb shell so plug in the cable to the PC/Mac/linux whatever:
execute this:
That's it. No root necessary.
Click to expand...
Click to collapse
Thanks! But do you have to do this every time you reboot or do you need to do this just once and it sticks? And what will happen if you update firmware (minor update)? Do you have to do it again?

droid27 said:
Thanks! But do you have to do this every time you reboot or do you need to do this just once and it sticks? And what will happen if you update firmware (minor update)? Do you have to do it again?
Click to expand...
Click to collapse
You have to do it once / release. When you upgrade, these types of settings are usually volatile. I just cut & paste it and do it once / version. It's working for me now on b360.
Edit: I thought about that some more and forgot that I had to rollback to 162 before I went back up to 360. Rollback kills all data, so maybe I had to enter the permissions statement due to that.

hachamacha said:
You have to do it once / release. When you upgrade, these types of settings are usually volatile. I just cut & paste it and do it once / version. It's working for me now on b360.
Edit: I thought about that some more and forgot that I had to rollback to 162 before I went back up to 360. Rollback kills all data, so maybe I had to enter the permissions statement due to that.
Click to expand...
Click to collapse
Thanks! So we have to do this every time there's a system update but do we have to do this every time we reboot or it sticks?

droid27 said:
Thanks! So we have to do this every time there's a system update but do we have to do this every time we reboot or it sticks?
Click to expand...
Click to collapse
I've done it once when upgrading to b360 Nougat and it has held and worked fine through a few reboots and a number of system changes. So, .. once should do it, but I'd never expect it to outlast an upgrade of OS.

I can't seem to get this to work. I've tried three times now and restarted the app and my phone every time.
I also tried including "-d" between "adb" and "shell" in the command (I saw this version on another page) but still nothing.

F1Fanatic27 said:
I can't seem to get this to work. I've tried three times now and restarted the app and my phone every time.
I also tried including "-d" between "adb" and "shell" in the command (I saw this version on another page) but still nothing.
Click to expand...
Click to collapse
You don't normally need the -d unless you've currently got more than one usb connected phone that adb could get to.
This command comes documented straight out of the latest version of GSAM. It actually tells you under help or in settings. I don't have a phone in front of me but the command is identical to whatever I put ^^ up there. I just tried this command on an unrooted Oneplus 5 running 7.1.1 and it worked fine there as well.
I wonder if there's any way you could have installed it without some basic permission that's a prerequisite for the usually unshown android.permission.BATTERY_STATS permission. You could go into apps and permissions and make sure it's got permission to write or whatever it's basic permissions should be. There's probably two or three.

hachamacha said:
You don't normally need the -d unless you've currently got more than one usb connected phone that adb could get to.
This command comes documented straight out of the latest version of GSAM. It actually tells you under help or in settings. I don't have a phone in front of me but the command is identical to whatever I put ^^ up there. I just tried this command on an unrooted Oneplus 5 running 7.1.1 and it worked fine there as well.
I wonder if there's any way you could have installed it without some basic permission that's a prerequisite for the usually unshown android.permission.BATTERY_STATS permission. You could go into apps and permissions and make sure it's got permission to write or whatever it's basic permissions should be. There's probably two or three.
Click to expand...
Click to collapse
You were bang on with the permissions, I didn't have Storage enabled. Didn't make a difference though. I even checked the advanced permissions (Usage access, draw over other apps etc..) and there wasn't anything there to activate.

F1Fanatic27 said:
You were bang on with the permissions, I didn't have Storage enabled. Didn't make a difference though. I even checked the advanced permissions (Usage access, draw over other apps etc..) and there wasn't anything there to activate.
Click to expand...
Click to collapse
Did you "force-close" the app after you enabled storage and reenabled the android.permission.BATTERY_STATS? If so, other than uninstall/reinstall and try again, I'm not sure. Are you running stock OS? There can always be something quirky in anyone's install that I'll never figure out. Good luck.
The only thing I recall is that the command doesn't do anything until after you've executed it, force closed and re-started the app. If it doesn't work then, then something else is going on.

F1Fanatic27 said:
You were bang on with the permissions, I didn't have Storage enabled. Didn't make a difference though. I even checked the advanced permissions (Usage access, draw over other apps etc..) and there wasn't anything there to activate.
Click to expand...
Click to collapse
You ever figure this out? I tried granting this permission on several monitoring apps and none work. It's a new phone and I feel like I broke it.

StewMaker said:
You ever figure this out? I tried granting this permission on several monitoring apps and none work. It's a new phone and I feel like I broke it.
Click to expand...
Click to collapse
I've done it on my phone recently. What steps did u follow?
Sent from my Honor 8 using XDA Labs

ayush rao said:
I've done it on my phone recently. What steps did u follow?
Sent from my Honor 8 using XDA Labs
Click to expand...
Click to collapse
I basically followed instructions from the apps.
I installed adb, device drivers, then in cmd, "adb devices" then "adb shell pm grant app_goes_here android.permission.BATTERY_STATS".
It worked once for BBS and GSAM, but never stuck. Now it doesn't work at all.

StewMaker said:
I basically followed instructions from the apps.
I installed adb, device drivers, then in cmd, "adb devices" then "adb shell pm grant app_goes_here android.permission.BATTERY_STATS".
It worked once for BBS and GSAM, but never stuck. Now it doesn't work at all.
Click to expand...
Click to collapse
I did it like 2 months back and it is still working.
Sent from my Honor 8 using XDA Labs

ayush rao said:
I did it like 2 months back and it is still working.
Sent from my Honor 8 using XDA Labs
Click to expand...
Click to collapse
I am sure it works for you and many other people but there are a few of us like OP who it does not work for. Just saying it works for you doesn't help me.

StewMaker said:
I am sure it works for you and many other people but there are a few of us like OP who it does not work for. Just saying it works for you doesn't help me.
Click to expand...
Click to collapse
U have a point oops. Anyway in ur previous post in ur command there's some "goes here" did u include that in the command or did u just write it for the post?
Sent from my Honor 8 using XDA Labs

Here is the exact command to be written. When I was doing it even I couldn't get it to work but later I realized I was writing gasm instead of gsam.
Sent from my Honor 8 using XDA Labs

ayush rao said:
Here is the exact command to be written. When I was doing it even I couldn't get it to work but later I realized I was writing gasm instead of gsam.
Sent from my Honor 8 using XDA Labs
Click to expand...
Click to collapse
Mine worked until I rooted at which point root takes care of that problem without the shell command.
The one thing I can think of is that the command differs (I read this somewhere) if you have GSAMPRO rather than GSAM (by just a word) and you'd have to google the correct word and substitute it. I got this the first time I started GSAM in an unrooted environment and just noted it. It showed up in a dialogue box on GSAM.

What iam doing wrong? :
adb>adb shell pm grant com.gsamlabs.bbm android.permission.BATTERY_STATS
Bad argument: java.lang.IllegalArgumentException: Unknown package: com.gsamlabs.bbm
Edit: problem solved: I have the Pro version and so the item was: 'com.gsamlabs.bbm.pro'

ayush rao said:
U have a point oops. Anyway in ur previous post in ur command there's some "goes here" did u include that in the command or did u just write it for the post?
Sent from my Honor 8 using XDA Labs
Click to expand...
Click to collapse
That's no problem. Hey, a response is better than no response.
I wrote the actual application name, not the goes here. Just a placeholder.

Sorry, but what is there a way to run this command locally in the Android Terminal Emulator?

[No Root] Remove the banner ad on the main screen

Wasn't sure if this has been posted before. Wanted to share.
Connect with adb and run...
Code:
pm uninstall -k --user 0 com.amazon.kso.blackbird
reboot
I'm not sure if the -k or --user 0 are necessary but its the same used on the kindle fire
I haven't tested but only way believed to return it is factory reset.

[email protected]:/ $ pm uninstall -k --user 0 com.amazon.kso.blackbird
Success
[email protected]:/ $ reboot
It seems to work, thanks!

Somebody sticky this.

krsmit0 said:
Wasn't sure if this has been posted before. Wanted to share.
Connect with adb and run...
I'm not sure if the -k or --user 0 are necessary but its the same used on the kindle fire
Click to expand...
Click to collapse
nyln said:
[email protected]:/ $ pm uninstall -k --user 0 com.amazon.kso.blackbird
Success
[email protected]:/ $ reboot
It seems to work, thanks!
Click to expand...
Click to collapse
So no ROOT needed (no # in the instructions) ? What would be the input to reverse this? It's always good to have the antidote, just in case.

Y314K said:
So no ROOT needed (no # in the instructions) ? What would be the input to reverse this? It's always good to have the antidote, just in case.
Click to expand...
Click to collapse
Correct, no root. And without trying it, the only way to return it is a factory reset or a OTA update.

krsmit0 said:
Correct, no root. And without trying it, the only way to return it is a factory reset or a OTA update.
Click to expand...
Click to collapse
Well, if you're rooted, you could flash the same firmware again, I assume.
If you have root, couldn't you do:
Code:
pm disable com.amazon.kso.blackbird
instead?

Sizzlechest said:
Well, if you're rooted, you could flash the same firmware again, I assume.
If you have root, couldn't you do:
instead?
Click to expand...
Click to collapse
I don't have root.
This doesn't remove anything from system, so reflashing the firmware is overkill to return this. Just a factory reset should return it although I'm not sure why you would return ads to the stock launcher.

krsmit0 said:
I don't have root.
Click to expand...
Click to collapse
Someone who does should attempt that instead. I have root, but I already did the uninstall command.
EDIT: I had a FireTV that I hadn't upgraded to the latest rbox firmware. I upgraded it and ran "pm disable com.amazon.kso.blackbird" as root and rebooted. The ads are gone.

krsmit0 said:
Correct, no root. And without trying it, the only way to return it is a factory reset or a OTA update.
Click to expand...
Click to collapse
Cool. Should be great for my friends on non-Rooted FTVS1-2.
krsmit0 said:
I don't have root.
This doesn't remove anything from system, so reflashing the firmware is overkill to return this. Just a factory reset should return it although I'm not sure why you would return ads to the stock launcher.
Click to expand...
Click to collapse
Guessing it should also work on Rooted devices with TWRP. We can just do a Factory Reset in TWRP to get back to normal if needed. Or maybe backup the APK & reinstall it. Maybe you can look at the code needed to reinstall it with the right rights. The APK reinstall could be an option for those on non-Rooted devices that don't which to Factory Reset.
Since Rooted devices have the option to disable & enable then they don't need that option.
Sizzlechest said:
Well, if you're rooted, you could flash the same firmware again, I assume.
If you have root, couldn't you do:
Code:
pm disable com.amazon.kso.blackbird
instead?
Click to expand...
Click to collapse
I wonder if like with the Method 2 Update Blocking for Non-Rooted devices we can do this for non-Rooted devices:
Code:
[STRIKE]pm hide com.amazon.kso.blackbird[/STRIKE]
Code:
[STRIKE]pm unhide com.amazon.kso.blackbird[/STRIKE]
Will test it shortly...
UPDATE: The HIDE command did not work. It did not hide the ad before or after restarting the device. Maybe it's missing something. Not sure. Luckily I a am rooted.
Sizzlechest said:
Someone who does should attempt that instead. I have root, but I already did the uninstall command.
EDIT: I had a FireTV that I hadn't upgraded to the latest rbox firmware. I upgraded it and ran "pm disable com.amazon.kso.blackbird" as root and rebooted. The ads are gone.
Click to expand...
Click to collapse
Thanks for the confirmation. Will test this Method 1 Update Blocking for Rooted devices too in a minute.
All my testing will be on one the same rooted device but with different ADB Shell $ & # options. $ for non-Rooted & # for Rooted.

Y314K said:
Cool. Should be great for my friends on non-Rooted FTVS1-2.
Guessing it should also work on Rooted devices with TWRP. We can just do a Factory Reset in TWRP to get back to normal if needed. Or maybe backup the APK & reinstall it. Maybe you can look at the code needed to reinstall it with the right rights. The APK reinstall could be an option for those on non-Rooted devices that don't which to Factory Reset.
Since Rooted devices have the option to disable & enable then they don't need that option.
I wonder if like with the Method 2 Update Blocking for Non-Rooted devices we can do this for non-Rooted devices:
Code:
[STRIKE]pm hide com.amazon.kso.blackbird[/STRIKE]
Code:
[STRIKE]pm unhide com.amazon.kso.blackbird[/STRIKE]
Will test it shortly...
UPDATE: The HIDE command did not work. It did not hide the add before or after restarting the device. Maybe it's missing something. Not sure. Luckily I a am rooted.
Thanks for the confirmation. Will test this Method 1 Update Blocking for Rooted devices too in a minute.
All my testing will be on one the same rooted device but with different ADB Shell $ & # options. $ for non-Rooted & # for Rooted.
Click to expand...
Click to collapse
On the kindle fire, we found no way to return it without a factory reset. i have used this to remove com.amazon.device.software.ota com.amazon.device.software.ota.override, it wont allow me to check if there is a system update any longer. not sure of long term function. Amazon disabled hide at some point on its devices so it wont work on an unrooted device. This has led me to wonder what com.amazon.videoads is and whats its effect if its removed/uninstalled.

krsmit0 said:
On the kindle fire, we found no way to return it without a factory reset. i have used this to remove com.amazon.device.software.ota com.amazon.device.software.ota.override, it wont allow me to check if there is a system update any longer. not sure of long term function. Amazon disabled hide at some point on its devices so it wont work on an unrooted device. This has led me to wonder what com.amazon.videoads is and whats its effect if its removed/uninstalled.
Click to expand...
Click to collapse
Yeah, went to backup some system Apps & did find two of them kind of interesting. I am wondering what they would do if disabled.
com.amazon.videoads.app (Could be ads when playing free vids &/or on Prime , not sure)
Tried the following commands. Could not see any difference in UI layout:
Code:
pm disable com.amazon.videoads.app
Code:
pm enable com.amazon.videoads.app
So left it enabled.
Local Recommendation Service (Not sure if it is related to the recommendations on the big banner below the ad banner we just disabled but it probably has to do with the recommendations from other app like Netflix, etc)
Not sure I want to mess with this one...
Backup a few other System apps in ES File Explorer without any Root privileges. And all also included a .systag file too.

hi,
tried this .. pm disable com.amazon.kso.blackbird
removed the banner ad ok.
but when you try .. pm enable com.amazon.kso.blackbird
banner ad does not return ?

john321321 said:
hi,
tried this .. pm disable com.amazon.kso.blackbird
removed the banner ad ok.
but when you try .. pm enable com.amazon.kso.blackbird
banner ad does not return ?
Click to expand...
Click to collapse
Did you reboot? I don't know if it matters since I never tried enabling.

john321321 said:
hi,
tried this .. pm disable com.amazon.kso.blackbird
removed the banner ad ok.
but when you try .. pm enable com.amazon.kso.blackbird
banner ad does not return ?
Click to expand...
Click to collapse
From what I remember, enable did work for me. Make sure you are at # & reboot/restart your device. The banner will be back.
Sizzlechest said:
Did you reboot? I don't know if it matters since I never tried enabling.
Click to expand...
Click to collapse
I think it does matter for it to show again.

Is there a way to remove the new "sponsored" bar in the latest update? It crashes the UI if you scroll over it with the ads disabled/uninstalled

tofu- said:
Is there a way to remove the new "sponsored" bar in the latest update? It crashes the UI if you scroll over it with the ads disabled/uninstalled
Click to expand...
Click to collapse
I'm experiencing this too, I tried to uninstall again in case the update added back but it was not there to uninstall. The plus is the sponsored bar is now at the bottom and isn't in my way.

I too am having same issue, can we just get the file from someone on here and reinstall it via adb pm install?

same problem here.
UI crashing...
enigma7820 said:
I too am having same issue, can we just get the file from someone on here and reinstall it via adb pm install?
Click to expand...
Click to collapse

have you tried a factory reset? the apk isnt truly uninstalled so reinstalling probably wont work.

I used uninstall not disable, if someone could provide the file from op we can install it back on

I accidentally "uninstalled" Quickstep

I was checking my battery usage stats and saw that Quickstep was using more battery than it should've. I didn't use the laucnher anyways, so I thought I would uninstall it. I used the adb shell and used "pm uninstall -k --user 0 com.android.launcher3". I later learned that this app was responsible for home button gestures, something I really use. I know I could factory reset my phone, but is there any way I can get this app back? Whenever I see it in Settings, it says "not installed for this user".

yqazi27 said:
I was checking my battery usage stats and saw that Quickstep was using more battery than it should've. I didn't use the laucnher anyways, so I thought I would uninstall it. I used the adb shell and used "pm uninstall -k --user 0 com.android.launcher3". I later learned that this app was responsible for home button gestures, something I really use. I know I could factory reset my phone, but is there any way I can get this app back? Whenever I see it in Settings, it says "not installed for this user".
Click to expand...
Click to collapse
I've never done it this way... But pm install should work opposite of pm uninstall...

rignfool said:
I've never done it this way... But pm install should work opposite of pm uninstall...
Click to expand...
Click to collapse
I could do this, but I need the APK file for Quickstep, which I have searched for hours. I am also not willing to root my phone as a solution of possibly retrieving the file directly from the system.

yqazi27 said:
I could do this, but I need the APK file for Quickstep, which I have searched for hours. I am also not willing to root my phone as a solution of possibly retrieving the file directly from the system.
Click to expand...
Click to collapse
Good luck...

yqazi27 said:
I was checking my battery usage stats and saw that Quickstep was using more battery than it should've. I didn't use the laucnher anyways, so I thought I would uninstall it. I used the adb shell and used "pm uninstall -k --user 0 com.android.launcher3". I later learned that this app was responsible for home button gestures, something I really use. I know I could factory reset my phone, but is there any way I can get this app back? Whenever I see it in Settings, it says "not installed for this user".
Click to expand...
Click to collapse
Sideload the OTA on top of what you have installed.
No need to root.

tech_head said:
Sideload the OTA on top of what you have installed.
No need to root.
Click to expand...
Click to collapse
Just sideloaded the OTA via ADB and nothing happened. I looked at Quickstep in my apps and it still says "not installed for this user".

yqazi27 said:
Just sideloaded the OTA via ADB and nothing happened. I looked at Quickstep in my apps and it still says "not installed for this user".
Click to expand...
Click to collapse
You have to sideload and run the update. You can't just sideload the os update and expect quickstep to appear.

autosurgeon said:
You have to sideload and run the update. You can't just sideload the os update and expect quickstep to appear.
Click to expand...
Click to collapse
I DID run the update earlier. Absolutely nothing changed, unless I am not understanding the process of running the update.

yqazi27 said:
I DID run the update earlier. Absolutely nothing changed, unless I am not understanding the process of running the update.
Click to expand...
Click to collapse
Updates don't re-enable disabled apps...

rignfool said:
Updates don't re-enable disabled apps...
Click to expand...
Click to collapse
So you're basically telling me to factory reset........

yqazi27 said:
So you're basically telling me to factory reset........
Click to expand...
Click to collapse
Probably...
If you don't want to root... You need to reset user 0...

rignfool said:
Probably...
If you don't want to root... You need to reset user 0...
Click to expand...
Click to collapse
Not resetting was my main condition, but I guess that is my only option unless someone else has a solution.

Yeah a factory reset might fix this....might...

yqazi27 said:
So you're basically telling me to factory reset........
Click to expand...
Click to collapse
Now that you have done the OTA, you don't see it as an installed app, just disabled?
If not then FDR?

tech_head said:
Now that you have done the OTA, you don't see it as an installed app, just disabled?
If not then FDR?
Click to expand...
Click to collapse
It shows up in the Apps list, but still says "Not installed for this user". The disable button is greyed out. I think I'll do a reset tonight.

yqazi27 said:
It shows up in the Apps list, but still says "Not installed for this user". The disable button is greyed out. I think I'll do a reset tonight.
Click to expand...
Click to collapse
Have you setup multiple users on ur phone?

I did the same - uninstall the quickstep app. But, it kept popping up a 'confirmation box' and the tablet became unusable. Have just reset the android tablet (all data, of course, got wiped out.)