Related
I have blocked all the hosts in the Host file. But, while trying to block OTA updates I get a different message in ADB.
When doing method 3 pm disable com.amazon.dcp
I get a message it was killed but not the message
“Package com.amazon.dcp new state: disabled”
Is there anything wrong or is it the same?
I mean there is a difference in killing a package and disabling it.
TIA
mloftus11 said:
I have blocked all the hosts in the Host file. But, while trying to block OTA updates I get a different message in ADB.
When doing method 3 pm disable com.amazon.dcp
I get a message it was killed but not the message
“Package com.amazon.dcp new state: disabled”
Click to expand...
Click to collapse
Did you go into super user mode first (ie: executed su) before doing the pm disable?
I would personally remove the lines from the hostsfile, as it looks like a factory reset will end you up with an unusable FTV.
JPDeckers said:
Did you go into super user mode first (ie: executed su) before doing the pm disable?
I would personally remove the lines from the hostsfile, as it looks like a factory reset will end you up with an unusable FTV.
Click to expand...
Click to collapse
Yes as far as I can tell. I followed the exact directions for Fire TV
Method 1: Disable Update Package – Recommended Method
This method disables the application on the Fire TV which checks for updates. This is the recommended method. Be aware that this method does not survive a factory reset and must be re-applied after the Fire TV competes its initial setup.
Connect to your Fire TV via ADB
At the command line type: adb shell and hit enter
Then type: su and hit enter (You may be asked to grant access on the Fire TV)
Then type: pm disable com.amazon.dcp and hit enter
You should see the message: “Package com.amazon.dcp new state: disabled”
Then type: exit and hit enter
Lastly, type: exit and hit enter again
what I get is
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Mike>cd C:\ADB\sdk\platform-tools
C:\ADB\sdk\platform-tools>adb shell
[email protected]:/ $ SU
SU
/system/bin/sh: SU: not found
127|[email protected]:/ $ su
su
1|[email protected]:/ $ pm disable com.amazon.dcp
pm disable com.amazon.dcp
Killed
137|[email protected]:/ $
You need to go to superuser first and under options set to grant root access by default. The default option is to pop up a window asking to grant permission or deny.
This way when you enter su you will get root access.
Enviado de meu GT-N7100 usando Tapatalk
KillerJoeBR said:
You need to go to superuser first and under options set to grant root access by default. The default option is to pop up a window asking to grant permission or deny.
This way when you enter su you will get root access.
Enviado de meu GT-N7100 usando Tapatalk
Click to expand...
Click to collapse
That was the problem. Thanks a bunch! I was worried about that. :laugh:
mloftus11 said:
That was the problem. Thanks a bunch! I was worried about that. :laugh:
Click to expand...
Click to collapse
Thanks for pointing this out. I've added some clarification to the tutorial to help others who run into the same issue.
fireTVnews.com said:
Thanks for pointing this out. I've added some clarification to the tutorial to help others who run into the same issue.
Click to expand...
Click to collapse
Well it is more me being a newb too ADB. But, I did know where to come too get help.
Disable individual services
Given that I'm not sure that disabling the entire com.amazon.dcp package is the thing to do, I started looking around and found:
http://forum.xda-developers.com/showpost.php?p=36568072&postcount=15
"When we developed the attached script we were very careful to only effect OTA and no other services"
After re-enabling the whole dcp package, I did run the disable-ota.sh script, and can confirm that update checks fail, enable-ota.sh enables them again. Note that the scripts need to be executed via adb, not SSH, as the latter will segfault. Anybody any idea why?
Feel quite a bit more confident now, now that only the OTA's have been blocked.
@mloftus11 You said you blocked updates through the hosts file so b careful not to reset your fire tv to default settings or you will end up soft bricked. You should revert your hosts to default to be safe and just use pm disable and router block.
Thanks I did unblock the hosts file. My Belkin n600 does not block individual websites though.
What about key words filtering? That's what mine is doing
{ParanoiA} said:
What about key words filtering? That's what mine is doing
Click to expand...
Click to collapse
No I will probably have to do it through OpenDNS
All I have for webfilters blocking choices is
Filtering Options >
Block Malicious, Adult and other non-family friendly sites
Block malicious and adult sites
Blocks malware, phishing, scam sites and sites that contain sexually explicit content
Block malicious sites
Blocks malware, phishing and scam sites
No Filters
JPDeckers said:
Given that I'm not sure that disabling the entire com.amazon.dcp package is the thing to do, I started looking around and found:
http://forum.xda-developers.com/showpost.php?p=36568072&postcount=15
"When we developed the attached script we were very careful to only effect OTA and no other services"
After re-enabling the whole dcp package, I did run the disable-ota.sh script, and can confirm that update checks fail, enable-ota.sh enables them again. Note that the scripts need to be executed via adb, not SSH, as the latter will segfault. Anybody any idea why?
Feel quite a bit more confident now, now that only the OTA's have been blocked.
Click to expand...
Click to collapse
I think you might be on to something. Anyone else noticing some of program art/images not displaying on the Fire TV side of things?
A day or so after blocking updates, I started noticing some of the Amazon content was not displaying images for certain shows -- just a black TV-looking image.
I've seen that Amazon firesticks have updated their software which has effected Firestarter. I just wanted to know three things:
Is it possible to block amazon updates? I've got a virgin superhub router.
Is there a way to backup the entire firestick and not just Kodi?
Can you previous firmwares versions be restored/downgraded on firesticks?
The last thing I think anyone wants is for an update that wipes of Kodi altogether :crying:
Yes, you can block updates. See my guide here: http://www.aftvnews.com/block
If the device is rooted and running TWRP custom recovery, you can backup and restore the entire device at once. There is no TWRP for the Fire TV Stick currently, but rbox is working on it. For now, all you can do is backup individual files and folders, like app data, but depending on where the data is stored, you may still need to be rooted. App data in /sdcard can be backed up without root, but app data in /data requires root to access.
You can only downgrade if the device is rooted and running TWRP custom recovery. There is an old downgrading method that requires root and uses the default recovery, but I have not tested it on Fire OS 5 devices.
Hey thanks for that, I think I managed to prevent the firestick from any updates using adb + terminal from you pointing me on the right track.
hi AFTVnews.
is the adb shell pm hide com.amazon.device.software.ota command still works ? i have tried yesterday and it worked fine, and today i try again the same commend on second device (fire stick) and i get : unknown command 'hide'
scofield27 said:
hi AFTVnews.
is the adb shell pm hide com.amazon.device.software.ota command still works ? i have tried yesterday and it worked fine, and today i try again the same commend on second device (fire stick) and i get : unknown command 'hide'
Click to expand...
Click to collapse
I'm on a firestick with 5.0.5 and ran the command no problem, and disconnected properly. I had issues though after a few fire stick reboots where my firestick was connected to my router and had an ip, but had no internet connection. Basically it seemed like the command blocked the firestick from doing anything. I used the unhide command and rebooted a few more times and then ran the command to hide it once more and rebooted a few more times. Now it appears it is blocking updates and i can still use kodi.
I also have been having router issues, so it could be my router.
AFTVnews.com said:
Yes, you can block updates. See my guide here: http://www.aftvnews.com/block
If the device is rooted and running TWRP custom recovery, you can backup and restore the entire device at once. There is no TWRP for the Fire TV Stick currently, but rbox is working on it. For now, all you can do is backup individual files and folders, like app data, but depending on where the data is stored, you may still need to be rooted. App data in /sdcard can be backed up without root, but app data in /data requires root to access.
You can only downgrade if the device is rooted and running TWRP custom recovery. There is an old downgrading method that requires root and uses the default recovery, but I have not tested it on Fire OS 5 devices.
Click to expand...
Click to collapse
Hi Aftvnews, how do you delete the update cache on the firestick? I got a new firestick but it was downloading update before I could stop it. It's there but if I can get into the folder to delete it that would be great. I saw mention how to do it but didn't show the command lines. Thanks!
scofield27 said:
hi AFTVnews.
is the adb shell pm hide com.amazon.device.software.ota command still works ? i have tried yesterday and it worked fine, and today i try again the same commend on second device (fire stick) and i get : unknown command 'hide'
Click to expand...
Click to collapse
The command only works on software version 5.0 and up. If that Stick is on 54.1.2.3 or older, then the only way to block updates is externally through a router or OpenDNS (method 3 and 4 in my guide).
eore227 said:
Hi Aftvnews, how do you delete the update cache on the firestick? I got a new firestick but it was downloading update before I could stop it. It's there but if I can get into the folder to delete it that would be great. I saw mention how to do it but didn't show the command lines. Thanks!
Click to expand...
Click to collapse
Your Stick must be rooted to delete the update file from /cache. Here's how to do it:
Code:
adb shell
su
rm -f /cache/*.bin
AFTVnews.com said:
The command only works on software version 5.0 and up. If that Stick is on 54.1.2.3 or older, then the only way to block updates is externally through a router or OpenDNS (method 3 and 4 in my guide).
Your Stick must be rooted to delete the update file from /cache. Here's how to do it:
Code:
adb shell
su
rm -f /cache/*.bin
Click to expand...
Click to collapse
Hi aftvnews can you show me how this command works for a mac? I just rooted a fire stick right now using king root. It says root was sucessful but I don't want to reboot as the update is on there. If I could delete this update before the update that would be good but I'm using mac terminal and typed in your command but it's not working. Thanks
---------- Post added at 02:09 AM ---------- Previous post was at 01:50 AM ----------
eore227 said:
Hi aftvnews can you show me how this command works for a mac? I just rooted a fire stick right now using king root. It says root was sucessful but I don't want to reboot as the update is on there. If I could delete this update before the update that would be good but I'm using mac terminal and typed in your command but it's not working. Thanks
Click to expand...
Click to collapse
Ok I have root access I typed adb shell then I did su to get root access. Now it shows [email protected] montoya: #
After the # i typed rm -f/cache/*.bin
Is this correct? I don't see anything happened
eore227 said:
Hi aftvnews can you show me how this command works for a mac? I just rooted a fire stick right now using king root. It says root was sucessful but I don't want to reboot as the update is on there. If I could delete this update before the update that would be good but I'm using mac terminal and typed in your command but it's not working. Thanks
---------- Post added at 02:09 AM ---------- Previous post was at 01:50 AM ----------
Ok I have root access I typed adb shell then I did su to get root access. Now it shows [email protected] montoya: #
After the # i typed rm -f/cache/*.bin
Is this correct? I don't see anything happened
Click to expand...
Click to collapse
First, be sure there is a space after the "f"
You won't see anything come up on the screen. I also just learned a few hours ago that there is an alternate location for the update file. So do the following to clear out both locations:
Code:
adb shell
su
rm -f /cache/*.bin
rm -f /sdcard/Android/data/com.amazon.device.software.ota/files/*.bin
Perfect that did the trick the update was deleted. I rebooted and still have root and uodate is gone. Thanks!
I want to unlock LTE on my phone.
Anyone know how to enable it?
deltadiesel said:
I want to unlock LTE on my phone.
Anyone know how to enable it?
Click to expand...
Click to collapse
Check out this link: https://forum.xda-developers.com/g4/general/guide-enabling-lte-bands-t3137818
if you haven't already.
sdembiske said:
Check out this link: https://forum.xda-developers.com/g4/general/guide-enabling-lte-bands-t3137818
if you haven't already.
Click to expand...
Click to collapse
It says permission denied
I am rooted.
Whats the problem?
Tried that link can't get passed permission denied
What SuperSU everyone using I'm still on 2.,82 says I'm rooted but maybe features are disabled
deltadiesel said:
It says permission denied
I am rooted.
Whats the problem?
Tried that link can't get passed permission denied
Click to expand...
Click to collapse
If you're referring to the link above that I posted, works fine for me. Maybe security setting in your browser - suggest you try looking at the security settings for the browser you're using or try a different browser.
Other option is to go to Google Search (preferably on a PC) and search XDA-Guide: Enabling LTE Bands.
sdembiske said:
If you're referring to the link above that I posted, works fine for me. Maybe security setting in your browser - suggest you try looking at the security settings for the browser you're using or try a different browser.
Other option is to go to Google Search (preferably on a PC) and search XDA-Guide: Enabling LTE Bands.
Click to expand...
Click to collapse
When I go to SuperSU is says denied
I need SuperSU pro I think
What is latest supersu
Its not my browser
I'm talking about when I run the line to enable it
Permission denied
deltadiesel said:
When I go to SuperSU is says denied
I need SuperSU pro I think
What is latest supersu
Click to expand...
Click to collapse
SuperSU doesn't have anything to do with accessing a link. I'm on v2.82, the latest update I've received to-date.
If using Chrome on your phone, turn off Safe Browsing in Settings > (under Advanced heading) > Privacy.
---------- Post added at 10:18 PM ---------- Previous post was at 10:10 PM ----------
deltadiesel said:
Its not my browser
I'm talking about when I run the line to enable it
Permission denied
Click to expand...
Click to collapse
Try enabling setenforce 0 in Terminal Emulator.
Just type in the following (enter each command separately):
su
setenforce 0 (to set permissive) or setenforce 1 (to re-enable enforcing)
and confirm with: getenforce
Failing that, it may be hard coded in your rom which may put you out of luck.
sdembiske said:
SuperSU doesn't have anything to do with accessing a link. I'm on v2.82, the latest update I've received to-date.
If using Chrome on your phone, turn off Safe Browsing in Settings > (under Advanced heading) > Privacy.
---------- Post added at 10:18 PM ---------- Previous post was at 10:10 PM ----------
Try enabling setenforce 0 in Terminal Emulator.
Just type in the following (enter each command separately):
su
setenforce 0 (to set permissive) or setenforce 1 (to re-enable enforcing)
and confirm with: getenforce
Failing that, it may be hard coded in your rom which may put you out of luck.
Click to expand...
Click to collapse
That works through terminal on my phone
Seems like running commands on my compute r it won't switch to root
Either way DFS isn't working now
Can't select my device
deltadiesel said:
Its not my browser
I'm talking about when I run the line to enable it
Permission denied
Click to expand...
Click to collapse
deltadiesel said:
That works through terminal on my phone
Seems like running commands on my computer it won't switch to root
Either way DFS isn't working now
Can't select my device
Click to expand...
Click to collapse
One other thought: failing to first enter adb shell will give that result on your PC.
The following worked for me -i.e., did not get permission-denied, on my laptop.
adb shell
su
echo 1 > /sys/devices/platform/lg_diag_cmd/diag_enable
sdembiske said:
One other thought: failing to first enter adb shell will give that result.
The following worked for me -i.e., did not get permission-denied.
adb shell
su
echo 1 > /sys/devices/platform/lg_diag_cmd/diag_enable
Click to expand...
Click to collapse
This doesn't work for me off my computer
It only works in terminal manager. It switches to root after su
Anyways now that I'm in where is this BAND tab in DFS
deltadiesel said:
This doesn't work for me off my computer
It only works in terminal manager. It switches to root after su
Anyways now that I'm in where is this BAND tab in DFS
Click to expand...
Click to collapse
With respect to the Band tab in DFS - post your questions now to the link I provided in the 1st instance.
If you do not have LGMobileDriver_WHQL_Ver_4.2.0 installed on your PC you will have problems with adb.
sdembiske said:
With respect to the Band tab in DFS - post your questions now to the link I provided in the 1st instance.
If you do not have LGMobileDriver_WHQL_Ver_4.2.0 installed on your PC you will have problems with adb.
Click to expand...
Click to collapse
That is installed
U know what forget this. Probably won't be able to enable band I want anyway
Wasting time
Made a new thread as seems this is demanded option. Some people already checked this and looks like this works. I can't check right now but if you want, please check and post if it works for you.
Restriction is phone number country code based, can be bypassed. Also looks like its developers left setting to disable country checks at all. To do that, you just need to change android setting 'pixel.oslo.allowed_override' to '1' or 'true'.
Connect Pixel 4 with developer mode and execute command in adb shell:
Code:
adb shell setprop pixel.oslo.allowed_override true
or
Code:
adb shell "setprop persist.pixel.oslo.allowed_override true; setprop ctl.restart zygote"
or edit system/build.prop with some app (eg. MagiskHide Props Config)
You need root to do this.
Also there is Xposed Module in xposed manager to do this automatically called "EnableSoliOnPixel4", here's thread about it https://forum.xda-developers.com/pixel-4-xl/themes/success-enable-soli-china-t3994917
Do I need root permission to execute this command via adb? Thanks
Sent from my Google Pixel 2 using XDA Labs
Monazite said:
Do I need root permission to execute this command via adb? Thanks
Sent from my Google Pixel 2 using XDA Labs
Click to expand...
Click to collapse
Yes, without root you can’t edit system props
Eugnis said:
Yes, without root you can’t edit system props
Click to expand...
Click to collapse
getting failed to set property reply. any idea what i'm doing wrong?
Does it mean that I still can use soli in any country even that country doesn't support for it ?
For example, If I traveled to Japan one day, I still can use soli after enable soli by this xposed module ?
Kris
omar5099 said:
getting failed to set property reply. any idea what i'm doing wrong?
Click to expand...
Click to collapse
Looks like ADB not received root rights on phone. To check this use
Code:
adb shell su
if you receive response ' su: not found ' then you should enable root access for adb on phone (with supersu or similar)
Also you can set this prop with MagiskHide Props Config from phone if you used Magisk to root it
Kris Chen said:
Does it mean that I still can use soli in any country even that country doesn't support for it ?
For example, If I traveled to Japan one day, I still can use soli after enable soli by this xposed module ?
Kris
Click to expand...
Click to collapse
Yes, this setting just disable country check at all. So Soli will work worldwide
Eugnis said:
Looks like ADB not received root rights on phone. To check this use
Code:
adb shell su
if you receive response ' su: not found ' then you should enable root access for adb on phone (with supersu or similar)
Also you can set this prop with MagiskHide Props Config from phone if you used Magisk to root it
Click to expand...
Click to collapse
I've obtained root for ADB shell via this command, however none of those 2 original adb lines are working. I'm still getting the failed to set property reply.
Any help appreciated...
Now I gotta root my phone and lose automatic updates just to be able to use it normally. Thanks a lot, Google!! _l_
You will still get automatic updates, you can root your phone, set the persistent property, and remove the root. Should persist across updates.
Bogega said:
I've obtained root for ADB shell via this command, however none of those 2 original adb lines are working. I'm still getting the failed to set property reply.
Any help appreciated...
Click to expand...
Click to collapse
yes same here, any1 got this to work ? thanks
Pixeling said:
You will still get automatic updates, you can root your phone, set the persistent property, and remove the root. Should persist across updates.
Click to expand...
Click to collapse
So if I set the property and then unroot, it will persist even after OTA updates? No need to root again and set it again after every OTA?
aco.falc said:
So if I set the property and then unroot, it will persist even after OTA updates? No need to root again and set it again after every OTA?
Click to expand...
Click to collapse
That's what I suspect since the property lives in /data which is not changed/erased after OTA. I've not tried it myself however that's probably what I will do when I get the phone.
aco.falc said:
So if I set the property and then unroot, it will persist even after OTA updates? No need to root again and set it again after every OTA?
Click to expand...
Click to collapse
Performing some more reading on the subject, there is a possibility that unlocking the bootloader by itself trips safetynet which in turn prevents OTA. I can't know whether this is true for sure, but in this case keeping Magisk root shall hide that and let you download the OTA.
Before applying the OTA you should use magisk to restore the boot.img, let the OTA install, and then let Magisk install itself to the other inactive flash slot where the OTA is. That will make sure that root is kept intact post update and keep hiding that the bootloader is unlocked. Can anyone confirm?
WORKED
hello, i can confirm its working, steps to follow :
when u flash the magisk_patched image the phone wont boot at first, so u have to flash the boot.img then reflash the magisk_patched.
then the phone will boot normally.
after that, download terminal from play store, and type in it : SU , this will ask u for root permissions
then u need to type these 3 commands within the terminal :
setprop pixel.oslo.allowed_override true
setprop persist.pixel.oslo.allowed_override true
setprop ctl.restart zygote
then motion sense will turn on.
enjoy!
if u need detailed steps about the whole thing let me know
sta3b said:
hello, i can confirm its working, steps to follow :
when u flash the magisk_patched image the phone wont boot at first, so u have to flash the boot.img then reflash the magisk_patched.
then the phone will boot normally.
after that, download terminal from play store, and type in it : SU , this will ask u for root permissions
then u need to type these 3 commands within the terminal :
setprop pixel.oslo.allowed_override true
setprop persist.pixel.oslo.allowed_override true
setprop ctl.restart zygote
then motion sense will turn on.
enjoy!
if u need detailed steps about the whole thing let me know
Click to expand...
Click to collapse
Can confirm that typing these commands in terminal did the trick. Used 'Terminal Emulator for Android' app from playstore.
And I skipped first steps (flashing boot.img etc) as I'm already rooted.
Thanks!
Bogega said:
Can confirm that typing these commands in terminal did the trick. Used 'Terminal Emulator for Android' app from playstore.
And I skipped first steps (flashing boot.img etc) as I'm already rooted.
Thanks!
Click to expand...
Click to collapse
It works for me! Thank you!
Do I need to do this all over again when I reboot my phone?
It seems that when rebooting the phone the soli is disabled again, can someone confirm?
Also I read here something about unrooting? can I really root and unroot everytime I want and retain OTA updates?
chris111111 said:
It works for me! Thank you!
Do I need to do this all over again when I reboot my phone?
Click to expand...
Click to collapse
Soli doesn't survive reboots if you're using this method.
There's a magisk module (non Xposed) which solves this though (https://forum.xda-developers.com/pixel-4-xl/themes/enable-soli-contries-magisk-module-t3997035)
wolfgangam31 said:
It seems that when rebooting the phone the soli is disabled again, can someone confirm?
Also I read here something about unrooting? can I really root and unroot everytime I want and retain OTA updates?
Click to expand...
Click to collapse
correct, rebooting the phone will cause SOLI to get disabled, you need to re-enter the commands in the terminal to get it to work again
Hello I have a question how to disable the update permanently ota I have rota and twrp after each update I have to upload everything from scratch so I want to disable these updates please help
sucks this is a forum
Try turning off system/developer options/automatic system updates
And
System/system updates/gear/auto download over wifi (turning this off will make the phone ask your permission to download)
Or
adb shell pm disable-user com.oneplus.opbackup
(Should disable updates)