Database Users

installation issues with apks

I can install from the market okay but if I have a .apk on my sd card I want to install I get the message that it cannot. Tells me the file cannot be viewed from here. Here is the exact words:
sdcard/download/amazon_appstore-release.apk
application/vnd.android.package-archive does not work.
Any ideas? This is getting frustrating and my searches have not turned out anything worthwhile.

Have checked the option for installing 3rd party apps in settings
Sent from my SPH-D700 using XDA App

yep! first thing i checked. Dont want to but I think I am going to wipe and reinstall rom, etc later tonight. Waiting to see if anyone has any other ideas.

ciccone said:
yep! first thing i checked. Dont want to but I think I am going to wipe and reinstall rom, etc later tonight. Waiting to see if anyone has any other ideas.
Click to expand...
Click to collapse
Maybe just reflash the package installer .apk from your rom
Sent from my SPH-D700

You could always try using adb to push the package from your PC to the phone while connected with USB debugging enabled.
adb install <package_file_name>

machx0r said:
You could always try using adb to push the package from your PC to the phone while connected with USB debugging enabled.
adb install <package_file_name>
Click to expand...
Click to collapse
Or file expert with root mode enabled.
cd's or tapes?

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

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

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

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

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

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

Already did it. :cyclops:

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Rooting Producedure

Anyone tried rooting Pixel XL and how does it works after rooting ? Reviews

Everything works fine here

Rooting generally does not and can not effect the device. What you do after may either harm or help the device.
All that rooting does is give you SU access it is what you do with the access that makes a difference.
Mind you even though in itself rooting is pretty harmless, Google will always try and detect the root and stop APPs like Android Pay from working.

AstroDigital said:
Rooting generally does not and can not effect the device. What you do after may either harm or help the device.
All that rooting does is give you SU access it is what you do with the access that makes a difference.
Mind you even though in itself rooting is pretty harmless, Google will always try and detect the root and stop APPs like Android Pay from working.
Click to expand...
Click to collapse
I mean is there any bootloop or something and how is everything working any lagging or somethjng

Huzaifaamirka said:
I mean is there any bootloop or something and how is everything working any lagging or somethjng
Click to expand...
Click to collapse
No issues here, Enable OEM unlock and unlock the device via ADB then use adb to "fastboot boot boot-to-root.img" allow it to reboot and set up again then away you go ( you might have to ADB BOOT the boot-to-root for it to stick )
Using the ad away work around now ad blocking is a go

Working fine with ElementalX kernel and root.

hutzdani said:
No issues here, Enable OEM unlock and unlock the device via ADB then use adb to "fastboot boot boot-to-root.img" allow it to reboot and set up again then away you go ( you might have to ADB BOOT the boot-to-root for it to stick )
Using the ad away work around now ad blocking is a go
Click to expand...
Click to collapse
Hi,
What is the adaway workaround?
Thank you for your help,
Bryan

trapperjohn said:
Hi,
What is the adaway workaround?
Thank you for your help,
Bryan
Click to expand...
Click to collapse
With USB Debuiing enabled open your ADB terminal and type :
"adb shell"
"su"
"mkdir /su/etc; cp /system/etc/hosts /su/etc/hosts; echo "#!/su/bin/sush\nmount -o bind /su/etc/hosts /system/etc/hosts" > /su/su.d/50adaway; chmod 0700 /su/su.d/50adaway"
After this reboot your device and apply ad blocking hosts with the latest ad away build

Thank you for the info!
I wonder if there are plans to update adaway so this procedure will not be needed..
Thanks again great detail
Bryan
Sent from my SM-N900V using XDA-Developers mobile app

Wrong sub forum.

trapperjohn said:
Hi,
What is the adaway workaround?
Thank you for your help,
Bryan
Click to expand...
Click to collapse
All you have to do is download the 3.2 Dev preview build and enable systemless mode in preferences. Works like a charm.
https://www.androidfilehost.com/?fid=312978532265366394

That's great so with version 3.2 dev no adb procedure is needed?

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?

Disable System Update

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