[UNLOCK][ROOT][TWRP][UNBRICK] FireTV 2 (sloane)

Search This thread

Sus_i

Senior Member
Apr 9, 2013
1,605
690
I've just set up a new sloan with latest update, magisk and a couple of other apps. I can't stand all the bloat. Please give me a hint on where I might find a custom launcher or other apk that will allow me to disable some of the bloatware. I'll be forever indebted. Thanks.
lol, have pushed the update on sdcard, but was too lazy to install it. I guess I'll skip it then ;)

Idk which launcher is currently the best, but in this thread you probably find the answer.
If not, ask SweenWolf or Finnzz
 
I've just set up a new sloan with latest update, magisk and a couple of other apps. I can't stand all the bloat. Please give me a hint on where I might find a custom launcher or other apk that will allow me to disable some of the bloatware. I'll be forever indebted. Thanks.
Hello,
On my sloane i installed ATV launcher Pro. then settings apk by Hoffi (com.markus.settings apk) to access firetv settings as sloane is stubborn once you start disabling launchers on latest firmwares due to adb / accessibility permission revocations.
So you have to play around with different launchers and configs.
I then installed the frowned upon 'luckypatcher' which is actually really good for viewing what apks do what and allowing you to disable/enable with ease.

Once i had installed ATV launcher i used luckypatcher to disable com.amazon.tv.launcher followed by com.amazon.firehomestarter a few seconds after.

I then set about diaabling the usual bloat from the /System/priv-app folder such as 'shopping' 'ags app' 'hedwig-news'.

OFC there is adb you can also use to disable the bloat but i use this luckypatcher as it gives a clearer view to what's on your device. You can also block ads and edit the host file etcetera etcetera. If you need any assistance let me know.


Regards
 
Last edited:

LocoMexican

Senior Member
Mar 12, 2017
116
31
OK, where can I find an "apk" for atv launcher pro? I'm more than happy to pay the $2.99 fee, but it won't d/l to my computer as a apk. Otherwise, I have the "settings" apk and the frowned on "Lucky Patcher" apk as well as the "free" version of atv launcher. And, I have successfully gotten rid of several system apps such as news, free time, photos, voice recorder, and several others. All I need to be a happy camper is the pro version of atv launcher. Suggestions are appreciated. Thanks for the help.
 

LocoMexican

Senior Member
Mar 12, 2017
116
31
Finally got apk for ATV Launcher Pro, but it doesn't seem to want to work. Has anyone had trouble loading up this apk? If so, what is the trick? Thanks for suggestions.
 

LocoMexican

Senior Member
Mar 12, 2017
116
31
You're most likely right. I found the apk and tried to install it after I de-bloated the device. I probably deleted a service necessary to run the app. Sooooooo, I'm going to unblock updates, let the unti complete the update, and then try again. I can always de-bloat again. Thanks for the idea.
 

fleisch80

Senior Member
Oct 29, 2015
74
2
Amazon Fire TV
Amazon Fire
Hi friend .
I was wondering , to install any rom below 5.2.6 what would I need to do for the flash to be
Successful.


I really want a rom like 5.0.1 back with the old interface , and I don't understand why
the flash is not taking .

Did Amazon in fact use an efuse that was triggered buy an update to prevent the older
os and gui from ever being reinstalled ? .


Any guidance is greatly appreciated .


Thanks so much .





Cf.
 

LocoMexican

Senior Member
Mar 12, 2017
116
31
Hi friend .
I was wondering , to install any rom below 5.2.6 what would I need to do for the flash to be
Successful.

Any guidance is greatly appreciated .
Not being an expert, I would try this:

1. Use the "short" (brick) method.
2. Run gpt-fix.sh. This should put you into TWRP.
3. Using TWRP, install Amonet-Sloane v1.1.
4. Using TWRP, "format" (not wipe) data.
5. Using TWRP, install your stock (not pre-rooted) ROM.
6. (a) If you want superuser permissions, using TWRP, install Magist.
(b) If you do not want superuser permissiions, do not run Magist.
7. Re-boot system.
8. Block updates.

If you want to revert to straignt stock, try this:

1. Use the "short" (brick) method.
2. Run gpt-fix.sh. This puts you into TWRP.
3. Using TWRP, "format" (not wipe) data.
4. Using TWRP, install the stock ROM of your choice.
5. Reboot system.
6. Block updates.

Not sure if any of his will work, but maybe you will have "success". Good luck.
 
  • Like
