yashsingh1/xdaforums huggingface dataset:
[Fire TV Original Android Development] SweenWolf:
I took logs for Netflix, no videos were loaded straight up hanged the stick.

Config:

6.2.8.1 (stock, non-rooted, only system and vender updated)
[Fire TV Original Android Development] tito_puente:
Can someone tell me if this rooting method also can help when my 4K stick is stuck on the white amazon logo?

The stick works fine for almost 2 years and now from one day to another it doesn't work anymore.

When I want to boot it up it gets stuck on the white amazon logo. Hardreset isn't possible because the remote doesn't connect to the device.

Can it help to root the device? Or is there any other option to Hardreset the 4k Stick?
[Fire TV Original Android Development] Sus_i:
Ok, updated my stick to 6281 stock and then I've got the same blackscreen freeze and/or reboot thing...

So I've tested all the newer TZ images up to 6276 (the last TZ without the efuse-thing) and none of them worked.

That's some kind of bad news I guess.
[Fire TV Original Android Development] SweenWolf:
Irrelevant question but can anyone provide info about where can i learn about ELF binaries.
[Fire TV Original Android Development] SweenWolf:
Yeah, i think tz is incompatible with newer images, i have no idea how or if we can patch the file. I also have no idea what kind of file is that.

Also i reverted back to 7.1. And the problem returned. I am unable to write to system if i use 7.1 or 7.3 and seems like their are two separate partition, on 8.0 and 8.1 there are no such issues. I have no time to look into those issues.

I was going to stay at 8.1 but issues with TZ.

My main plan WAS

patch all the files in the system (non signed) and OTA also so no more updates.

If FOTA is patched it will never ask for update, and patching OTA so no System update is downloaded manually. So it has no way to download any files related to OS.

I patch boot image to remove efuse startup and with efuse and writer also removed it would never blow the fuse.

And then just flash back the patched boot image by hacked bl.

I know TWRP prevents TZ updates and all, but even on stock if theres no files to patch, then what will it patch.

And i could unlock anytime.

