[UNLOCK][ROOT][TWRP][UNBRICK] Fire TV Stick 3 and Fire TV Stick Lite (sheldon/p)

Search This thread

Rortiz2

Senior Member
Mar 1, 2018
2,448
1,858
Barcelona
Hi,
I've two question about this topic:
  1. if I bought a new FireStick 4K by now, it should be already patched or is there any possibility it has FireOS < 7.2.7.3
    When the device arrive is there any check I can do before opening the box? (eg. manufacturing date or similar)
  2. in the case the exploit work can I still use apps for streaming (eg. Netflix, Disney+, ...) or the root will break anything on DRM libs?
First of all, this thread is dedicated exclusively to the 3rd generation Fire TV Stick and you are talking about the 4K device, which is a different story.

In your case, if you receive the device with something lower than FireOS 6.2.8.7, you should be able to use the preloader-exploit to unlock the device.

Yes, DRM (Netflix, HBO, Prime) will still work after unlocking the bootloader, as long as you don't erase IDME/KB/DKB.
 

Noisemaker00

Senior Member
Apr 9, 2013
66
21
yep sorry, I wrote badly 4K on my post, I mean standard firestick
btw I found the firestick in a phisical shop near me (I tried to search before ordering on amazon due to stores may have old stocks) and... YES
It's unlockable :D
I'm now installing LineageOS on the firestick
 

Greenstuff4

Member
Jun 7, 2019
9
0
So I have managed to install twrp and lineage os, but when I try to play anything on netflix it says this content is not available. Does anyone have a fix?
 

thelastsupper

New member
May 26, 2022
2
0
I have a Fire TV Lite from mid 2021 but I lose the remote so it's been sitting in my drawer. I did all of the instruction on the first page, but I'm stuck on step number 2. When I run `./bootrom-step.sh`, it's showing "Waiting for device" and then I plugged in my Fire TV Lite but nothing happens.

If it helps, I'm using Ubuntu VM inside proxmox with USB passthrough. The amazon device is detected in the `lsusb`.

Or maybe is it because my Fire TV is turned on? as the instruction says "Plug in the stick (powered off)", but when Fire TV is plugged in, it will automatically boot, is there any way to turn it off without remote?
 
Last edited:

Rortiz2

Senior Member
Mar 1, 2018
2,448
1,858
Barcelona
I have a Fire TV Lite from mid 2021 but I lose the remote so it's been sitting in my drawer. I did all of the instruction on the first page, but I'm stuck on step number 2. When I run `./bootrom-step.sh`, it's showing "Waiting for device" and then I plugged in my Fire TV Lite but nothing happens.

If it helps, I'm using Ubuntu VM inside proxmox with USB passthrough. The amazon device is detected in the `lsusb`.

Or maybe is it because my Fire TV is turned on? as the instruction says "Plug in the stick (powered off)", but when Fire TV is plugged in, it will automatically boot, is there any way to turn it off without remote?
You need to run the script as sudo.
 

thelastsupper

New member
May 26, 2022
2
0
You need to run the script as sudo.
tried but doesn't seem to be working with sudo

here's the output of lsusb
Code:
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 004: ID 1949:03a1 Lab126, Inc. AFTSS
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

the Amazon Fire TV is detected (AFTSS) when plugged in, but it's still stuck at "Waiting for device"

Code:
[email protected]:/home/kamakiri-sheldon-1.0/kamakiri# ls -a
.   bin               boot-recovery.sh  brom-payload      gpt-fix.sh  modules
..  boot-fastboot.sh  bootrom-step.sh   fastboot-step.sh  lk-payload
[email protected]:/home/kamakiri-sheldon-1.0/kamakiri# sudo ./bootrom-step.sh
[2022-05-27 02:47:42.156232] Waiting for device
 

Rortiz2

Senior Member
Mar 1, 2018
2,448
1,858
Barcelona
tried but doesn't seem to be working with sudo

here's the output of lsusb
Code:
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 004: ID 1949:03a1 Lab126, Inc. AFTSS
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

the Amazon Fire TV is detected (AFTSS) when plugged in, but it's still stuck at "Waiting for device"

