Database Users

Sideloading Wonder Machine taken Down

It would appear that even on the website (which shows At&T blocked apps) that the sideloading wonder machine is gone.
Dang! wish I had got the sideloading machine.

isnt it still available at android central? Those are the guys who wrote it, I thought...

if at was at androidcentral then you would have to sideload it, completely defeating the purpose.

Why don't you just put the .apk on your phone and install it?
Sent from my MB860 using Tapatalk

that's sideloading. Anything other than a direct market download is sideloading, and blocked by At&T

Techcruncher said:
that's sideloading. Anything other than a direct market download is sideloading, and blocked by At&T
Click to expand...
Click to collapse
Yea...that's what I'm saying. Enable side loading it takes like 30 seconds. It's more of a hassle to use wonder machine.
Sent from my MB860 using Tapatalk

Techcruncher said:
It would appear that even on the website (which shows At&T blocked apps) that the sideloading wonder machine is gone.
Dang! wish I had got the sideloading machine.
Click to expand...
Click to collapse
http://forum.androidcentral.com/and...40770-ac-sideload-wonder-machine-windows.html
They moved it to only be available on their forum. You have to create a username/password, but the links then become available for download.

iceman4357 said:
http://forum.androidcentral.com/and...40770-ac-sideload-wonder-machine-windows.html
They moved it to only be available on their forum. You have to create a username/password, but the links then become available for download.
Click to expand...
Click to collapse
But I can't Sideload due to At&T so how can I download it from their website. That's sideloading?
I'm confused....

Techcruncher said:
But I can't Sideload due to At&T so how can I download it from their website. That's sideloading?
I'm confused....
Click to expand...
Click to collapse
lol....The Side load wondermachine stays on your computer. You download an .APK file oyu want, plug the phone in and it will side load it to your phone for you. You do not place the APK on the phone at all.
There is also a video on how to use the program:
http://www.youtube.com/watch?v=zzs_1DeSgWI&feature=player_embedded
Quote from the website:
"Installation:
Unzip the SWM folder to a conveinent place on your Windows computer. The program, and all files inside the SWM folder need to stay together.
You will need to install the USB driver for your model of Android device. Information about this can be had from your carrier, or from your device manufacturer.
Usage:
Ensure that USB debugging is enabled on your Android device. For most devices, this can be found in menu>settings>applications>development
Plug your Android device into a high speed USB port on your computer.
Start the application, and browse to the apk file you would like to install by clicking the "Choose a file" button.
Once you have chosen the apk to install, the "Go" button will be enabled. Click it, and you'll see the command window which prompts you as it installs the file. "

Techcruncher said:
But I can't Sideload due to At&T so how can I download it from their website. That's sideloading?
I'm confused....
Click to expand...
Click to collapse
Root the phone. It's completely safe. If you follow DG's instructions on the thread it's pretty much idiot proof too. And then sideloading will be enabled!
edit: a bunch of other things will be enabled too. and he also has an unroot script there for you.

Yeah, I don't really get this. Download SuperOneClick. You can root your phone and enable sideloading all at once. If you ever want to go back SuperOneClick will also unroot your phone as well. There's no danger doing it this way.

SuperOneClick isn't the best way to root and enable your phone. There is an issue with Busybox. Designergears recommends using aroot to root and enable sideloading. If you used SuperOneClick to root...simply unroot it.

I'm afraid I don't know enough about software to use superoneclick and such.

Techcruncher said:
I'm afraid I don't know enough about software to use superoneclick and such.
Click to expand...
Click to collapse
Hey, i think the best way for you is to do it like it says in this thread:
http://forum.xda-developers.com/showthread.php?t=981866
except if you have a bell atrix, i think than youll have to wait a bit so the devs make it for it (im not sure if its a problem tho)

use aroot. I rooted with super one click and also clicked enable outside apps but it didn't work. I then used aroot and everything worked fine.
Sent from my MB860 using XDA App

Techcruncher said:
I'm afraid I don't know enough about software to use superoneclick and such.
Click to expand...
Click to collapse
You didnt try the Sideload wonder machine? Check out all the links and instructions I posted. It is really easy, especailly if you dont trust yourself enough to root the phone.

iceman4357 said:
You didnt try the Sideload wonder machine? Check out all the links and instructions I posted. It is really easy, especailly if you dont trust yourself enough to root the phone.
Click to expand...
Click to collapse
Seriously, he posts that the SWM is down but I don't think he even knows what the SWM is.
And for everyone telling him to root, transferring files with SWM is so much easier that rooting just for side loading is kind of a waste.

