Database Users

Permission issues with su and rom .3

Hey guys,
Im new to Android and after being a BlackBerry user for 8 years, anyway heres my issue.
1. I did the root rom per the instructions...no problem
2. flashed the recovery and have that working...no problem
3. downloaded the .3 rom with the built in busybox and su...Here's where things get confussing for me.
I tried to use adb and it asks me (are you root?), tried adb remount and got (operation not permitted) the usb debug is on and working and the su app on the phone maintains a black screen....(I think this is not right...)
Then I closed out the current cmd window...opened a fresh cmd window and typed>adb shell and got $, then i entered su and got # from here im stuck, what are the commands to get back to adb shell and su also how do I get the whitelist permissions working...
In short adb shell worked fine with the original root rom, I'm sure its an operator error any help is appreciated.
Chris

SO if I understood correctly you already have v3 installed?
If you do check on your phone its probably asking you for permission on the phone when you click on always allow the command should go thru adb.
make sure you have debuggin on otherwise all you will get is a black screen when su permission pops up.

t2noob said:
SO if I understood correctly you already have v3 installed?
If you do check on your phone its probably asking you for permission on the phone when you click on always allow the command should go thru adb.
make sure you have debuggin on otherwise all you will get is a black screen when su permission pops up.
Click to expand...
Click to collapse
can you guys post a walk through for noobies? imstuckat black screen

vash8806 said:
can you guys post a walk through for noobies? imstuckat black screen
Click to expand...
Click to collapse
There are plenty around... seriously google it. But, this specific issue I just experienced. Seems on the custom ROM that is out (EvilEris) the SU request screen doesn't work right off the bat. I went and used an app on the device to request root (terminal) then when the black screen pops up, hit back or home, or action. As the phone is basically frozen at this point it prompted me to forceclose the superuser.apk. I did. Once forceclosed, it worked fine.

adb shell
su
look at phone, click allways all
...
..
.
jcase

jcase said:
adb shell
su
look at phone, click allways all
...
..
.
jcase
Click to expand...
Click to collapse
Or just download Terminal Emulator from Market.
open it up.
Type su.
Hit allow/always allow.
Now try it for other stuff (like wireless tether) and see if it pops up instead of a black screen.

haha..I simply went to settings>Applications>Development and checked the USB debugging mode.... [read it on another thread...should have read before I posted...haha]

vash8806 said:
haha..I simply went to settings>Applications>Development and checked the USB debugging mode.... [read it on another thread...should have read before I posted...haha]
Click to expand...
Click to collapse
niiiice

Rooted Nook Question

So I rooted my nook and everything was working fine, I powered it off and when I went to power it back on it's stuck on the book screen that says "nook c" or whatever in different colors.
Update: It actually stops at "nook c" when it's suppose to spell out "nook color" -____-

Could you detail what you were doing before you shut down? Installing anything, reinstalling from Titanium Backup, etc.
Are you using the stock ROM? Are you able to see the device with adb when you boot up (just use "adb devices" in a command prompt and see if the device name comes up)? If so, you might want to check the system logs. You can use "adb logcat" to see a few lines, or write to file with "adb logcat > logcat.txt" and view with a regular text viewer. You'll probably have to cut it off that command after a few seconds (with Ctrl+c) as the log file tends to be big. You could try posting any errors from the logcat file.

bluebear13 said:
Could you detail what you were doing before you shut down? Installing anything, reinstalling from Titanium Backup, etc.
Are you using the stock ROM? Are you able to see the device with adb when you boot up (just use "adb devices" in a command prompt and see if the device name comes up)? If so, you might want to check the system logs. You can use "adb logcat" to see a few lines, or write to file with "adb logcat > logcat.txt" and view with a regular text viewer. You'll probably have to cut it off that command after a few seconds (with Ctrl+c) as the log file tends to be big. You could try posting any errors from the logcat file.
Click to expand...
Click to collapse
I don't know what you mean by "am I able to see the device with adb? Well I ended up just doing a three finger reset and so now it's not rooted but I will try to root once again when I'm home and see how that goes I originally wanted honeycomb. Do I have to root and then flash honeycomb?

tamaramarrero said:
I don't know what you mean by "am I able to see the device with adb?
Click to expand...
Click to collapse
If you connect the Nook to your computer and run "adb devices" in a command prompt (from the sdk platform-tools folder), your Nook should be identified if it's still alive and running processes. It's a nice way to check if you're running into startup issues or if the thing just froze. Since you're starting over, I guess I won't detail this further. Have you gotten adb running? If not, you might want to consider it if you're playing with root. Have you been following the nookdevs website (http://nookdevs.com/Portal:NookColor)? There's a lot of detail there and good instructions on all this as well.
tamaramarrero said:
Do I have to root and then flash honeycomb?
Click to expand...
Click to collapse
You don't need root to flash a new ROM; you just need an unsecured bootloader, which the Nook has. I've only ever tried honeycomb from an unstable developer build a few months back booting from an SD card. Has anyone gotten honeycomb 3.2 compiled for Nook? CyanogenMod7 is a stable build of gingerbread. I'm running that now, and it's quite nice. I even like the Nook app better than the stock Nook experience, especially since it started supporting magazines.

I originally wanted honeycomb.
Click to expand...
Click to collapse
Then I suggest that you get a different tablet with it pre-installed from the factory. Google has not and will not release the source code so there is no bug free version for you to install. Gingerbread (CM7) is your best option. If you really like the look of Honeycomb you can later install a Honeycomb looking theme.

[Support Thread] ArchLinux on the TF300T(G)

Hi everyone,
If you have any questions relating to Arch on the TF300, please post them here and not in the dev thread
I'll do my best (as well as others, I'm sure) to answer them, but bear in mind that you should have some basic Linux knowledge before flashing!

this is awesome!
cb22 said:
Hi everyone,
If you have any questions relating to Arch on the TF300, please post them here and not in the dev thread
I'll do my best (as well as others, I'm sure) to answer them, but bear in mind that you should have some basic Linux knowledge before flashing!
Click to expand...
Click to collapse
I can't thank you enough for this, it's been fantastic so far! I only have a few questions, as I am extremely new to arch linux...as in this is the first time I've used anything aside from debian in the linux world.
To start, how would we go about changing DE's? I've downloaded a couple, but i get errors every time i try to start one saying that another window manager is already running. With ubuntu one just logged out and chose from the log in screen, but there doesn't appear to be a log out process for this, i get a black screen every time i do. Other than that, are there any general programs/settings/tweaks that you would suggest applying? While this is very nice, it still seems to be missing some basic functions, such as putting the screen to sleep and having a set system time.
Despite all of that, this has breathed new life into my tablet, you're doing fantastic work and I hope you only continue to make it more amazing!