This was my theory, what do you want to say about it, I'm now trying to gather more info about the subjects.
[Fire TV Original Android Development] nomobytes:
The resolution of my set is 1080p, and as I reported, all flashing has been done under TWRP, using stock or @rbox firmware. TZ is tricky as it can update KB. (post #411)
[Fire TV Original Android Development] nomobytes:
Is everything working again when you revert back to 6280 stock?
[Fire TV Original Android Development] rbox:
So I just got around to testing this 6.2.8.1, and see the freeze as well. My roms I remove the fuse blower. Are you saying its still not safe to update the TZ? I remmeber in the past I've included TZ updates once or twice.
[Fire TV Original Android Development] rbox:
Flashing back to 6.2.8.0 works for me.
[Fire TV Original Android Development] Sus_i:
At least we need to stop flashing any kind of stock rom, but your prerooted rom should be safe...

Yes, I remember it.

If you provide a prerooted 6.2.8.1 with an updated 6.2.8.1 TZ (all older TZ images won't work), we'll see what happens.

I guess it will work fine.

Edit: Maybe we need to disable TWRP cache recovery commands too, in order to protect people with an enabled OTA updater...
[Fire TV Original Android Development] Skel40:
Here's a prerooted 6.2.8.1, this may not be the updated tz.

https://xdaforums.com/attachments/mantis-6-2-8-1-r1-zip.5359843/
[Fire TV Original Android Development] rbox:
I updated my prerooted thread with 6.2.8.1_r2. This includes the new TZ and video playback seems to work.
[Fire TV Original Android Development] k4y0z:
Can you add a warning, that people who have installed this version at one point should refrain from installing any stock >= 6.2.8.0 if they want to keep their efuse?
[Fire TV Original Android Development] rbox:
Sure
[Fire TV Original Android Development] Pretoriano80:
Disabling TWRP Cache recovery commands might be a good idea, but probably the best thing the users should do is disabling any kind of OTA updates (system apps and firmware),because we don't know what Amazon might do to workaround the efuse service disabling.

Btw, TZ updating is a one way trip or it can be downgraded?
[Fire TV Original Android Development] Skel40:
I'm sure you can downgrade when you can still unlock. I've done the exploit numerous times unless the efuse disables the downgrade which is what it exactly does. If you want to try downgrading, look for any firmware from rbox's pre-rooted from 6.2.6.5 or 6.2.6.6 (tz)

The links are down from anything older than 6.2.7.1 so refer to a stock image for the image files
[Fire TV Original Android Development] Sus_i:
Yes, I guess they could easily push a system app that does the same thing as the ewriter prog.

Yes, downgrade is not a problem, TZ flashs to TEE1 and 2, stuff on KB isn't changed.
[Fire TV Original Android Development] Skel40:
@Sus_i quick question. All the images from the firmware including tz, tee1, tee2, lk, etc, are they responsible for making the bootloader detect it's been unlocked when the apps block you from even using a certain app?
[Fire TV Original Android Development] Sus_i:
The PL is the preloader, the first boot stage after the bootrom.

The LK is the second boot stage, which steps up to the boot.img.

TZ is the trustzone, KB the keybox.

No. The LK does a lookup for an unlock code during boot, which can be stored in IDME on the boot1 area. But since nobody knows the unlock code, kamakiri use a LK payload and a microloader,

Many apps detect root, the unlock and/or modifications on system, but you can use magisk hide to hide root and magisk modules instead modificatons on system, in order to get such apps to work.

Edit: Besides that, 6281 enforces DRM (requires an updated TZ). All the older OS versions should work fine without the TZ update (for now).
[Fire TV Original Android Development] Pretoriano80:
Basically there's no good reason to update to 6.2.8.1 unless Amazon forces us to do it. xD
[Fire TV Original Android Development] Russell80:
Netflix stopped working on multiple unlocked FireTV4k. The firmware was updated to the latest OS 6.2.8.1 (NS6281/3385) What's the best way to get Netflix working again? I already did a factory reset, reapplied kamakiri-mantis-v1.2 from scratch, and had the same problem. What's the best way to downgrade. Please provide the link. Thank you in advance
[Fire TV Original Android Development] Pretoriano80:
You can downgrade by installing a previous full Stock FireOS (from here - > https://xdaforums.com/t/fire-tv-sti...ps-official-cloud-front-direct-links.4088247/ ) with TWRP.

If the file type is "bin" , rename it to "zip" and install it with TWRP.
[Fire TV Original Android Development] SweenWolf:
Read this post

Updating TZ will solve your problem, read instructions from op and flash the 6.2.8.1 r2

Read notes first
[Fire TV Original Android Development] Russell80:
What's the command to restore the stock image?

I just tried to restore back to stock image but I ended up with white screen with FireTV logo and nothing changes. I moved the image file "update-kindle-mantis-NS6277_user_3033_0004597733764.zip" to sdcard folder and ran the following command. What's the proper command? I don't have otg y cable to connect mouse or keyboard.

I ran "reboot recovery" and after getting into recovery mode
echo "--update_package=/sdcard/update-kindle-mantis-NS6277_user_3033_0004597733764.zip" > /cache/recovery/command
echo "--wipe_cache" >> /cache/recovery/command
reboot recovery
[Fire TV Original Android Development] Sus_i:
I guess you need to call su, in order to write the commands to cache, like this

adb shell
su
echo "--update_package=/sdcard/update-kindle-mantis-NS6277_user_3033_0004597733764.zip" > /cache/recovery/command
echo "--wipe_cache" >> /cache/recovery/command
exit
reboot recovery

You can use twrp commandline too, if you like, i.e.:

adb reboot recovery
adb shell
twrp install /sdcard/update-kindle-mantis-NS6277_user_3033_0004597733764.zip
reboot

There are reports, that going back to 6277 won't work (without wiping data/factory reset), if you come from anything higher than 6280.

The best is probably if you just flash the new prerooted rom from rbox.
[Fire TV Original Android Development] Russell80:
Thank you, guys. I downgraded to 6280 and everything is working now. By the way, I've used in the past to disable update the following script. Is it still correct or should I use other methods?

pm disable-user --user 0 com.amazon.device.software.ota
pm disable-user --user 0 com.amazon.device.software.ota.override
[Fire TV Original Android Development] Sus_i:
(y)

I use this...

su
pm disable com.amazon.device.software.ota
pm disable com.amazon.device.software.ota.override
pm disable com.amazon.tv.forcedotaupdater.v2
pm clear com.amazon.device.software.ota
exit
[Fire TV Original Android Development] Jesstr8803:
I'm not sure if the FireOS has the driver's pre installed or not, I'm not very familiar with StickMount, just how to use it. Haha. But I feel like FireOS must have driver's for NTFS, and it must run some sort of script when you plug in a USB drive. I'm basing my hypothesis on the fact that when you plug in a drive that isn't FAT, you get a popup in the OS asking to reformat or disconnect. I also remember seeing some time ago (tried to find old post, couldn't find it) someone had found a script in an old version of fireOS that handled the mounting of USB drives.

I could be wrong, I'm just making a guess.

On a side note,

Is there a way to edit files directly in ADB, like similar to using nano on a Linux system? The best way I have found so far is to ADB pull files off, edit/view on local computer then push back if I made any changes.

Thanks!
[Fire TV Original Android Development] c3po_droid:
There is an easier way. Just use ADBLink. ADBLink has its own file manager and within this file manager you can edit textfiles directly and save them. I used this method always on my Fire TV 2 Box (Sloane) to edit the build.prop file for blocking updates. I cannot think of an easier way for such operations.
[Fire TV Original Android Development] Jesstr8803:
Awesome! I'll give that a try.

Thank you
[Fire TV Original Android Development] t3ch42:
Great work! Very excited to see this and also enthused to see the attention by [MENTION=3991724]rbox[/MENTION]. Install went well for me, only took a few tries to catch the points.

With the successful install of magisk, was going to ask if anybody had installed busybox yet.

Thanks again to all involved!
[Fire TV Original Android Development] Pretoriano80:
Fire OS doesn't have ntfs-3g support by default, and if i remember correctly, StickMount will ask user to download the binaries in case they are missing.

However, i managed to build myself a Magisk module which adds NTFS/exFAT (RO/RW) support, but the OTG device must be connected when booting FireOS, otherwise auto-mounting won't work.

Also, the module will set Selinux to permissive (still haven't found a way to keep it Enforcing).

I also played a bit with the kernel and enabled SDCARDFS and non-fuse exFAT driver (exfat.ko module).

After some testing it seems that NTFS/exFAT it's pretty stable, but the problem is when there's heavy I/O loading, like writing and reading from the device at the same time.
[Fire TV Original Android Development] asislife20:
Do you need a full system image to get a ton going? I thought I read somewhere that you needed one. If you still do, I just bought a second 4k stick and would be willing to backup the images you need.
[Fire TV Original Android Development] sconnyuk:
I wouldnt mind a backup made in TWRP, so I can restore it to my stick.
[Fire TV Original Android Development] TitanUranus:
Would it be safe to run nanodroid patcher? I want to install microg services & patched playstore but need signature spoofing. I just don't know if the patcher alters just the system or if it patches the bootloader (and if it'd be safe for it to do so, which I guess it wouldn't). I don't care if I mess up the ROM testing sfuff as long as I can recover with TWRP backup, but can't go through the insane hassle I had installing TWRP again.

Please don't think that's criticism, I appreciate so much the work you've all done making this so simple (and in better times it would have been simple for me). Unfortunately I have a pinched nerve making using more than 1 hand a nightmare (I suffer tremors too which isn't ideal). After a lot of messing about I realised I couldn't use my netbook for the task as it only has thunderbolt ports & the install won't work over a USB Hub. So I used my server PC. But the monitors are in a different room to the PC so I used a long cable - which didn't provide enough power. So I ended up in a poorly lit room surrounded by a billion cables & HDD's, using an external HDD as a worktop, a piece of chicken wire fencing as tweezers and a video call from my phone to my tablet showing me what was on the monitor next door! By some miracle I got it flashed OK but like I say, don't want to have to do that again any time soon - haha.

I seriously recommend having someone else around to plug the cable in the PC if you are just holding the wire short in place. Especially if you have crappy coordination like me!

Also, the Linux ISO failed to boot on a GPD Win v1 or I'd have used that. Again, not a criticism just mentioning it in case the information is useful.
[Fire TV Original Android Development] asislife20:
I Made a backup with my first stick in twrp, and it got screwed up when I tried to install gapps. I restored the backup from twrp but it made it worse and all I could do was load twrp. My second one I backed up everything in twrp, and tried to use the backup to restore my broken one, but it wouldn't even show the partitions were in the backup. I don't think twrp is backing up correctly.
[Fire TV Original Android Development] sconnyuk:
It won't show the partitions because it will be a different serial number on firestick number 2, the trick is to make a small backup of stick number 2 (the boot partition for example) and then it will create the correct folder name with the correct serial number, then you transfer the contents of the first backup into that folder.

This way you will see partitions to restore and I'm sure system and data is all you would want to restore.
[Fire TV Original Android Development] Sus_i:
That's probably caused by your missing MLC. I know you think that the stick works fine without that...

But it's like I said before, without a proper VDDi connection, the EMMC isn't stable.

May be that it worked for you the first time, in case of a read error the controller simply attempt a second read of the sector...

But if you write to the unstable flash, it corrupts some of your flashed data, especially if you write/flash a bigger zip file. Thats probably the reason that the gapps install messed your stick up.

Thats the reason why your TWRP Backup restore fails... it can't write properly to a stick damaged like that.

As conclusion I bet that the TWRP Backup/Restore isn't the cause of your failure. Just my opinion...

That is what sandisk tells for example about the connection you probably lost:

VDDi Connections
The VDDi (K2) ball must only be connected to an external capacitor that is connected to VSS.
This signal may not be left floating. The capacitor’s specifications and its placement instructions
are detailed below.
The capacitor is part of an internal voltage regulator that provides power to the controller.
[B]Caution: Failure to follow the guidelines below, or connecting the VDDi ball to any external signal
or power supply, may cause the device to malfunction. [/B]
The trace requirements for the VDDi (K2) ball to the capacitor are as follows:
• Resistance: <2 ohm
• Inductance: <5 nH
The capacitor requirements are as follows:
• Capacitance: >=0.1 uF
• Voltage Rating: >=6.3 V
• Dielectric: X7R or X5R

---------- Post added at 11:17 AM ---------- Previous post was at 11:12 AM ----------

Hmm, unstable? You may check your repair, see the sandisk instructions above mentioned...

Edit:

[MENTION=6711909]asislife20[/MENTION] [MENTION=5665338]kigba[/MENTION]

Of course, something else may be damaged too, who knows.
[Fire TV Original Android Development] kigba:
Hello. I have few familiar masters of good work, who can check the quality of repairs on the part of electrical engineering. I used the simplest and most affordable repair method - to return to the place, as it was before. Looks like I did it. Damaged circuits were checked for compliance with the parameters of the data that you provided. This voltage is 1.1V and the capacitance is 0.1uF. Examination of adjacent elements also does not indicate defects. There is no short circuit, the adjacent capacitor is also not damaged. The check was visual under a microscope and the electrical parameters of the damaged unit were additionally checked - everything is normal. If possible, I will try to find another specialist to check the scheme, but I have no more ideas what could be damaged there additionally. The last assumption is that the flash memory is damaged, but how it happened and why - I do not know. The stick was new, never connected to the TV. Dismantling was simple and neat enough and also could not lead to mechanical damage. The last idea is, if possible, to make a script that can flash the bootloader completely to the factory state. And then repeat the unlock procedure.
[Fire TV Original Android Development] Sus_i:
Maybe your friends can hook up the three cables to the serial console like k4y0z suggested, may be you get an answer with that.
[Fire TV Original Android Development] kigba:
Unfortunately, they don’t have time (and desire) to delve deeply into my problems :( There remains the option of trying to make a UART connection myself and understand this. But I have a weak level of knowledge for such work. There is a simple general understanding of the process and even here I not sure if this is the correct understanding. :(
[Fire TV Original Android Development] Sus_i:
It isn't that hard, if you look at youtube, there is maybe a video...

and of course you could ask here, if any questions occur ;)
[Fire TV Original Android Development] kigba:
when I get the courage and buy technical equipment, I will definitely turn here for help and advice, thanks :)
[Fire TV Original Android Development] idaxd:
Thanks for the exploit:) Finally root! But when I disable com.amazon.tv.launcher in order to change the launcher, the screen stays black - does anyone have any idea what this could be?

---------- Post added at 02:48 PM ---------- Previous post was at 02:04 PM ----------

...found the solution: pm disable com.amazon.firehomestarter/.HomeStarterActivity
[Fire TV Original Android Development] asislife20:
You could be completely correct, I'm not that knowledgeable. But what I do know is I was able to flash gapps twice, but the packages wouldn't work so I factory reset which worked twice. The third gapps package I tried the stick booted but got stuck on a black screen that said the fire stick was completing an upgrade. I then factory reset again, but still got the same screen. That's when I tried restoring from the backup, I only backed up boot, and system images though.

---------- Post added at 04:36 PM ---------- Previous post was at 04:31 PM ----------

I'll give this a go.
[Fire TV Original Android Development] 4qman:
Hey everyone,

It has been a while since i did some modding and i have had the afternoon preparing the fireTV 4k stick.

Ive done what was instructed on the first page, then i attempted to plug the stick into the USB port and realised the blooming thing is HDMI lol

Is there an adapter, any other option?

EDIT: I forgot to mention i use a x200 laptop and it doesnt have HDMI. I will try another laptop and plug the stick into the HDMI port :fingers-crossed:
[Fire TV Original Android Development] Sus_i:
Don't know, I can be wrong too, we will see it if rbox finishs his awesome prerooted rom.

I wish you good luck and I hope you get this sorted out :good:

Hmm, what? ;)

Plug the HDMI into your TV and power the stick with usb port from your laptop...
[Fire TV Original Android Development] emkorial:
Why are you bothering to upgrade in the first place?

If it ain't broke, don't fix it. Upgrades are almost always worthless on any device.
[Fire TV Original Android Development] alias100:
How can i remove TWRP and lock the Bootloader again?
[Fire TV Original Android Development] 0815hoffi:
https://xdaforums.com/t/fire-stick-4k-return-to-stock.4163417/

Stock rom

https://xdaforums.com/t/fire-tv-sti...ps-official-cloud-front-direct-links.4088247/
[Fire TV Original Android Development] alias100:
Thx. I'll try it in the next days.
[Fire TV Original Android Development] SweenWolf:
You'll will not be able to unlock you stick anymore after that, its a one way trip.
[Fire TV Original Android Development] luciferin:
My USB-OTG seems to not work after accidentally updating to 6281. It's turning what should be a simple TWRP flash into a nightmare for me. Does anyone have any experience on dealing with this?
[Fire TV Original Android Development] Pretoriano80:
Maybe i'm missing something, but why is a one way trip?

As long as he is using TWRP to install the stock rom and then use fastboot to flash the boot.img , then the device should still be unlockable .

Unless the stock recovery is also installed, so FireOS would be able to flash a full rom, including the critical partitions.
[Fire TV Original Android Development] Sus_i:
Hacked fastboot doesn't apply the microloader, so if you flash a stock boot, the unlock is almost removed.

At the next reboot, TWRP gets replaced with the stock recovery.

Yes, if there is any update and if the user enabled the updates in the first place (infront flashing the stock boot)...

Edit: I think you had a look at this script some time ago ;)
[Fire TV Original Android Development] Pretoriano80:
Thanks! This was still unclear for me, if FireOS manage to install the stock recovery upon the next reboot (i know there's a script responsible for that xD).

From this point to a blown efuse there's just a small step.
[Fire TV Original Android Development] SweenWolf:
Yeah, Sus_i is right.

You won't be able to go fully stock unless you

Relock bootloader

And wipe userdata (if you don't wipe it then some apps like Peacock Tv will still not work, it checks everything)

About the one way trip.

If he hasn't done anything to the system, and flashes the stock boot img via hacked bl then on the next reboot it will run "install_recovery.sh" from bin, which checks and replaces any recovery with the stock one, at that point you will no longer have any access to TWRP, it will perform another reboot and you are somewhat fully stock.

If you delete the script from bin and it doesn't replace the recovery, then there are two scenarios, both results in bootloop but if you have intact efuse you can unlock again, if your efuse is blown how will you unlock.

(I have tried this myself, with efuse intect, and this is the risk I'm not willing to take again)

About the partially stock part (for Peacock TV only) if he resets his stick after that, he'll have to go through OOBE again forcing him another update which will blow his efuse and the stick is patched.

[EDIT]

Few things i forgot to mention.

If you flash stock rom without efuse and stock boot.img your efuse will not be blown but it will ask for update on oobe which can be bypassed with TWRP backup (in case you want to stay stock OS<7.7) and you can flash boot.img via fastboot (hacked) and then blocking system updates. Otherwise no matter what you do you will be forced to update on OOBE.
[Fire TV Original Android Development] nagi_007pk:
I have vm170 firestick lying around. Can I root it? Here's a picture of the serial number.

Edit: Deleted attachment
[Fire TV Original Android Development] 0815hoffi:
I would delete the image, otherwise anyone can use your serial number.

Yes you can root if you not updated to 6.2.8.x