Related
Usually I let my fire tv update it self,cause I don't really care bout something going to be broken since I have no root in there..but not anymore since the last update (5.0.5)kick in,and that messed up one of my helpful app i used..Name is mouse toggle i used for the remote..uninstall tried to put it back but can't get none of the sideload apps to work with my fire tv..anyone out there kwn which one that's working or in PC..any links please? your help would be appreciate.I'm a none root user possibly will use for that purpose as well
Ths
im using this on 5.0.5 on my rooted AFTV2, my boys non rooted stick the one with the voice controller, & my AFTV stick without the voice controller & non rooted. Works on all of them, since you have installed OS5 things have changed in the settings of Firestarter which need to be changed, ADB only works with one device at a time so you have to look in your firestarter settings? try a fresh reboot? or reintall the app again?
Ok..deanr1977 I got it all figured..i now that i root, I'm waiting for a working costume recovery so I can install a nice launcher get ridded of somes bloats..thanks for your replied though
So do you own where to get the latest ADB software so I can try to block the update?
donjan3 said:
So do you own where to get the latest ADB software so I can try to block the update?
Click to expand...
Click to collapse
ADB -
http://www.aftvnews.com/how-to-setup-adb-and-fastboot-on-a-mac-or-windows-computer/
How to connect ADB to a Stick -
http://www.aftvnews.com/how-to-connect-to-a-fire-tv-or-fire-tv-stick-via-adb/
How to block updates -
http://www.aftvnews.com/how-to-block-software-updates-on-the-amazon-fire-tv-or-fire-tv-stick/
Commands -
adb shell
su
pm disable com.amazon.device.software.ota
exit
exit
PLEASE NOTE
On the su part be sure to select “Grant” if your Fire TV prompts you for superuser access!!!!
If this helps press that thanks button
Sent from my SM-G900F using Tapatalk
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
Hey guys,
I just received a brand new Fire TV 4K. I want to prevent my device from updating to the newest version, so that I can get root easily. However, when I use the following guide in order to skip the initial update procedure it continues to show me the error message instead of jumping to the registration screen. I set up my router to block the domains according to the guide and I turn of my Wi-Fi router the moment "connection succesful" appears on the screen. Any ideas how to fix this? Or does the method do not work if the Fire TV is shipped with the latest firmware?
Guide: http://www.aftvnews.com/how-to-complete-the-fire-tv-stick-initial-setup-without-updating/
wohltat said:
Hey guys,
I just received a brand new Fire TV 4K. I want to prevent my device from updating to the newest version, so that I can get root easily. However, when I use the following guide in order to skip the initial update procedure it continues to show me the error message instead of jumping to the registration screen. I set up my router to block the domains according to the guide and I turn of my Wi-Fi router the moment "connection succesful" appears on the screen. Any ideas how to fix this? Or does the method do not work if the Fire TV is shipped with the latest firmware?
Guide: http://www.aftvnews.com/how-to-complete-the-fire-tv-stick-initial-setup-without-updating/
Click to expand...
Click to collapse
i had the exact issue with my fire stick, it's on 5.0.5
after about 100 tries i was about to return it to the store
i went to try it one more time and took it out of the bag and plugged it in again ,it booted up and went straight to checking for updates without asking me to configure the network settings
so i quickly unplugged my modem from my router and it finally went to the registration screen
now i do not know if this thing remember the DNS /network settings i am guessing that it does not since it usually asks you to reconfigure them every time it is powered on prior to completing the setup
i guess it at least remembered the network and password , but i don't know about the DNS settings
it was not the 1st time it booted up and went straight to checking for updates without me configuring DNS settings , but the other few times it also failed to go to the registration screen, i am thinking that this FW has a block that detects if a proxy or open DNS is being used and then refuses to go to registration if it is,
my guess is that when it rebooted that time with out me going to advanced and entering open DNS settings
that it got through to amazon servers and that is what made the FW finally let me go to registration, also forgot to mention that it was downloading an update, but i was able to stop it in time and block the updates with ADB
so i did manage to prevent the update in the end
my guess is that the 1st step in that guide is the problem ,
my guess is that using open DNS to block amazon servers will make it impossible to get to the registration screen on the newer FW's ,at least on 5.0.5
you could always try to do the guide without blocking amazon servers using open DNS
and be really quick to unplug it after you get past registration , then just enable ABD and unknown apps and disconnect your modem from your router and connect to it and block updates via ADB
gdroid666 said:
i had the exact issue with my fire stick, it's on 5.0.5
after about 100 tries i was about to return it to the store
i went to try it one more time and took it out of the bag and plugged it in again ,it booted up and went straight to checking for updates without asking me to configure the network settings
so i quickly unplugged my modem from my router and it finally went to the registration screen
now i do not know if this thing remember the DNS /network settings i am guessing that it does not since it usually asks you to reconfigure them every time it is powered on prior to completing the setup
i guess it at least remembered the network and password , but i don't know about the DNS settings
it was not the 1st time it booted up and went straight to checking for updates without me configuring DNS settings , but the other few times it also failed to go to the registration screen, i am thinking that this FW has a block that detects if a proxy or open DNS is being used and then refuses to go to registration if it is,
my guess is that when it rebooted that time with out me going to advanced and entering open DNS settings
that it got through to amazon servers and that is what made the FW finally let me go to registration, also forgot to mention that it was downloading an update, but i was able to stop it in time and block the updates with ADB
so i did manage to prevent the update in the end
my guess is that the 1st step in that guide is the problem ,
my guess is that using open DNS to block amazon servers will make it impossible to get to the registration screen on the newer FW's ,at least on 5.0.5
you could always try to do the guide without blocking amazon servers using open DNS
and be really quick to unplug it after you get past registration , then just enable ABD and unknown apps and disconnect your modem from your router and connect to it and block updates via ADB
Click to expand...
Click to collapse
Thanks for the reply. However, it does not help me much. I did not block updates via Open DNS but via settings in my router.
For those you do not understand the problem, I created a short video: https://gaming.youtube.com/watch?v=vt2ntBk4K-M&feature=share
After the update error message, I should setup the Wi-Fi again and when the message "you are connected" appears, I have to turn off the router. This is what I do. However, the Fire TV does not skip to serach for updates and does not go straigth to registration.
wohltat said:
Thanks for the reply. However, it does not help me much. I did not block updates via Open DNS but via settings in my router.
For those you do not understand the problem, I created a short video: https://gaming.youtube.com/watch?v=vt2ntBk4K-M&feature=share
After the update error message, I should setup the Wi-Fi again and when the message "you are connected" appears, I have to turn off the router. This is what I do. However, the Fire TV does not skip to serach for updates and does not go straigth to registration.
Click to expand...
Click to collapse
well mine was hanging on checking for updates for like an hour and would never go to the registration screen, just back to the error screen .
ok you are not using open DNS ,but you are still blocking amazon servers, i think it may be that the new FW will not give you the registration screen until it gets an amazon server and connects to it
or it may have some other method of detecting that we are trying to block domains, be it through open DNS or our routers
or it could just be a huge coincidence that it worked for me when i did not configure the open DNS settings, but i i tried it literally over 100 times with open DNS and it would never go past the error screen
i might have tried it like 3 or 4 times without setting up open DNS and blocking the servers and it still would not go past the error screen, but that one time it worked i did not enter the open DNS settings
you can keep on trying and report back if it works with the domains blocked in your router, but if you get to a point where you give up like i did then you can try it without blocking the domains and see if it will go to the registration screen
Hi all,
I have recently upgraded my FireTV 1 to the latest Prerooted stock image as per this forum page: https://forum.xda-developers.com/fire-tv/development/prerooted-stock-images-t2882337
Software Version: 51.1.5.3_user_515040320
I upgraded from FireOS 3 so did the TWRP recovery first.
I also installed the su /sdcard fix as outlined in the forum page as well.
Everything installed correctly, and the FireTV boots correctly to the main screen. I am experiencing problems however:
The Home, Your Videos, Movies and TV Shows screens never load, just stay black with the three small dots bottom right of screen animating.
The Apps and Settings screens work as expected.
Connection to the Internet works, Netflix and YouTube apps work as expected, as does Kodi and others.
Individual application updates work, and are automatically triggered as expected.
I have no DNS/IP filtering setup in my router or hosts file on the FireTV
I have blocked updates from running with the following command: pm disable com.amazon.device.software.ota
Any advice on getting the rest of the interface working would be greatly appreciated.
fionn.colvin said:
Hi all,
I have recently upgraded my FireTV 1 to the latest Prerooted stock image as per this forum page: https://forum.xda-developers.com/fire-tv/development/prerooted-stock-images-t2882337
Software Version: 51.1.5.3_user_515040320
I upgraded from FireOS 3 so did the TWRP recovery first.
I also installed the su /sdcard fix as outlined in the forum page as well.
Everything installed correctly, and the FireTV boots correctly to the main screen. I am experiencing problems however:
The Home, Your Videos, Movies and TV Shows screens never load, just stay black with the three small dots bottom right of screen animating.
The Apps and Settings screens work as expected.
Connection to the Internet works, Netflix and YouTube apps work as expected, as does Kodi and others.
Individual application updates work, and are automatically triggered as expected.
I have no DNS/IP filtering setup in my router or hosts file on the FireTV
I have blocked updates from running with the following command: pm disable com.amazon.device.software.ota
Any advice on getting the rest of the interface working would be greatly appreciated.
Click to expand...
Click to collapse
Since you are not blocking updates thru OpenDNS or thru your Router then my only advice is to do a cache wipe thru TWRP. Also make sure you don't have any VPN apps running. And also go into Settings/My Account & choose Sync Amazon Content & reboot.
Connect a keyboard to your FTV.
Then choose Launch Recovery.
Then go into WIPE & Choose Advanced Wipe.
From Advanced Wipe choose both "Dalvik / Art Cache" & "Cache" (This is not a Factory Reset).
Then Swipe to Wipe & restart your FTV.
It will take no more then 10 minutes to reload & everything should be unchanged (Apps, Settings, etc).
Then redo the ADB Method 1 FireOS 5 update blocking command. Just to make sure it is still blocking updates.
Use the "Troubleshooting" part of this guide for visuals:
http://www.aftvnews.com/how-to-installupdate-a-package-using-twrp-on-the-amazon-fire-tv/
If this doesn't work. Then maybe you will need to do a Factory Reset & reflash the whole PreRooted ROM.
Thanks for the advice.
Followed the steps suggested with the same results.
Would rather not factory refresh, however will do that if there re no other suggestions to try.
PS. I've also got a Fire Stick not rooted with latest firmware that works as expected, so shows there are no network reasons for it to not work on the FireTV
fionn.colvin said:
Thanks for the advice.
Followed the steps suggested with the same results.
Would rather not factory refresh, however will do that if there re no other suggestions to try.
PS. I've also got a Fire Stick not rooted with latest firmware that works as expected, so shows there are no network reasons for it to not work on the FireTV
Click to expand...
Click to collapse
You can try both forgetting the Wifi info & logging out & in of your Amazon Account.
Also restart your modem & router. And make sure you turned off both Featured Content.
Any chance you tried to debloat your device?
Guess you can try reflasing the PreRooted ROM without doing a Factory Reset. Only the same Dalvik & Cache. You would keep the same Apps installed. But you probably still need to reinstall the XPosed Framework. And update SuperSU. From what I remember.
After trying a number of different things I ended up performing a factory refresh following the guide from aftvnews
After doing that, blocking updates, re-installing the su sdcard patch, and then all my apps and settings everything is working as expected.
Thanks for all the suggestions. Happy to have everything back to normal again.
fionn.colvin said:
After trying a number of different things I ended up performing a factory refresh following the guide from aftvnews
After doing that, blocking updates, re-installing the su sdcard patch, and then all my apps and settings everything is working as expected.
Thanks for all the suggestions. Happy to have everything back to normal again.
Click to expand...
Click to collapse
Glad to hear everything has been resolved. :good:
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