fankuan19 said:
To start, how would we go about changing DE's? I've downloaded a couple, but i get errors every time i try to start one saying that another window manager is already running. With ubuntu one just logged out and chose from the log in screen, but there doesn't appear to be a log out process for this, i get a black screen every time i do. Other than that, are there any general programs/settings/tweaks that you would suggest applying? While this is very nice, it still seems to be missing some basic functions, such as putting the screen to sleep and having a set system time.
Click to expand...
Click to collapse
Take a look at the .xinitrc file in the home directory. It's a hidden file so you may need to "show hidden" or give an editor the full path (/home/user/.xinitrc)
The file runs the following by default:
Code:
exec startxfce4 --with-ck-launch
You can change everything after `exec` to the script for a different DE, such as `startkde`. If you don't know the command, there should be a list of session templates in /usr/share/xsessions/. Inside each .desktop file there's an "Exec=" line, everything after that is the command to sub in.
My crappy bash skills threw together a quick command to get a list of installed xsessions:
Code:
grep "Exec=" /usr/share/xsessions/*.desktop | sed -E 's/^Exec=(.+)$/\1/'
The output on the default rootfs will just be "startxfce4". If you have KDE another line should output "startkde", and so on. Put the command in your .xinitrc (making sure to replace the current one) and then reboot as there's no proper way to log out.

whoops
timothyb89 said:
Take a look at the .xinitrc file in the home directory. It's a hidden file so you may need to "show hidden" or give an editor the full path (/home/user/.xinitrc)
The file runs the following by default:
Code:
exec startxfce4 --with-ck-launch
You can change everything after `exec` to the script for a different DE, such as `startkde`. If you don't know the command, there should be a list of session templates in /usr/share/xsessions/. Inside each .desktop file there's an "Exec=" line, everything after that is the command to sub in.
My crappy bash skills threw together a quick command to get a list of installed xsessions:
Code:
grep "Exec=" /usr/share/xsessions/*.desktop | sed -E 's/^Exec=(.+)$/\1/'
The output on the default rootfs will just be "startxfce4". If you have KDE another line should output "startkde", and so on. Put the command in your .xinitrc (making sure to replace the current one) and then reboot as there's no proper way to log out.
Click to expand...
Click to collapse
First of all, thanks for the help! Unfortunately, I appear to have done something incorrectly, as the Linux partition will no longer boot. That code didn't return anything but a ">", although as I type this i realize I may have needed to be root...haha, regardless, I tried to edit the .xinitrc file with "exec /bin/usr/startlxde", which is what was after "exec=" in the xsessions directory, nothing happened after waiting quite a while after boot.
I suppose I'll have to reflash the entire partition, considering i can't access the filesystems to change it back. Ah, the wonders of linux!

Sorry if I repeat my question,but how can i activate the keyboard without using a pc with linux ?

fankuan19 said:
First of all, thanks for the help! Unfortunately, I appear to have done something incorrectly, as the Linux partition will no longer boot. That code didn't return anything but a ">", although as I type this i realize I may have needed to be root...haha, regardless, I tried to edit the .xinitrc file with "exec /bin/usr/startlxde", which is what was after "exec=" in the xsessions directory, nothing happened after waiting quite a while after boot.
I suppose I'll have to reflash the entire partition, considering i can't access the filesystems to change it back. Ah, the wonders of linux!
Click to expand...
Click to collapse
You should be able to gain access easily via Recovery. Just adb shell in, mount /dev/mmcblk0p8 /mnt and look in /mnt/linux - that's your root file system...
Razorbacktrack5535 said:
Sorry if I repeat my question,but how can i activate the keyboard without using a pc with linux ?
Click to expand...
Click to collapse
Without using a PC... Hmm, that could be tricky. If you're in Android, and you add this line to the top of /data/linux/home/user/.xinitrc
Code:
maliit-server &
(before the exec line)
It should give you the virtual keyboard when you restart into Linux.

cb22 said:
You should be able to gain access easily via Recovery. Just adb shell in, mount /dev/mmcblk0p8 /mnt and look in /mnt/linux - that's your root file system...
Click to expand...
Click to collapse
I was actually able to just use the terminal emulator in android to navigate back to the .xinitrc file, turns out i wasn't supposed to leave the "--with-yadda-yadda" bit, so i got lxde working...and as it turns out, i don't like it nearly as much as the DE you included, so i'll be switching back to that!

First off: thank you SO much for your hard work at this! My tab has never browsed the web this well. It's better than the desktop I'm sitting next to. Arch is amazing!
Just a few questions. Do we have basic tab controls yet? I'm looking for, specifically:
Brightness Control
Enable/Disable Touchpad
Volume Control
Sleep/Suspend/Hibernate
Especially that last one! As far as I can tell, if I'm not going to use the tab for more than a couple minutes, it's apparently best to shut it down or reboot back into Android so it can "sleep". Or plug it in. I know we're rough around the edges yet, but is this stuff in, or no?

koiulpoi said:
First off: thank you SO much for your hard work at this! My tab has never browsed the web this well. It's better than the desktop I'm sitting next to. Arch is amazing!
Just a few questions. Do we have basic tab controls yet? I'm looking for, specifically:
Brightness Control
Enable/Disable Touchpad
Volume Control
Sleep/Suspend/Hibernate
Especially that last one! As far as I can tell, if I'm not going to use the tab for more than a couple minutes, it's apparently best to shut it down or reboot back into Android so it can "sleep". Or plug it in. I know we're rough around the edges yet, but is this stuff in, or no?
Click to expand...
Click to collapse
I don't think sleep/suspend/hibernate is implemented at all quite yet. The backlight seems to turn off completely when the screen times out though so you can fake having a low power mode, though obviously true sleep would be nice.
As for volume control, use pavucontrol. You may need to install it with `pacman -S pavucontrol`.
For brightness ... there's no good way to do this as far as I can tell. XFCE has a brightness control applet you can add to the bottom panel but it doesn't seem to work, and most of the usual packages (e.g. xbacklight, etc) don't detect the backlight device. Oddly enough I gave e17 a try and its builtin brightness applet worked fine, I wonder what they do differently ...
At any rate you can control it manually: the file /sys/class/backlight/pwm-backlight/brightness has a 0-255 value which controls the screen brightness. Note that you need to run the echo command as root
Code:
# echo "1" > /sys/class/backlight/pwm-backlight/brightness # minimum brightness
# echo "255" > /sys/class/backlight/pwm-backlight/brightness # maximum brightness
# echo "0" > /sys/class/backlight/pwm-backlight/brightness # completely turns off backlight. use with care
Setting it to zero makes it next to impossible to see the screen. I ended up having to ssh into the device (or reboot) to get it back.

I modified the file through a PC and It works ! Thanks, no problems with wifi

Sleep / Suspend isn't implemented yet.
But, I did a bit of testing, and the TF should last for about ~40 hours with the screen off, and the processor in the Low Power mode (which it does automatically. Obviously, it's still wasteful compared to proper suspend, but it's not too bad.

Really liking this so far, other than managing to break wifi once, which I fixed by doing a quick re(install I guess is the proper term). Any chance of a future release having SLiM or something setup out of the box(I'd do it but looking at some of the guides, we are missing some files(?) :s) either that or is there a way to autologin a new user other than the default one named user?
(edit for more info) I've tried following a guide I found on the arch wiki which had me modify [email protected], but it didn't boot so I had to edit it back to the default.
Thanks for all your work cb22, and thanks for taking my advice and switching file hosts

This may be a dumb question
But I can't for the life of me find out how to flash the hybridkernel.blob, I've already done every other thing, but i'm lost as to what to do there. Can I get a bit of guidance please?
:Nevermind: Silly me forgot to go to fastboot, I was trying to do it with adb, for any others though, reboot to fastboot on your tf300t and then run go to the location of fastboot on your pc and hold shift and right click and select open comand line here. Then move the hybridkernel.blob to the same location as the fastboot and run fastboot -i 0x0B05 flash staging blob

Shingaling said:
But I can't for the life of me find out how to flash the hybridkernel.blob, I've already done every other thing, but i'm lost as to what to do there. Can I get a bit of guidance please?
:Nevermind: Silly me forgot to go to fastboot, I was trying to do it with adb, for any others though, reboot to fastboot on your tf300t and then run go to the location of fastboot on your pc and hold shift and right click and select open comand line here. Then move the hybridkernel.blob to the same location as the fastboot and run fastboot -i 0x0B05 flash staging blob
Click to expand...
Click to collapse
Disregard, didn't see the edit until after you posted essentially the same thing I did.

So, does Adobe Flash support work at all in Chromium? I haven't gotten it to recognize the plugin at all. Any way to get this working, or is it just gonna keep bugging me to install it?

koiulpoi said:
So, does Adobe Flash support work at all in Chromium? I haven't gotten it to recognize the plugin at all. Any way to get this working, or is it just gonna keep bugging me to install it?
Click to expand...
Click to collapse
I don't think it works at all, I've tried every permutation sudo pacman -S flash-plugin that I could think of and I've gotten notwhere.

They is no flash for ARM for pure Linux.
Wysyłane z mojego ASUS Transformer Pad TF300T za pomocą Tapatalk 2

Itege said:
Any chance of a future release having SLiM or something setup out of the box(I'd do it but looking at some of the guides, we are missing some files(?) :s) either that or is there a way to autologin a new user other than the default one named user?
(edit for more info) I've tried following a guide I found on the arch wiki which had me modify [email protected], but it didn't boot so I had to edit it back to the default.
Click to expand...
Click to collapse
In theory you should be able to install a proper display manager without too many issues:
Code:
# pacman -S lightdm lightdm-gtk-greeter
# systemctl enable lightdm
...though when I tried this the DM would never actually be run. I was able to run it manually over SSH without issues (both lightdm and slim worked, more or less). I'm in the process of investigating why it isn't run at startup like it should be, whatever the issue is doesn't seem to be related to the display manager itself.

I have an issue with wifi.
1: The WLAN do not find any Network with Channel 12 or 13.. I think I must change the region in germany, but where?
2. The WLAN do not connect, they search for an network adress and after 30seconds they ask for wlan key again.. the key is correct and my router shows the connection.. but archlinux means the key is wrong.. testet with router und smartphone wlan hotspot..
3. 3G not connecting, i have create a profile for BASE Germany, but they do not connect.
UPDATE:
for 2: Sometimes they connect and I can surf. But the ping are more then 600ms.. After few seconds the connection lost, sometimes they connect again, sometimes say ask for wlan key again.
Maybe you can help me. Sorry for my bad english.
Yours Sincelery
Robert

Could any of you guys find out if you have a process running in "interruptible" state named "kinteractive_lo"?
You can check that using "top" in CLI or installing gnome-system-monitor. I guess the standard xfce task manager works as well.
It's driving me nuts and I believe is one of the reasons why I have to hard-reboot my tablet, since invoking reboot with --force works perfectly.
Thanks in advance!

Customizing the Fire TV Stick 4K (mantis) - Debloat - Replace launcher and Testing

EDIT (12/08/22): Parts of this guide may be out of date, it hasn't been updated since December 2019.
TL; DR Version in the second post, it's also a short overall summary. Might be best to have a look so you don't get overwhelmed by this first post.
Just thought I would share my experience with the 4K. Just as an FYI this is my first firestick and I've only had it for about a week but I've been playing with it quite a bit.
Personally I'm interested in removing all amazon related products/apps/services etc. With the exception of the store as I would like to get some of my apps through it.
Making it as lean and fast as possible.
Getting as close to AndroidTV as possible without losing any functionally and keeping stability.
I'm primarily interested in Plex and/or Kodi (with no addon apps, just vanilla kodi).
Having root. I like to have the ability to do anything, and I personally found rooting the stick easy so I found no reason not to do it. With that in mind everything I did I had root. I have no idea if any of these steps work without root.
Pre info
I chose to not flash the Prerooted Stock Image due to the comment Sus_i made here. I updated, then rooted.
EDIT (12/08/22): Updating before rooting is no longer recommended.
Step1
Plug it in, run through the setup and let it update. Go to settings -> My Fire TV -> Developer Options and enable ADB Debugging and Apps from Unknown Sources.
Step 2
Root it!
Guide here
This guide/post was helpful also. There is a good video of them opening up the firestick to access the necessary point to short/ground to allow the root script to work. Just be careful with what you use. I just used a small copper wire.
After getting root. Put it back in the case. and plug it in to your tv.
Step 3
Running commands with adb
Get and install adblink, link here
Information on how to use it is on the site. You will need to get the IP address of the firestick. Go to setting -> device -> network -> about
open adblink
click adb shell
type
Code:
reboot recovery
then enter
You'll now be in TWRP
Step 4
Install Magisk
Get the latest stable magisk zip from here
No need for the Magisk Manager apk, that will get installed with the above zip.
Put the zip in the same folder that the adblink.exe is in. (you can find that by clicking adb shell in adb link and then typing exit, then enter. It will show you where you should put the zip file)
Open adblink if you closed it (just leave it open)
click adb shell
which should show the bellow on screen
Code:
mantis:/$
type exit
then paste the following (replace the "Magisk-v20.1.zip" with the correct name of the magisk zip you downloaded)
Code:
adb push Magisk-v20.1.zip /sdcard/
then type
Code:
adb shell
echo "--update_package=/sdcard/Magisk-v20.1.zip" > /cache/recovery/command
echo "--wipe_cache" >> /cache/recovery/command
reboot recovery
It will reboot and install magisk, then reboot to the launcher.
You can now check if you like if magisk is installed correctly and if you have root (you should)
Step 5
Install [Magisk][Module] FireTV 4K Stick Add-Ons
This gets rid of the amazon launcher and does a few other things, including installing xposed framework.
Follow the instructions in that thread. But here's some additional info. Which is just a copy of how we installed magisk.
Download and put the zip in the same folder that the adblink.exe is in.
Open adblink if you closed it (just leave it open)
click adb shell
which should show the bellow on screen
Code:
mantis:/$
type exit
then paste the following (replace the "AFTV-MM-1.9.zip" with the correct name of the AFTV-MM .zip you downloaded)
Code:
adb push AFTV-MM-1.9.zipp /sdcard/
then type
Code:
adb shell
echo "--update_package=/sdcard/AFTV-MM-1.9.zip" > /cache/recovery/command
echo "--wipe_cache" >> /cache/recovery/command
reboot recovery
It will reboot and install AFTV-MM, then reboot to the launcher. It does some things automatically on first boot and may reboot on it's own just let it do it's thing. Some additional commands need to be run via ADB, go to the thread and follow the instructions there: [Magisk][Module] FireTV 4K Stick Add-Ons
Step 6
Remove amazon bloat. *More info below*
Now I've seen a few lists here and there and tried to guess which things to disable on my own until I found these scripts.
Now these scripts weren't made for the 4k (mantis) firestick as you can see from the compatibility list. But I assumed the packages installed would be close so I'm guessing this isn't a bad starting point. But just remember this clearly wasn't meant for this device.
Download the script from here All credit for the original script goes to esc0rtd3w.
and put it in your adblink folder.
Open adblink if you closed it (just leave it open)
click adb shell
which should show the bellow on screen
Code:
mantis:/$
type exit
Code:
adb push bloat-disable.sh /sdcard/
then type
Code:
adb shell
su
cp /sdcard/bloat-disable.sh /data/local/tmp/
chmod 755 /data/local/tmp/bloat-disable.sh
sh /data/local/tmp/bloat-disable.sh
The script will then disable all the bloat. If you would like to enable all the bloat then use this script, download it and follow the same instruction from above. If you just need to enable a single app/service then you can run:
Code:
adb shell
su
pm enable com.amazon.dcp
replacing "com.amazon.dcp" with the app you want to enable.
Step 7
If you want Kodi as the launcher
You can get a modified apk here The thread where this came from originally is here Discussion of an update here
Side load the apk with adblink. Should be self explanatory, click install apk. Once installed open LauncherHijack and select Kodi as the launcher.
Step 8
Setting Kodi (or any other launcher) as the launcher
Install Launcher Hijack (Clone Mod), get the apk here
Follow the instructions here to install it and get it working. By now you should be getting comfortable with abdlink, use it to install the apks and run the adb shell commands.
Other apps to install
Smart Youtube TV (no ads)
OpenVPN install if you want or need it. In my case I need to slightly deviate from the guide. I simply didn't need to create the login.conf file. I Just copied opvn config over and then in settings chose "Certificates" for type and insert the password in "private key password".
That's it for now. I'm curious what other modifications can be done on the 4K (mantis). I'm thinking about/planning on trying a few I've seen around. I think as long as I can get back to TWRP then worse case I should be able to flash the stock ROM to recover. Would be interested to hear what other people may have pulled off.
*Step 6 more info*
This script will remove all packages that esc0rtd3w deemed safe to remove as of Fire OS 5.2.7.2 on the FireStick2. It will leave the amazon launcher enabled and allow use of the amazon app store. The amazon app store can also be disabled but disabling the amazon launcher breaks access to the settings.
My slightly edited version of his script
esc0rtd3w firestick-loader github. All credit for the script goes to him.
List of services/packages that are new for Fire OS 6.2.6.8
If anyone can inform me of the packages/services that can be safely disabled, please let me know and I can include them in the script. For now they are left untouched/enabled.
Info I found and used for this post
[UNLOCK][ROOT][TWRP][UNBRICK] Fire TV Stick 4K (mantis)
[Magisk][Module] FireTV 4K Stick Add-Ons
[FireTVStick4k] Updated Info November 2019
[NEWBIE GUIDE] How to Unlock Bootloader/Root and install Addons FireStick 4k
FireTV4k Stick: Achieving Root With Magisk
[LAUNCHER] XBMC/Kodi for Fire TV (Root)
Updated Kodi 18.5 version by the developer elmerohuesoWhich is posted here
Install OpenVPN on fireTV (no root required)
Running scripts on the Firestick, in this case the disable-bloat.sh script

This assumes you have an understanding of how to use adb and if more detail of any of the following steps is necessary then follow the steps in the first post.
Step 1
Plug it in, run through the setup and let it update. Enable ADB and Unknown Sources.
Step 2
Root it!
Guide here
Step 3
Get adb installed
Step 4
Install Magisk
Step 5
Install [Magisk][Module] FireTV 4K Stick Add-Ons
Step 6
Remove amazon bloat.
Download the script from here
Run on firestick via ADB
Step 7
If you want Kodi as the launcher, See the first post.
Step 8
Setting Kodi (or any other launcher) as the launcher, See the first post.
Step 9
Install other apps
OpenVPN install Seeing first post for more info
Smart Youtube TV (no ads)
Step 10
Other Tweaks
Stop firestick from going to sleep/returning to the home screen.

Things that don't work or I'm interested in trying to get working.
-Can't "install" apps from amazon. The app store is there and can install from "the cloud" but can't search for new apps. Likely due to something being disabled., just not sure what. I assume installing from amazon web into the cloud or something like that could be a work around. Might be that the only way to search for apps is with the default launcher?
-Voice search doesn't work. Looks like some people have kind of gotten it to work but I have not.
-Chromecast support.
Both would likely have a better chance if google play services/store could be installed. I see there was some effort put forth in trying to do that on previous firetvstick models so I may try some of the info that is out there. Seeing as we now have root its a lot more possible.....I assume.

reserved 1

reserved 2

I keep meaning to test nanodroid with microg & the patched play store. I've not done it yet as I was afraid patching the system would screw everything up & I had so much difficulty getting bootloader patched to begin with. It may not be necessary to patch system, I recall using an xposed module for spoofing some time ago on an old phone so that could be a possibility.
It might not work, but there's probably less that can go wrong as there's less "deep" system integration than using official gapps. Just an idea if you fancy trying it.

Booting between FireOS and TWRP
Below are the first steps in rooting the firestick 4k:
Once it reboot’s into TWRP do you now have root privs?
Can you stop here and not install a “pre-rooted image”?
Can I now boot between FireOS and TWRP if so How?
Thank You,
1.Boot the ISO
2.Download and extract the exploit package.
3.Open a terminal in the kamakiri directory
Run
Code:
4. ./bootrom-step.sh
Short one of the points in the attached photo to ground (the cage of the shielding).
Ideally you want to use DAT0, since that is tiny it might be easier to short the point marked CLK instead.
It is very important that you use a piece of soft wire or aluminum foil or something similar for shorting. Don't use tweezers as that makes it incredibly easy to knock of the capacitor off the PCB and kill the board!
5. Connect the stick to your computer (while keeping it shorted)Both USB and HDMI ???
6. The script should tell you to release the short and hit enter
Once finished run
Code:
7. ./fastboot-step.sh
Your device will now reboot into TWRP

RPM99 said:
Below are the first steps in rooting the firestick 4k:
Once it reboot’s into TWRP do you now have root privs? (Yes, but you need to install magisk to manage su)
Can you stop here and not install a “pre-rooted image”? (Yes, you don't need to install the image)
Can I now boot between FireOS and TWRP if so How? (adb commands or the reboot menu if you have the magisk module installed. For adb, insure you have adb debugging turned on, then log into the firestick (that's all in the guide) and run "reboot recovery")
Thank You,
1.Boot the ISO
2.Download and extract the exploit package.
3.Open a terminal in the kamakiri directory
Run
Code:
4. ./bootrom-step.sh
Short one of the points in the attached photo to ground (the cage of the shielding).
Ideally you want to use DAT0, since that is tiny it might be easier to short the point marked CLK instead.
It is very important that you use a piece of soft wire or aluminum foil or something similar for shorting. Don't use tweezers as that makes it incredibly easy to knock of the capacitor off the PCB and kill the board!
5. Connect the stick to your computer (while keeping it shorted)Both USB and HDMI ??? (hdmi isn't needed, just usb)
6. The script should tell you to release the short and hit enter
Once finished run
Code:
7. ./fastboot-step.sh
Your device will now reboot into TWRP
Click to expand...
Click to collapse
I replied inline in brackets. On mobile so a pain to in another way.

Thanks for the clarification
bnevets27 said:
I replied inline in brackets. On mobile so a pain to in another way.
Click to expand...
Click to collapse
Hi,
Inline with great answers is just fine, thank you.
I will investigate magisk, I didn't realize that's what it is for.
And "reboot recovery" at the adb command line will put me back in TWRP mode - This was great info!!
I ordered a new firestick to try this on, it will be here next week so I have some time to read up.
Thanks again,
Steve

More questions if you can please
RPM99 said:
Hi,
Inline with great answers is just fine, thank you.
I will investigate magisk, I didn't realize that's what it is for.
And "reboot recovery" at the adb command line will put me back in TWRP mode - This was great info!!
I ordered a new firestick to try this on, it will be here next week so I have some time to read up.
Thanks again,
Steve
Click to expand...
Click to collapse
When you short to ground and then plug into usb to boot firestick is that considered bootloader mode?
At what point is the greatest risk of bricking the firestick?
Thanks,
Steve

RPM99 said:
When you short to ground and then plug into usb to boot firestick is that considered bootloader mode?
At what point is the greatest risk of bricking the firestick?
Thanks,
Steve
Click to expand...
Click to collapse
I guess that would probably be technically correct.
Only time there's a chance of bricking, usually for flash anything, is during the writing process. Or a corrupt file.
I've done a hand full and haven't had any issues. Just take normal precautions like do what you can to prevent a power outage during the flash and once it's plugged in and flashing don't touch anything till its finished.
Personally I plugged in the mirco USB into the firestick first, then lined up the USB into the computer but didn't push it in. Held a small solid copper wire against the rf shield (the metal that surrounds the chip) and touched the side of what I think is a capacitor (you can't get to clk without taking the surrounding metal piece off). It's the "other" point they mention you can use. While doing that with one hand I plug in the USB to the computer. Remember the script has to be run first, waiting to see the stick before you plug it in.
If you miss time it or don't make the connection, the script just won't tell you to remove the short and press enter, so you'll just have to try again.

bnevets27 said:
...
Both would likely have a better chance if google play services/store could be installed. I see there was some effort put forth in trying to do that on previous firetvstick models so I may try some of the info that is out there. Seeing as we now have root its a lot more possible.....I assume.
Click to expand...
Click to collapse
Did you try https://forum.xda-developers.com/fire-tv/development/magisk-gapps-fireos-6-t4019095 ?

Kramar111 said:
Did you try https://forum.xda-developers.com/fire-tv/development/magisk-gapps-fireos-6-t4019095 ?
Click to expand...
Click to collapse
I haven't no. I might have missed that one. I've been pretty happy the the end result of using his module in this thread. And after updating to the latest version, voice search is working for me.
I have some other projects at the moment so I'm not working on this but I'll come back to later on.

bnevets27 said:
I haven't no. I might have missed that one. I've been pretty happy the the end result of using his module in this thread. And after updating to the latest version, voice search is working for me.
I have some other projects at the moment so I'm not working on this but I'll come back to later on.
Click to expand...
Click to collapse
When you say voice search is working, does that mean you can click the little mic icon at the top left of the Android TV launcher and it will search? Does it work well? Thanks

gogorman said:
When you say voice search is working, does that mean you can click the little mic icon at the top left of the Android TV launcher and it will search? Does it work well? Thanks
Click to expand...
Click to collapse
Yeah you have to click the mic on screen then the mic on the remote. Seems to work pretty well but haven't used it much more then just to see if it worked.

bnevets27 said:
Step 2
Root it!
Guide here
Click to expand...
Click to collapse
This exploit does not give you root. This unlocks the bootloader and then installs TWRP recovery.
.... I just used a small copper wire.
Click to expand...
Click to collapse
I used a Reese's candy wrapper! I just rolled it between my fingers and wedged it under the metal "cover," touching the CLK and DATA points. Then plugged it in to the USB port.
Step 4
Install Magisk
Click to expand...
Click to collapse
This is what gives you ROOT access.
Took me a while, reading through all the threads, to figure out which exploit does what.
Step 5
Install [Magisk][Module] FireTV 4K Stick Add-Ons
Click to expand...
Click to collapse
This module is great. It also disables Amazon firmware updates. There are a bunch of other tips in that thread too.
Thanks for the tips and tricks!

When trying to run the disable script I get i get an error at the last command. /data/local/tmp/bloat-disable.sh[7]: syntax error: 'newline' unexpected.When running command " sh /data/local/tmp/bloat-disable.sh "

Can you create a bloat-disable script dedicated to fire stick 4k (mantis) ? that would be beneficial for everyone.

[GUIDE] Amazon Fire 7 2019 9th gen FireOs 6.3.1.2 to LineageOs 14.1

First i want to say Speacial Thanks to @xyz`, @k4y0z, @diplomatic and @ggow who make it possible to get a costum rom on a fire 7(9th gen)!
But i needed informations from more sites to get it work and i want to collect all informations in this Thread to make it easier for noobs like me I hope thats okay, i only collect informations, credits goes to:
@k4y0z and @xyz` for the bootloader hack
@diplomatic for the temp root
@ggow for the lineageos for mustang
So i will show the hole way From Stock FireOs 6.3.1.2 until you boot LineageOs 14.1
In this Guide i will use the Software method to get into bootrom mode. Software method: use mtk-su to do the thing.
Careful: this will break your device… and then you fix it by installing a new OS.
Any OS above 6.3.1.2 needs to use the hardware method!
Here you can find the hardware method: https://forum.xda-developers.com/am...ire-7-2019-mustang-unbrick-downgrade-t3944365
I flash some devices but that was the most difficult. It will help if you have some experience how to flash devices.
NOTICE :
Before you move further, make clear that rooting device -
Your warranty will be void
Some of functions may not work on rooted device, some function may get back with un rooting, some may never.
All your data on device will be lost
Flashing custom binaries may brick (Usually soft but can be hard brick too) your device, so follow it on your own risk!
If you are ready with condition, move further -
Click to expand...
Click to collapse
Make sure you read this guide completely before starting!
This Hardware you need:
Working Amazon Fire 7 2019 9th gen (tested with FireOs 6.3.1.2)
USB cable for Kindle Fire
empty USB drive (min. 2Gb)
computer that can boot from USB drive
Download This Software:
lubuntu-19.10-desktop-amd64.iso # get it here https://lubuntu.net and download the AMD64 version
rufus-3.9.exe # get it here https://rufus.ie
mtk-su_r21.zip # get it here https://forum.xda-developers.com/attachment.php?attachmentid=4971443
amonet-mustang.zip # get it here https://forum.xda-developers.com/attachment.php?attachmentid=4785431&d=1561925516
lineage-14.1-20190827-UNOFFICIAL-mustang.zip # get it here https://androidfilehost.com/?w=files&flid=297948
open_gapps-arm-7.1-mini-20200403.zip # go to https://opengapps.org and choose AMR -> 7.1 -> and a variant of your choice i use mini
Step 1 Prepare Usb Stick
################################
Okay first we make the usb stick ready with Lubuntu.
1.1 Start the rufus-3.9.exe
1.2 choose the Lubuntu image file and push start
1.3 it will ask ISO image mode or DD image mode, choose the DD image mode!
1.4 after that put these files to C:\ :
mtk-su_r21.zip
amonet-mustang.zip
lineage-14.1-20190827-UNOFFICIAL-mustang.zip
open_gapps-arm-7.1-mini-20200403.zip
1.5 Turn off your Computer!
Step 2 Boot Live Linux
################################
2.1 Turn on your Computer and boot from usb and start lubuntu
(2.1.1 If you use wlan connect with it)
2.2 Open a terminal window # (go to "start button" at the left corner choose -> system tools -> QTerminal)
2.3 type "sudo apt install python3 python3-serial android-tools-adb android-tools-fastboot" push enter
2.3.1 it ask you something, say yes
2.4 type "sudo apt-get remove modemmanager" push enter
2.4.1 it ask you something, say yes, if it done close this window
2.5 Click on the "Computer" icon on Desktop
2.6 Search your Windows device and copy the 4 files from step 1.4 to lubuntu home directory (make it easier later)
Step 3 Prepare kindle
################################
3.1 Go to settings and enable developer options (need to push the serialnummber multiple times)
3.2 Go to developer options Enable USB debugging
3.3 Connect kindle to computer
3.3.1 On the kindle,
3.3.2 pull down the menu,
3.3.3 click the USB charging, “tap for other USB options” and select PTP for “transfer photos”
3.3.4 Click Accept to allow permission for your computer.
Step 4 Temporary root (Terminal window1)
################################
4.1 Open the mtk-su_r21.zip
4.2 copy the arm folder to lubuntu home directory
4.3 Open a new terminal window
4.4 type "sudo adb push arm/mtk-su /data/local/tmp” push enter
once successful, run these commands:
4.5 type "adb shell" push enter
4.6 type "cd /data/local/tmp" push enter
4.7 type "./mtk-su" push enter
4.8 type "getenforce" push enter # Just to confirm it says Permissive
4.9 type "echo 0 > /sys/block/mmcblk0boot0/force_ro" push enter
4.10 type "dd if=/dev/zero of=/dev/block/mmcblk0boot0 bs=512 count=8" push enter
Dont close this window!. you will need it in a moment.
Step 5 Bootrom Mode (Terminal window2)
################################
5.1 Open the amonet-mustang.zip
5.2 copy the amonet-mustang folder to lubuntu home directory
5.3 Open a new terminal window
5.4 type "cd amonet-mustang/" push enter
5.5 type "sudo ./bootrom-step.sh" push enter
5.6 Go back to the first Terminal window and type "reboot" push enter
5.7 Go back to the second Terminal, the tablet should restart, and the amonet script will begin to run.
Press Enter to continue, it will start copying things. Should take about 4 minutes.
Once the script finished, the kindle will restart into fastboot mode.
5.8 All you will see if the amazon logo. to verify that the device is in fastboot mode go back to the first Terminal window
and type "sudo fastboot devices" push enter
it will list the device # if it find 1 device you make all right
Step 6 Fastboot & TWRP
################################
6.1 Go back to the second Terminal window
6.2 type "sudo ./fastboot_step.sh"
The tablet will flash some text and do a few things. give it a minute or two.
The tablet will flash and appear to restart, let it do its thing until the screen goes dark.
6.3 Tap the power button twice and TWRP will pop up.
SUCCESS! # TWRP (Team Win Recovery Project) is now installed and can be launched by holding down VOL Down (left most button from pwr) and Power when starting up the device.
(At this point you can try to put the files on a SD Card, but i try it with multiple ones and TWRP dont find one, if you have one that work you can jump to step 8.4)
Edit: or use adblink from here https://forum.xda-developers.com/fire-tv/themes-apps/adblink-v2-04-t3389826
Step 7 Set permissions to Copy
################################
7.1 In TWRP on you kindle push wipe -> push Format Data and Swipe to reset
7.2 Now we need to obtain the idVendor of the kindle.
Go to the first Terminal window and type "sudo dmesg" push enter look for idVendor"XXXX", for me, the ID was "18d1".
7.3 Next, you need to give the ”plugdev” group access to the device.
You are going to create a file and then change some permissions then restart the services.
7.4 type "sudo nano /etc/udev/rules.d/51-android.rules" # create the file
7.5 and type the following line: #(Change idVendor to your ID)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0666", GROUP="plugdev"
7.6 push ctrl + x , and hit y to save. # push a button and it close but hold the terminal open
7.7 Now assign read permissions on the files, reload udev and reload the adb daemon:
7.7.1 type "sudo chmod a+r /etc/udev/rules.d/51-android.rules" push enter
7.7.2 type "sudo udevadm control --reload-rules" push enter
7.7.3 type "adb kill-server" push enter
7.7.4 type "adb start-server" push enter
(You may have to disconnect and connect again your device to the USB port) # i dont needed it
Step 8 Copy & Install LineageOs
################################
NOW you can copy the files using the adb push command, like we did before.
8.1 type "sudo adb push /lineage-14.1-20190827-UNOFFICIAL-mustang.zip /data/local/tmp/lineage.zip" push enter
8.2 type "sudo adb push /open_gapps-arm-7.1-mini-20200403.zip /data/local/tmp/gapps.zip" push enter
After it finish copying, use TWRP to install the image
8.3 In TWRP push install go to path /data/local/tmp/ # there you find lineage.zip & gapps.zip
8.4 Choose lineage.zip and swipe to install
8.5 After that go back and choose gapps.zip and swipe to install
8.6 if its done you can push "Reboot System"
You are Finaly Done LineageOs 14.1 will booting now! # it will take some time at the first boot
Edit:
Install the "sod-fix-test.zip" by using TWRP you can find it here https://forum.xda-developers.com/showpost.php?p=80621157&postcount=253 @Ziona
(This fix the charge issue)
i find so much usefull things at xda-developers to flashing much devices include this device
So for this device it was really difficult and i was think it will be great thanks when i collect all informations for other(and me for the next time ).
And i think, thats understandable for anyone. I Hope it will help other People too.
Sources:
Unlock & root By xyz` https://forum.xda-developers.com/am...ire-7-2019-mustang-unbrick-downgrade-t3944365
Amazing Temp Root By diplomatic https://forum.xda-developers.com/android/development/amazing-temp-root-mediatek-armv8-t3922213
LineageOS 14.1 By ggow https://forum.xda-developers.com/amazon-fire/orig-development/rom-lineage-14-1-t3957329

Thanks for the guide, do you know if this also applies to Fire OS 6.3.1.5 ? as I have a fire 7 mustang version

At first start i connet the fire 7 with wifi and it makes a small update to 6.3.1.4 then i make a factory reset with stock recovery and i was back to 6.3.1.2
Try the factory reset if that dont work and you are still on 6.3.1.5, dont try this Guide i only test it with a 6.3.1.2 device!

It's all good, followed your guide and I'm on lineage os now. Thanks again!

So just to understand, Cozzysa: you sis it with 6.3.1.5 ?

Hi, I try here, and I stooped in the step 4.6, the result is: No such file or directory.
What's wrong?
edit: I founded the error, in the step, please correct the folder temp to tmp.

lucas.lop said:
Hi, I try here, and I stooped in the step 4.6, the result is: No such file or directory.
What's wrong?
edit: I founded the error, in the step, please correct the folder temp to tmp.
Click to expand...
Click to collapse
Thanks! i edit it! if you find some other things tell me
nimrodk3 said:
So just to understand, Cozzysa: you sis it with 6.3.1.5 ?
Click to expand...
Click to collapse
Thats a good question

_SWaTcH_ said:
Thanks! i edit it! if you find some other things tell me
Thats a good question
Click to expand...
Click to collapse
I try here with 6.3.1.5 and don't work. I'm with this problem too.

lucas.lop said:
I try here with 6.3.1.5 and don't work. I'm with this problem too.
Click to expand...
Click to collapse
This guide will only work if you are on 6.3.1.2 or below.
MTK-su = Amazon Fire 7 2019 -- up to Fire OS 6.3.1.2 build 0002517050244 only
---------- Post added at 01:19 PM ---------- Previous post was at 01:10 PM ----------
---------- Post added at 01:22 PM ---------- Previous post was at 01:19 PM ----------
@_SWaTcH_
You might want to give credit to "diplomatic" for his temp root and you should possibly change to links to their threads.
For example 14.1 has this right next to the link to download. "*** Please do NOT create any mirrors ***"
I would also recommend a note that any OS above 6.3.1.2 needs to have the hardware unlock and link them over to the over thread.
Very nice instructions though!

Is no way out for 6.3.1.5?

lucas.lop said:
Is no way out for 6.3.1.5?
Click to expand...
Click to collapse
Go here for the hardware unlock method-
https://forum.xda-developers.com/am...ire-7-2019-mustang-unbrick-downgrade-t3944365
Once you get into TWRP, you can install Lineage. You can put the lineage on your sdcard, or transfer to your download folder from a PC. You odnt have to use adb to push files. an easy way of transfering files is to use adblink from here...
https://forum.xda-developers.com/fire-tv/themes-apps/adblink-v2-04-t3389826
Or when plugged in set it to file transfer and it would come up as a removable media on a computer.
follow the instructions from the 14.1 thread for install.

Michajin said:
@_SWaTcH_
You might want to give credit to "diplomatic" for his temp root and you should possibly change to links to their threads.
For example 14.1 has this right next to the link to download. "*** Please do NOT create any mirrors ***"
I would also recommend a note that any OS above 6.3.1.2 needs to have the hardware unlock and link them over to the over thread.
Very nice instructions though!
Click to expand...
Click to collapse
Im sorry that i miss the credit for diplomatic :silly:
I add note that you need to use the hardware method for Os version above 6.3.1.2 and add links to their threads.

Device offline MTP Error
I follow everything flawlessly until step 7. None of my SD cards are recognized. So I follow the steps posted in Step 7. In my device list I see "omni mustang" then it says I cant access this drive. I do step 7 then go to push lineage onto the system it says device offline.
I have rebooted the tablet many times Disable MTP and Enabled MTP countless times.
Sorry this is all jumbled up. Hopefully you understand what I am trying to say.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

nimrodk3 said:
So just to understand, Cozzysa: you sis it with 6.3.1.5 ?
Click to expand...
Click to collapse
Yeah it worked perfectly with the hardware hack

Ozed20 said:
I follow everything flawlessly until step 7. None of my SD cards are recognized. So I follow the steps posted in Step 7. In my device list I see "omni mustang" then it says I cant access this drive. I do step 7 then go to push lineage onto the system it says device offline.
I have rebooted the tablet many times Disable MTP and Enabled MTP countless times.
Sorry this is all jumbled up. Hopefully you understand what I am trying to say.
Click to expand...
Click to collapse
So i think you have install TWRP and you only need to copy the files to your fire 7, Michajin post a other way:
Michajin said:
Once you get into TWRP, you can install Lineage. You can put the lineage on your sdcard, or transfer to your download folder from a PC. You odnt have to use adb to push files. an easy way of transfering files is to use adblink from here...
https://forum.xda-developers.com/fire-tv/themes-apps/adblink-v2-04-t3389826
Or when plugged in set it to file transfer and it would come up as a removable media on a computer.
follow the instructions from the 14.1 thread for install.
Click to expand...
Click to collapse

Worked then broke
Not sure what happened. Got everything installed booted into lineage 14.1 downloaded apps browsed the web etc. I went into the list of apps and turned off auto start on things I wasn't planning to use the tablet for. Mail, messages, etc to save on memory usage these devices don't seem to come with much to spare. Then held the power button, clicked restart and it never came back, doesn't respond on the power button. Not sure where I need to go from here.
Additional Info: I had to use the hardware method since reset to factory took me back to 6.3.1.5

DrGuns4Hands said:
Not sure what happened. Got everything installed booted into lineage 14.1 downloaded apps browsed the web etc. I went into the list of apps and turned off auto start on things I wasn't planning to use the tablet for. Mail, messages, etc to save a memory usage. Then held the power button, clicked restart and it never came back, doesn't respond on the power button. Not sure where I need to go from here.
Click to expand...
Click to collapse
Hold the power button for about 10 seconds to do a power off...
It is a known issue with 14.1 Lineage rom for this. Did you install the sod patch? Check out the 14.1 thread here.... Post #566
https://forum.xda-developers.com/amazon-fire/orig-development/rom-lineage-14-1-t3957329/page57

Michajin said:
Hold the power button for about 10 seconds to do a power off...
It is a known issue with 14.1 Lineage rom for this. Did you install the sod patch? Check out the 14.1 thread here.... Post #566
https://forum.xda-developers.com/amazon-fire/orig-development/rom-lineage-14-1-t3957329/page57
Click to expand...
Click to collapse
Not sure what sod means. I did hold down the power button for quite a while and the tablet wouldn't turn on, but I can't say for certain it was 10 seconds I'll have to try again when I get home. Perhaps this patch should be in the installation instructions here if this is a known issue?

DrGuns4Hands said:
Not sure what sod means. I did hold down the power button for quite a while and the tablet wouldn't turn on, but I can't say for certain it was 10 seconds I'll have to try again when I get home. Perhaps this patch should be in the installation instructions here if this is a known issue?
Click to expand...
Click to collapse
Screen Of Death. You might have to pull the battery. The Developer who created the Rom has been unavailable, being custom roms expect bugs. Always good to look at the last few pages of any thread to know status and current issues. When the GGOW returns he will likely update the latest security patches and install the patches into the latest. Remember these are volunteers who have no obligation to do this. Some don't even accept donations.

Michajin said:
Screen Of Death. You might have to pull the battery. The Developer who created the Rom has been unavailable, being custom roms expect bugs. Always good to look at the last few pages of any thread to know status and current issues. When the GGOW returns he will likely update the latest security patches and install the patches into the latest. Remember these are volunteers who have no obligation to do this. Some don't even accept donations.
Click to expand...
Click to collapse
Thanks. This is my first time with a custom ROM. I got the tablet just to do chromecast control for my TV in the living room and realized quickly that Fire OS just felt to clunky to keep on the device. Guess I'll be learning how to do update patches since I think that lineage will still be the better solution overall. Any suggestion on where to look to understand how to do the updates? I followed this guide as a step by step assuming it would be the whole kit and kaboodle, so can't really say I understand what pieces I'd need to update or where to look to keep things up to date to the most stable version.