You can also sideload via adb without root.

I've used wonder machine and worked beautifully.

you can always use Droidexplorer or adb
and if you can navigate this website and consciously comprehend what is being discussed (aka process the text on the screen in your mind) you should be able to follow DGs root method

Android Pay - rooted - will not work - HELP

I have unlocked bootloader, TWRP recovery, Xposed installed, and rooted. Installed Android Pay, linked CC.
Then I get a message that software is not compatible and exits. Any work arounds?
CC

I never used it, but was able to get it setup.
You go into the SuperSU app.
Then settings, disable root, reboot.
Setup android pay.
Then reenable root
Seemed to work for me, but never used it to confirm
Sent from my Nexus 6 using Tapatalk

jaben2 said:
I never used it, but was able to get it setup.
You go into the SuperSU app.
Then settings, disable root, reboot.
Setup android pay.
Then reenable root
Seemed to work for me, but never used it to confirm
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
This^^ except you don't even need to reboot. Just disable SU, add card in Pay, re-enable SU. I've done it 4 times on 2 separate phones

cc999 said:
I have unlocked bootloader, TWRP recovery, Xposed installed, and rooted. Installed Android Pay, linked CC.
Then I get a message that software is not compatible and exits. Any work arounds?
CC
Click to expand...
Click to collapse
The Xposed app RootCloak seems to also do the trick without needing to mess with anything else.

Bootup said:
This^^ except you don't even need to reboot. Just disable SU, add card in Pay, re-enable SU. I've done it 4 times on 2 separate phones
Click to expand...
Click to collapse
_ranch said:
The Xposed app RootCloak seems to also do the trick without needing to mess with anything else.
Click to expand...
Click to collapse
Since you mentioned 2 separate phones, I just want to add that disabling SuperSU with and without rebooting, as well as trying RootCloak did not allow me to setup a card on my G4.

geoff5093 said:
Since you mentioned 2 separate phones, I just want to add that disabling SuperSU with and without rebooting, as well as trying RootCloak did not allow me to setup a card on my G4.
Click to expand...
Click to collapse
Not that it matters since we all know by now that Android Pay doesn't work on rooted phones but I was able to setup cards on my gf rooted G4. Simply disabling SU (didn't even need reboot) and she was able to add her cards.
Of course, she can't actually use Pay....

Google Security Engineer Explains Issues With Root and Android Pay in the XDA Forums

Once Xposed is installed the security model is broken for card addition.
Xposed and root must be removed to install cards.
Once the cards are added.
Xposed can be re-installed and root reactivated.
You then will need to run an Xposed root cloak.
It does work, but once you add Xposed no new cards.

tech_head said:
Once Xposed is installed the security model is broken for card addition.
Xposed and root must be removed to install cards.
Once the cards are added.
Xposed can be re-installed and root reactivated.
You then will need to run an Xposed root cloak.
It does work, but once you add Xposed no new cards.
Click to expand...
Click to collapse
I wonder if this will eventually be detected and continue the cat and mouse game? Probably so. And there's no telling how the game will change once we're running Marshmellow.
Personally, I intended to go into Marshmellow virgin stock. With Marshmellow's app data backup, I won't need the #1 reason I used to root. Titanium Backup. Otherwise, I'm a fan of vanilla Android with the Moto customizations. So no reason for me to root.

I tried root cloak but don't know what I am supposed to do with it. Can someone please tell me why to do? Do I do anything on the opening page? Or, do I hit the + and look for the app.

People say even when hiding root it was always fail during the transaction.
Sent from my XT1575 using Tapatalk

Darn it. I really want to have wallet tap and pay, but I want to keep root way more. I uninstalled Android Pay and the new Wallet and installed Wallet v8. It appears that tap and pay is functional (for now).
I detached Wallet from Google Play, so it shouldn't get updated without my permission. We'll see how this goes. I'll heck it out at the nearest Home Depot tomorrow.

The best place to test is at McDonald's. Theirs is always working. But Home Depots in my area stopped working with Tap and Pay many months ago.
Sent from my Nexus 10 using Tapatalk
---------- Post added at 08:20 PM ---------- Previous post was at 08:17 PM ----------
sdelcegno said:
People say even when hiding root it was always fail during the transaction.
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
That's right. The Google engineer said all the major checks occur during the transaction. So adding cards really means nothing, if you can't use them...
Sent from my Nexus 10 using Tapatalk