Code:
[email protected]:/home/kamakiri-sheldon-1.0/kamakiri# ls -a
.   bin               boot-recovery.sh  brom-payload      gpt-fix.sh  modules
..  boot-fastboot.sh  bootrom-step.sh   fastboot-step.sh  lk-payload
[email protected]:/home/kamakiri-sheldon-1.0/kamakiri# sudo ./bootrom-step.sh
[2022-05-27 02:47:42.156232] Waiting for device
Try with a LiveUSB then.
 

POPE3909

Member
Feb 12, 2013
17
3
Any idea why I'd be getting this error? I've never used Linux before but I installed Ubuntu on a laptop I had lying around. I followed the guide precisely for my 3rd gen Firestick.

I would like to be able to install stock android on the firestick so that I can exclusively run Kodi on it and nothing else. Kind of like LibreELEC does for the Raspberry Pi but it has no support for Firestick. If I can accomplish this goal by purchasing a different version of Firestick then please let me know.

Screenshot from 2022-05-27 10-29-06.png
 
Last edited:

POPE3909

Member
Feb 12, 2013
17
3
Hi there

The fix for the 'downgrade' issue is written to this thread a few times...
Ah, yes... I see where you replied to someone with "try it again and again until it works" which isn't helping because I tried it a dozen times an nothing different happens.

EDIT: I got it to work using another method.
 
Last edited:
  • Like
Reactions: Sus_i

Mehraadsm

New member
Jun 5, 2022
2
0
After 2nd step my fire stick reboot and logo comes then colour is showing i am unable to usb my fire tv stick please help me
 

mondalex

Member
Jan 16, 2018
10
1
Hey, a noob here. So the question is how do I interact with twrp (since it has got no touch screen like on my phone)? Do I need to connect a mouse with an OTG cable? Or does the remote works somehow?

EDIT: Figured it out, thanks!
 
Last edited:

Wolverine86mi

New member
Jan 14, 2020
3
1
1. Flash a stock rom with twrp
2. wipe data
3. reboot into hacked fastboot and flash the boot.img via fastboot flash command (make sure to extract/use the boot.img out of the stock rom you flashed in the first place).
Hello I would like to flash the recovery stock can you explain it to me in detail
thank you
 

Sus_i

Senior Member
Apr 9, 2013
1,601
688
Hello I would like to flash the recovery stock can you explain it to me in detail
thank you
I don't know if the procedere is 100% the same as for mantis or sloane devices, so you may ask the OP @k4y0z
Could be that a restore of the boot.img isn't enough in case of sheldon, i.e. you may need to flash the recovery.img too.
 

erojas97

Member
May 6, 2022
6
0
Ah, yes... I see where you replied to someone with "try it again and again until it works" which isn't helping because I tried it a dozen times an nothing different happens.

