Related
Hi guys how do I update Kodi to a newer version
trickyrick said:
Hi guys how do I update Kodi to a newer version
Click to expand...
Click to collapse
One easy way is to install FireStarter and then go to update tab and update or install Kodi from there. FireStarter is a great launcher as well.
Thanks I just tried that. It installs ok but when I try to update Kodi I get "Install blocked for security your phone is set to block installation of apps obtained from unknown sources". I have old software on Fire TV so in developer options I can't turn that option off.
Is there any other way to update Kodi without uninstalling first.
Fire TV version. 51.1.0.1-user-510055620
trickyrick said:
Thanks I just tried that. It installs ok but when I try to update Kodi I get "Install blocked for security your phone is set to block installation of apps obtained from unknown sources". I have old software on Fire TV so in developer options I can't turn that option off.
Is there any other way to update Kodi without uninstalling first.
Fire TV version. 51.1.0.1-user-510055620
Click to expand...
Click to collapse
you can update it using adb install with the -r command: adb install -r your kodi apk
Hi all
Sorry if this is a repeat but hope not.
My AFTV updated to 5.0.5. Claims an installed date of 21 Jan 16, but only recently have I noticed a number of issues, so not sure why they took so long to show up, unless 21 Jan is actually the 5.0.5 build date, rather than install. So here's what I've found (on Fire TV and stick - got both).
1. First Llama stopped working - I used LLama events with Condition/Action setup to start Kodi whenever I started Ikono (and switched logos). Testing the condition appeared to work, i.e. Kodi fired up but the difference was that in the test BEFORE you used to see Ikono fire up for a few seconds then switch to Kodi. After the 5.0.5 the test just fired up Kodi. And then when you start Ikono in the normal way, Kodi does not fire. Same for all my other "shortcuts".
2. Wukong: would not work for a while, the mouse pointer showed up by clicks did not fire off any action on AFTV side. A few reboots and messing around solved it but even now a bit flakey, compared to solid before.
3. Side-loading: cannot side-load apps now! Can connect via ADB, but running "adb install xxxxxx.apk" results in a:
error: device not found
- waiting for device -
4. Apps that update themselves, e.g. ShowBox, are failing (probably for the same reason as 3)
So is this common? I'm assuming Amazon have put in a range of changes to lock-down the device? Are there any workarounds / fixes?
Jed
JedSpink said:
Hi all
Sorry if this is a repeat but hope not.
My AFTV updated to 5.0.5. Claims an installed date of 21 Jan 16, but only recently have I noticed a number of issues, so not sure why they took so long to show up, unless 21 Jan is actually the 5.0.5 build date, rather than install. So here's what I've found (on Fire TV and stick - got both).
1. First Llama stopped working - I used LLama events with Condition/Action setup to start Kodi whenever I started Ikono (and switched logos). Testing the condition appeared to work, i.e. Kodi fired up but the difference was that in the test BEFORE you used to see Ikono fire up for a few seconds then switch to Kodi. After the 5.0.5 the test just fired up Kodi. And then when you start Ikono in the normal way, Kodi does not fire. Same for all my other "shortcuts".
2. Wukong: would not work for a while, the mouse pointer showed up by clicks did not fire off any action on AFTV side. A few reboots and messing around solved it but even now a bit flakey, compared to solid before.
3. Side-loading: cannot side-load apps now! Can connect via ADB, but running "adb install xxxxxx.apk" results in a:
error: device not found
- waiting for device -
4. Apps that update themselves, e.g. ShowBox, are failing (probably for the same reason as 3)
So is this common? I'm assuming Amazon have put in a range of changes to lock-down the device? Are there any workarounds / fixes?
Jed
Click to expand...
Click to collapse
1) Lama does not work under OS5
2) Sometimes I have to reboot as well
3) go in settings/ Developer Options/and turn off and on ADB debugging a three times ....
bula1ca said:
1) Lama does not work under OS5
2) Sometimes I have to reboot as well
3) go in settings/ Developer Options/and turn off and on ADB debugging a three times ....
Click to expand...
Click to collapse
Thanks for confirming 1), I tried AutomateIt too and it seems to have the same problem, so I suppose it's some sort of OS-level blocking of the kind of hooks that Llama and others used in the past? Guess they could argue it was a security improvement as allowing one app to start another could be abused...
Re: Wukong and side-loading being blocked.... I played a bit more and similar results to you.... I don't think the OS is deliberately blocking / preventing but there may be a bug or issue. For example if I do a reboot of the box then, say, Wukong, will work fine but then tried:
adb kill-server
adb start-server
adb connect xx.xx..x.xx
and then quick test with: adb shell
and get the error: device not ready.
Do a reboot, don't connect Wukong and try the above commands and adb shell works (quick test) and then any commands like adb push / install work too. But then Wukong seems blocked, e.g. may connect as mouse pointer but using the click function does nothing, or may not connect at all.
I'll try your fix of the ADB debug off/on instead of reboot; and see how that goes.
Fun times!
Wukong seems working fine for me but the remote mouse for fire t.v. unable to click
did you carry on using your device as is with the same data from the old version?i.e. no factory reset after the update?
i ask because things often break after an OTA.
i factory reset my fire stick after the update and then again after kingroot(do not push super su on it yet if you want root-wait for a pre-rooted image if you want super su).
so after re-logging in, i enabled adb, sent kodi to the device and i can launch it from Apps on the left hand side, no need to go into settings anymore or even use llama. it's there. it won't be in the recent apps, i don't know why, but at least it shows up in apps.
i don't use wukong, but i have set up my rooted phone to be a bluetooth mouse, just encase or even use my ps4 touchpad.
El_Nino9 said:
did you carry on using your device as is with the same data from the old version?i.e. no factory reset after the update?
i ask because things often break after an OTA.
i factory reset my fire stick after the update and then again after kingroot(do not push super su on it yet if you want root-wait for a pre-rooted image if you want super su).
so after re-logging in, i enabled adb, sent kodi to the device and i can launch it from Apps on the left hand side, no need to go into settings anymore or even use llama. it's there. it won't be in the recent apps, i don't know why, but at least it shows up in apps.
i don't use wukong, but i have set up my rooted phone to be a bluetooth mouse, just encase or even use my ps4 touchpad.
Click to expand...
Click to collapse
Lama is broken in OS5. Are you sure about it?
bula1ca said:
Lama is broken in OS5. Are you sure about it?
Click to expand...
Click to collapse
i never said llama works under OS5.
all i said it's not needed anymore due to kodi being available to launch from the apps menu on the left hand side.
Zenroid said:
Wukong seems working fine for me but the remote mouse for fire t.v. unable to click
Click to expand...
Click to collapse
My remote mouse for fire tv works fine on OS5 prerooted rom
Zenroid said:
Wukong seems working fine for me but the remote mouse for fire t.v. unable to click
Click to expand...
Click to collapse
Hi that's what I get sometimes, shows mouse pointer but click does not work. I find a reboot of the fire box fixes... what i've noticed it that once you have got say Wukong working then adb will not do adb - install or push: gets the device not ready error. Again a reboot will fix but then, say, Wukong won't work properly.
So it seems like something is blocking the other process - hence why I was wondering if a bug.
Take on the point about doing a factory reset from @El_Nino9 but then I'll have to reinstall and setup Kodi and my other side-loaded apps from scratch?
Jed
JedSpink said:
Take on the point about doing a factory reset from @El_Nino9 but then I'll have to reinstall and setup Kodi and my other side-loaded apps from scratch?
Jed
Click to expand...
Click to collapse
as with all factory resets, you have to redo the setup. there are tools available to back up your setups and its easy enough to adb install apps. plus you might be able to push all the latest versions of the apps back on the fire if you haven't done so already.
it depends what you want to achieve and what you want to eliminate. it all involves doing some sort of work, however i understand the more little work you have to do the better it is. no need.
El_Nino9 said:
as with all factory resets, you have to redo the setup. there are tools available to back up your setups and its easy enough to adb install apps. plus you might be able to push all the latest versions of the apps back on the fire if you haven't done so already.
it depends what you want to achieve and what you want to eliminate. it all involves doing some sort of work, however i understand the more little work you have to do the better it is. no need.
Click to expand...
Click to collapse
You are right of course. Just being a bit lazy. It's mainly Kodi I worry about as I have a lots of add-ons and takes time to setup correctly. I know you can backup your Kodi configuration but never done a backup / restore of Kodi. Will take a look into it and if I can preserve my add-ons then will do factory reset and adb -install them again.
JedSpink said:
You are right of course. Just being a bit lazy. It's mainly Kodi I worry about as I have a lots of add-ons and takes time to setup correctly. I know you can backup your Kodi configuration but never done a backup / restore of Kodi. Will take a look into it and if I can preserve my add-ons then will do factory reset and adb -install them again.
Click to expand...
Click to collapse
i rooted my device and would use titanium back up. however kodi within itself has various tools.
they have an addon called back up and they also have other features.
however, on the stick, you can use storage easily unless you know how to adb well.
for simple use i would recommend titanium back up and then back up to a cloud service such as gdrive.
each user has different preferences.
if you aren't rooted just use the addon back up too or there is a 3rd party app that also does similar stuff which i've never used so can't help.
if you do decide to root, do not use supersume app after kingroot. stick to king root su until a rooted system image is released for the device. i used kingroot 4.1 from xda thread and despite it saying failed i had root.
if you're not comfortable don't do it
You can use Tasker instead of llama
I have been having some problems of Amazon updates downloading and trying to install on my FTV and FTV2 boxes. They are rooted and I tried to block using the router address blocks and using adb commands to block. However the last two days I have seen my FTV stuck at TWRP screen. I'm think the update tried to install and got stopped by TWRP.
Just wondering if there is any new methods for blocking these updates from Amazon?
Have you tried a system app remover or disabler?
If you look through your system applications, look for com.amazon.device.software.ota and attempt to uninstall it or disable it. I mostly disable packages within adb shell, su, pm disable com.amazon.device.software.ota. Just by getting rid of this package should give you an update error which is completely normal until there's a prerooted rom available for the Fire TV. Let me know if you need any help
Personally, I have an OpenDNS setup blocking stuff. I have 2 AFTV2 boxes, and much easier to setup the dns in the wifi settings, than to do other things.
Plus, I'm all set for any future devices I may get!
On a side note, I also use Blokada. And in the section to whitelist/blacklist, I came upon a 'All apps'....and it adds, just that! I did notice a lot of those same services in the mix, but unknown if I'd trust just using that to stop updates.
Hi
I have a Fire TV STICK Gen 2 TANK TataSky Binge Edition which comes with preinstalled Binge app.
I wanted to use the device without Binge Subscription Just to watch youtube amazone prime and others just as a normal Firestick
But without binge subscription the device will not allow to open any other Apps including YouTube or VLC.When i Try to open a subscription Expired Message shows
So i Unlocked aand rooted using Magisk and uninstalled Binge app.But Now the The try to open any app does Nothing.
Also replaced Amzone laucher with wolflauncher and still the app wont open(Even tried to lauch activity through ADB,and does nothing)
So I downloaded prerooted Stock Firmawre and flashed but after the setup completion the Binge app automatically Installed.
So anyone know how to use this stick without Binge but with stock firmware .
Currently I am using it with LineageOS 12.1 .But i like to use Alexa .
Any Help will be appreciated
REDISBLOOD said:
Hi
I have a Fire TV STICK Gen 2 TANK TataSky Binge Edition which comes with preinstalled Binge app.
I wanted to use the device without Binge Subscription Just to watch youtube amazone prime and others just as a normal Firestick
But without binge subscription the device will not allow to open any other Apps including YouTube or VLC.When i Try to open a subscription Expired Message shows
So i Unlocked aand rooted using Magisk and uninstalled Binge app.But Now the The try to open any app does Nothing.
Also replaced Amzone laucher with wolflauncher and still the app wont open(Even tried to lauch activity through ADB,and does nothing)
So I downloaded prerooted Stock Firmawre and flashed but after the setup completion the Binge app automatically Installed.
So anyone know how to use this stick without Binge but with stock firmware .
Currently I am using it with LineageOS 12.1 .But i like to use Alexa .
Any Help will be appreciated
Click to expand...
Click to collapse
First of all, you need to tell me what app is giving the overlay. I also need to know the priority of that.
I do not know anything about tata sky binge but we can try.
When your stick shows you expiration page, click on the alexa button, does the blue bar appear above or below the expiration page?
Simply saying, is the alexa voice bar visible or not
I also need the binge app, if you can share the apk (the one which is auto installing after flashing prerooted system image
SweenWolf said:
I also need the binge app, if you can share the apk (the one which is auto installing after flashing prerooted system image
Click to expand...
Click to collapse
Here is the com.tataskymore.open.uat from about mid 2019
Sus_i said:
Here is the com.tataskymore.open.uat from about mid 2019
Click to expand...
Click to collapse
Thanks for the app, is the stub app preinstalled on the FS?
I need more info, and seems like no one else is interested in sharing that.
SweenWolf said:
Thanks for the app, is the stub app preinstalled on the FS?
I need more info, and seems like no one else is interested in sharing that.
Click to expand...
Click to collapse
sorry for the delay in reply.
today i reinstalled stock firmware registered with another Amazon account completed the setup.
Then installed youtube .When i Click open button Nothing Happens.In home screen The Binge Icon already there(maybe stub) so i installed Binge App too
Now when i click Open The Overlay saying that Your Binge subscription is Not active.
I can press the Alexa Button and Blue bar appears and can talk to Alexa while staying in Overlay screen.
So without binge app no overlay.But app just cant Open.
So i guess the overlay from Binge App It somehow intercept the Intent and show the overlay
Attached app pulled from my device
Bing app com.tataskymore.open.uat
SweenWolf said:
I need more info
Click to expand...
Click to collapse
It's always the same for the prerooted and/or the stock rom.
pm.disable or uninstall the app won't work.
Seems the app comes over the air as soon as the stick gets connected to the internet (setup).
The binge app is part of some weird DRM, I guess boot1 related (serial or whatever...) but an attempt to change the serial with idme command failed too.
Besides the binge app, I guess there are some other apps and/or settings that gets pushed...
K4y0z looked at it in 2019.
I think without such a binge stick on the desk, it's a really hard job.
Without a binge stick in hands, the closest way to examine this thing is probably a full TWRP backup of an registered binge stick, in the best case with a valid working subscription.
If you restore such a backup on a tank, it should work the same as the original stick. A mmcblkboot1 backup shouldn't be necessary, but may be become handy too.
Sus_i said:
It's always the same for the prerooted and/or the stock rom.
pm.disable or uninstall the app won't work.
Seems the app comes over the air as soon as the stick gets connected to the internet (setup).
The binge app is part of some weird DRM, I guess boot1 related (serial or whatever...) but an attempt to change the serial with idme command failed too.
Besides the binge app, I guess there are some other apps and/or settings that gets pushed...
K4y0z looked at it in 2019.
I think without such a binge stick on the desk, it's a really hard job.
Without a binge stick in hands, the closest way to examine this thing is probably a full TWRP backup of an registered binge stick, in the best case with a valid working subscription.
If you restore such a backup on a tank, it should work the same as the original stick. A mmcblkboot1 backup shouldn't be necessary, but may be become handy too.
Click to expand...
Click to collapse
probably right.As soon as it connects to internet it downlaod OTA i guess .
If it Just only the Binge App then uninstall will do the trick.But without Binge App clicking the open button do nothing.
Tried to launch the app using ADB and same result.nothing Happens .
The lauch activity get blocked at system Level
Sus_i said:
It's always the same for the prerooted and/or the stock rom.
pm.disable or uninstall the app won't work.
Seems the app comes over the air as soon as the stick gets connected to the internet (setup).
The binge app is part of some weird DRM, I guess boot1 related (serial or whatever...) but an attempt to change the serial with idme command failed too.
Besides the binge app, I guess there are some other apps and/or settings that gets pushed...
K4y0z looked at it in 2019.
I think without such a binge stick on the desk, it's a really hard job.
Without a binge stick in hands, the closest way to examine this thing is probably a full TWRP backup of an registered binge stick, in the best case with a valid working subscription.
If you restore such a backup on a tank, it should work the same as the original stick. A mmcblkboot1 backup shouldn't be necessary, but may be become handy too.
Click to expand...
Click to collapse
If the stick is doing same thing with the prerooted image then its changing system partition, and not the bootloader, and if lineageos is able to open the apps then its definitely the system itself.
We need to compare the system partition before and after the "System Updation part " during Initial setup process.
Either its modifying /bin folder or /framework
We need to compare these folders.
We can push a binge clone to the system so the normal update will not be able to modify it.
There are fotaprovider and ota apps which must be removed from system.
We will see about that,
BTW
I he can setup up the file i gave yesterday,
Enable the second option.
It will toast out the currently running app
---------- Post added at 03:27 PM ---------- Previous post was at 03:26 PM ----------
REDISBLOOD said:
probably right.As soon as it connects to internet it downlaod OTA i guess .
If it Just only the Binge App then uninstall will do the trick.But without Binge App clicking the open button do nothing.
Tried to launch the app using ADB and same result.nothing Happens .
The lauch activity get blocked at system Level
Click to expand...
Click to collapse
If you are rooted try replacing
/bin folder with the prerooted image
SweenWolf said:
If the stick is doing same thing with the prerooted image then its changing system partition, and not the bootloader, and if lineageos is able to open the apps then its definitely the system itself.
We need to compare the system partition before and after the "System Updation part " during Initial setup process.
Either its modifying /bin folder or /framework
We need to compare these folders.
We can push a binge clone to the system so the normal update will not be able to modify it.
There are fotaprovider and ota apps which must be removed from system.
We will see about that,
BTW
I he can setup up the file i gave yesterday,
Enable the second option.
It will toast out the currently running app
---------- Post added at 03:27 PM ---------- Previous post was at 03:26 PM ----------
If you are rooted try replacing
/bin folder with the prerooted image
Click to expand...
Click to collapse
I lost a bit here.Cant find any file you mentioned.
i already installed Rom https://forum.xda-developers.com/fire-tv/development/fire-tv-stick-2-tank-prerooted-stock-t3912271 this thread and installed Magisk too.Unfortunatly i cant open magisak but can get Su on ADB.
Do how can i replace Bin Folder and how i can get that folder from prerooted image?
Also with Lineage OS i can open apps installed.
so there maybe the options.
one to block the updates even before on setup screen
other one is to remove updates after the setup
or patch Binge App
REDISBLOOD said:
I lost a bit here.Cant find any file you mentioned.
i already installed Rom https://forum.xda-developers.com/fire-tv/development/fire-tv-stick-2-tank-prerooted-stock-t3912271 this thread and installed Magisk too.Unfortunatly i cant open magisak but can get Su on ADB.
Do how can i replace Bin Folder and how i can get that folder from prerooted image?
Also with Lineage OS i can open apps installed.
so there maybe the options.
one to block the updates even before on setup screen
other one is to remove updates after the setup
or patch Binge App
Click to expand...
Click to collapse
You can use twrp
Or adb shell to push files to system
REDISBLOOD said:
If it Just only the Binge App then uninstall will do the trick.But without Binge App clicking the open button do nothing.
Click to expand...
Click to collapse
That is what I mean, the command works ofc, but it isn't a solution for your problem
SweenWolf said:
If the stick is doing same thing with the prerooted image then its changing system partition, and not the bootloader, and if lineageos is able to open the apps then its definitely the system itself.
Click to expand...
Click to collapse
Yes, something gets altered, but this must be triggered somehow (at the setup) by some unique IDME data stored on boot1 partition.
And yes, the bootloader (aka preloader) sitting on boot0 has nothing to do with it.
SweenWolf said:
We need to compare the system partition before and after the "System Updation part " during Initial setup process.
Either its modifying /bin folder or /framework
We need to compare these folders.
We can push a binge clone to the system so the normal update will not be able to modify it.
There are fotaprovider and ota apps which must be removed from system.
Click to expand...
Click to collapse
Maybe someone can provide a TWRP backup from system on mega, gdrive or something like that
REDISBLOOD said:
I lost a bit here.Cant find any file you mentioned.
i already installed Rom https://forum.xda-developers.com/fire-tv/development/fire-tv-stick-2-tank-prerooted-stock-t3912271 this thread and installed Magisk too.Unfortunatly i cant open magisak but can get Su on ADB.
Click to expand...
Click to collapse
You can play with the TWRP file manager, in case you've an OTG cable and a mouse... or you can use TWRP shell, and use adb commands like cd and ls
REDISBLOOD said:
Do how can i replace Bin Folder and how i can get that folder from prerooted image?
Click to expand...
Click to collapse
Same here, TWRP file manager or shell, commands like cp, you may be able to find a list of adb shell commands in the net.
REDISBLOOD said:
one to block the updates even before on setup screen
other one is to remove updates after the setup
or patch Binge App
Click to expand...
Click to collapse
I'm unsure about a fake binge apk, might not work. Can't remember, but that may be tested already.
As SweenWolf said, compare system before/after the setup might be the best move for now.
SweenWolf said:
You can use twrp
Or adb shell to push files to system
Click to expand...
Click to collapse
yes i am usind adb and TWRP command line to push and pull files.Currenlyt dont have OTG cable that suitable for fire stick.
And to replace the bin folder how can i get files from stock image?
Sus_i said:
I'm unsure about a fake binge apk, might not work. Can't remember, but that may be tested already.
.
Click to expand...
Click to collapse
right there maybe signature checks too,maybe Mod the Apk to return subscription status as Active?
REDISBLOOD said:
yes i am usind adb and TWRP command line to push and pull files.Currenlyt dont have OTG cable that suitable for fire stick.
And to replace the bin folder how can i get files from stock image?
right there maybe signature checks too,maybe Mod the Apk to return subscription status as Active?
Click to expand...
Click to collapse
do a
pm list packages
And search for any other tata sky app
SweenWolf said:
do a
pm list packages
And search for any other tata sky app
Click to expand...
Click to collapse
already did that and i didnt find any other tatasky Apps
Code:
package:com.amazon.net.smartconnect
package:com.amazon.tv.resolutioncycler
package:com.amazon.recess
package:com.amazon.platform.fdrw
package:com.amazon.ssmsys
package:com.amazon.tv.ime
package:com.amazon.whisperplay.contracts
package:com.android.providers.media
package:com.amazon.venezia
package:com.amazon.dcp.contracts.library
package:com.amazon.ftv.xpicker
package:com.android.wallpapercropper
package:com.amazon.metrics.api
package:com.amazon.vizzini
package:com.amazon.tv.devicecontrolsettings
package:com.amazon.device.controllermanager
package:com.amazon.bueller.notification
package:com.amazon.bueller.photos
package:com.ivona.orchestrator
package:com.amazon.device.sync
package:amazon.fireos
package:com.amazon.device.logmanager
package:com.android.documentsui
package:com.amazon.appaccesskeyprovider
package:com.android.externalstorage
package:com.amazon.dpcclient
package:com.android.htmlviewer
package:com.amazon.ceviche
package:com.amazon.amazonvideo.livingroom.firetv
package:com.amazon.alta.h2clientservice
package:com.android.providers.downloads
package:com.amazon.firetv.youtube
package:com.amazon.tv.parentalcontrols
package:com.android.providers.tv
package:com.amazon.ftv.screensaver
package:com.amazon.malcolm
package:com.amazon.tv.ottssolib
package:com.amazon.ftv.glorialist
package:com.amazon.dp.logger
package:com.amazon.ods.kindleconnect
package:com.android.inputmethod.pinyin
package:com.android.defcontainer
package:com.android.providers.downloads.ui
package:com.android.pacprocessor
package:com.amazon.tv.intentsupport
package:com.amazon.sharingservice.android.client.proxy
package:com.amazon.wcast.sink
package:com.amazon.webview
package:com.amazon.android.marketplace
package:com.android.certinstaller
package:android
package:com.amazon.tifobserver
package:com.amazon.dialservice
package:com.amazon.client.metrics.api
package:com.amazon.aca
package:com.amazon.ale
package:com.amazon.cpl
package:com.amazon.dcp
package:com.amazon.imp
package:com.amazon.ssm
package:com.amazon.sync.service
package:com.amazon.fireinputdevices
package:com.amazon.tv.settings.v2
package:com.android.backupconfirm
package:com.amazon.tv.csapp
package:com.amazon.logan
package:com.amazon.tahoe
package:com.amazon.tcomm
package:com.mediatek.floatmenu
package:com.amazon.naatyam
package:com.amazon.storm.lightning.tutorial
package:com.amazon.identity.auth.device.authorization
package:com.amazon.kindle.cms
package:com.android.providers.settings
package:com.amazon.kindleautomatictimezone
package:com.android.sharedstoragebackup
package:com.amazon.tv.fw.metrics
package:com.amazon.firehomestarter
package:com.amazon.securitysyncclient
package:com.amazon.unifiedshare.actionchooser
package:com.amazon.firerestapiframework
package:com.amazon.tv.routing
package:com.amazon.device.messaging
package:com.amazon.device.bluetoothkeymaplib
package:com.amazon.device.metrics
package:com.amazon.device.messaging.sdk.internal.library
package:com.amazon.providers
package:com.amazon.tv.devicecontrol
package:com.amazon.tv.ottssocompanionapp
package:com.android.onetimeinitializer
package:com.amazon.tv.alexanotifications
package:com.android.keychain
package:com.amazon.device.sale.service
package:com.amazon.cardinal
package:com.android.packageinstaller
package:com.svox.pico
package:com.amazon.tcomm.client
package:com.amazon.tv.forcedotaupdater.v2
package:com.amazon.client.metrics
package:com.amazon.device.settings.sdk.internal.library
package:com.android.proxyhandler
package:com.amazon.acos.providers.UnifiedSettingsProvider
package:amazon.jackson19
package:com.android.managedprovisioning
package:com.amazon.device.details
package:com.amazon.imdb.tv.android.app
package:com.amazon.tmm.tutorial
package:com.amazon.device.software.ota
package:com.amazon.gloria.smarthome
package:com.amazon.wifilocker
package:com.amazon.dcp.contracts.framework.library
package:com.amazon.device.bluetoothdfu
package:com.amazon.storm.lightning.services
package:com.amazon.whisperlink.core.android
package:com.amazon.kor.demo
package:com.amazon.device.messaging.sdk.library
package:com.amazon.tv.notificationcenter
package:com.dolby
package:com.amazon.tv.support
package:com.amazon.ags.app
package:com.amazon.tv.alexaalerts
package:com.amazon.tv.nimh
package:com.amazon.tv.oobe
package:com.amznfuse.operatorredirection
package:com.amazon.sync.provider.ipc
package:com.amazon.tv.legal.notices
package:com.android.settings
package:com.amazon.tv.settings.core
package:com.amazon.firebat
package:android.amazon.perm
package:com.amazon.tv.keypolicymanager
package:com.amazon.android.service.networkmonitor
package:com.amazon.kso.blackbird
package:com.amazon.providers.contentsupport
package:com.amazon.avl.ftv
package:com.android.vpndialogs
package:com.amazon.awvflingreceiver
package:com.amazon.device.crashmanager
package:com.amazon.whisperjoin.middleware.np
package:com.amazon.application.compatibility.enforcer
package:com.amazon.whisperplay.service.install
package:com.ivona.tts.oem
package:com.android.shell
package:com.amazon.tv.launcher
package:com.android.providers.userdictionary
package:com.amazon.shoptv.client
package:com.amazon.device.software.ota.override
package:com.android.location.fused
package:com.android.systemui
package:com.amazon.alexashopping
package:com.amazon.franktvinput
package:com.amazon.aria
package:com.amazon.avod
package:com.amazon.communication.discovery
package:com.amazon.alexa.externalmediaplayer.fireos
package:com.tataskymore.open.uat
package:com.amazon.tv.releasenotes
package:com.amazon.bluetoothinternals
package:com.amazon.ssdpservice
package:com.amazon.device.settings
package:com.amazon.tv.livetv
package:com.amazon.device.sync.sdk.internal
package:com.amazon.gloria.graphiq
package:com.amazon.connectivitydiag
package:com.android.bluetooth
package:com.amazon.device.lowstoragemanager
package:com.android.captiveportallogin
package:com.amazon.providers.tv
package:com.amazon.webview.chromium
package:com.amazon.bueller.music
package:com.amazon.hedwig
package:com.amazon.kindle.devicecontrols
package:com.amazon.katoch
package:com.amazon.application.compatibility.enforcer.sdk.library
Is there any way to block the updates even before the initial setup??
REDISBLOOD said:
already did that and i didnt find any other tatasky Apps
Is there any way to block the updates even before the initial setup??
Click to expand...
Click to collapse
Be careful with this.... I tried going though registration process and disabling OTA, deleting the binge app.
When booting the 5.2.7.3 the device wouldn't let me enter another amazon account when I logged out of the one that was tied to the stick originally.
The result was I had to flash pre-rooted stock again, and the binge app became apparent yet again.
As @SweenWolf said it is to do with the app writing to system each time registration connects.
I don't know of anyway round this (I looked everywhere) K4y0z and Sus_i Tamojitray all had a crack at it, and AFAIK lineage was the only way round it.
Bertonumber1 said:
Be careful with this.... I tried going though registration process and disabling OTA, deleting the binge app.
When booting the 5.2.7.3 the device wouldn't let me enter another amazon account when I logged out of the one that was tied to the stick originally.
The result was I had to flash pre-rooted stock again, and the binge app became apparent yet again.
As @SweenWolf said it is to do with the app writing to system each time registration connects.
I don't know of anyway round this (I looked everywhere) K4y0z and Sus_i Tamojitray all had a crack at it, and AFAIK lineage was the only way round it.
Click to expand...
Click to collapse
Sorry I didnt post this Update soon.
But i already confirmed that it has nothing to do with the system partition
What i actually did was take a TWRP backup of my FireStick just after i completed the initial setup.Then i re flash the Full stock ROM.Then Restored Only Data partition turned of my Router(Just to block WIFI) and booted firestick
Installed VLC from ADB and tried to launch VLC from settings>Apps Nothing Happens
Then I installed Binge App ADB(firestick Not connected to internet yet) and then opened VLC and the subscription expired page appeared.
So i can confirm that this has nothing to do with system partition.
and its somehow linked to amazon account and that specific Firestick .so this stick cant use like as retail version.
but can use LOS(Ofcourse without Alexa)
the only hope here is mod the Binge apk.I found some Amazon specific permissions and activities related to subscription Expired page.But i dont know the subscription check is from Amazon or Binge apk
REDISBLOOD said:
Sorry I didnt post this Update soon.
But i already confirmed that it has nothing to do with the system partition
What i actually did was take a TWRP backup of my FireStick just after i completed the initial setup.Then i re flash the Full stock ROM.Then Restored Only Data partition turned of my Router(Just to block WIFI) and booted firestick
Installed VLC from ADB and tried to launch VLC from settings>Apps Nothing Happens
Then I installed Binge App ADB(firestick Not connected to internet yet) and then opened VLC and the subscription expired page appeared.
So i can confirm that this has nothing to do with system partition.
and its somehow linked to amazon account and that specific Firestick .so this stick cant use like as retail version.
but can use LOS(Ofcourse without Alexa)
the only hope here is mod the Binge apk.I found some Amazon specific permissions and activities related to subscription Expired page.But i dont know the subscription check is from Amazon or Binge apk
Click to expand...
Click to collapse
Yeah I knew it was tied to the serial and amazon headend, but thought it had to be part of /system to have that level of control (preventing apps from opening)
Ofc lineage works :good: and Alexa is a spy anyway lol
--
REDISBLOOD said:
Hi
I have a Fire TV STICK Gen 2 TANK TataSky Binge Edition which comes with preinstalled Binge app.
I wanted to use the device without Binge Subscription Just to watch youtube amazone prime and others just as a normal Firestick
But without binge subscription the device will not allow to open any other Apps including YouTube or VLC.When i Try to open a subscription Expired Message shows
So i Unlocked aand rooted using Magisk and uninstalled Binge app.But Now the The try to open any app does Nothing.
Also replaced Amzone laucher with wolflauncher and still the app wont open(Even tried to lauch activity through ADB,and does nothing)
So I downloaded prerooted Stock Firmawre and flashed but after the setup completion the Binge app automatically Installed.
So anyone know how to use this stick without Binge but with stock firmware .
Currently I am using it with LineageOS 12.1 .But i like to use Alexa .
Any Help will be appreciated
Click to expand...
Click to collapse
Did You get any Solution .. If yes then please let me Know
i have tried twrp backup from other firestick 2ng gen
(which has stock firmware installed without tatsky bing ) but it's same the bing app automatically appears from no where my last options is lineage os but it has some flows that google voice search is not working and also bt speaker is not working and the bigest one is alexa eco devices are not working with it if you guys get any update one how to bypass tata bing app please let me know
Hi,
I recently bought a new Fire TV 4K that came with Version 6.2.8.1 out of the Box. It also has a Serial Number containing VM in it. According to some posts here this means, that it has some efuses blown and the USB Download Mode disabled in its bootrom, which makes it impossible right now to root or downgrade it.
The reason I need to downgrade is that I need to automate some tasks on the Fire TV for example with tasker. For exmaple I need the Fire TV to switch the Input at Boot automatically. It does this only when I press the home button. Automating this with tasker however requires the Accessibility Service, which Amazon has removed in current Versions of the Firmware. So the only solution is to root it or go back to older Firmwares, and both ways seem to have been blocked by AMazon right now.
Is this the latest information or are there solutions for this device to still root it?
And are there alternative ways to automate for example Home button press without root and Acessibility Service?
And which Fire Tv Stick can still be rooted right now even with the latest Firmware installed?
Any help would be appreciated.
According to this post, only versions with "VM190 or higher" have the fuse blown.
[UNLOCK][ROOT][TWRP][UNBRICK] Fire TV Stick 4K (mantis)
NOTE: There have been multiple reports of devices with serial numbers containing VM190 or higher being shipped with DL-Mode disabled in BROM. These devices cannot be unlocked using kamakiri. These devices do not show up at all on USB when...
forum.xda-developers.com
So maybe your unit has a s/n lower then VM190.
Yeah my Serial contains *VM081* but I bought it far later than the post you mentioned. Also that post was made before Version 6.2.8.1 was released and efuses burned, which apparently does not allow downgrading anymore. And the guy who found the exploit has not posted anymore since 2019.
My understanding is that the USB Download mode being disabled and the efuses blown are two different things.
I have not yet read any comment on wether you can root a fresh out of the box device that has Version 6.2.8.1 on it.
And additionally newer devices seem to have no USB Download mode.
Is there a way to check whether my devices efuses are blown or not? And whether my device has USB Download mode before I open and short the device. RIght now I can still send back the device, but not once I have opened it. I don't wanna find out after opening the device that I can not root it.
So before I open the Fire TV, I wanna know whether it is rootable or not. Otherwise I will send it back. I wanna know wether the rooting method does also work once the device has been updated to 6.2.8.1.
ALso it would help to know wether the efuses burning only is limted to the 4K model. In that case I could get a Lite or Version 2 of the Fire TV. Unfortunately I have not found any FAQ regarding such questions.
Spamm00r said:
My understanding is that the USB Download mode being disabled and the efuses blown are two different things.
Click to expand...
Click to collapse
No, it's most likely the same thing...
Spamm00r said:
Is there a way to check whether my devices efuses are blown or not?
Click to expand...
Click to collapse
Yes, you can short the stick, connect usb and watch in lsusb. It will show no sign of the stick if the efuse is gone.
You can also connect an USB TTL UART Adapter, while doing the shorting. Then the log shows you that the boot-process goes to halt.
Spamm00r said:
So before I open the Fire TV, I wanna know whether it is rootable or not. Otherwise I will send it back. I wanna know wether the rooting method does also work once the device has been updated to 6.2.8.1.
Click to expand...
Click to collapse
The root/unlock method based on BR DL-Mode (via shorting), will not work on any 4k stick running 6.2.8.0 or later, regardless of the serial number.
The new Lite Stick, the new fTV Stick and the newest fTV 4K-Max Stick are also BR DL-Mode disabled.
So its game over for the current Fire TV Stick Models in regards to rooting right?!
This wouldn't be such a big issue if Amazon hadn't removed accessibility services, which dramatically reduces the use of a Fire Tv Stick.
I guess we will have to search for alternative routes. WHile it is probably still possible to root the device via eMMC hardware method, this is way too complex for me.
I have already a few ideas.
My plan now is to use a raspberry pi in conjunction with the Fire TV and issue the automation commands via adb from the raspberry pi.
All I need is issue the Home key at certain points. Everything else Tasker can already do without root and accessibility services.
Also Tasker contains ADB over WIFI Plugin, and only needs a one time issue of the adb tcp command after every boot. After taht you have a adb client running on the fire tv itself to do the rest for automation.
My plan is to let the raspberry issue this adb command at every boot of the fire tv and after that Tasker will be able to do the rest via adb WIFI.
I hope that works out.
For further reference and anyone else stumbling over these issues. Before buying a Fire TV, I wasn't aware of these issues, that for example Accessibility services have been removed and Rooting is impossible right now. So Right now I think the better option is to avoid any Fire TV and buy a Raspberry 4 and run Android TV on it. That way you already have root access and can do anything you want on it.
Spamm00r said:
So its game over for the current Fire TV Stick Models in regards to rooting right?!
Click to expand...
Click to collapse
That is valid for the current methods. There is still further development, but development needs time...
So it's best if you take a look into the xda forums from time to time
Spamm00r said:
So its game over for the current Fire TV Stick Models in regards to rooting right?!
This wouldn't be such a big issue if Amazon hadn't removed accessibility services, which dramatically reduces the use of a Fire Tv Stick.
I guess we will have to search for alternative routes. WHile it is probably still possible to root the device via eMMC hardware method, this is way too complex for me.
I have already a few ideas.
My plan now is to use a raspberry pi in conjunction with the Fire TV and issue the automation commands via adb from the raspberry pi.
All I need is issue the Home key at certain points. Everything else Tasker can already do without root and accessibility services.
Also Tasker contains ADB over WIFI Plugin, and only needs a one time issue of the adb tcp command after every boot. After taht you have a adb client running on the fire tv itself to do the rest for automation.
My plan is to let the raspberry issue this adb command at every boot of the fire tv and after that Tasker will be able to do the rest via adb WIFI.
I hope that works out.
For further reference and anyone else stumbling over these issues. Before buying a Fire TV, I wasn't aware of these issues, that for example Accessibility services have been removed and Rooting is impossible right now. So Right now I think the better option is to avoid any Fire TV and buy a Raspberry 4 and run Android TV on it. That way you already have root access and can do anything you want on it.
Click to expand...
Click to collapse
You don't need to issue TCP command. By default, wireless adb debugging is turned on in Fire TV stick.
Shaikh Amaan FM said:
You don't need to issue TCP command. By default, wireless adb debugging is turned on in Fire TV stick.
Click to expand...
Click to collapse
But the Tasker adb function needs it or how else can I make that Tasker function work?
Spamm00r said:
But the Tasker adb function needs it or how else can I make that Tasker function work?
Click to expand...
Click to collapse
You might already knew this that in normal Android mobile phones, with "adb tcpip 5555" command in PC, you start the wireless adb on port 5555 in phone. But when you enable ADB Debugging in Fire TV from it's settings, the wireless ADB Debugging is by default started, so you don't need to run that TCP command as the wireless debugging is already on and then Tasker will use it to get it's work done.
Shaikh Amaan FM said:
You might already knew this that in normal Android mobile phones, with "adb tcpip 5555" command in PC, you start the wireless adb on port 5555 in phone. But when you enable ADB Debugging in Fire TV from it's settings, the wireless ADB Debugging is by default started, so you don't need to run that TCP command as the wireless debugging is already on and then Tasker will use it to get it's work done.
Click to expand...
Click to collapse
Yes I agree the adb is active one the Fire Tv Stick and you can connect to it via wifi on port 5555.
But tasker still does not work with the adb function.
How did you make it work?
According to this:
https://tasker.joaoapps.com/userguide/en/help/ah_adb_wifi.html
You need to run this comamnd everytime you reboot.
Spamm00r said:
Yes I agree the adb is active one the Fire Tv Stick and you can connect to it via wifi on port 5555.
But tasker still does not work with the adb function.
How did you make it work?
According to this:
https://tasker.joaoapps.com/userguide/en/help/ah_adb_wifi.html
You need to run this comamnd everytime you reboot.
Click to expand...
Click to collapse
I am not using Tasker. But as you said above that you'll use raspberry to issue adb tcip command to the stick to turn on wireless debugging, that's not needed.
As far as I think, you'll have a profile of device boot event in Tasker and in it you'll have a ADB Wifi action which will have the button press command.
If that's the case then it should work without any issue.
In ADB WiFi action, set host to 127.0.0.1 ( Just saw that this is optional as well )
If it doesn't works let me know, I'll try installing tasker in my stick and test adb wifi in it.
How do you change volume in your volume change app without root?
Maybe I can issue the command for changing hdmi input the same way.
Shaikh Amaan FM said:
I am not using Tasker. But as you said above that you'll use raspberry to issue adb tcip command to the stick to turn on wireless debugging, that's not needed.
As far as I think, you'll have a profile of device boot event in Tasker and in it you'll have a ADB Wifi action which will have the button press command.
If that's the case then it should work without any issue.
In ADB WiFi action, set host to 127.0.0.1 ( Just saw that this is optional as well )
If it doesn't works let me know, I'll try installing tasker in my stick and test adb wifi in it.
Click to expand...
Click to collapse
Spamm00r said:
How do you change volume in your volume change app without root?
Maybe I can issue the command for changing hdmi input the same way.
Click to expand...
Click to collapse
What's the adb command to change hdmi input?
Shaikh Amaan FM said:
What's the adb command to change hdmi input?
Click to expand...
Click to collapse
There is no adb command to do that diretcly, but the Fire TV switches to HDMI source, if you press home button. SO I wanna issue Home key input via adb to make it switch the HDMI source to the Fire TV Stick.
"key_home": "adb shell input keyevent 3",
As far as I know you need to have root to issue CEC COmmands diretcly. Otherwiese you ahve to make a system method do that for you.
You probably bought one with a serial number of
G4N0VM081..... which is the new blown fuse version. You need to scour ebay for serial number
G070VM190..... or lower, then follow the current rooting guide. Make sure it's BRAND NEW and never been opened or else you're SOL since used sticks have probably been updated. New rootable sticks exists. I found half dozen on ebay a few months ago.
Spamm00r said:
There is no adb command to do that diretcly, but the Fire TV switches to HDMI source, if you press home button. SO I wanna issue Home key input via adb to make it switch the HDMI source to the Fire TV Stick.
"key_home": "adb shell input keyevent 3",
As far as I know you need to have root to issue CEC COmmands diretcly. Otherwiese you ahve to make a system method do that for you.
Click to expand...
Click to collapse
Ok so I just installed Tasker in my stick, tested adb wifi in it, it didn't worked. But I can develop an app which can execute provided adb command on every boot. It's night in my timezone, I'll develop that app tomorrow inshaallah.
That would be awesome.
Please keep the command to execute generic, as it may be useful to also execute other commands at boot. Let the user decide what command to execute.
Shaikh Amaan FM said:
Ok so I just installed Tasker in my stick, tested adb wifi in it, it didn't worked. But I can develop an app which can execute provided adb command on every boot. It's night in my timezone, I'll develop that app tomorrow inshaallah.
Click to expand...
Click to collapse
Spamm00r said:
That would be awesome.
Please keep the command to execute generic, as it may be useful to also execute other commands at boot. Let the user decide what command to execute.
Click to expand...
Click to collapse
[APP][NO ROOT] ADB on Boot | Run adb commands at boot automatically
How to use? 1. Enable ADB Debugging from Fire TV settings 2. In this app, add the adb commands that you want to execute on every boot 3. Set whether you want to display a Toast message on completion of command execution 4. Test the script if...
forum.xda-developers.com
I have to correct myself about adb wifi out of tasker not working.
ADB Wifi does work depending on the app that you are using. Local ADB shell does not work, while Remote ADB Wifi app does work.
The adb plugin for tasker does not work, but the adb wifi action from Tasker itself does work right away. In my earlier tests, other apps were just blocking adb wifi and I was confused and thought tasker's adb wifi is not working. But you have to properly close the abd wifi session with a "exit" command. Also the windows adb tool freezes and has to be killed in taskmanager. That is a source of error for testing adb on fire TV.
Also the adb wifi of tasker will not accept semicolon seperated commands. Shaikh Amaan FM's tool however does. In tasker You will have to create new task for every command and only issue one command. I don't know why, but thats the result of my troubleshooting.
Also you have to make sure that Tasker is properly bought, a trial version or a not genuine version won't work, as Tasker has signature checks implemented which silently brakes plugins without any obvious error messages.
Plugins however also do not work in Macrodroid.
So best thing is to use Remote ADB Shell app or Tasker's built in adb wifi task. Thatway you can mostly work around the fact that Fire TV is locked down, has no root and has accessibility services disabled.
So this is the solution to:
Solution for no Root and no Accessibility Service on Fire TV 4K Mantis on Version 6.2.8.1
Thatway I'm able to make Fire TV switch input via tasker by issuing a home button press via adb.
That's the best thing you can do under these conditions that you can't have root on Fire TV right now.