Darnell_Chat_TN said:
The best place to test is at McDonald's. Theirs is always working. But Home Depots in my area stopped working with Tap and Pay many months ago.
Click to expand...
Click to collapse
No more Home Depot, eh? That's too bad. I did notice that Whole Foods updated their registers to remove the tap and pay a year or so ago, too. OK, well, I do like the McD fish sandwiches, and there is one a couple of blocks away, so it is pretty easy to check. Thanks for the info.

sdelcegno said:
People say even when hiding root it was always fail during the transaction.
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
i have my phone rooted and xposed installed. I was able to add cards w/ root disabled and am able to may purchases w/ root disabled. it DOES check root on purchase so you have to keep it disabled to use AP.

FunkeeC said:
i have my phone rooted and xposed installed. I was able to add cards w/ root disabled and am able to may purchases w/ root disabled. it DOES check root on purchase so you have to keep it disabled to use AP.
Click to expand...
Click to collapse
That seems to fail with others. I wonder if it is store dependant and some are doing something else with security.
Sent from my XT1575 using Tapatalk

sdelcegno said:
That seems to fail with others. I wonder if it is store dependant and some are doing something else with security.
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
or dependent on what modules being used perhaps? im only using xposed for apm+ and gravity box. i can tell you ive used at various retailers (macys and a local liquor store being 2) and once i realized i had to have root off for the purchase i have not had an issue.

Android Pay - Root, Unroot?

I am interested in using Android Pay but understand the phone cannot be rooted.
I am curious I am would be able to Root for whatever purposes, and the unroot for day to day use to retain the ability to use Android Pay. I am willing to stay on the stock rom and install if needed.
Thanks

MoreGone said:
I am interested in using Android Pay but understand the phone cannot be rooted.
I am curious I am would be able to Root for whatever purposes, and the unroot for day to day use to retain the ability to use Android Pay. I am willing to stay on the stock rom and install if needed.
Thanks
Click to expand...
Click to collapse
I've seen threads that say to disable supersu, add cards, and reenable supersu and it should work. However, I tried this on the 6 and it never worked. As of now there doesn't seem to be surefire way to get Pay to work while rooted. If xposed is made for 6.0 a root cloak should work, but I can't be sure. Others may be able to provide addition info on this.

theycallmerayj said:
I've seen threads that say to disable supersu, add cards, and reenable supersu and it should work. However, I tried this on the 6 and it never worked. As of now there doesn't seem to be surefire way to get Pay to work while rooted. If xposed is made for 6.0 a root cloak should work, but I can't be sure. Others may be able to provide addition info on this.
Click to expand...
Click to collapse
What if you root your phone, apply an adblock, change your dpi, etc....and then unroot, leaving your changes intact. Then will android pay work?

ArkAngel06 said:
What if you root your phone, apply an adblock, change your dpi, etc....and then unroot, leaving your changes intact. Then will android pay work?
Click to expand...
Click to collapse
Some reports say the a DPI change causes AP to fail.
As far as the other, that should work fine.

Can anyone confirm this..? No Adblock is killing me.

I'm curious about this too. I've read that with nexus devices your have to lock the boatloader again as well as unroot. But then I've also seen people say these root then unroot tricks only work for adding cards, not for actually paying with them. I really like the idea of Android pay and hope nfc payments spread more, but everyday I ask myself "how many stores have nfc payment today vs how many things could I do with root today..." Not sure how long I can hold out.

It would be nice if we had a definitive answer or steps on how to add Android Pay but keep root. I'm using a systemless root now but have modified mixer_paths to increase headphone volume. I'm thinking about flashing stock boot then trying to add a card then going back to the modified boot.

Guys - you cannot root with the /system way (the traditional way).
Modifying anything in /system will cause Android Pay to fail. That explains editing hosts, DPI, build.prop, etc. /system has to be clean otherwise when you go to actually pay it will fail but allow you to add your payment methods.

new root method
http://www.androidpolice.com/2015/1...d-root-without-touching-the-system-partition/
http://forum.xda-developers.com/showpost.php?p=63197935&postcount=2
New root method that does not modify the /system

exSD said:
Guys - you cannot root with the /system way (the traditional way).
Modifying anything in /system will cause Android Pay to fail. That explains editing hosts, DPI, build.prop, etc. /system has to be clean otherwise when you go to actually pay it will fail but allow you to add your payment methods.
Click to expand...
Click to collapse
Are you saying even if you edit DPI, Android Pay will not work ? Can anyone confirm this ?

