Hi all,
I'd previously rooted, installed recovery, etc on my FireTV version 1. Everything was working great, and I thought I'd disabled updates. I turned it on recently and It somehow lost root. Everything is still installed, but can't open SuperSU, towelroot says the device isn't supported. Still says that Xposed is installed with the framework though.
The system says I'm now on 51.1.4.1_user_514013920 for some reason. Checking for system update still gives an error. What went wrong, and is there any way to fix it?
@AFTVNews, I'm mainly looking at you
Does anyone know?
If you disabled updates its probably the fact that the fire tv has updated its self, im afraid thats why su (root) isnt working & your device isn't supported because your firmware has upgraded. You have no way to root at the moment in time unless a os5 root for AFTV gen1 is created sometime in the near future? It is possible because Rbox is making a Os5 root for Gen 1.... But i think you need root already for that? My advice would be if you still want root, get a AFTV 2 while root is still possible & root/block updates & wait for the new recovery & rom being developed by Rbox which fingers crossed should be very near to be released. I still cant get over why you would want to unblock updates for when you had root & exposed framework? oh well whats done is done now.
If this helps press that thanks button
If he install clockword mod and if he can still get into it, couldn't he flash the latest rom and get root back?
That's very confusing?
Disabling updates should've been the first thing you did after rooting (presumably a long time ago if you have gen 1.)
Disabling updates, successfully or not, shouldn't've caused you to lose root. If you have CWM, your aftv should not be able to receive a stock update. Of course towel root won't work because your firmware is based on stock software that is not rootable. Are you certain you did nothing else other than disable updates?
I'm basing all of this off the assumption you have CWM. If so then just push the same firmware you currently have installed to /sdcard and flash it again. Install busybox and I'd think you'd be ok. You probably already know this but aftvnews has all rbox's prerooted roms.
Maybe you only disabled ota on your router? Have you taken it anywhere else? Or got a new router?
Sent from my SM-G900F using Tapatalk
Yes, I disabled updates when I first rooted. I did this on the firetv, not my router. I followed @aftvnews guide to do it, and it worked perfectly. I'm not looking to get another device, but to restore this one. I still have cwm, busybox, supersu all installed (I think I still have cwm, don't remember how to boot to it). I still don't believe you can just flash a rooted rom over top...
ldeveraux said:
Yes, I disabled updates when I first rooted. I did this on the firetv, not my router. I followed @aftvnews guide to do it, and it worked perfectly. I'm not looking to get another device, but to restore this one. I still have cwm, busybox, supersu all installed (I think I still have cwm, don't remember how to boot to it). I still don't believe you can just flash a rooted rom over top...
Click to expand...
Click to collapse
If the firmware has gone to an updated latest unrootable firmware I'm sure what ever you flash onto it will brick your device even if you do have cwm?
Sent from my SM-G900F using Tapatalk
deanr1977 said:
If the firmware has gone to an updated latest unrootable firmware I'm sure what ever you flash onto it will brick your device even if you do have cwm?
Sent from my SM-G900F using Tapatalk
Click to expand...
Click to collapse
Yeah that's what I assumed. I thought it might be too far gone. Was hoping AFTVnews might see this and offer advice.
ldeveraux said:
Yeah that's what I assumed. I thought it might be too far gone. Was hoping AFTVnews might see this and offer advice.
Click to expand...
Click to collapse
You're not understanding. First, the firmware you have MUST have boot menu installed. Therefore you can choose to boot recovery from there. OR connect adb and reboot recovery. Adbfire simplifies this...
You should be fine to flash a prerooted rom and it should fix whatever got messed up.
Again, theres NO way youre running stock because im fairly certain rbox's recovery wont allow the installation. Theres an issue with you su no doubt but im thinking youre still rooted.
Sorry I missed this thread until now. Do you know what version pre-rooted ROM you had installed last? You say it's on 51.1.4.1, but are you positive that is not the version it was always on? If by some strange way it did install a stock update, there's no way it would have updated to 51.1.4.1 since Amazon is pushing 51.1.6.3 to all devices now. Just because you can't open SuperSU doesn't mean you lost root. What happens when you connect via ADB and enter the "su" command? Is your bootloader unlocked? Here's how to check.
AFTVnews.com said:
Sorry I missed this thread until now. Do you know what version pre-rooted ROM you had installed last? You say it's on 51.1.4.1, but are you positive that is not the version it was always on? If by some strange way it did install a stock update, there's no way it would have updated to 51.1.4.1 since Amazon is pushing 51.1.6.3 to all devices now. Just because you can't open SuperSU doesn't mean you lost root. What happens when you connect via ADB and enter the "su" command? Is your bootloader unlocked? Here's how to check.
Click to expand...
Click to collapse
Huh, looks like everything is still good. I ADB in and "su" still shows [email protected] I guess I still have root and unlocked bootloader. I disabled automatic updates again just in case, it says "Package com.android.dcp new state: disabled". I feel like I should update the the ROM though as my install is feeling a bit awkward. Is there a guide on AFTVnews?
EDIT: I just checked and I don't have RBOX's Boot Menu installed. Does that mean I should downgrade to 51.1.4.0, install the boot menu, then upgrade the ROM in that order?
ldeveraux said:
Huh, looks like everything is still good. I ADB in and "su" still shows [email protected] I guess I still have root and unlocked bootloader. I disabled automatic updates again just in case, it says "Package com.android.dcp new state: disabled". I feel like I should update the the ROM though as my install is feeling a bit awkward. Is there a guide on AFTVnews?
EDIT: I just checked and I don't have RBOX's Boot Menu installed. Does that mean I should downgrade to 51.1.4.0, install the boot menu, then upgrade the ROM in that order?
Click to expand...
Click to collapse
Yes, install 51.1.4.0, then install the boot menu, then install 51.1.6.3
AFTVnews.com said:
Yes, install 51.1.4.0, then install the boot menu, then install 51.1.6.3
Click to expand...
Click to collapse
Hey cool everything works.
Only issue right now is the google play store. I installed it as in your guide, but it keeps updating and won't work at all on version 6.0.5. I saw this user UnderXP (http://forum.xda-developers.com/fire-tv/help/how-to-disable-google-play-store-auto-t3135642/page2) who used XPrivacy to stop the storee/services from auto updating. I've had no luck at it.
What do you recommend?
ldeveraux said:
Hey cool everything works.
Only issue right now is the google play store. I installed it as in your guide, but it keeps updating and won't work at all on version 6.0.5. I saw this user UnderXP (http://forum.xda-developers.com/fire-tv/help/how-to-disable-google-play-store-auto-t3135642/page2) who used XPrivacy to stop the storee/services from auto updating. I've had no luck at it.
What do you recommend?
Click to expand...
Click to collapse
I haven't looked into the Google Play Store in a while. I plan to update my guide once Fire OS 5 is released to older devices, since any changes I make now likely won't work after the update.
Related
Hello to anyone who decides to read this, and thank you for taking the time to haha.
I'm new here, and I'm relatively new to the whole rooting and modding scene, although I'm pretty confident in using Odin and various software involved in this, so, hopefully this won't be too complicated.
I have a question about my Note 10.1 2014. I have the WiFi model (P6000), which was bought in China since I was a student there for a year. Now I'm back in England. I flashed my ROM to a UK version so I could use Google Play services and Facebook integration, along with several other features and services which are blocked in China for various reasons. Now, my problem is, I have no real reason to have a rooted device other than for this. I also know I didn't need to root my device to flash the ROM, but I had some problems with my keyboard in China, but I have since solved them and have no use for the root. I want to take advantage of OTA updates since apparently my device should have one, but I can't because I'm rooted. Is it at all possible to unroot and lock the bootloader so I can update, without losing the ROM flash that is making my device run the UK firmware? If so, how would I go about doing this on my device? If it's not possible, is there are method in which I can update my firmware?
Sorry if I'm a little clueless about this stuff, and thanks in advance.
haofeng93 said:
Hello to anyone who decides to read this, and thank you for taking the time to haha.
I'm new here, and I'm relatively new to the whole rooting and modding scene, although I'm pretty confident in using Odin and various software involved in this, so, hopefully this won't be too complicated.
I have a question about my Note 10.1 2014. I have the WiFi model (P6000), which was bought in China since I was a student there for a year. Now I'm back in England. I flashed my ROM to a UK version so I could use Google Play services and Facebook integration, along with several other features and services which are blocked in China for various reasons. Now, my problem is, I have no real reason to have a rooted device other than for this. I also know I didn't need to root my device to flash the ROM, but I had some problems with my keyboard in China, but I have since solved them and have no use for the root. I want to take advantage of OTA updates since apparently my device should have one, but I can't because I'm rooted. Is it at all possible to unroot and lock the bootloader so I can update, without losing the ROM flash that is making my device run the UK firmware? If so, how would I go about doing this on my device? If it's not possible, is there are method in which I can update my firmware?
Sorry if I'm a little clueless about this stuff, and thanks in advance.
Click to expand...
Click to collapse
What rom version you're running right now? Do you have a full UK factory firmware 4.4 available?
buhohitr said:
What rom version you're running right now? Do you have a full UK factory firmware 4.4 available?
Click to expand...
Click to collapse
Sorry for the late response, I was travelling.
I'm not entirely sure haha. Here's my device info, does this explain my situation?
As for the second question, I'm not entirely sure what you mean? I looked for the firmware for flashing but couldn't find a Android 4.4 version, despite my device telling me I have an available update and the internet saying my device should be updated to 4.4?
haofeng93 said:
Sorry for the late response, I was travelling.
I'm not entirely sure haha. Here's my device info, does this explain my situation?
As for the second question, I'm not entirely sure what you mean? I looked for the firmware for flashing but couldn't find a Android 4.4 version, despite my device telling me I have an available update and the internet saying my device should be updated to 4.4?
Click to expand...
Click to collapse
OK, you have 4.3 and waiting for 4.4 OTA update. If you open your SuperSU app, then go to settings, scroll down to "Full unroot", select that and it should unroot. After done reboot your device and verify that the SuperSU is no longer in your app draw. I don't know if you modify anything else on your device like build.props or installed any rooted apps, if you do you need to remove them ALL, unfreeze any system apps using Titanium backup and revert build.props back to factory original, BEFORE YOU UNROOT. Once everything done you should be ok to take the OTA update. The OTA update will not erase your data so you should be fine there.
buhohitr said:
OK, you have 4.3 and waiting for 4.4 OTA update. If you open your SuperSU app, then go to settings, scroll down to "Full unroot", select that and it should unroot. After done reboot your device and verify that the SuperSU is no longer in your app draw. I don't know if you modify anything else on your device like build.props or installed any rooted apps, if you do you need to remove them ALL, unfreeze any system apps using Titanium backup and revert build.props back to factory original, BEFORE YOU UNROOT. Once everything done you should be ok to take the OTA update. The OTA update will not erase your data so you should be fine there.
Click to expand...
Click to collapse
Thanks for the speedy reply. I tried to option within SuperSU, but it seems to have been uninstalling for about 15 minutes with no result. I realised that I froze the stock Samsung keyboard since it overtakes the Google Chinese Pinyin Input when using a keyboard, and I work primarily in Chinese. Could this be the reason why the uninstall seems to have failed or got stuck? Not sure what to do now, oops.
haofeng93 said:
Thanks for the speedy reply. I tried to option within SuperSU, but it seems to have been uninstalling for about 15 minutes with no result. I realised that I froze the stock Samsung keyboard since it overtakes the Google Chinese Pinyin Input when using a keyboard, and I work primarily in Chinese. Could this be the reason why the uninstall seems to have failed or got stuck? Not sure what to do now, oops.
Click to expand...
Click to collapse
Did you read my instructions?? you must un-freeze all the system apps first before unroot otherwise the OTA may failed. Let it sits for another 10 min then reboot your phone and check to see root has been removed.
buhohitr said:
Did you read my instructions?? you must un-freeze all the system apps first before unroot otherwise the OTA may failed. Let it sits for another 10 min then reboot your phone and check to see root has been removed.
Click to expand...
Click to collapse
Yeah, I did read the instructions. It was just a moment of stupidity on my behalf, completely forgot I'd frozen the stock keyboard. I'll leave a little longer and then reboot.
buhohitr said:
Did you read my instructions?? you must un-freeze all the system apps first before unroot otherwise the OTA may failed. Let it sits for another 10 min then reboot your phone and check to see root has been removed.
Click to expand...
Click to collapse
Well, it seems to have gone a little weird. I have no root access anymore but SuperSU is still installed and my device status is still custom, so the OTA update won't run. I'm guessing I ought to reroot and properly clear out/unfreeze stuff, right? Sorry for being a pain haha...
haofeng93 said:
Well, it seems to have gone a little weird. I have no root access anymore but SuperSU is still installed and my device status is still custom, so the OTA update won't run. I'm guessing I ought to reroot and properly clear out/unfreeze stuff, right? Sorry for being a pain haha...
Click to expand...
Click to collapse
You need to remove the SuperSu app by go to playstore search for Supersu then you should see the uninstall option. The OTA failed probably because it detected that you have modified the system. You need to think what you did to your system and revert back before try again. I would just use towelroot app and reroot then unfreeze any frozen apps, then uninstall then try again. If you can't remembered what you did and the OTA stills failing, then the next step is use Odin and flash factory firmware either 4.3 or 4.4. Remember to read my instructions before and ask if in doubt before taken any action. After you re-root, make sure you use Titanium to run a full backup of all your userapps. if you don't want to be bother, then just use Odin to flash either 4.3 or 4.4 but you need to re setup and re-download all your apps.
Hey all, wondering if anyone has the update.zip file for the 10/30 Verizon update to Software Build: VS98511C
I have a buddy who's rooted (like me) but is receiving errors trying to install it so I'm hoping this will help. His phone is set up basically exactly the same as mine but only he has had the error and we've exhausted all possibly fixes
Thanks guys
Looking for the same.. Do we have a way to upgrade while keeping root?
I am also looking for update.zip for VS98511C.
Cyber Warrior said:
Looking for the same.. Do we have a way to upgrade while keeping root?
Click to expand...
Click to collapse
If you can update via the ota, you will keep root. I did it just fine and it's been reported from others that they haven't had a problem either. My friend's phone is having some sort of unique error that we can't figure out :/
xxxdc5 said:
If you can update via the ota, you will keep root. I did it just fine and it's been reported from others that they haven't had a problem either. My friend's phone is having some sort of unique error that we can't figure out :/
Click to expand...
Click to collapse
So you kept root while updating? No need to re-root? Any tricks like using root keeper? I never took an ota while rooted so it makes me nervous.. I always manually updated with a rooted version. I have some stuff modified and frozen.. I guess un-doing all my mods and putting things back to stock shouldnt be too much of a pain so i can take the ota. Its always been easier to just flash something though. Maybe i'll wait a few days to see if theres a better way.
If you have twrp installed and take the ota you will boot into twrp until you do a twrp terminal hack or tot/kdz back to fresh stock.
I have twrp installed also. So how do we take the update then without going into a twrp boot loop?
Cyber Warrior said:
So you kept root while updating? No need to re-root? Any tricks like using root keeper? I never took an ota while rooted so it makes me nervous.. I always manually updated with a rooted version. I have some stuff modified and frozen.. I guess un-doing all my mods and putting things back to stock shouldnt be too much of a pain so i can take the ota. Its always been easier to just flash something though. Maybe i'll wait a few days to see if theres a better way.
Click to expand...
Click to collapse
ThePagel said:
If you have twrp installed and take the ota you will boot into twrp until you do a twrp terminal hack or tot/kdz back to fresh stock.
Click to expand...
Click to collapse
marcogiudice said:
I have twrp installed also. So how do we take the update then without going into a twrp boot loop?
Click to expand...
Click to collapse
I don't have twrp installed so I'm not sure
I didn't use any tricks or special apps or anything. I saw that others took the ota while rooted and it turned out fine so I just went for it. I figured there's really no scenario I could get into that I wasn't comfortable finding a fix for so I just lazily shrugged and pushed update LOL. I didn't need to worry though as everything updated fine and normal for me.
Again though, I don't have a custom recovery installed so idk how it'll work out with twrp :/
I didnt have a custom recovery..only root with xposed and some other mods. I defrosted anything that i froze.. put back any tinkered system files..uninstalled xposed. I took the ota system update.. Everything is working great and still have root access.
I have a rooted Samsung Tab S wifi with this firmware installed T800XXU1ANFB. In order to unroot do i need to flash it with the same stock firmware it has on it. Or can i flash it with an updated stock firmware?
Metamorph22 said:
I have a rooted Samsung Tab S wifi with this firmware installed T800XXU1ANFB. In order to unroot do i need to flash it with the same stock firmware it has on it. Or can i flash it with an updated stock firmware?
Click to expand...
Click to collapse
Just select full unroot from settings in the supersu app.
I am a newbie... so here goes.
I did root it but when I go to verify it it doesn't verify. SuperSU was put on my device, but it wants to update the binary and I did that, but it keeps failing.
What I want to do is unroot it entirely and set it back to factory settings so I went to the settings in SuperSU like said above. If it is unrooted, how would I know? SuperSU is still on my table And only able to.bto.be disabled instead of e tirely removed.
I also think it didn't work because maybe I was trying to root it with a auto file for kitkat instead of lollipop. And links to the version for this lollipop are in a few places but each time I try to extract what I've downloaded the file is corrupt and it never unzips.
I've got the galaxy tab s 10.5; 16gb; wifi only (sm-t800) running lollipop 5.0.2
I'd really like to root so I can get the bloatware off, but if it isn't possible at the moment then I'd might as well go back to an unrooted device.
I'll take all the help I can get or be directed to. I've been pulling my hair out for two days on how to figure it out.
After you have unrooted reboot and you will be unrooted. Root can be verified with Root validator.
For root you can use my build here:
http://forum.xda-developers.com/showthread.php?t=3079488
ashyx said:
After you have unrooted reboot and you will be unrooted. Root can be verified with Root validator.
For root you can use my build here:
http://forum.xda-developers.com/showthread.php?t=3079488
Click to expand...
Click to collapse
On a second reboot I noticed I wasn't rooted. Thanks. I finally am rooted now.
ashyx said:
After you have unrooted reboot and you will be unrooted. Root can be verified with Root validator.
For root you can use my build here:
http://forum.xda-developers.com/showthread.php?t=3079488
Click to expand...
Click to collapse
I'm having a different problem but I am sure it is related to this topic.
I ended up being properly rooted after I got the correct one for lollpop 5.0.2. Then I realized that The Sims Freeplay would not work. I tried to use root cloak and I had no luck. I thend tried to use xposed, but it hasn't been upgraded to Lollipop yet.... so I thought about if rooting my device was really worth it since the only game I religiously play is The Sims Freeplay (apparently they are cracking down on people who hack their game.... which is all good and well because because it has nothing to do with my game... I have a rooted device to get rid of bloatware, not to hack the game that I play in a legit way -- but whatever)...
So I chose to unroot from SuperSU like I did once before (when I wasn't properly rooted, but SU was still on my device) just to see what would happen.
I've used Odin two more times to put back the original root file I got to work for Lollipop and now on the second reboot, SuperSU still hasn't been put on my device (like it originally had did long before I even rooted properly).
So now TWRP boots up every time I want to just go straight to my download screen and from there I click on download to get to my screen. That's when I use odin and the cf-auto.
I hope I don't sound confusing. I just want to know where can I go from here?
Apparently the Sims Freeplay is being a real PITA about people trying to play their game on a root device (doesn't surprise me with EA), but I want to play it on my device rooted or not... but now my tablet feels like it's both. It's not straight out of the store box and it's not fully rooted...
What the heck am I doing wrong now?
If you have twrp installed you don't need to flash cfautoroot again. Just reboot from within twrp and it will offer to root.
If you are still having problems see the link below.
http://forum.xda-developers.com/galaxy-tab-s/development/root-cf-autoroot-twrp-t800-t3079488
If you are having problems getting into download mode you are not doing it properly.
Hold POWER + VOL DOWN + HOME.
Under which category will it offer to root and will there be a way to get the sims freeplay working? If not I'd like to get back to straight out of the box for the tablet... but something tells me after reading for a few hours last night that thats impossible.
geekery15 said:
Under which category will it offer to root and will there be a way to get the sims freeplay working? If not I'd like to get back to straight out of the box for the tablet... but something tells me after reading for a few hours last night that thats impossible.
Click to expand...
Click to collapse
If you unroot with the supersu app you will be fully unrooted.
To reroot boot into twrp then reboot.
Just wondering if anyone has toggled Enable superuser off and on in SuperSU and whether there were any issues. I have a couple of apps that check for root and will not run if detected. In the past (ran rooted S3s for the past 3.5 years), I have just been able to turn it off to use the apps and then turn it back on with no issues, but like everyone else am still learning the ins and outs of the Pixel. I am running a Verizon Pixel XL and a non-XL (wife's phone). Both are bootloader unlocked and rooted running NDE63P. I have not had time to update to NDE63X or install TWRP yet, not that any of hat matter to the original question.
sliding_billy said:
Just wondering if anyone has toggled Enable superuser off and on in SuperSU and whether there were any issues. I have a couple of apps that check for root and will not run if detected. In the past (ran rooted S3s for the past 3.5 years), I have just been able to turn it off to use the apps and then turn it back on with no issues, but like everyone else am still learning the ins and outs of the Pixel. I am running a Verizon Pixel XL and a non-XL (wife's phone). Both are bootloader unlocked and rooted running NDE63P. I have not had time to update to NDE63X or install TWRP yet, not that any of hat matter to the original question.
Click to expand...
Click to collapse
Are you running a custom kernel?
The reason I ask is because I havent tried the method you mentioned but if it turns out it doesnt work for you, I would suggest flashing(reflashing) a custom kernel because that will knock out root, then boot back into the bootloader and boot to root again.
On second thought I think I missed your intent though, Im thinking more in terms of like Snapchat which checks for root only at login (so if you logged in before rooting you will continue to be good after) as opposed to apps that check every time the app is ran. Disregard if this is not helpful.
I want to say the unroot option in the app didn't work but that may have only been for the earlier releases that were pixel compatible.
pcriz said:
Are you running a custom kernel?
The reason I ask is because I havent tried the method you mentioned but if it turns out it doesnt work for you, I would suggest flashing(reflashing) a custom kernel because that will knock out root, then boot back into the bootloader and boot to root again.
On second thought I think I missed your intent though, Im thinking more in terms of like Snapchat which checks for root only at login (so if you logged in before rooting you will continue to be good after) as opposed to apps that check every time the app is ran. Disregard if this is not helpful.
I want to say the unroot option in the app didn't work but that may have only been for the earlier releases that were pixel compatible.
Click to expand...
Click to collapse
Your are correct in your second thought. Not a Snapchat type issue, but a check each time the app runs. FWIW though , not a custom kernel but I laughed at the thought of flashing one and re-rooting each time I needed to run the apps in question
sliding_billy said:
Your are correct in your second thought. Not a Snapchat type issue, but a check each time the app runs. FWIW though , not a custom kernel but I laughed at the thought of flashing one and re-rooting each time I needed to run the apps in question
Click to expand...
Click to collapse
I'll say though if that ends up being the path you take, to unroot and root, you should look into TWRP because at least that way you won't need a computer to fastboot the boot-to-root.img, you can just flash the SU zip.
pcriz said:
I'll say though if that ends up being the path you take, to unroot and root, you should look into TWRP because at least that way you won't need a computer to fastboot the boot-to-root.img, you can just flash the SU zip.
Click to expand...
Click to collapse
Oh yeah. I have been using TWRP for many years. Just waiting for the dust to settle a little on the process of getting from where I am now to using TWRP and finding a suitable custom ROM with a current base.
sliding_billy said:
Oh yeah. I have been using TWRP for many years. Just waiting for the dust to settle a little on the process of getting from where I am now to using TWRP and finding a suitable custom ROM with a current base.
Click to expand...
Click to collapse
I can't see the initial process of loading it changing. Right now there are issues with restoring but if you don't make a back up it won't affect a thing but it will make flashing mods and updates to the TWRP easier.
Aside from using a tool kit, installing it seems to be spot on so long as all the steps are followed.
So once a stable build comes out I will simply flash in the TWRP I currently have.
So I rooted my Fire TV when it first came out. Later I gave the device to my sister so we could have Playstation Vue in multiple rooms in the house. Since then it looks like the device was updated to 5.2.1.1 and I lost root. Now my Vue app wont open and I figure it's because I need to update the OS version.
From what I understand, I can't root it again with that OS version. Instead, how do I safely update the box? I blocked automatic updates and completely forgot how. I've read that factory reset is a bad idea, so I don't plan on doing that.
Was the bootloader fully unlocked? TWRP should still be on there, yes?
Sizzlechest said:
Was the bootloader fully unlocked? TWRP should still be on there, yes?
Click to expand...
Click to collapse
I can't really remember about the bootloader since it's been so long. I do still have TWRP installed.
Also, I did find my old files that I believe I used back then, and I have a aftv-full-unlock. So, my bootloader was probably fully unlocked?
If you have TWRP installed, flash the latest zip from
https://forum.xda-developers.com/fire-tv/development/prerooted-stock-images-t2882337