EDIT: I got it to work using another method.
What method did you use? I also updated but I couldn't do anything
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    Hey guys.
    Big thanks to the dev. I've succesully rooted my firetv with this script and fixed some stuff. So I've made a guide for who need some help https://github.com/daboynb/Root_firestick .
    1
    What method did you use? I also updated but I couldn't do anything
    This worked for me:
    Open up the main.py in kamakiri's modules folder and comment out (disable) line 73 to 76, i.e. set a # infont of each line. Then the script will skip reading the rpmb and proceed...
    1
    Yeah it should already have executable permission, maybe that's not the problem anyway, that's why I wanted to see ls -l. In case it was the problem, you'd need to do a 'chmod +x bootrom-step.sh'

    Did you install all the needed dependencies?
    Well, I tried it again. And, for whatever reason, it started working for me...despite the fact that I was doing absolutely nothing different from before. So, disregard, I guess...but very frustrating.
  • 32
    Read this whole guide before starting.
    This is for the 3rd gen Fire TV Stick (sheldonp) and Fire TV Stick Lite (sheldon).

    NOTE: FireOS < 7.2.7.3 required

    NOTE: This process does not require you to open your device.

    What you need:
    • A Linux installation or live-system
    • A micro-USB cable

    Install python3, PySerial, PyUSB, adb, fastboot. For Debian/Ubuntu something like this should work:
    • sudo apt update
    • sudo add-apt-repository universe
    • sudo apt install python3 python3-serial python3-usb adb fastboot dos2unix

    Make sure ModemManager is disabled or uninstalled:
    • sudo systemctl stop ModemManager
    • sudo systemctl disable ModemManager

    NOTE: If you have issues running the scripts, you might have to run them using sudo.
    Also try using different USB-ports (preferably USB-2.0-ports)


    1. Extract the attached zip-file "kamakiri-sheldon-1.0.zip" and open a terminal in that directory.

    2. Start the script:
    • sudo ./bootrom-step.sh
    It should now say Waiting for device.

    3. Plug in the stick (powered off) and wait for the script to finish.
    If it fails at some point, stop it and restart the process from step 2.

    4. Your device should now reboot into unlocked fastboot state.

    5. Run:
    • ./fastboot-step.sh

    6. Wait for the device to reboot into TWRP.

    7. Use TWRP to flash custom ROMs, Magisk etc.

    NOTE: Only ever flash boot/recovery images using TWRP, if you use FlashFire or other methods that are not aware of the exploit, your device will likely not boot anymore (unless you flashed a signed image). TWRP will patch recovery/boot-images on the fly.

    NOTE: NEVER erase Preloader, otherwise you’ll hard brick the device and you won’t be able to unbrick it (since bootrom isn’t accessible).

    Important information

    Don't flash boot/recovery images from FireOS (FlashFire, MagiskManager etc.)

    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.

    special thanks to @Sus_i for all the testing and support.

    Contributors
    @xyz`
    @k4y0z
    @Rortiz2
    @t0x1cSH
    6
    Yeah, probably just needs a more recent FireOS installed the TZ in kamakiri is from 7.2.4.9
    Had a look into all fw bin's, TZ is the same until the newest 7.2.7.3 got an updated one...

    @etami @yacinecino @Tech0308 and all other people with the netflix/disney error):
    Can you provide more Information, i.e. what kind of stick (sheldon or sheldonp) and the installed fireOS, please!?
    Make sure (check in stettings) that the stick hasn't got an update already, because the latest OS will need the updated TZ.

    FYI, disable updates with:

    Code:
    adb shell
    su
    pm disable com.amazon.device.software.ota
    pm disable com.amazon.device.software.ota.override
    pm disable com.amazon.tv.forcedotaupdater.v2
    exit
    exit

    Maybe someone of you with a sheldonp device can install 7.2.4.9 from here, without to flash magisk behind the OS update please, to see if it works?

    Users with sheldon can flash this too, but you need to change this prop first from twrp shell:
    Code:
    adb shell
    resetprop ro.product.device sheldonp
    exit
    4
    @k4y0z will a similar unlocking method be used for the Max once we receive the 7.2.7.3 update?
    No, the Max isn't vulnerable to the preloader-exploit
    3
    I have the same problem since I flashed only TWRP alone and didn't installed anything on it just to be sure that my sheldon don't update ,Now any application who try to check DRM on stock firmware cause a bug and a reboot of the system. like netflix and disney+ or live tv with DRM..
    Could be that this is TZ related...
    We saw the same on mantis 4k fireTV stick, hangs and wont play if the TZ image on tee partition is too old compared to the installed fireOS version. Anyways, your problem sounds different to @Tech0308 problem.

    @Tech0308 You don't see this without a magisk install, then everything plays fine?
    3
    @Sus_i and @bloot and @Tech0308 and @Rortiz2 just to say all your painstaking coaching and my reading paid off (for me anyway😊) Instead of magisk, flashed the older 7.2.4.2/2907 update (from before ota update processes became protected) and set LM to block updates. It also fixed the issues with Netflix, Disney etc. Will look to flash Lineage custom rom sometime, now that I know how, and also put Linux on one of my laptops. Thanks heaps!

    Open TWRP, then mount /system, go to file explorer, go to navigate to priv-app and delete the folder
    "com.amazon.device.software.ota"
    Usually you should be good to go now, but goto /data/app and check for same folder (it will have something as suffix) if its present then delete it, your ota should be blocked.
    @SweenWolf thanks for your suggested fix . . . appreciate your work (and that of your good mate TDUK😊) LM and Debloat Tool are must-haves. This other way to block updates, is it somehow more permanent or safer than thru LM or Debloat Tool?