Good article on just what SafetyNet (Googles tamper checking for Android pay) does behind the scenes:
https://koz.io/inside-safetynet/
About 1/3 the way down the page it details the checks that are run to determine if the device has been tampered
Pretty interesting stuff, with a fairly important point: it does not reside on the actual device, its actually pulled down and run real-time when you fire up Android Pay. The interesting part about it is that could allow Google to disable some of the checks, to allow for things like Root, DPI changes, etc to actually NOT list the device as tampered. Will they? Who knows.

I have root and Android pay working fine. I've mad purchases multiple times this way
Sent from my Nexus 6P using Tapatalk

trebills said:
I have root and Android pay working fine. I've mad purchases multiple times this way
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
You have systemless root.
---------- Post added at 05:22 PM ---------- Previous post was at 05:21 PM ----------
kolyan said:
Are you saying even if you edit DPI, Android Pay will not work ? Can anyone confirm this ?
Click to expand...
Click to collapse
That is what I'm saying.
You edit DPI by modifying your build.prop file. That file resides in /system.
If you make any change to /system, Android Pay will NOT work. Period. You can root cloak/add card/unroot after editing DPI/etc but when it comes time to actually pay, the SafetyNet will fail because you've modified your /system.

kolyan said:
Are you saying even if you edit DPI, Android Pay will not work ? Can anyone confirm this ?
Click to expand...
Click to collapse
Confirmed.
Here's the testing ive done:
Unlocked bootloader...AP works entirely.
rooted...AP will not allow you add a card, or process a transaction. If you have a card added prior to root, AP will not allow a transaction.
Disable root in SuperSu...AP will work entirely after you disable root and reboot your phone with root disabled. If you enable root again, AP will continue to work until you reboot.
With a modded DPI/no root...AP will not process a transaction.
Modified hosts file via Adfree/Adaway-root disabled...adblocking with a modified hosts file has no effect on AP
Click to expand...
Click to collapse
Those tests are all completed transactions at a terminal.

exSD said:
Guys - you cannot root with the /system way (the traditional way).
Modifying anything in /system will cause Android Pay to fail. That explains editing hosts, DPI, build.prop, etc. /system has to be clean otherwise when you go to actually pay it will fail but allow you to add your payment methods.
Click to expand...
Click to collapse
This is not universally true. I tested/verified a working method for using AndroidPay on a Sprint LG G3 that had a modified /system partition. Obviously that's a completely different phone, but it's one of the first things I'll be testing once my Angler comes in on Monday. Same method works for enabling adding cards the same as making a purchase. Here's what worked for me.
I got it figured out as well and so here's my method. I honestly think, though, that its every man for himself out there on this and that what works for one is unlikely to work for another.
Mine does not use XPosed, I don't have it installed. Requires use of SuperSU as your superuser manager and be currently rooted. I am running BarePapA-TE_V3 and NavelA-V1.6.
Download RootCloak Plus (Cydia) and Cydia Substrate from the Play Store.
Open Substrate. It tells me "Note: something about your device made it impossible for Substrate to perform its internal safety check; can you please contact saurik via e-mail?". Doesn't seem to effect anything.
Open RootCloak Plus (Cydia). Here you are going to be adding apps to a list of ones you don't want knowing you have root. There are a bunch of defaults already which you can leave. Add AndroidPay (com.google.android.apps.walletnfcrel). Now beyond that, I went ahead and added a number of other Google Apps and be certain any of them are required, but its what I did. I added the new Wallet app, Google Play Services, Play Store, Google Partner Setup, Google Account Manager, and Google Services Framework. Basically, my reasoning was that given the commitment to blocking rooted devices from using AndroidPay, it'd be useful to cloak any of the other financial apps and core GAPPS as well . . . because who knows how they are checking for root?
Reboot device.
Open SuperSU and uninstall superuser.
Reboot device. AndroidPay now works, buy yourself an Oreo McFlurry with your phone you clever hacker.
Obviously, your rooted apps won't work. So, if you want them back you will have to open SuperSU and reinstall superuser. That is going to break AndroidPay. Each time you want to use it again, you have to repeat the last two steps. So, there's the compromise . . . you can either leave your phone unrooted or have to reboot every time you want to use it.
Click to expand...
Click to collapse

