So I just purchased a Fire Stick 4k, and happily learned that you can unlock it! But I've been out of the custom ROM/Root/Bootloader Unlock scene for a few years. So I'm hoping you fine folks that have experience with these Fire Stick devices might be able to reassure me that I understand the guides correctly.
I've read the [UNLOCK][ROOT][TWRP][UNBRICK] Fire TV Stick 4K (mantis) guide.
I've also read the [NEWBIE GUIDE] How to Unlock Bootloader/Root and install Addons FireStick 4k.
All of the following questions assume I'm starting with a Fire Stick straight out of the packaging, brand new:
Am I correct that after running kamakiri successfully, I'll have an unlocked bootloader allowing me to use fastboot? After it's unlocked, how do you actually get it into fastboot mode? Do you always have to boot first, and then run adb reboot bootloader?
The procedure to boot into TWRP is simply connecting a USB OTG cable? If one is detected, you'll get a prompt on boot to enter TWRP?
How does one update TWRP? Unlike for phones, I can't seem to find a thread anywhere for TWRP development for this device, nor can I find an official build at twrp.me.
The newbie guide talks about installing a pre-rooted stock ROM then disabling OTA immediately. But the unlock guide says that this exploit can't be patched out. So would it be better to go through the initial setup and let Amazon OTA the device to latest, then run kamakiri, install Magisk, and then disable OTA? Would that be effectively the same as installing a pre-rooted stock ROM?
I don't understand the Amazon FireOS versioning scheme. I see that the prerooted stock ROM has a version number of 6.2.7.1_r1, while this thread has a version of 6.2.7.1 (2495_00035909630). Does the prerooted ROM have all these extra APK's already installed? Do I have to install these extra apks after installing the prerooted ROM?
Does Amazon do monthly security updates like Google does for Pixel devices? How does one keep the ROM up to date after Amazon releases an OTA?
Mogul345 said:
So I just purchased a Fire Stick 4k, and happily learned that you can unlock it! But I've been out of the custom ROM/Root/Bootloader Unlock scene for a few years. So I'm hoping you fine folks that have experience with these Fire Stick devices might be able to reassure me that I understand the guides correctly.
I've read the [UNLOCK][ROOT][TWRP][UNBRICK] Fire TV Stick 4K (mantis) guide.
I've also read the [NEWBIE GUIDE] How to Unlock Bootloader/Root and install Addons FireStick 4k.
All of the following questions assume I'm starting with a Fire Stick straight out of the packaging, brand new:
Am I correct that after running kamakiri successfully, I'll have an unlocked bootloader allowing me to use fastboot? After it's unlocked, how do you actually get it into fastboot mode? Do you always have to boot first, and then run adb reboot bootloader?
The procedure to boot into TWRP is simply connecting a USB OTG cable? If one is detected, you'll get a prompt on boot to enter TWRP?
How does one update TWRP? Unlike for phones, I can't seem to find a thread anywhere for TWRP development for this device, nor can I find an official build at twrp.me.
The newbie guide talks about installing a pre-rooted stock ROM then disabling OTA immediately. But the unlock guide says that this exploit can't be patched out. So would it be better to go through the initial setup and let Amazon OTA the device to latest, then run kamakiri, install Magisk, and then disable OTA? Would that be effectively the same as installing a pre-rooted stock ROM?
I don't understand the Amazon FireOS versioning scheme. I see that the prerooted stock ROM has a version number of 6.2.7.1_r1, while this thread has a version of 6.2.7.1 (2495_00035909630). Does the prerooted ROM have all these extra APK's already installed? Do I have to install these extra apks after installing the prerooted ROM?
Does Amazon do monthly security updates like Google does for Pixel devices? How does one keep the ROM up to date after Amazon releases an OTA?
Click to expand...
Click to collapse
After completing that procedure, you will have TWRP installed. You will also be able to use fastboot. AFAIK, running "adb reboot bootloader" is the only way to get into fastboot. However, the firestick always boots into TWRP. You will have 5 seconds to cancel the reboot from TWRP to system.
I know of no way to update TWRP. The TWRP version installed is not an official build.
I don't use the prerooted ROMs, so I can't answer questions on them, nor on updates. Personally, I don't want to receive updates, so I just ran the procedure, installed Magisk, and ran this de-bloat script.
https://github.com/esc0rtd3w/firestick-loader/blob/master/scripts/debloat/bloat-disable.sh
Amazon does not do monthly security updates.
dcarvil said:
After completing that procedure, you will have TWRP installed. You will also be able to use fastboot. AFAIK, running "adb reboot bootloader" is the only way to get into fastboot. However, the firestick always boots into TWRP. You will have 5 seconds to cancel the reboot from TWRP to system.
I know of no way to update TWRP. The TWRP version installed is not an official build.
Click to expand...
Click to collapse
Thanks for clearing that up that it always boots into recovery first. And I guess if you can't update TWRP, probably no reason to boot into the bootloader.
dcarvil said:
Amazon does not do monthly security updates.
Click to expand...
Click to collapse
Well, this thing is definitely getting put into the IoT network then. I wonder if they backport any security updates at all. I know this version of Fire OS is based on Nougat, and Google isn't maintaining it anymore.
dcarvil said:
I don't want to receive updates, so I just ran the procedure, installed Magisk, and ran this de-bloat script.
https://github.com/esc0rtd3w/firestick-loader/blob/master/scripts/debloat/bloat-disable.sh
Click to expand...
Click to collapse
Before you ran the procedure, did you run the initial setup and enable ADB on the Fire Stick? I see conflicting info on whether or not to setup the stick prior to running kamakiri in the newbie guide thread.
Mogul345 said:
Before you ran the procedure, did you run the initial setup and enable ADB on the Fire Stick? I see conflicting info on whether or not to setup the stick prior to running kamakiri in the newbie guide thread.
Click to expand...
Click to collapse
Yes, I did initial setup and enabled ADB. I'm not sure, but I suspect enabling ADB is required.
Related
A coworker gave me a rooted (towelroot) fire TV sw version 51.1.0.1_user_510055620. After I hooked it up to my WiFi and registered it with my account there's no apps on it and it won't allow me to download Netflix. What is my next step? How do I get this thing up and running?
PrO... said:
A coworker gave me a rooted (towelroot) fire TV sw version 51.1.0.1_user_510055620. After I hooked it up to my WiFi and registered it with my account there's no apps on it and it won't allow me to download Netflix. What is my next step? How do I get this thing up and running?
Click to expand...
Click to collapse
Do you know if CWM is installed? Im thinking the netflix available on Amazon is incompatible with your old firmware.
Basically, i youre going to want to update to one of rbox's prerooted firmware versions. Its not hard but you do need to follow the guides carefully. Best bet is to go to aftvnews. He breaks it down really well.
I'm not sure. How do I check? I also need to update the xbmc to kodi (I've started to search!)
So far I've only been able to unlock the bootloader but I can't push the recovery.img for some reason. I hope there's an easier way by now. Lol
PrO... said:
So far I've only been able to unlock the bootloader but I can't push the recovery.img for some reason. I hope there's an easier way by now. Lol
Click to expand...
Click to collapse
just follow this guide up to the point of your existing software and then update to the latest custom rom by rbox.
http://www.aftvnews.com/start/
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.
Hey all,
I own a FireTV 1st Gen with Software Version 51.1.4.0 which is not rootable but can be bootloader unlocked (if it was rooted).
This thing was never actually used because I didnt want to risk it beeing updated and loosing the ability to root and/or bootloader unlock... (this Software is the one with which it was shipped..)
I also own a FireTV Stick which is upgraded to 5.0.5 and rooted with kingroot.
I need some advice what to do with the 1st gen FireTV - I could update it to 5.0.5 and root with kingroot, but then it would also update the bootloader to be not unlockable, right?!
I also have that eMMC Adapter but couldnt bring myself to attempt to do the soldering root method - but actually that would be best or? Then I could unlock the bootloader, and install custom recovery..
Or might there become a way available to have custom recovery on the 5.0.5 version without prior bootloader unlock?
Halp please!
zroice said:
Hey all,
I own a FireTV 1st Gen with Software Version 51.1.4.0 which is not rootable but can be bootloader unlocked (if it was rooted).
I also own a FireTV Stick which is upgraded to 5.0.5 and rooted with kingroot.
I need some advice what to do with the 1st gen FireTV - I could update it to 5.0.5 and root with kingroot, but then it would also update the bootloader to be not unlockable, right?!
I also have that eMMC Adapter but couldnt bring myself to attempt to do the soldering root method - but actually that would be best or? Then I could unlock the bootloader, and install custom recovery..
Or might there become a way available to have custom recovery on the 5.0.5 version without prior bootloader unlock?
Halp please!
Click to expand...
Click to collapse
I'm going to release recovery for both locked and unlocked Fire TV 1. The big difference being if you brick an unlocked unit, you can boot straight to recovery and fix it. If you brick a locked one, you're pretty much hosed.
rbox said:
I'm going to release recovery for both locked and unlocked Fire TV 1. The big difference being if you brick an unlocked unit, you can boot straight to recovery and fix it. If you brick a locked one, you're pretty much hosed.
Click to expand...
Click to collapse
thx for the reply.
Can unlocked bootloader be kept unlocked even with update to 5.0.5? Or does the new version require the new not unlockable bootloader?
Only way to unlock would be to hardware root the one I have or is there any other way? (with the 51.1.4.0 software)
zroice said:
thx for the reply.
Can unlocked bootloader be kept unlocked even with update to 5.0.5? Or does the new version require the new not unlockable bootloader?
Only way to unlock would be to hardware root the one I have or is there any other way? (with the 51.1.4.0 software)
Click to expand...
Click to collapse
Yes. If it's unlocked it will stay unlocked.
I believe there is a way to enter the unlock code through fastboot. One of the Amazon tablet devices uses that for their unlock. I don't remember which device it is though.
rbox said:
Yes. If it's unlocked it will stay unlocked.
I believe there is a way to enter the unlock code through fastboot. One of the Amazon tablet devices uses that for their unlock. I don't remember which device it is though.
Click to expand...
Click to collapse
but amazon is not giving those out isnt it? =)
zroice said:
but amazon is not giving those out isnt it? =)
Click to expand...
Click to collapse
The tablet that uses that for their unlock has a program to generate the unlock codes. It's similar to my unlock, but it runs on your computer to generate the code versus my unlock that runs on the device.
but to run yours the thing has to be rooted 1st correct? So basically if I really want an unlocked bootloader i better do the hardware root ..? (sorry if those questions are noobish hehe)
zroice said:
but to run yours the thing has to be rooted 1st correct? So basically if I really want an unlocked bootloader i better do the hardware root ..? (sorry if those questions are noobish hehe)
Click to expand...
Click to collapse
Yes, mine requires root.
@rbox, has anything been learned about a custom recovery for the fire sticks now that we have root access?
zroice said:
but to run yours the thing has to be rooted 1st correct? So basically if I really want an unlocked bootloader i better do the hardware root ..? (sorry if those questions are noobish hehe)
Click to expand...
Click to collapse
No. Not a hardware root. Just wait on the @rbox prerooted software rom for the Fire TV/Stick. And shortly after that AFTVnews will provide an extensive how to root guide. Just be patient and you will eventually have a rooted/unlocked Fire TV/Stick.
BreakingDroid said:
@rbox, has anything been learned about a custom recovery for the fire sticks now that we have root access?
Click to expand...
Click to collapse
I'm trying to get recovery for FireTV1 working, before I work on the stick. The problem is if I brick the stick, it's game over. I'm trying to find all the ways that I can brick it while working on the FireTV1, so I don't do it with the stick.
mjbxx said:
No. Not a hardware root. Just wait on the @rbox prerooted software rom for the Fire TV/Stick. And shortly after that AFTVnews will provide an extensive how to root guide. Just be patient and you will eventually have a rooted/unlocked Fire TV/Stick.
Click to expand...
Click to collapse
hmmm but didnt I read that once you update the bootloader unlock is no longer possible?
I got the FireTV with old software still which accoding to atfnews is not rootable but bootloader unlockable.
I read that once you update that the eFuse thing will become active and prevent unlock attempts.
All in all I just need to know if I should update the 1st Gen from the current " 51.1.4.0" build to the latest one to get root, disable OTA etc and still be able to unlock bootloader and boot directly to a recovery or if it would needed to be hardware rooted in order to do that. (to prevent the bootloader update.. which activates the efuse)
zroice said:
Hey all,
I own a FireTV 1st Gen with Software Version 51.1.4.0 which is not rootable but can be bootloader unlocked (if it was rooted).
This thing was never actually used because I didnt want to risk it beeing updated and loosing the ability to root and/or bootloader unlock... (this Software is the one with which it was shipped..)
I also own a FireTV Stick which is upgraded to 5.0.5 and rooted with kingroot.
I need some advice what to do with the 1st gen FireTV - I could update it to 5.0.5 and root with kingroot, but then it would also update the bootloader to be not unlockable, right?!
I also have that eMMC Adapter but couldnt bring myself to attempt to do the soldering root method - but actually that would be best or? Then I could unlock the bootloader, and install custom recovery..
Or might there become a way available to have custom recovery on the 5.0.5 version without prior bootloader unlock?
Halp please!
Click to expand...
Click to collapse
rbox said:
I believe there is a way to enter the unlock code through fastboot. One of the Amazon tablet devices uses that for their unlock. I don't remember which device it is though.
Click to expand...
Click to collapse
rbox is right. You can unlock the bootloader of a 1st-gen Fire TV using only an A-to-A usb cable. Although I'm not sure if it works on 51.1.4.0. I think it requires 51.1.0.2 or older.
I was going to write a guide, but the python script to generate the unlock code/file has been taken down, and it was really only useful for those who bricked with a locked bootloader, so I didn't try to find the script. Pretty sure the script was called cublock.py from here.
Assuming you can get ahold of the script, and it works on your software version, you would connect an A-to-A usb cable and reboot into fastboot by connecting via ADB and running
Code:
adb reboot fastboot
then run
Code:
fastboot devices
to ensure you're in fastboot and connected, then run
Code:
fastboot oem emmc-info
to get a code that you need for the python script. The code is in the form
Code:
(bootloader) 0x12345678
and you use the python script to generate the unlock code like this
Code:
./cublock.py 56 12345678
That will generate an unlock file which you then use as follows:
Code:
fastboot flash unlock /path/to/file.unlock
After that, you can use fastboot to flash custom recovery if you'd like. Instructions are at the bottom of this guide under the "Repair Recovery with Fastboot Mode" section. I've attached a screenshot of the process from my notes for the unwritten guide, back when I tried it.
ill try that - thanks very much
what driver to use for fastboot mode?
zroice said:
what driver to use for fastboot mode?
Click to expand...
Click to collapse
I'm not sure which Windows drivers to use. My Mac didn't need any.
This should help concerning Windows ADB/Fastboot drivers:
http://forum.xda-developers.com/showthread.php?t=2317790
http://forum.xda-developers.com/kin...tools-create-unlock-img-fix-boot-img-t3050689
Tools.zip package from this post includes the cublock.py file
ARGH that sob Fire TV.. Cannot root the damn thing in current stage with Kingroot and cant get my PC(s) to connect to fastboot.
My flashing PC which has all sorts of drivers installed only detects it as ADB device - "fastboot devices" doesnt work. And my Laptop does recognize it as "Fire TV" with no drivers installed in fastboot mode.
I need help to get that damn fastboot goin please. On the PC I forced driver install of some "universal" fastboot drivers but it still wont show up in fastboot devices (to get the info needed for the python script..). No idea why the pc thinks its an adb device when connected in fastboot mode.. (adb doesnt work in that stage either...)
Downgrading & Bootloader unlocking after updating to 5.0.5 probably wont work, right? Because the bootloader cannot be downgraded I guess..
zroice said:
ARGH that sob Fire TV.. Cannot root the damn thing in current stage with Kingroot and cant get my PC(s) to connect to fastboot.
My flashing PC which has all sorts of drivers installed only detects it as ADB device - "fastboot devices" doesnt work. And my Laptop does recognize it as "Fire TV" with no drivers installed in fastboot mode.
I need help to get that damn fastboot goin please. On the PC I forced driver install of some "universal" fastboot drivers but it still wont show up in fastboot devices (to get the info needed for the python script..). No idea why the pc thinks its an adb device when connected in fastboot mode.. (adb doesnt work in that stage either...)
Downgrading & Bootloader unlocking after updating to 5.0.5 probably wont work, right? Because the bootloader cannot be downgraded I guess..
Click to expand...
Click to collapse
P.S: I could try to boot linux from USB if that helps - but that probably also needs some sort of drivers doesnt it?
Hey guys,
we had a nice Fire TV 4K sale here in Germany and so I got that little box. However, now I am a bit confused and I hope that you could help me out.
Shall I update the box?
I learned that I need to root the Box in order to be able to connected my external HDD that is formated with NTFS. That is because originally the Fire TV does not support NTFS. I also learned that getting root is still possible with the newest two fireware versions but way more complicated because you need a A-to-A USB cable.
Of course I could block updates and just root the firmware that is currently installed. But I learned that Kodi is way better integrated into the interface of the newer firmwares. Is it possible to root the old firmware, do an OTA update and still have root on the newest firmware?
Since there are several firmwares out there. Is there any best firmware version that you recommend?
wohltat said:
Hey guys,
we had a nice Fire TV 4K sale here in Germany and so I got that little box. However, now I am a bit confused and I hope that you could help me out.
Shall I update the box?
I learned that I need to root the Box in order to be able to connected my external HDD that is formated with NTFS. That is because originally the Fire TV does not support NTFS. I also learned that getting root is still possible with the newest two fireware versions but way more complicated because you need a A-to-A USB cable.
Of course I could block updates and just root the firmware that is currently installed. But I learned that Kodi is way better integrated into the interface of the newer firmwares. Is it possible to root the old firmware, do an OTA update and still have root on the newest firmware?
Since there are several firmwares out there. Is there any best firmware version that you recommend?
Click to expand...
Click to collapse
not sure if this will help.
http://www.aftvnews.com/everything-you-need-to-know-about-usb-storage-with-the-amazon-fire-tv/
You could go with either the latest 5.0.5.1 or with 5.0.5. I personally use 5.0.5 because I like using Firestarter to access all my sideloaded apps. Until Firestarter is officially updated by the programmer, you could use Firestopper which has been updated to work on 5.0.5.1.
I also wirelessly transfer movies to my external hard drive which is an NTFS drive so that I can have HD video. I have use the Kingroot method and the USB cable method. I'd also recommend aftvnews.com for guides as they are a great resource (especially for windows users). I also have guides for Mac users over at marksmods.com
How can I install the 5.0.5, I am still on the 5.0.3.1 and I guess the 5.0.5 would be better for me (used it on my aftv stick before) autoupdates will probably lead me to 5.0.5.1, which I try to avoid due to firestarter and sky go
shaDNfro said:
How can I install the 5.0.5, I am still on the 5.0.3.1 and I guess the 5.0.5 would be better for me (used it on my aftv stick before) autoupdates will probably lead me to 5.0.5.1, which I try to avoid due to firestarter and sky go
Click to expand...
Click to collapse
http://www.aftvnews.com helped me a lot. You root with kingroot, install recovery, install prerooted 5.0.5.1. Just follow their instructions.
wohltat said:
http://www.aftvnews.com helped me a lot. You root with kingroot, install recovery, install prerooted 5.0.5.1. Just follow their instructions.
Click to expand...
Click to collapse
Thx for your reply, I checked that page. But what I really want is the following:
I am currently under 5.0.3.1 original and I want to have 5.0.5 (not 5.0.5.1), but without root! (SkyGo does not run on rooted devices, if it detects root).
I could perform OTA update --> would lead me to 5.0.5.1
What I really want is a way to push the official 5.0.5 to my aftv (best withoug kingrooting, due to the fact you need a full whipe, wich may also then give problems to my sky go accounts, which are limmited).
Is there some way to get an official rom, which I then can push via adb or put it on my aftv, that the aftv detects it and installs it ?
(I can still block the ota update after I am on 5.0.5)...
Bests,
shaDN
Is no one providing the original rom? However, in order to install it, you would need to root and install a recovery first anyways. Just instead of installing a prerooted rom you would install a not rooted one.
hmm, there must be a way to place an update somewhere on the aftv, that the aftv recognizes it as an official update and install it...
just installed 5.0.4, then 5.0.5 then unplugged lan and blocked updates
I love the new update routine
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