Hey guys. I have a 2nd gen fire TV. There are 518 megabytes of 5.6 GB of storage available. The software version is fire OS 5.2.9.3(684782320). I have a memory card in the back of the fire TV, and I have moved every single app to that memory card. The thing is still almost out of storage. I have no idea where I can check to see what actually makes up all of the items that are supposedly filling this storage. All we use this for is for watching TV. If you can put pictures or anything on a fire TV we certainly do not have any of that. This has been an ongoing issue for about 3 years. I usually clear the cache and I am able to get the warning messages to go away. Last week I move more apps over to the memory card so that every single app is located on it. I cleared the apps cache. Now the warning messages are coming up more and more frequently, the fire TV is rebooting more often, and it is notably slower. The issue is getting to a point where it needs to be fixed. Since I have no idea what is taking up all of the storage, I'm kind of at a loss except to factory reset the thing, and I certainly do not want to do that. How do I see what is making up all of the storage space and how do I clear it? Do I need to download a third party app?
EDIT: I finally got some hits on this issue when I started searching more and more with. "XDA" in the Google search. I also started to get some hits on Reddit. Here is a short summary of what I have read. The culprit is on Reddit
It's a file called mbcache.db that's the problem. It's located here /data/data/com.amazon.tv.launcher/ databases/mbcache.db
Do I need to root my fire TV to be able to access directories and delete files? That's a bunch of crap. Is there a work around to access this stuff today in 2022? Last mention of this issue on any forum is a few years old.
Edit #2: ES file explorer on Amazon is $9.99/month? Are they high? What could you possibly do with ES file explorer to get $9.99 /month value unless you are a developer?
You can't access that directory without root but you can clear it to delete any accumulation of data. It's completely safe (equivalent of clear storage), just run this ADB command:
Code:
pm clear com.amazon.tv.launcher
Check your available space before and after running this command to see if that's where your space has actually gone.
You might also want to download a file manager like Total Commander (free in app store) or MiXplorer and manually check the folders to make sure you don't have any junk in your Download folder, Downloader (if you use that app) folder, or any other folders left behind by old and uninstalled apps in your main storage area.
Finnzz said:
You can't access that directory without root but you can clear it to delete any accumulation of data. It's completely safe (equivalent of clear storage), just run this ADB command:
Code:
pm clear com.amazon.tv.launcher
Check your available space before and after running this command to see if that's where your space has actually gone.
You might also want to download a file manager like Total Commander (free in app store) or MiXplorer and manually check the folders to make sure you don't have any junk in your Download folder, Downloader (if you use that app) folder, or any other folders left behind by old and uninstalled apps in your main storage area.
Click to expand...
Click to collapse
Thanks for the reply. So that command will clear the mbcache.db? Does mixplorer have to be adb pushed to the firetv? I'll have to look later if it's in the app store on Amazon.
Schroeder09 said:
Thanks for the reply. So that command will clear the mbcache.db? Does mixplorer have to be adb pushed to the firetv? I'll have to look later if it's in the app store on Amazon.
Click to expand...
Click to collapse
Yes the clear command deletes all the user data for the Amazon Launcher (com.amazon.tv.launcher), including any database files like mbcache.db. It's not harmful so feel free to clear whenever you like, the Launcher just rebuilds/reloads it over time.
Yes MiXplorer has to be sideloaded, it's not in the Amazon App store but Total Commander is.
Finnzz said:
Yes the clear command deletes all the user data for the Amazon Launcher (com.amazon.tv.launcher), including any database files like mbcache.db. It's not harmful so feel free to clear whenever you like, the Launcher just rebuilds/reloads it over time.
Yes MiXplorer has to be sideloaded, it's not in the Amazon App store but Total Commander is.
Click to expand...
Click to collapse
I'm going to try these as commands later tonight. I'm sure I could just look this up on Google, but is issuing commands to a firetv just like issuing them to a phone?
1.) In platform tools folder issue .\adb devices, .\adb reboot bootloader, then issue your command?
Does having mixplorer help much with this particular issue or will clearing these things require root access?
Granted I haven't had time to do deep searches, the last rooting attempts I saw online for a gen 2 firetv were a couple years old with notes that the root access wouldn't persist through a reboot.
Yes the ADB command line is the same on FireTV and Android. The easiest way to run ADB commands is to install Remote ADB Shell on an Android phone/tablet, and connect to the FireTV over WiFi.
Remote ADB Shell - Apps on Google Play
Connect to ADB running on another Android device over the network
play.google.com
If you prefer you can use a computer to connect to the command line (ADB connect <IP of FireTV>)
Having a file manager app will let you see any files that user apps downloaded, or that you uploaded. You won't be able to see system app data without root, but you can still use the clear command to delete their data.
If it's the 2nd gen Stick (Tank), there's this:
[UNLOCK][ROOT][TWRP][UNBRICK] Fire TV Stick 2nd gen (tank)
Read this whole guide before starting. This is for the 2nd gen Fire TV Stick (tank) Current relase: amonet-tank-v1.2.2.zip NOTE: Recent reports indicate a change that disables brom DL-mode The change seems to have been introduced with devices...
forum.xda-developers.com
If it's the FireTV 2 box (Sloane):
[UNLOCK][ROOT][TWRP][UNBRICK] FireTV 2 (sloane)
Read this whole guide before starting. This is for the 2nd gen Fire TV (sloane) Current relase: amonet-sloane-v1.1 NOTE: This process does not require you to open your device if you're already rooted or you have TWRP. NOTE: If something goes...
forum.xda-developers.com
Finnzz said:
Yes the ADB command line is the same on FireTV and Android. The easiest way to run ADB commands is to install Remote ADB Shell on an Android phone/tablet, and connect to the FireTV over WiFi.
Remote ADB Shell - Apps on Google Play
Connect to ADB running on another Android device over the network
play.google.com
If you prefer you can use a computer to connect to the command line (ADB connect <IP of FireTV>)
Having a file manager app will let you see any files that user apps downloaded, or that you uploaded. You won't be able to see system app data without root, but you can still use the clear command to delete their data.
If it's the 2nd gen Stick (Tank), there's this:
[UNLOCK][ROOT][TWRP][UNBRICK] Fire TV Stick 2nd gen (tank)
Read this whole guide before starting. This is for the 2nd gen Fire TV Stick (tank) Current relase: amonet-tank-v1.2.2.zip NOTE: Recent reports indicate a change that disables brom DL-mode The change seems to have been introduced with devices...
forum.xda-developers.com
If it's the FireTV 2 box (Sloane):
[UNLOCK][ROOT][TWRP][UNBRICK] FireTV 2 (sloane)
Read this whole guide before starting. This is for the 2nd gen Fire TV (sloane) Current relase: amonet-sloane-v1.1 NOTE: This process does not require you to open your device if you're already rooted or you have TWRP. NOTE: If something goes...
forum.xda-developers.com
Click to expand...
Click to collapse
I used the above advice and issued the commands from my PC. I didn't download the app to my phone. I was able to connect with ADB over wifi. Issuing your command ( with the addition of "adb PM" or something like that added to the front) gave me a message in the PowerShell that said "successful" almost immediately upon issuing the command. However, the storage didn't change by a single MB. I then downloaded file commander on the Amazon firetv and saw all the different apps' package names. I said the same command you listed for the launcher for each of these different apps. After doing 95% of the apps the storage dropped by about 100MB.
What is there left to do? File commander lets me see all the different file says even if I can't delete a lot of them, and none of them are that large. I'm at a loss on this? There are discussions about this topic all over the internet. The only thing to do is to factory reset or root and manually delete files? That seems absurd. What was Amazon thinking? Rotting kinda defeats the point of the whole investigation anyway. I didn't wanna have to wipe the fire TV and start all over. I don't have all that time. For $100-$130 I'll just get the Amazon cube TV thing. Are these gen 2 fire tvs really this unserviceable?
If you open a shell prompt you will get more output, in case there are any errors running a command. But it sounds like it ran fine.
Code:
ADB connect <fireTV IP address>
ADB shell
Now you should be at the FireTV's shell prompt.
Check your user storage
Code:
cd /sdcard
du -hs */ | sort -nr | head
This will list all your user folders and their size and give you an idea if there is any trash you can delete.
The other primary area that uses up space is /data/data where app data and cache is stored but you can't traverse that directory without root. So I'm not sure how you can see how much space is being used by system apps there.
Factory reset of course is an option.
It's getting harder to run a device on 8GB, as apps themselves grow in size as well as their cache and storage requirements.
My personal bias is that the 2nd gen Cube for $60 on sale is still the best bang for your buck. It comes with 12.9GB of usable space vs 5.6GB on the sticks. And is the fastest AndroidTV (FireOS) box you can get at that price and that can stream from all the major streaming apps.
Related
What's the fastest way to install KODI & Firestarter? I'm using abdfire for everything, however, the whole process takes too long.
Any ideas? Also, is there a way to bypass the Amazon login portion.
If you take the time to figure out how to connect to the device via ADB, and put the files you want to install (eg kodi.apk, starter.apk) in the same directory as adb.exe, installing both can be done in about a minute. First on the FireTV > Settings > System > Developer Options, enable ADB Debugging and Apps from Unknown Sources.
Next start a command prompt in the adb.exe directory (Shift+right-click in the directory and select "Open command window here"). Execute commands:
Code:
adb connect 192.168.1.2
adb install -r kodi.apk
adb install -r starter.apk
Skip the -r if this is a fresh install rather than a re-install or update. To get your device's local IP address, go to Settings > System > About > Network and look at the first line
I don't know whether you can bypass logging into Amazon. What happens if you boot the device without internet access?
Patrick_445 said:
If you take the time to figure out how to connect to the device via ADB, and put the files you want to install (eg kodi.apk, starter.apk) in the same directory as adb.exe, installing both can be done in about a minute. First on the FireTV > Settings > System > Developer Options, enable ADB Debugging and Apps from Unknown Sources.
Next start a command prompt in the adb.exe directory (Shift+right-click in the directory and select "Open command window here"). Execute commands:
Code:
adb connect 192.168.1.2
adb install -r kodi.apk
adb install -r starter.apk
Skip the -r if this is a fresh install rather than a re-install or update. To get your device's local IP address, go to Settings > System > About > Network and look at the first line
I don't know whether you can bypass logging into Amazon. What happens if you boot the device without internet access?
Click to expand...
Click to collapse
Awesome, thanks! If I were to drop my backup folder into the same directory as adb.exe and run
adb install backup.folder
Do you think that would work? I'm at work & cant test it myself just yet.
Also, about the logging into Amazon part, I don't think you can bypass it because you need to enable ADB Debugging and Apps from Unknown Sources.
UNLESS, you can enable it somehow without logging in or correcting to the interest...
The backup folder would have to be pushed to the correct directory
Android\data\org.xbmc.kodi\files\
Sent from my iPhone using Tapatalk
Agk fire is another good tool that you can use...
Sent from my LGLS991 using Tapatalk
The adbfire GUI does this perfectly. I've got it down to a 15 min process from stock to modified inc add-ons etc. I'd recommend hardwiring the computer you run adbfire on, and have the firestick as close to the router as possible (or hardwire if it's a FTV.) If the add-ons arnt a big deal, you can have Kodi and Firestarter done within 10mins using the GUI. Anyway, restore process that works best for me is:
-Connect Firestick to WiFi, log in, enable adb debugging and unknown apps.
-Get IP from Settings>About>Network
(The rest can be done from a PC now.)
-Load adbfire GUI, connect using IP found above.
-Install APK (select the Kodi apk.)
-Install Firestarter using the button provided.
-Click 'Restore' and select backup taken using 'Backup' from a previously modded Firestick (with all the add-ons/build you prefer.)
-This can take between 15min and 1 hour depending on your connections to router (what I mentioned above about hard wire etc) and also the size of the backup. My build is over 1GB, hardwired PC with Firestick 3 feet from the router, it takes me 13min to restore.
Personally this took my install time down from ~2 hours to 15minutes, mainly because the build I prefer is so large and takes a lot of tweaking to get going (however once I had it sorted, taking a backup means newly-restored devices are 100% ready when the backup process is done.)
I've spent more time on this than I'd like to admit but I got sick of spending 2hours and headaches each and every time!
Lol. said:
Personally this took my install time down from ~2 hours to 15minutes, mainly because the build I prefer is so large and takes a lot of tweaking to get going (however once I had it sorted, taking a backup means newly-restored devices are 100% ready when the backup process is done.)
Click to expand...
Click to collapse
Why is your build so large? do you install other apps besides Kodi? Which addons do you use?
For those with a slow connection who are trying to build a FireTV (not the Stick), it might be faster to place the kodi backup on a microSD plugged into the device and move the directory from there to the Kodi userdata directory instead of trying to move it from a computer over Wifi.
The way i did it was...
1) Installed ES File Explorer
2) Installed Firestarter using ES File Explorer
3) Installed latest stable version of Kodi from FireStarter
4) Used Fusion/Wizard to install popular Add-ons (TVMC)
extremely easy
Patrick_445 said:
Why is your build so large? do you install other apps besides Kodi? Which addons do you use?
For those with a slow connection who are trying to build a FireTV (not the Stick), it might be faster to place the kodi backup on a microSD plugged into the device and move the directory from there to the Kodi userdata directory instead of trying to move it from a computer over Wifi.
Click to expand...
Click to collapse
Andy's build v7 - it's impressive - but a pain in the ass to get working (i4atv updated last week causing major headaches.) The latter is what led me down the backup/restore route.
Lol. said:
The adbfire GUI does this perfectly. I've got it down to a 15 min process from stock to modified inc add-ons etc. I'd recommend hardwiring the computer you run adbfire on, and have the firestick as close to the router as possible (or hardwire if it's a FTV.) If the add-ons arnt a big deal, you can have Kodi and Firestarter done within 10mins using the GUI. Anyway, restore process that works best for me is:
-Connect Firestick to WiFi, log in, enable adb debugging and unknown apps.
-Get IP from Settings>About>Network
(The rest can be done from a PC now.)
-Load adbfire GUI, connect using IP found above.
-Install APK (select the Kodi apk.)
-Install Firestarter using the button provided.
-Click 'Restore' and select backup taken using 'Backup' from a previously modded Firestick (with all the add-ons/build you prefer.)
-This can take between 15min and 1 hour depending on your connections to router (what I mentioned above about hard wire etc) and also the size of the backup. My build is over 1GB, hardwired PC with Firestick 3 feet from the router, it takes me 13min to restore.
Personally this took my install time down from ~2 hours to 15minutes, mainly because the build I prefer is so large and takes a lot of tweaking to get going (however once I had it sorted, taking a backup means newly-restored devices are 100% ready when the backup process is done.)
I've spent more time on this than I'd like to admit but I got sick of spending 2hours and headaches each and every time!
Click to expand...
Click to collapse
If I start jailbreaking these and selling them on Craigslist, should I be worried about Amazon suspending my email / account for using the same IP or email too many times?
vurze said:
If I start jailbreaking these and selling them on Craigslist, should I be worried about Amazon suspending my email / account for using the same IP or email too many times?
Click to expand...
Click to collapse
Well for a start, jailbreaking is not the right term here, lets leave that to iOS
Secondly, I'm not in the best position to advise, I don't sell these, I simply have a few and didn't want to spend hours sorting them all out once an update or a different build is released. I would suggest you do NOT use your personal Amazon account if you plan to do this though, it's not worth the risk. Perhaps look into creating a different one...
vurze said:
If I start jailbreaking these and selling them on Craigslist, should I be worried about Amazon suspending my email / account for using the same IP or email too many times?
Click to expand...
Click to collapse
gee.. how did I know the OP question was for this reason....
As stated in a previous post, I avoid adb all together and use ES Explorer to download Kodi apk and FireStarter Apk and then use Fusion Config Wizard for most popular add-ons.. I can get this all done under 10 minutes a stick.. On Black Friday and Cyber Monday I purchased 100 Firesticks for $2500 ($25/piece sale) (purchased in Delaware to avoid sale tax) and have been selling them side loaded with Kodi for $80-$100. Let's just say it's going to be a good Christmas. The market is saturated with these (Craigslist, eBay) I usually sell by word of mouth and I even have a few store owners who bought 5 at a discount.
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 an old Gen 1 firestick that has latest kodi on it and an iptv service as well as some other addons, and all works fine allbeit slow sometimes, so i upgraded to the latest and great 4k version with all it's audio spying gumf, however if i remember rightly there was a "fair" bit involved in getting to the stage to allow kodi to go on and run the add ons, is this still the case with the 4k version because all the links i have seen point to something called "Aptoide TV and this seem to allow you to run kodi and stuff like that but it also seems a gateway to other add ons and i don't want that i just to root/jailbreak the stick throw kodi on and install the addons i know i like or just instal kodi and away you go which in my simple mind means no jailbreaking is needed is it that simple nowadays?
Aptoide is just a 3rd party app store
There's two ways you can get any app onto a firestick that I use
1 - adb via pc
2 - adb via app on phone
If using option one download app to pc & also get adb set up (there's loads of guides about adb so Google that)
Enable adb on the firestick in dev options
Note down the ip address of the firestick from about device section
In a command prompt on pc type
adb connect ip_of_firestick
adb devices
adb install nameofapp.apk
For option two
Download app to phone
Download apps2fire from playstore
Enable adb on firestick in dev options
Note down firestick ip addres
Enter firestick ip address in apps2fire settings
Select arrow at top to install app
Navigate to where apk is
Note that apps2fire may fail on first connection - just connect again & it should work
Hello!
Do you know how to backup & restore the settings of apps that are installed on a Fire TV stick 4K?
I have SuperTuxKart and 2 other games on that device and need to reset it. In order not to lose the kids' playing progress (* cough, cough *), I would like to backup the settings of these games, including (hopefully) also the playing progress.
This stick is not rooted, and I do not want to root it.
Thanks for any helpful hints!
PS:
I am now looking into Oandbackup, available from F-Droid. Well, it needs 'su', so without root, no backup.
I have access via adb. But as I have no clue, where the games' settings are placed, this will be complicated.
Without root.
adb backup -f myapp.ab -apk com.myapp
# backup on one device
adb restore myapp.ab
adb shell pm list packages -f
# to get the appname com.******
@0815hoffi
Great - thank you so much!
Slightly OT:
Despite I ticked the box to always allow adb connections via network from this device, the message pops up on the fire tv on every adb connection attempt (and the box is then always again un-ticked). Is there a way to allow this really permanently?
@0815hoffi
This does not seem to work. The backup command results in this message:
Code:
Now unlock your device and confirm the backup operation...
The start page of the fire tv is shown throughout this process, and I had given permission for the adb connection before.
Any hints what I am doing wrong or could do? Thanks once more!
Have you Turned on
“Apps from Unknown Sources”
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