Reactions: Sus_i

vrl2

Senior Member
Feb 2, 2008
61
9
New Haven, CT
Hello all,

Thanks for maintaining this rom! I'm writing because I was successfully running the rooted rbox rom for years. However, I did not boot up my AFTV for a few months. I turned it on this week and experienced the following boot loop: Amazon logo against a white background, turning on and off, with a blinking light.

To fix this, I opened up my FireTV box and after successfully shorting it, ran both bootrom-step.sh and fastboot-step.sh. Although the AFTV2 didn't immediately boot into recovery, I then ran boot-recovery.sh and finally my AFTV was in TWRP (please see screenshots initial_success_twrp.jpeg and initial_success_preloader.jpeg).

Unfortunately, I have not been able to get back into TWRP. Once I got into TWRP through the steps above, I wiped (using the option to type in 'yes') and rebooted into recovery. Since then, I have been in a new boot loop - this time, there is no Amazon flash screen. The light turns on and off.

When I try to re-run the bootrom-step.sh, I keep getting the same input/output error (please see the attached log bootrom_io_error.png).

Also, now when I run boot-recovery.sh, it seems to get through the process without error but I still cannot get to recovery (please see the attached log boot_recovery_error.png). The same thing happens with boot-fastboot.sh. From dmesg (also attached as a screenshot) the USB device seems to come on in preloader mode and then turn off.

Any guidance would be much appreciated. Thank you.
 

Attachments

  • initial_success_twrp.jpeg
    initial_success_twrp.jpeg
    2.9 MB · Views: 20
  • initial_success_preloader.jpeg
    initial_success_preloader.jpeg
    2.2 MB · Views: 16
  • dmesg_preloader_error.jpeg
    dmesg_preloader_error.jpeg
    3.1 MB · Views: 16
  • boot_recovery_error.png
    boot_recovery_error.png
    108.6 KB · Views: 12
  • bootrom_io_error.png
    bootrom_io_error.png
    581.4 KB · Views: 14
Last edited:

vrl2

Senior Member
Feb 2, 2008
61
9
New Haven, CT
The confusing part is that bootrom-step.sh from amonet-sloane-v1.1 worked initially, and after running fastboot-step.sh from the same package, I was able to get into TWRP.

However, after performing a wipe within TWRP (the option that requires typing 'yes') I get nothing but a blank screen and a flashing light.

Should I:
  1. Start over and try shorting it again and running bootrom-step.sh from amonet-sloane-v1.0.0 or amonet-sloane-v1.0.1 or amonet-sloane-v1.3? Or
  2. Will I eventually get over the I/O error if I keep re-trying to short it and re-run bootrom-step.sh from the v1.1 package?
  3. Is there another option that does not require repeating the short?

I'm just trying to understand why bootrom-step.sh worked initially, but now consistently gives the I/O error.

Thank you.
 

LocoMexican

Senior Member
Mar 12, 2017
116
31
Using the short method, make sure you are making good contact with the correct spot on the chip. With the short in place, and everything else connected to the unit and ready to go, power the unit (plug it in) and wait a few seconds. If the unit's power light comes on (lights up) then you do not have a good short. Unplug the unit and readjust the short contact and power up again. Keep doing this trial and error until you can power up the unit and the power light does not come on. Next, run your script on the computer such that it says "waiting for boot rom" and then, plug your usb to usb into your computer (it should already be plugged into your sloan device). Your computer screen should react with "remove short", at which poiint you remove the short. The script should run from there. Your problem may very well be more involved than this, but this is what i would try first. Remeber, when you first power up the unit, the power light should not come on if you have a good short on the correct spot of the chip.

Once you are in TWRP, Install amonet 1.01. After you install amonet 1.01, be sure you FORMAT (not wipe) the data. Then, click on Install, and install the sloane version of your choice. Finally, install Magist v23 if you want adminstrative privleges. Reboot system and you should be good to go. Good luck.

Hope this helps.
 
  • Like
Reactions: vrl2

vrl2

