no, you don't. if you want to verify it is there..
adb reboot recovery
[UNLOCK][ROOT][TWRP][UNBRICK] Fire TV Stick 4K (mantis)
- Thread starter k4y0z
- Start date
adb reboot recovery
Looks like I must have done some damage to mine. Trying to use the remote today and it either doesn't respond or makes loads of clicks together. Not blaming anyone as I knew the risks but just to caution folk.
try another remote... i scratched the heck out of mine and shorted everything on the board during testing... i have (4) complete without issues....
Hmm, mine looks a bit different than the photo from OP, so i wonder if it will still work...
Attachments
was going to post the exact same thing
Just popped the heatsink and I too have a sandisk, and also DAT0 and CLK are under the quarter round "notch" ... the only point I could potentially reach with a hairpin (clipped to ground) would be CMD, if it's the same as in OP's picture (ie. right side of 3rd component from the right at the bottom of the chip).
Has anyone got it working by shorting this point? is it safe to assume it's the same point as in OP's SEC 819 etc. memory chip?
Yeah, the points are a bit hidden under the "notch".was going to post the exact same thing
Just popped the heatsink and I too have a sandisk, and also DAT0 and CLK are under the quarter round "notch" ... the only point I could potentially reach with a hairpin (clipped to ground) would be CMD, if it's the same as in OP's picture (ie. right side of 3rd component from the right at the bottom of the chip).
Has anyone got it working by shorting this point? is it safe to assume it's the same point as in OP's SEC 819 etc. memory chip?
It shouldn't really matter what manufacturer the EMMC is, the basic layout should be the same.
Mine is a sandisk as well...
Yeah, that's a similar chip.
I've shorted always the third one in that row, on the picture called CMD, works fine for me :good:
I didn't touch that one under the shield.
Last edited:
Yeah tried a different remote. Also tried the suspect remote with a Fire Stick 2 and it worked fine.
Things are OK with the Fire Stick 4K when I'm up close but far away the remote seems to lose connection a lot. The other remote on the other Fire TV works fine at the same distance. I guess I did some damage to the bluetooth or something....
I have a Skynix with that little notch. I bent it back in order to get at DAT0. Ended up shorting CLK though.was going to post the exact same thing
Just popped the heatsink and I too have a sandisk, and also DAT0 and CLK are under the quarter round "notch" ... the only point I could potentially reach with a hairpin (clipped to ground) would be CMD, if it's the same as in OP's picture (ie. right side of 3rd component from the right at the bottom of the chip).
Has anyone got it working by shorting this point? is it safe to assume it's the same point as in OP's SEC 819 etc. memory chip?
Could someone check something for me please? I'll attach a photo and could you tell me if the part I have circled is exposed like mine is? Because I had a small fine piece of steel that like an idiot I mislaid and I'm wondering could its absence be the cause of my bluetooth issues? Could be barking up the wrong tree altogether as I'm out of my comfort zone here.
Attachments
Thanks for this info, it boots into TWRP fine. I shouldn't have ignored you last time I thought that would only work at the flash screen that shows up after the initial hack.
Nope, that is covered by a small piece of silver something, maybe steel, idk.
Don't think that this can cause bt issues. Have you checked for a remote update in settings?
Edit: Hmm, don't know why, but my small silver something is gone.
Edit2: Found it, it's sticking at the tape on the shield. On an another stick it's in place.
Edit3: Tried to investigate that, seems that the manufacturer sometimes paste that shield into the slot.. and sometimes above on the heatshield . It doesn't matter at all.
Last edited:
You were right it was a software issue. I'm a prize wally. I had updates blocked all along by means of Pi-Hole DNS. After I performed the exploit the Stick somehow updated itself to the latest FireOS. I was getting loads of Fire Remote update notifications and then did a factory reset out of panic.
Anyway thank you and I don't have to buy a new 4K Fire Stick.
It is still advised to block Ota.
Can you tell us how to disable Ota update on the fire tv stick 4k after a successful root.
And since there is no superuser installed how can this be done.
Can you tell us how to disable Ota update on the fire tv stick 4k after a successful root.
And since there is no superuser installed how can this be done.
Absolutely fantastic ! Thanks very much for the continued effort.
I've had a 4k stick in my draw for months that I bought in a job lot and won't go past setup screen, suspected blocked by Amazon.
Now we have TWRP is there anyone kind enough to upload a backup made in TWRP for me to restore toy stick (thus bypassing registration screen).
This way around worked fine for a 2nd gen stick I had that was the same suspected blacklisted.
Can anyone help ?
Thanks.
I've had a 4k stick in my draw for months that I bought in a job lot and won't go past setup screen, suspected blocked by Amazon.
Now we have TWRP is there anyone kind enough to upload a backup made in TWRP for me to restore toy stick (thus bypassing registration screen).
This way around worked fine for a 2nd gen stick I had that was the same suspected blacklisted.
Can anyone help ?
Thanks.
You guys rock! Unlocked without issues. Rooted with Magisk 19.3.
Note: in my case, correct pin was left side of 3rd smd component from right.
Heatsink can be easely detached with flat screwdriver (just rotate it in points as on the picture)
Note: in my case, correct pin was left side of 3rd smd component from right.
Heatsink can be easely detached with flat screwdriver (just rotate it in points as on the picture)
Attachments
Last edited:
ota can be disabled with root by following commands:
Code:
adb shell
su
pm disable com.amazon.tv.forcedotaupdater.v2
pm disable com.amazon.device.software.ota
pm disable com.amazon.device.software.ota.overrideTry to rename the offending setup apk in twrp, so it's not blocking you! It's one of apks in /system/priv-app
Thanks for the reply, have you any idea on which one in system/Priv is the offender ?
There are alot in there and I wouldn't know which to disable.
Appreciate your time.
Thanks.
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone