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?
Related
I'm a little confused guys.
I pretty much followed the instructions for part 1 and 2 here: http://forum.xda-developers.com/showpost.php?p=12631216&postcount=2911
I flashed my phone back to 1.2.6 then ran the before update script. Then updated, then ran the after update script. I am able to download .apk files and run them without being pestered. But I tried to run boot strap, and nothing would happen when i hit "Recovery boot". I know the gignger blur installation instructions says to make sure I'm plugged in to an AC charger so I did. Didn't work. I plugged it into my car charger. Didn't work. Tried my USB cable connected to the PC for sh*ts and giggles, but still nothing.
So I though maybe my phone isn't rooted properly? I googled a little and found this: http://androidforums.com/32282-post3.html
I installed the terminal app and ran su and it said permission denied. But I think I am able to access /data/app-private (I type in cd /data/app-private and it doesn't do anything so I assume I'm in the app-private directory, no?)
...So I guess I'm just here to ask, am I going in the right direction to check to see if my phone is rooted? Any other way of checking to see if I'm rooted correctly? I'm not exactly looking for the easy way, I'm looking for the correct way.
Any help is appreciated =)
If you are properly rooted, there will be an application called Superuser in your app tray.
Sent from my MB860 using XDA App
delmarvahockey29 said:
If you are properly rooted, there will be an application called Superuser in your app tray.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
I have that app, how come when I su in terminal it denies me permission?
Open up Superuser and make sure it is in your "allow" list.
Sent from my MB860 using XDA App
delmarvahockey29 said:
Open up Superuser and make sure it is in your "allow" list.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
When I open up superuser it only says "No apps in list" under my Apps tab. And hitting the menu button (the button with the 4 squares) does nothing whenI'm in the Apps tab.
Strange... So when you type "su" in the terminal, does it give you a pop-up to allow superuser access?
Sent from my MB860 using XDA App
delmarvahockey29 said:
Strange... So when you type "su" in the terminal, does it give you a pop-up to allow superuser access?
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Nope, just says "Permission denied"
Try switching usb settings from none to storage then back to none, and also uncheck usb debug and recheck it. I know when I updated my phone to restore root that is what I had to do or I would get premission denied.
-illusion
rboone18 said:
Try switching usb settings from none to storage then back to none, and also uncheck usb debug and recheck it. I know when I updated my phone to restore root that is what I had to do or I would get premission denied.
-illusion
Click to expand...
Click to collapse
Still no luck, I think I might have lost root ( http://forum.xda-developers.com/showpost.php?p=12685034&postcount=3303 )
How do you even loose root?
Yes, you don't have root. I was in a similar situation when I first tried the Mac version of aRoot. There was a bug in the script so I didn't actually get rooted, but it installed superuser anyway so I thought I was. Anything that requires root will simply fail.
maledyris said:
Yes, you don't have root. I was in a similar situation when I first tried the Mac version of aRoot. There was a bug in the script so I didn't actually get rooted, but it installed superuser anyway so I thought I was. Anything that requires root will simply fail.
Click to expand...
Click to collapse
How did you fix your problem?
So I just ran across this. I was able to find the baidu folder in question. Have any of you found this or know anything about it?
https://www.google.com/url?sa=t&sou...7uOd0zoUs7lk9k38g&sig2=G0GrwgJd5biYyaP0UZtNJg
Sent from my D5803 using XDA Free mobile app
http://www.xperiablog.net/2014/10/2...pyware/?utm_source=dlvr.it&utm_medium=twitter
This thread appears to have the most information
https://talk.sonymobile.com/t5/Xper...n-starting-phone-each-time/td-p/819877/page/6
Sent from my Nexus 7 using XDA Free mobile app
with out reading all the forums... would this affect the USA models released on 11/2/2014?
Sounds like it, I can not tell you for sure though. But apparently apps like esfile explorer load it too. It appears to be some sort of push service. It is part of the Xperia app to remotely find and wipe an Xperia phone. But it is constantly communicating with Chinese based ips.
Sent from my Nexus 7 using XDA Free mobile app
About haft a year until now, almost manufacturers intergrated Baidu Location tracking for China compatible.
Just like removing "What's New" from NavRing (http://forum.xda-developers.com/z3-...-rootremove-whats-navring-small-apps-t2902419), you can use ADB on unrooted devices to block it.
Code:
adb shell pm block com.sonymobile.mx.android
adamk7 said:
Just like removing "What's New" from NavRing (http://forum.xda-developers.com/z3-...-rootremove-whats-navring-small-apps-t2902419), you can use ADB on unrooted devices to block it.
Code:
adb shell pm block com.sonymobile.mx.android
Click to expand...
Click to collapse
When I tried this on my Z3 I was getting the new Block status = false, when I looked at my Current Running Apps I noticed that the name was com.sonymobile.mx.android:bdservice , so I tried it again with the additional part of the name and it told me that it was blocked.
Anyway, I rebooted and for my surprise the baidu folder was there again and it was created after the reboot, so it seems that it's not working after all.
**Edit** just saw that it came back so I checked again and noticed that the service running on MyXperia app was com.sonymobile.mx.android:bdservice_V1, so I did the same blocking that one, it was successful, rebooted and there it is again.**
erasat said:
When I tried this on my Z3 I was getting the new Block status = false, when I looked at my Current Running Apps I noticed that the name was com.sonymobile.mx.android:bdservice , so I tried it again with the additional part of the name and it told me that it was blocked.
Anyway, I rebooted and for my surprise the baidu folder was there again and it was created after the reboot, so it seems that it's not working after all.
Click to expand...
Click to collapse
As per the reddit comments, try:
pm block com.sonymobile.mx.android
Clean the data of the MyXperia App
Reboot
Delete the "baidu" folder manually
Reboot
Also, as mentionned earlier, some other apps can also initiate it - noteably the ES suite
adamk7 said:
As per the reddit comments, try:
pm block com.sonymobile.mx.android
Clean the data of the MyXperia App
Reboot
Delete the "baidu" folder manually
Reboot
Also, as mentionned earlier, some other apps can also initiate it - noteably the ES suite
Click to expand...
Click to collapse
I tried to follow this instructions but when I try pm block com.sonymobile.mx.android, the block status says False, if I try the other 2 that I mentioned in my previous post then it changes to Block = true.
In addition to that, when I go to the my Xperia App I can't Clean Data, just cache, so I do it, then the reboot but then it keeps coming back, maybe because it is not simply working as per instructions.
*EDIT: Nevermind me. What I said was covered above.
adamk7 said:
As per the reddit comments, try:
pm block com.sonymobile.mx.android
Clean the data of the MyXperia App
Reboot
Delete the "baidu" folder manually
Reboot
Also, as mentionned earlier, some other apps can also initiate it - noteably the ES suite
Click to expand...
Click to collapse
ack154 said:
*EDIT: Nevermind me. What I said was covered above.
Click to expand...
Click to collapse
Thanks for your help attempts, I really appreciate it, but like I mentioned, I'm already doing that, but in my case it's not working as expected. I had ES File Explorer Installed but after reading that it may be linked to it also, I uninstalled it, rebooted and tried all this again, just with the same results.
So you've got ADB working, right? You do "adb devices" and get a response back with your device serial #, right?
Once you have that, run "adb shell" as its own command. Then do the "pm block com.sonymobile.mx.android" and see what you get.
ack154 said:
So you've got ADB working, right? You do "adb devices" and get a response back with your device serial #, right?
Once you have that, run "adb shell" as its own command. Then do the "pm block com.sonymobile.mx.android" and see what you get.
Click to expand...
Click to collapse
No, I was not using the adb devices first as I was using the same instructions that were posted to block the WhatsNew option, I was just going straigth to adb shell and then the rest.
So, to be sure and very optimistic I just did the whole process, step by step, beginning with adb devices and waiting for the serial number and then going from there to adb shell but I just got the exact same results, no pm block com.sonymobile.mx.android, it just always say False, and then can't clean data on my Xperia App, just cache. After trying to complete the whole process of deleting folders and rebooting I just got frustrated again to see the folder created again and my Xperia app still running with the com.sonymobile.mx.android:bdservice_V1 process linked to it.
I just got it working, it seems that my problem was that I had the my Xperia app activated as a Device Administrator, that was preventing everything from work. After deactivating it and do the process and reboot, I no longer have the folder, feel a little more relief now, thanks.
erasat said:
I just got it working, it seems that my problem was that I had the my Xperia app activated as a Device Administrator, that was preventing everything from work. After deactivating it and do the process and reboot, I no longer have the folder, feel a little more relief now, thanks.
Click to expand...
Click to collapse
Thanks for your updates on this.
I had this folder on my moto G 4.4.4 stock no rooted , deleted it , it has not come back .
After the last update i deleted the folder and it's gone permanently from my device. Bye bye Baidu!
Here's how I have Android Pay working on my rooted 5x:
-Starting from stock 6.01 (Some other ROMs are reported working. Most importantly it needs to be a ROM where Android Pay was working prior to systemless root)
-Flashed systemless SuperSU 2.67 from TWRP (See UPDATE 3 below to make sure you have a systemless install)
-run "adb shell"
-from adb shell run "su"
-from adb shell run "chmod 751 /su/bin"
Have fun!
With this change the checks in SafetyNet Helper are passing and I can add cards and make purchases with Android Pay. The change is surviving reboots and doesn't require messing with any settings in the SuperSU app to enable/disable root.
UPDATE 1: As others have pointed out this permissions change can also be done with a file manager like Root Explorer that lets you change permissions. Probably easier for most than ADB commands.
UPDATE 2: Some people haven't been able to get Android Pay working with just this permission change. Check if you have /su/xbin_bind - deleting this may get it working. Thanks to @bobby janow and @CSX321 for pointing this out.
UPDATE 3: To clarify on the systemless SuperSU installation (this seems to be a trouble point for some) - there are settings that need to be configured for the SuperSU install to make it systemless and to not create the system/xbin binding. The installer reads these options from a file on /data/. Since you don't have root yet you need write these settings over ADB in TWRP. If you don't see the /su/ directory, you probably don't have a systemless install. In that case you can go back to stock (restore system, boot, and vendor partitions). Then, when you reinstall SuperSU, these are the commands you need to send from your TWRP ADB shell:
Code:
echo SYSTEMLESS=true>>/data/.supersu
echo BINDSYSTEMXBIN=false>>/data/.supersu
Once you've got SuperSU installed, change the permissions of /su/bin/ (either chmod or using a file explorer)
You can check Android pay by simply trying to add a card and you'll know right away.
buru898 said:
You can check Android pay by simply trying to add a card and you'll know right away.
Click to expand...
Click to collapse
Yeah just removed my card and added it again. Went through all the contacting bank stuff and it worked. I think this is the real deal.
Try and make a purchase and report back! Thanks though!
Ya sometimes you can add a card but fail a purchase. Adding the card isn't a sure thing
jgummeson said:
Yeah just removed my card and added it again. Went through all the contacting bank stuff and it worked. I think this is the real deal.
Click to expand...
Click to collapse
Hmm now I want test this out. Need to flash ROM again.
If you're able to try a purchase, please let us know.
buru898 said:
Hmm now I want test this out. Need to flash ROM again.
If you're able to try a purchase, please let us know.
Click to expand...
Click to collapse
That's the only trouble with Android Pay - no one takes it. I'll see if I can stop by Trader Joe's tonight and pick something up. They're the only place around here I know of that takes it.
jgummeson said:
That's the only trouble with Android Pay - no one takes it. I'll see if I can stop by Trader Joe's tonight and pick something up. They're the only place around here I know of that takes it.
Click to expand...
Click to collapse
Don't forget anywhere you see the NFC lines symbol should work. I've even seen some that didn't have the symbol but still had an NFC scanner.
Sent from my Nexus 7 using Tapatalk
Yep Android Pay worked for a purchase. Just chmod your /su/bin/ directory to 751. Works for me on stock with systemless root and I imagine it may work on other ROMs that used to work until the recent change in the SafetyNet checks.
Running Chroma with SU 2.66. After running those commands AP will let me at least add a card, which I couldn't do before those commands (get can't verify android error). Will try testing in store tomorrow hopefully.
This is great news!
Tell the reddit people and get famous!
Does anyone know for certain if passing through SafetyNet Helper means it'll always work with pay?
smac7 said:
Does anyone know for certain if passing through SafetyNet Helper means it'll always work with pay?
Click to expand...
Click to collapse
Always? No. Google is actively trying to keep Android Pay safe in the eyes of banks and credit card companies, whether that is by blocking system/system-less root, or making adjustments server side to prevent workarounds that could potentially exploit the Android Pay experience.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Always? No. Google is actively trying to keep Android Pay safe in the eyes of banks and credit card companies, whether that is by blocking system/system-less root, or making adjustments server side to prevent workarounds that could potentially exploit the Android Pay experience.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Well, i know google is trying to lock us out, but i thought safetynet was what Android pay uses to verify the the phone is indeed "safe". If the previous statement is correct, it would stand to reason that if it passes through safetynet helper then it'll also pass through android pay.
smac7 said:
Well, i know google is trying to lock us out, but i thought safetynet was what Android pay uses to verify the the phone is indeed "safe". If the previous statement is correct, it would stand to reason that if it passes through safetynet helper then it'll also pass through android pay.
Click to expand...
Click to collapse
That API is probably the best indicator of success right now but I could also see that changing if Google decides it needs to be more thorough in its approach
Sent from my Nexus 5X using Tapatalk
buru898 said:
This is great news!
Tell the reddit people and get famous!
Click to expand...
Click to collapse
Yeah I posted it on the Reddit and it sank to the bottom and everyone ignored it. No fame for me. I'll have to settle for Android Pay.
jgummeson said:
Yeah I posted it on the Reddit and it sank to the bottom and everyone ignored it. No fame for me. I'll have to settle for Android Pay.
Click to expand...
Click to collapse
Well you could always try having it posted to the xda portal and replying to this thread.
https://www.reddit.com/r/Android/comments/43bl05/newest_safetynet_check_detects_systemless_root/
buru898 said:
Well you could always try having it posted to the xda portal and replying to this thread.
https://www.reddit.com/r/Android/comments/43bl05/newest_safetynet_check_detects_systemless_root/
Click to expand...
Click to collapse
Yeah that's where I posted it - it's a comment way down on the bottom. Maybe I just don't know how to Reddit... Well started a new thread on there. Hopefully someone is paying attention this time.
jgummeson said:
Yeah that's where I posted it - it's a comment way down on the bottom. Maybe I just don't know how to Reddit... Well started a new thread on there. Hopefully someone is paying attention this time.
Click to expand...
Click to collapse
You just have to wait for somebody else to repost it:
https://www.reddit.com/r/Android/comments/44be69/android_pay_working_with_root/
jgummeson said:
Let me know if anyone else can confirm this works.
Click to expand...
Click to collapse
Yep! I just got a Mt. Dew from the machine at work. I did have to delete the card, reboot, and add the card back again. Pay seems to remember if it's ever failed with a card, and refuse to work with that card until you delete and re-add it.
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?
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