Related
sorry to bring this up i have the rooted phone 2.1(droid eris) i have an app that saying super permission, i click on it and show just black screen what does this so pose to do
and how do i remove the factory apps
sorry i think its a stupid question but what should i see in superuser permission one time i only saw this +2000-2000 and something else
I was having trouble with super user too. I reverted to a working back up
ampinc said:
sorry to bring this up i have the rooted phone 2.1(droid eris) i have an app that saying super permission, i click on it and show just black screen what does this so pose to do
and how do i remove the factory apps
Click to expand...
Click to collapse
Enable USB Debugging in
Settings > Applications > Development
If you have SDK set up on your computer, do ,
adb shell
$
type SU
$ su
Wait a while, you should see on your phone, press Always Accept
#
From now on ,it should work for everything.
Framework43 said:
From now on ,it should work for everything.
Click to expand...
Click to collapse
"Always Allow" only allows connections from the same source (computer, etc) so if you load up Terminal Emulator, youll have to Always Accept for that too...etc etc
gohamstergo said:
"Always Allow" only allows connections from the same source (computer, etc) so if you load up Terminal Emulator, youll have to Always Accept for that too...etc etc
Click to expand...
Click to collapse
Yeah but if you do it via adb shell first,
it will work everytime after that.
If not, it will always force close on you.
Framework43 said:
Enable USB Debugging in
Settings > Applications > Development
If you have SDK set up on your computer, do ,
adb shell
$
type SU
$ su
Wait a while, you should see on your phone, press Always Accept
#
From now on ,it should work for everything.
Click to expand...
Click to collapse
iam sorry but i dont know where adb shell is
ampinc said:
iam sorry but i dont know where adb shell is
Click to expand...
Click to collapse
have you downloaded the Android SDK? If so, open a command prompt and navigate to the SDK's Tools folder. then do adb shell
Framework43 said:
Yeah but if you do it via adb shell first,
it will work everytime after that.
If not, it will always force close on you.
Click to expand...
Click to collapse
no, what i meant was, clicking Always Allow only allows the current process to be always allowed.
ex: if you connect via adb on a computer and Always Allow, then you still have to allow other programs like Terminal Emulator, drocap2, etc also Always Allow isn't universal, only applies to the current app that is requesting the permission.
don't remove this app
and there is no need to run this app manually
if an app requests root-rights, this app will auto popup
i dont know what i did wrong but its not working please some help thanks
jriley60 said:
I was having trouble with super user too. I reverted to a working back up
Click to expand...
Click to collapse
can you please link me to a working backup of superuser.....I am having issues too.
there isn't a fully working one. the version we are using is from another phone completely. Until the author of superuser.apk writes one for us. the only method of getting superuser.apk to work right is.
1. enable usb debugging
2. plug your usb into your phone
3. choose HTC sync and wait for it to fail to connect if not installed.
4. while in sync mode start the app that needs root access and wait for the su prompt
5. select always allow
6. enjoy your app
some root apps like wifi tether require multiple access prompts to be fully functional.
hope this helps
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.
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?
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
Hi,
I have a rooted OP8P running Magisk 21.0 (21000), and using Magisk Manager 8.0.2 (307)(11). My OS build is Oxygen OS 10.5.13.IN11AA(enhanced by xXx_NoLimits_ 12.3).
I keep getting the pesky notification to Update to Oxygen OS 11.IN1AA, the one that gives me the option to "Download and Install Now". I have no plans nor any desire to go to Android 11 as of yet, so I would like to do two things, stop this notification from showing up, and ensure that the update doesn't install itself.
Normally, I wouldn't worry about it updating without some user input but just today I got a second notification telling me that "System update installation failed" prompting me to "Try Again"(See attached pic). This is both good and bad I suppose, but it's still troubling since this newest notification indicates that it tried to update without me knowing about it. This simply will not do.
Any advice? I know it's not as simple as disabling the notification, as it doesn't allow me to do so.
Thanks!
KingKazmaOfficial said:
Hi,
I have no plans nor any desire to go to Android 11 as of yet,
Thanks!
Click to expand...
Click to collapse
I'm seeing the same and contemplated the same question. What are your reasons for avoiding the upgrade?
p.s. I can think about a way of disabling system notifications (using root access), but I worry about missing important notifications, so I left this pesky message on.
NYCgirl said:
I'm seeing the same and contemplated the same question. What are your reasons for avoiding the upgrade?
p.s. I can think about a way of disabling system notifications (using root access), but I worry about missing important notifications, so I left this pesky message on.
Click to expand...
Click to collapse
I just don't see any real reason to update, OOS 10 is working fine for me. From what I've seen OOS 11 doesn't bring anything compelling enough to the table to make me to want to upgrade. Also, OOS 10 has been around long enough that there are robust resources and development communities built around it, meaning more reliable troubleshooting and overall easier research. On top of all that, having to factory reset and re-root to avoid potential bugs due to OOS 10 residuals isn't very attractive either.
I mean don't get me wrong, I love the feeling and idea of being on the bleeding edge as much as the next guy, but I'd rather all my ducks be in a row beforehand...if that makes any sense.
Can you freeze the app in titanium??
Freezing System Update 2.2.3... did the trick for me.
---------- Post added at 01:54 AM ---------- Previous post was at 01:51 AM ----------
KingKazmaOfficial said:
On top of all that, having to factory reset and re-root to avoid potential bugs due to OOS 10 residuals isn't very attractive either.
.
Click to expand...
Click to collapse
That makes sense. If you have to factory reset, how would you restore your data? AFAIK, there not yet TWRP for Android 11, which means relying on something else. This make me nervous...
dladz said:
Can you freeze the app in titanium??
Click to expand...
Click to collapse
Don't have the pro version.
You can use the adb command to disable the update as well notification
adb shell pm disable-user --user 0 com.oneplus.opbackup
KingKazmaOfficial said:
Don't have the pro version.
Click to expand...
Click to collapse
VRaju said:
You can use the adb command to disable the update as well notification
adb shell pm disable-user --user 0 com.oneplus.opbackup
Click to expand...
Click to collapse
Use the terminal app on phone or cmd on PC?
You can try either should work.
App to disable is ""com.oneplus.opbackup""
KingKazmaOfficial said:
Use the terminal app on phone or cmd on PC?
Click to expand...
Click to collapse
VRaju said:
You can use the adb command to disable the update as well notification
adb shell pm disable-user --user 0 com.oneplus.opbackup
Click to expand...
Click to collapse
Buy it, they deserve the payment for all they've done
hi, if disable system update then can i enable again ? do you have a cmd comand for enable ?
sefai77 said:
hi, if disable system update then can i enable again ? do you have a cmd comand for enable ?
Click to expand...
Click to collapse
VRaju said:
You can try either should work.
App to disable is ""com.oneplus.opbackup""
Click to expand...
Click to collapse
I'd like to know that as well.
Yes you can re enable if required.
adb shell pm enable com.oneplus.opbackup
KingKazmaOfficial said:
I'd like to know that as well.
Click to expand...
Click to collapse
VRaju said:
Yes you can re enable if required.
adb shell pm enable com.oneplus.opbackup
Click to expand...
Click to collapse
Works for disable and re-enable! Thanks alot!
today i formatted my phone and i try to give this command again but it doesn't work
That's an apk OnePlus released which may help you guys in this situation. If you check news in the Oxygen updater, there's an in depth article about it.
Major failing on OnePlus' part.
Here's the apk they're referring to, apparently it stops the update forcing wipes from OB3 not to go ahead.
https://drive.google.com/file/d/15RO5WSwMZ3PAHktUWMVr4f6sRm-th_he/view
Please check out the article before installing anything.
Edit: actually this is more for the people who were forced to update. Apologies, I'll leave it here as someone may see it.
sefai77 said:
today i formatted my phone and i try to give this command again but it doesn't work
Click to expand...
Click to collapse
Why did you format, did you update to OOS 11?
Also, when running the command line, make sure you open the command prompt within the same folder as your ADB files.
KingKazmaOfficial said:
Why did you format, did you update to OOS 11?
Also, when running the command line, make sure you open the command prompt within the same folder as your ADB files.
Click to expand...
Click to collapse
i formated for cleaning my oneplus8pro and i dont updtae OOS 11. i open command with adb files but i cant do this.
sefai77 said:
i formated for cleaning my oneplus8pro and i dont updtae OOS 11. i open command with adb files but i cant do this.
Click to expand...
Click to collapse
first run the command
Code:
adb devices
to ensure that you phone is connected, and that you have the proper drivers are installed.
Then, make sure that your phone is unlocked (not the bootloader, just actually unlocked so the screen is on). After running that above command, you should see a popup come up on your phone screen asking you to allow permission to your computer. Tap "always allow" checkbox and grant the permissions.
Now try to run the command again.
KingKazmaOfficial said:
first run the command
Code:
adb devices
to ensure that you phone is connected, and that you have the proper drivers are installed.
Then, make sure that your phone is unlocked (not the bootloader, just actually unlocked so the screen is on). After running that above command, you should see a popup come up on your phone screen asking you to allow permission to your computer. Tap "always allow" checkbox and grant the permissions.
Now try to run the command again.
Click to expand...
Click to collapse
i can do it now thanks