cabbieBot said:
This is not universally true. I tested/verified a working method for using AndroidPay on a Sprint LG G3 that had a modified /system partition. Obviously that's a completely different phone, but it's one of the first things I'll be testing once my Angler comes in on Monday. Same method works for enabling adding cards the same as making a purchase. Here's what worked for me.
Click to expand...
Click to collapse
My phone is rooted in the normal way by flashing SuperSu.
If you change DPI on the phone it no longer passes a check of hardware configuration, so the device fails.
Other files have no effect. Hosts file does not describe HW so it doesn't matter.
Build.conf can be modified but not in areas that don't match the hardware.
I've had xposed installed after adding cards and added root cloak and had no isses.

I am rooted with system less root and android pay works fine. N6p angler.
---------- Post added at 12:02 AM ---------- Previous post was at 12:01 AM ----------
kolyan said:
Are you saying even if you edit DPI, Android Pay will not work ? Can anyone confirm this ?
Click to expand...
Click to collapse
That's correct do not edit stock dpi or pay will not work /at least as far as adding cards anyway (tested).

Thanks. I guess no AP for me. I root only to edit built.prop

puritan007 said:
I am rooted with system less root and android pay works fine. N6p angler.
---------- Post added at 12:02 AM ---------- Previous post was at 12:01 AM ----------
That's correct do not edit stock dpi or pay will not work /at least as far as adding cards anyway (tested).
Click to expand...
Click to collapse
Rooted with system less root and Android Pay works....are you referring to it works without disabling root and rebooting? Or it just works regardless?
Seems there are some posts saying it works as long as you reboot with root disabled, and others saying "it works" but need clarification of any process that needed to be done before using it.

chrisexv6 said:
Rooted with system less root and Android Pay works....are you referring to it works without disabling root and rebooting? Or it just works regardless?
Seems there are some posts saying it works as long as you reboot with root disabled, and others saying "it works" but need clarification of any process that needed to be done before using it.
Click to expand...
Click to collapse
With any root before 5.46 you had to Un root to add cards. With 5.46 system less I did nothing it just works how it should with no messing about

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?

How to delete system update files?

Okay so here is the deal. I connected my phone to my home wifi to adjust some settings to shut off my internet at night so the kids will go to bed... well be more likely to go to bed when they can't just sit and watch youtube/netflix all night. Personally I don't think they need tablets or entertainment to fall asleep, but they are my fiance's kids, and it is what it is because they have used this method for so long.
Anyway enough personal stuff, when I connected my phone, it downloaded a system update. I could not stop it, and now it is bugging me to restart and update but I dont want to. I can delay it, up to 9 times, for a later time, but I want to delete the update files entirely.
I was hoping there would be a way to do it without root, but I am fairly certain that at this point, I'm going to have to bite the bullet and install the update

Use adhell3 or adb to disable com.wssyncmldm

lightmastertech said:
Use adhell3 or adb to disable com.wssyncmldm
Click to expand...
Click to collapse
Thanks I will look up the adb command.

b3y0ndd34th said:
Thanks I will look up the adb command.
Click to expand...
Click to collapse
https://www.xda-developers.com/uninstall-carrier-oem-bloatware-without-root-access/
Best guide I've seen, including how to reinstall apps disabled though adb, which most people seem to think is impossible.
EDIT: the shorted link on my end says "...root access" at the end. Just to be clear, the not shortened end of that link actually says "uninstall-carrier-oem-bloatware-without-root-access/", so yes, it works without root.

lightmastertech said:
https://www.xda-developers.com/uninstall-carrier-oem-bloatware-without-root-access/
Best guide I've seen, including how to reinstall apps disabled though adb, which most people seem to think is impossible.
EDIT: the shorted link on my end says "...root access" at the end. Just to be clear, the not shortened end of that link actually says "uninstall-carrier-oem-bloatware-without-root-access/", so yes, it works without root.
Click to expand...
Click to collapse
Thanks for the guide, but it tells me the package isn't installed for user 0.

b3y0ndd34th said:
Thanks for the guide, but it tells me the package isn't installed for user 0.
Click to expand...
Click to collapse
When I disabled this the entire settings option for system update disappears, and back in early March when I was still holding out for a Snapdragon root my phone auto downloaded an update and gave me a persistent notification about installing update. Disabling this made it go away and it couldn't auto-install it.
You can install App Inspector to see a searchable list of every app on your phone, including the package name you need for adb.
BTW, there's an option in developer options that will let you disable auto-installing updates on restart.