Senior Member
Feb 2, 2008
61
9
New Haven, CT
Using the short method, make sure you are making good contact with the correct spot on the chip. With the short in place, and everything else connected to the unit and ready to go, power the unit (plug it in) and wait a few seconds. If the unit's power light comes on (lights up) then you do not have a good short. Unplug the unit and readjust the short contact and power up again. Keep doing this trial and error until you can power up the unit and the power light does not come on. Next, run your script on the computer such that it says "waiting for boot rom" and then, plug your usb to usb into your computer (it should already be plugged into your sloan device). Your computer screen should react with "remove short", at which poiint you remove the short. The script should run from there. Your problem may very well be more involved than this, but this is what i would try first. Remeber, when you first power up the unit, the power light should not come on if you have a good short on the correct spot of the chip.

Once you are in TWRP, Install amonet 1.01. After you install amonet 1.01, be sure you FORMAT (not wipe) the data. Then, click on Install, and install the sloane version of your choice. Finally, install Magist v23 if you want adminstrative privleges. Reboot system and you should be good to go. Good luck.

Hope this helps.
Thank you for your help!
Yes, I am certain that the light is off when the short is in place .Looks like the short is working . I have run it 15-20 times now. When I run bootrom-step.sh, it no longer works despite the initial successful run.

Sometimes I get to the point where I get the prompt to remove the short -- but it doesn't get much further. If I can get past the handshaking phase, then the furthest it gets is to "Check GPT" at which point it stalls at "Check GPT" with this EMMC read error:

"File "/home/ubuntu/Desktop/amonet/modules/common.py", line 199, in emmc_read"

It often stalls earlier (usually at either "waiting for bootrom" or if it gets past that, it stalls at "Clear preloader header" or "Init Crypto Engine")

Thanks.
 

Attachments

  • Screen Shot 2022-04-25 at 8.36.39 PM.png
    Screen Shot 2022-04-25 at 8.36.39 PM.png
    503.1 KB · Views: 7
Last edited:

LocoMexican

Senior Member
Mar 12, 2017
116
31
You might try a different usb port on your computer. Make sure you have your computer's environment set up as described. Also, you might want to try using the gpt-fix in v.1.3. If gpt-fix runs, it should put you into TWRP and you can install from there. Good luck.
 

LocoMexican

Senior Member
Mar 12, 2017
116
31
My device took an update this p.m. Now has OS 5.2.8.8 (676742620). Had to adb reboot recovery and re-install Magist v23. Everything looks good, except now I have to de-bloat again. I guess practice makes perfect.
 
  • Like
Reactions: Sus_i

LocoMexican

Senior Member
Mar 12, 2017
116
31
My device took an update this p.m. Now has OS 5.2.8.8 (676742620). Had to adb reboot recovery and re-install Magist v23. Everything looks good, except now I have to de-bloat again. I guess practice makes perfect.
Also, I was finally able to capture the update url using logcat. After piecing things together, this is what I came up with if anyone wants to try it.

 
  • Like
Reactions: dcellini21

testbankbuddy

New member
May 13, 2022
3
1
Yes, it will work just fine. Make sure to read both the first and the second post.
If you already have rbox's TWRP, you can just flash the ZIP with it.​
My version is 5.2.8.8, unrooted. can you downgrade unrooted firetv? Or carry on with this guide without a root prior to this tutorial since my version is too high.

