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

Search This thread

xflbret

Senior Member
Mar 15, 2013
346
36
Tucson, AZ
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.
 
  • Like
Reactions: bloot

dony71

Senior Member
Dec 1, 2010
290
15
I made that same mistake Sunday, so I had to open fireOS with a
- "fresh zip of kamakiri-Sheldon-1.0" (Yes, use a new zip)
- boot-recovery.sh
- gpt-fix.sh.
- Then followed by reinstalling LOS 18.1 zip
- Magisk apk, and it's good again.

BTW - I don't install the GAPPS (Less Goo - option)
Sorry, I don't get it what you mean with "fresh zip kamakiri-Sheldon-1.0"
The only zip I found on post#1 is

kamakiri-sheldon-1.0.zip
17.4 MB · Views: 3,583
 

CoffeeSkwerl

Member
Mar 28, 2022
22
3
Sorry, I don't get it what you mean with "fresh zip kamakiri-Sheldon-1.0"
The only zip I found on post#1 is

kamakiri-sheldon-1.0.zip
17.4 MB · Views: 3,583
-"fresh zip of kamakiri-Sheldon-1.0" (Yes, use a new zip)

Okay, I start with another copy of that same zip, as the first copy often retains files from the original installation. So again, extract another copy from the same zip you downloaded.
 

dony71

Senior Member
Dec 1, 2010
290
15
-"fresh zip of kamakiri-Sheldon-1.0" (Yes, use a new zip)

Okay, I start with another copy of that same zip, as the first copy often retains files from the original installation. So again, extract another copy from the same zip you downloaded.
Using new extracted zip, still keep having this issue :

~/FireTV/kamakiri-sheldon-1.0/kamakiri# ./boot-recovery.sh
[2022-06-25 10:08:12.871822] Waiting for device
[2022-06-25 10:08:58.202505] Found port = /dev/ttyACM0
[2022-06-25 10:08:58.213193] Handshake
Traceback (most recent call last):
File "/root/FireTV/kamakiri-sheldon-1.0/kamakiri/modules/handshake2.py", line 23, in <module>
handshake2(dev,cmd)
File "/root/FireTV/kamakiri-sheldon-1.0/kamakiri/modules/handshake2.py", line 10, in handshake2
dev.handshake2(cmd)
File "/root/FireTV/kamakiri-sheldon-1.0/kamakiri/modules/common.py", line 133, in handshake2
c = self.dev.read()
File "/usr/local/lib/python3.9/site-packages/serial/serialposix.py", line 595, in read
raise SerialException(
serial.serialutil.SerialException: device reports readiness to read but returned no data (device disconnected or multiple access on port?)
 

dony71

Senior Member
Dec 1, 2010
290
15
Using new extracted zip, still keep having this issue :

~/FireTV/kamakiri-sheldon-1.0/kamakiri# ./boot-recovery.sh
[2022-06-25 10:08:12.871822] Waiting for device
[2022-06-25 10:08:58.202505] Found port = /dev/ttyACM0
[2022-06-25 10:08:58.213193] Handshake
Traceback (most recent call last):
File "/root/FireTV/kamakiri-sheldon-1.0/kamakiri/modules/handshake2.py", line 23, in <module>
handshake2(dev,cmd)
File "/root/FireTV/kamakiri-sheldon-1.0/kamakiri/modules/handshake2.py", line 10, in handshake2
dev.handshake2(cmd)
File "/root/FireTV/kamakiri-sheldon-1.0/kamakiri/modules/common.py", line 133, in handshake2
c = self.dev.read()
File "/usr/local/lib/python3.9/site-packages/serial/serialposix.py", line 595, in read
raise SerialException(
serial.serialutil.SerialException: device reports readiness to read but returned no data (device disconnected or multiple access on port?)
dmesg says

[956544.855627] usb 3-1.4: new high-speed USB device number 101 using ehci-platform
[956544.969505] usb 3-1.4: New USB device found, idVendor=0e8d, idProduct=2000
[956544.969519] usb 3-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[956544.969524] usb 3-1.4: Product: MT65xx Preloader
[956544.969529] usb 3-1.4: Manufacturer: MediaTek
[956545.075103] cdc_acm 3-1.4:1.1: ttyACM0: USB ACM device
[956545.275914] cdc_acm 3-1.4:1.1: failed to set dtr/rts
[956545.302772] cdc_acm 3-1.4:1.1: failed to set dtr/rts
[956545.402636] usb 3-1.4: USB disconnect, device number 101
[956545.403215] cdc_acm 3-1.4:1.1: failed to set dtr/rts
 

RedPenguin2

Member
Feb 26, 2017
10
1
I know that this was semi answered in the thread but I haven't seen any definite answers.

My Fire TV Stick Lite is sucessfully rooted and running from this thread.

Now I am at 7.2.4.2 atm.

Is it recommended to never update the device and leave it alone or am I actually safe in going to some of the newer updates for some of the newer features?

I assume if need be, I could technically have Magisk reflash 7.2.4.2 if ever needed?

I guess technically it doesn't matter as I noticed Amazon never seems to change the "Base OS" version of Android, no matter how many updates they do. So you are always on Android 9.0, no matter how often you update.
 

dony71

Senior Member
Dec 1, 2010
290
15
dmesg says

[956544.855627] usb 3-1.4: new high-speed USB device number 101 using ehci-platform
[956544.969505] usb 3-1.4: New USB device found, idVendor=0e8d, idProduct=2000
[956544.969519] usb 3-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[956544.969524] usb 3-1.4: Product: MT65xx Preloader
[956544.969529] usb 3-1.4: Manufacturer: MediaTek
[956545.075103] cdc_acm 3-1.4:1.1: ttyACM0: USB ACM device
[956545.275914] cdc_acm 3-1.4:1.1: failed to set dtr/rts
[956545.302772] cdc_acm 3-1.4:1.1: failed to set dtr/rts
[956545.402636] usb 3-1.4: USB disconnect, device number 101
[956545.403215] cdc_acm 3-1.4:1.1: failed to set dtr/rts
FYI, I manage to fix it by flashing from Linux Mint
 

dony71

Senior Member
Dec 1, 2010
290
15
I know that this was semi answered in the thread but I haven't seen any definite answers.

My Fire TV Stick Lite is sucessfully rooted and running from this thread.

Now I am at 7.2.4.2 atm.

Is it recommended to never update the device and leave it alone or am I actually safe in going to some of the newer updates for some of the newer features?

I assume if need be, I could technically have Magisk reflash 7.2.4.2 if ever needed?

I guess technically it doesn't matter as I noticed Amazon never seems to change the "Base OS" version of Android, no matter how many updates they do. So you are always on Android 9.0, no matter how often you update.

According to thread below, root still OK flashing to firmware > 7.2.7.3
 

sintoo

Senior Member
Nov 26, 2009
184
15
Hello all. Could you help me to know if this Rooted Rom works with my "Fire TV Stick 4K"? with Microphone button but no Netflix/Amazon/Dazn/Disney buttons? Thank you so much.
PXL_20220629_115720336.MP.jpg
 

goapy

Senior Member
Dec 30, 2021
156
39
Could you help me to know if this Rooted Rom works with my "Fire TV Stick 4K"? with Microphone button but no Netflix/Amazon/Dazn/Disney buttons?

The remote style doesn't matter. It will work on an older mantis device so long as the firmware is lower than 6.2.8.7.

Since your device has newer firmware, it won't work with the current exploit.
 

Ironrobi

Senior Member
Nov 15, 2010
51
7
Looking at picking up a few Fire Stick Lites on the upcoming prime day sale. Wondering if anybody has purchased recently and if they're still shipping with a f/w version low enough to root them?
 

vertycall

Member
Jan 13, 2015
18
3
Guys, will need some help figuring out how to bring back to life my sheldon device.

After successfully installing Lineage 18 , I couldnt pair my remote, so I tried to reset it - didnt work. Then used twrp to wipe data/system/cache and tried to reinstall the OS again. Then after restarting the device is stuck in FASTBOOT mode and cant get twrp to load.
Tried to start the whole procedure from scratch but when I execute the script - sudo ./bootrom-step.sh - its just says - waiting for device .
On command - ./fastboot-step.sh - I get this message error - FAILED (remote: 'the command is restricted on locked hw').
Same error I get when try to flash twrp from fastboot.
Any ideas how to deal with this case?
 

vertycall

Member
Jan 13, 2015
18
3
You can try the boot-fastboot script in order to get into the hacked (unlocked) fastboot...
or try the boot-recovery.sh script to boot twrp.

In case that won't work, bootrom-step + fastboot-step is the only way to fix it...
Hi, Sus_i and thanks for your answer !
Unfortunately none of the above seem to work here:

boot-fastboot and boot-recovery sripts hang on "waiting for device"
bootrom-step is also "waiting for device"
fastboot-step gets this:

target reported max download size of 134217728 bytes
sending 'recovery' (13930 KB)...
OKAY [ 0.613s]
writing 'recovery'...
FAILED (remote: the command is restricted on locked hw)
finished. total time: 0.616s
 

Sus_i

Senior Member
Apr 9, 2013
1,664
711
Hi, Sus_i and thanks for your answer !
Unfortunately none of the above seem to work here:

boot-fastboot and boot-recovery sripts hang on "waiting for device"
bootrom-step is also "waiting for device"
fastboot-step gets this:

target reported max download size of 134217728 bytes
sending 'recovery' (13930 KB)...
OKAY [ 0.613s]
writing 'recovery'...
FAILED (remote: the command is restricted on locked hw)
finished. total time: 0.616s
You can connect an uart adapter if you like and capture a boot log... then we may know more about your issue (which may be PC and/or OS related too).
 

SweenWolf

Senior Member
Mar 18, 2016
672
565
Paradise
Amazon Fire TV
Hi, Sus_i and thanks for your answer !
Unfortunately none of the above seem to work here:

boot-fastboot and boot-recovery sripts hang on "waiting for device"
bootrom-step is also "waiting for device"
fastboot-step gets this:

target reported max download size of 134217728 bytes
sending 'recovery' (13930 KB)...
OKAY [ 0.613s]
writing 'recovery'...
FAILED (remote: the command is restricted on locked hw)
finished. total time: 0.616s
You are in original Fastboot and not in Hacked Fastboot. Did you by any chance removed the exploit accidentally?
Try
fastboot boot twrp.img
But i am sure this won't work also
 

Hutch MD

Senior Member
Feb 25, 2016
58
19
I'm such a noob;
I spent forever to get bootable linux running on Virtual Box, and get to the point where I type in ./bootrom-step.sh

"Waiting for Device"
and nothing happens/device isn't recognized;

Did I do something wrong?

I opened up the device out of curiosity, and it almost looks like the same thing as the Firestick 4k;
Will the shorting method work for this 3rd gen stick too?

Update: I gave up on VirtualBox and used a USB stick for bootable Lubuntu. Success!
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    Can you help me because amazon team not response me
    Looks like you didn't understand the joke. There's no way to unlock the 4K max.
    1
    thanks , but What do you mean by ""your stick is patched""?
    Patched = Amaz. blocked the exploit with a firmware update,
    see the OP for details.
    1
    I want to Install twrp and lineageos but there ist no way?
    Let us know if you find a way...
    1
    Hi
    I have the sheldonp with firmware version 7.2.8.5
    Is a hardware root possible and are there instructions?

    thanks!
    No, it has to be below 7.2.7.3 as clearly stated at the beginning of the post
    1
    My fire stick 4k max block please help me for unlocking
    Give amazon some phone calls, they can do it over-the-air.
    Annoy the support... violently ;) :p
  • 34
    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?