Is it possible to downgrade unrooted firetv 2 sloane
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    My daughter's device took an update three days ago. I needed to install an new apk, and when I went to check that "developers options" was correctly checked so I could install apk from unknown sources, I couldn't find "Developers Options" anywhere on the device? I think the new update removed that option from the settings menu. Any ideas on what happened to developers options? Your thoughts are appreciated.
    It's still there, it's just hidden now like regular android devices


    A short guide to unhide it:
    1
    Tried this out. Works fine. Thanks for the info.
  • 10
    Read this whole guide before starting.

    This is for the 2nd gen Fire TV (sloane)

    Current relase: amonet-sloane-v1.1

    NOTE: This process does not require you to open your device if you're already rooted or you have TWRP.
    NOTE: If something goes horribly wrong and your device gets bricked, you'll have to open it and unbrick it through bootrom (post 2).
    NOTE: This process will modify the partition-table (GPT) of your device.

    NOTE: Your device will be reset to factory defaults (including internal storage) during this process.
    NOTE: Flashing prerooted ROM will disable unlocked TWRP. It's recommended to flash an stock update.bin
    until that gets sorted out.

    To update to the current release if you are already unlocked, just flash the zip in TWRP.

    What you need:
    • A Linux installation or live-system
    • A a-a cable
    1. Download the attached zip-file "amonet-sloane-v1.1zip".
    2. Copy the zip-file to the internal storage of the box or copy the zip-file to an external SD/USB storage and connect it to the box.
    3. Reboot the FireTV to rbox's TWRP recovery and flash the zip-file.

    NOTE: If you are on firmware 5.2.7.3 or newer, a downgrade is necessary, this requires bricking the device temporarily. (The screen won't come on at all)
    If you chose the brick option, you need to continue with bootrom-step-minimal.sh:




    NOTE: Please refer to the #2 post on how to prepare your environment before proceeding.
    NOTE: If you use this method to unlock the device you don't need to flash the unlock-zip once you're in TWRP.

    Once the zip-file finished flashing, disconnect the device and run:
    Code:
    sudo ./bootrom-step-minimal.sh
    Then plug the device back in.

    The device will reboot to hacked fastboot mode (Static Amazon White Logo + white blinking LED).
    Then run:
    Code:
    sudo ./fastboot-step.sh


    After that, the device will reboot to unlocked TWRP. Then go to Wipe > Format Data and type "YES".
    You can now install Magisk from there.

    Important information

    NOTE: This has nothing to do with the unlock process.

    You have 10 seconds to force TWRP to keep ADB over USB active by using
    Code:
    adb wait-for-recovery && adb shell setprop twrp.usb.mode 0

    In the new partitioning scheme your boot/recovery-images will be in boot_x/recovery_x respectively, while boot/recovery will hold the exploit.
    TWRP takes care of remapping these for you, so installing zips/images from TWRP will work as expected.

    Don't flash boot/recovery images from FireOS (FlashFire, MagiskManager etc.) (If you do anyway, make sure you flash them to boot_x/recovery_x)

    Should you accidentally overwrite the wrong boot, but your TWRP is still working, rebooting into TWRP will fix that automatically.

    TWRP will prevent updates from overwriting LK/Preloader/TZ, so generally installing an update should work without issues (only full updates, incremental updates won't work).

    For ROM developers there is still an option to overwrite these, which should only be done after thorough testing and if needed (LK should never be updated).

    It is still advised to disable OTA.

    Very special thanks to @k4y0z and @t0x1cSH for making all this possible by porting the LK exploit to sloane and implementing the RPMB-key derivation for sloane.
    Special thanks also to @xyz` for making all this possible and releasing the original amonet exploit for karnak.
    Special thanks also to @retyre for porting the bootrom-exploit to mt8173.
    Special thanks also to @Sus_i and @DanielF50 for testing.
    Special thanks also to @diplomatic for his wonderfull mtk-su, allowing you to unlock without opening the device.
    5
    I would advise you pull your ROM's boot.img, patch it with MagiskManager & then flash this manually via hacked fastboot, otherwise it won't work & you'll probably brick your device again.

    Don't worry, magisk flashing in TWRP works (now). ;)
    5
    When I tried to install Magisk in TWRP it failed. It isn't that big of a problem as I am running one of Rbox's pre rooted ROMs but just thought it was odd.

    It was Magisk 19.5? I believe, can't remember off the top of my head.
    You are probably using rbox-twrp instead unlocked twrp.
    I don't think there's any reason to use an old Magisk release either.

    Unfortunately the update overwrote the prerooted version with a standard unrooted version and you would have to go through the whole process again to unlock, but you would have to use the latest prerooted version once it is available so there no updates to mess it up. and then block future updates after that. I decided to just wait for the newest prerooted version so I don't have to go through the process again.

    The good thing is that it is a fully functional unit for reasonably cheap.
    Can you please stop giving nonsense advice?
    1. There is no reason to redo the unlock.
    2. We currently DO NOT recommend using the prerooted ROM together with the unlock.
    5
    In case someone needs some newer 'full OTA update' packages of the stock rom, only for sloane:

    Fire OS 5.2.7.3 (652614020).

    Fire OS 5.2.7.4 (656638420).

    Fire OS 5.2.7.6 (659654620).

    5.2.7.6 is the latest OS (as of today).
    Don't forget to rename the file, i.e. .bin to .zip.
    5
    According to Amazon the latest software update is Amazon Fire TV (2nd Generation): Fire OS 5.2.7.8 (664657320) not 5.2.8.8.
    but I haven't found a link for it yet.

    Me too. Where to find link for full stock Fire OS 5.2.7.8 (664657320)? I'd like to keep my practice demo up to date.

    Fire OS 5.2.7.8 (664657620) for sloane:


    md5: 087cef3f082b0017231e8b938feaeec7