yashsingh1/xdaforums huggingface dataset:
[Fire TV Original Android Development] Sus_i:
Do the unlock, flash the rom I've linked you in my last post and then install magisk. That's the latest rom as of today and you're done.

If the step above fails for you and if it's stuck again at the logo, boot into twrp and wipe system, data, cache and dalvik. Flash the rom and magisk. Reboot. In this case the amz. setup waits for you.

No, the stick isn't dead, unless you damage something at the unlock process. Just be careful ;)
[Fire TV Original Android Development] FeelslikeanArbysNight:
Rooted?

Not sure if I rooted or not. I have TWRP installed and pushed/installed Magisk 20.1 from the commands in post #55, but I am unable to disable the OTA updates per post #37. I'm using the FireISO USB and ADB devices shows the Mantis as attached. Once in ADB shell I can pm list packages, but I get an error with the su command and none of the pm disable commands work.

Edit: I solved my own issue. I had to go into Magisk - Superuser and grant access to ADB shell. I also installed Root Checker and it shows I have root access now. I've been able to disable the OTA updates and my next challenge is an alternate launcher.
[Fire TV Original Android Development] deluxemongo:
Hi, tried out both steps. Same as before. Orange logo appears and then a black screen. If I hit -> and ESC the factory reset dialog appears. So I think the system is up... tried that as well, but still got a black screen.

Then tried to flash 6.2.6.8 and update boot with fastboot and the unzipped boot.img. No way, fastboot flash boot /tmp/boot.img fails with error.

Any other ideas? If not the stick will end up in recycle bin :D

EDIT: I mentioned that one of the capicitors is gone. It is the third one from the right. So now am able to do the exploit as often as I want without a bridge. Kamakiri scripts will work every time...
[Fire TV Original Android Development] Sus_i:
You see, if you wipe system, there isn't a system anymore that could be up...

Have you tried to let the black screen alone for a few minutes?

Have you tried that factory reset option?

I don't know why you mess with fastboot? :confused:

I've suggested to wipe system, data, cache and dalvic, install the 6.2.6.8 rom followed by the magisk.zip. That's all.

If you wan't to give that another try, you could flash the kamakiri v1.2.zip after the wipe, just before flashing the rom followed by magisk.zip.

:D
[Fire TV Original Android Development] deluxemongo:
Yes, I did. Nothing happens

Yes, I did. Ended in the same result: black screen after the orange amz logo.

I wanted to remove twrp and all modifications to see if the stick then boots correctly. I have read here that applying a stuck firmware via twrp and then boot into hacked bl to override boot will remove the modifications.

That’s what I have done :D ended up with: black screen.

What I did step by step:

-Wiped system,data,cache and davlik via twrp

-installed stock firmware via twrp

-installed magisk20.1

-boot system: white amz logo appeared, orange amz logo appeared, black screen, after 20 minutes I removed power cable

- did all previous steps again

-Hit -> and ESC to get the factory reset screen

-did factory reset:ended up with black screen

-wipe all data via twrp

-installed stock firmware

-boot into hacked bl to push boot.img from the zip file of stock fw

-booted, ended up with black screen

-did factory reset:ended up with black screen.

-tried it also with stock fw 6.2.6.6: same result

Do I have to wipe cache and davlik after pushing fw an magisk via twrp? Or is there anything else I did not correctly? :rolleyes:
[Fire TV Original Android Development] Sus_i:
In case you do a fw up- or downgrade, it's better if you wipe cache & dalvik.

Maybe you try another stick but please do the unlock carefully without cracking parts off ;)

If it works, you can do a backup with twrp. Gives you the option to restore that backup to your faulty stick, maybe that is a fix, idk.
[Fire TV Original Android Development] deluxemongo:
I‘ll try that tomorrow ?

I think the missing capacitor has not been soldered correctly or when I bridged it got heated and then dropped off. And I can’t try it with another 4K stick because I haven’t got another one :D

Thank you for your help. I will post here if the stick is up or when it gets recycled :)
[Fire TV Original Android Development] daver:
same problem

I have the same problem stuck@ black screen firestick logo

i have tried all your steps the same.

Somebody needs to please give explicit instructions on how to recover an exploited stick back to original state.

Without this option of a recovery..its pointless doing this exploit..You only end up with a useless stick..NOT GOOD

I have messaged k4y0z so hopefully we can resolve this issue...of being able to recover to virgin state
[Fire TV Original Android Development] Sus_i:
If you read his post again, you see that he had an orange fireTV logo and after that the black screen without a logo. ;)

100% completely different to your situation...

I doubt that will help.

First thing is that in the stock rom isn't a working recovery implemented.

Second thing is that I already wrote you a fix for almost all fw based user mistakes. If that won't work for you, the issue is most likely a hardware damage.

The way to stock is already described in this thread. Please stop spreading misinformation.

As stated in the OP:

Before proceeding make sure to read and understand this entire post.

One thing for sure, If you carefully follow the OP, you never ever get such problems.
[Fire TV Original Android Development] daver:
thankyou but the information you provided to me does not work.. and neither does it work for the other member..

So ask yourself where the mis-information is coming from

there is no hardware problem

i have done several expoits not a problem..

I am simply requesting a proven method of restoring the stick back to virgin state.. if you cannot help..then please dont comment

This problem is with a few members not just me..and will become more apparent
[Fire TV Original Android Development] Sus_i:
A few members from about 2000 people that used the latest kamakiri. ;)

Apparent is that some people can't read/understand/follow the easiest instructions.

Since that whole unlock/root thing is done in 5 minutes, including stick disassembly & boot up fireISO

Alright, I'll ignore your postings. Wish you good luck :good:
[Fire TV Original Android Development] daver:
recover to original version state

Well no answer again....not remotely helpful to anyone on this forum..

An exploit is provided to unlock bootloader and root device..yes ok

If someone changes their mind and would like to revert to original virgin state..there is no proven method to do this.

wiping with twrp..flashing roms..flashing boot.img with fastboot..all the half instructions..dont work..

Can somedody provide explicit instructions on how to do this?
[Fire TV Original Android Development] Pretoriano80:
If you think that the previous instructions that you got from other members are wrong or doesn't work for you, then try this:

1) Do a factory reset from TWRP

2) Download this update package - > https://xdaforums.com/fire-tv/devel...-mantis-prerooted-stock-t3983091/post80857211

2b) Flash the update package with TWRP

3) Flash all the images from the downloaded firmware (you must extract them first, obviously) with fastboot

4) Reboot

P. S : Remember that when you decide to unlock/root or mess with your device in any manner, you accept to do it on your own risk, nobody can be held responsible for your actions, so if you are uncomfortable with this, then you better stay stock.

Also being rude towards other members that are trying to help you, will not get you more help from other members, so please be respectful.

Edit: Added step "2b" just to make sure you are flashing the latest version
[Fire TV Original Android Development] deluxemongo:
Okay. I think the stick is dead :D

Tried all mentioned steps serveral times.

Big thanks to all that tried to help. My stick is now going into recycle bin ;)
[Fire TV Original Android Development] daten2342:
Possibly a hijack of this thread - feel free to tell me if that's the case (not quite sure what's android/vendor/product specific, not familiar with the Android eco system):

For some reason disabling the amazon services (pm disable ..) have seemingly random effects, resulting in two scenarios (and nothing in between):

- disabled (amazon-)services still start (guess: they are dependencies of still enabled services)

- nothing starts (incl. wifi not coming up) and the Fire TV is stuck at the "FireTV"-with-3-animated-dots screen

What I'm actually trying to achieve: Getting rid of the amazon services (as in: them not being started) and starting my own installed APK by default (and wifi coming up). I fail with this seemingly easy task. Could anybody provide advice? Again, if that's off-topic: happy about a pointer where it fits better.

Magisk installed and running.

Thanks for all the work!
[Fire TV Original Android Development] SacredDeviL666:
Thread Cleaned.

Kindly stay on topic.

Thanks

SacredDeviL666.
[Fire TV Original Android Development] itsyaboy:
Can’t figure out how to Delete my post
[Fire TV Original Android Development] SweenWolf:
You Disabled the launcher also?
[Fire TV Original Android Development] daten2342:
Most likely yes, given I disabled almost everything under com.amazon.*
[Fire TV Original Android Development] jamesjones28:
Hello, I bought a fire tv 4k that ended up being blacklisted by amazon. Would I be able to get it to work if follow this guide?

Thanks
[Fire TV Original Android Development] SweenWolf:
You know there is no default option for launcher in FireOS, which is why we have to use Launcher Hijack, and also the settings resides also in the launcher, so either your firestick cannot find any activity to open, or sometimes so apps stops the FS from fully booting up, in my case Google Play Services did that, which i solved with adb, try enabling the launcher and check if it works.
[Fire TV Original Android Development] jamesjones28:
After running the adb push of the manthis.zip Im getting terminate called after throwing an instance of 'std::bad_alloc'.... What Im I doing wrong?
[Fire TV Original Android Development] TheVeryLostOne:
Have you been able to solve this? I keep getting the same error. I've tried numerous different ports and cables but still have the same error.
[Fire TV Original Android Development] hidroela:
I am having the same problem :rolleyes:
[Fire TV Original Android Development] TheVeryLostOne:
Just out of curiosity, what EMMC does your stick have? Mine is using Hynix. Wondering if I'm hitting a roadblock due to that.

Update: Issue has been resolved. I used version 1.1 and it worked with that. Further details, I did shutdown everything and then tried again the next day. That could have been the resolution as well? Also, I went straight to v1.1 instead of trying v1.2 again.
[Fire TV Original Android Development] hidroela:
in my case have to reboot two times one to flash the exploit and second to flash recovery.
[Fire TV Original Android Development] canynballa:
what's the point in rooting a fire tv? is it cosmetic to change the look? I'm just curious because I was hoping to remove some bloatware.
[Fire TV Original Android Development] nos1609:
Some people are able to get Russian locale on the device thanks to the root. Even if I know English, it doesn't mean that my aged part of the family does:)

The rest is the same root functionality as always like gapps, adaway etc which is unavailable without root. So it has a point to root if the device is being used outside the US.
[Fire TV Original Android Development] Lei_Wulong:
I suppose with root it is also possible to mount external drives with NTFS and/or exFAT file system. Has anyone done that? I found some apps like Paragon or Stickmount, but I don't know if they work together with the Fire Stick 4K (I did not root so far).
[Fire TV Original Android Development] xdaDarko:
Is it possible to power off Firestick 4k with power button on remote if I root Firestick 4k?

Now if I do that it power off my TV.
[Fire TV Original Android Development] xdaDarko:
I wont to have rooted Firestick 4k but without success.

At that point I get error permission denied:

adb shell

mantis:/ $ su

Permission denied

How to Fix this?

I cannot get root to My Firestick 4k to work.
[Fire TV Original Android Development] xdatin1:
Finaly I have rooted Firestick 4k...

But one problem...with Power off in Power menu I can not power off Firestick but only reboot.

I need power off if its possible.
[Fire TV Original Android Development] xdaDarko:
Does rooted Firestick goes to sleep after 20 minutes?
[Fire TV Original Android Development] tsynik:
Yes (by default). You can set any interval u want over adb.

su
# increase sleep timeount to 30m
settings put secure sleep_timeout 1800000
[Fire TV Original Android Development] xdaDarko:
Sometimes after boot or when Firestick is on sleep mode remote wont work.

Then I use TV remote, push some buttons and then Firestick remote work again.
[Fire TV Original Android Development] Sus_i:
On older fireTV devices that app is named: com.amazon.dcp.apk

Backup and rename with TWRP...
[Fire TV Original Android Development] Pretoriano80:
Sorry for the OT, but now that we have finally unlocked the 4k,anyone has an idea how to (properly) add exFAT/NTFS support?

I tried a few possible solutions, but i couldn't manage to mount it as RW, only read-only.
[Fire TV Original Android Development] sconnyuk:
I've managed to get into the system, basically with root and magisk manager installed, I've installed a different launcher, and am start the launcher.

Thing is even thou Ive disabled the APK you spoke about it still boots to the screen where it asks to pair remote then WiFi then update and goes to the cannot update.

I can am start my other launcher while connected but ideally need it to go straight to the launcher, on top of this the home button brings me to the failed update screen, and the shortcut to device settings in the launcher app brings me there also.
[Fire TV Original Android Development] Sus_i:
Ok, you may try to rename that apps too:

com.amazon.device.software.ota

com.amazon.device.software.ota.override

or if you're able to call su in adb shell, do that:

pm disable com.amazon.device.software.ota

pm disable com.amazon.device.software.ota.override

If the stock launcher doesn't start up, you may need to search/ investigate in logcat for errors

Edit: Years ago the solution was simply renaming that com.amazon.dcp.apk to skip the registration screen. I bet amaz. blocked that solution in nougat. Maybe you can find out what app starts that process. Maybe in logcat, maybe with a task manager app, idk.
[Fire TV Original Android Development] sconnyuk:
ive am started my launcher (toptv launcher v1) v2 dont work for some reason while in there ive started titanium backup up and went through and frozen all update services and the services related to what you told me.

Im not sure how to use logcat but i would of thought that it would work, i could give that a go if its easy enough to use ?

is it an android app or a computer app ? or is it a service inside adb ?

appreciate taking the timeout to help by the way.
[Fire TV Original Android Development] Sus_i:
Logcat is the android system log. You can print the log with adb continuous to a file on your laptop. At boot, connect adb and run:

adb logcat -d > log.txt

(CTRL C stops the log. File saves to the adb folder).

I would do the initial setup thing to the update screen, then look in logcat. Question is what apps could be the culprit for that initial setup thing, what blocks the launcher... Then try freezing with titanium or maybe better 'pm disable **.apk' that app...
[Fire TV Original Android Development] sconnyuk:
Will do, have had a little play with logcat and can see alot of things in the text file.

Will restore to stock and install magisk, and also quite importantly enable ADB with TWRP, then have full access to everything over adb, will post any result and logcat outputs to you tomorrow.

Thankyou for the continued support.
[Fire TV Original Android Development] mircam:
Thanks

Good job! Thanks for your hard work k4y0z and [MENTION=295159]xyz[/MENTION], you are the best! Thank you all who helped them in this task!

For noobies like me, who want to revive firestick (mine at startup just loop forever with starting screen and reboot): after your stick enter in TWRP just type "Adb shell twrp wipe data" on your console, and then "adb shell twrp reboot"
[Fire TV Original Android Development] asislife20:
Anyone else have trouble accessing any of the stick Amazon settings after this? I was able to do it and successfully root, but now none of the settings will open you click and it just automatically closes.
[Fire TV Original Android Development] menace211:
This is for the 4K FireStick only correct? The 4K Pendant is still a no go?
[Fire TV Original Android Development] bilitte22:
Magisk

I m wondering if Magisk can be installed via twrp after rooting the fire tv stick 4k.To block update I need superuser access so I can block Ota update provided that magiskmanager apk is installed.

Can anyone shed the light on that.

---------- Post added at 04:21 AM ---------- Previous post was at 04:16 AM ----------

Thanks k4y0z.
[Fire TV Original Android Development] rbox:
Well that was easy! And my stick isn't on the latest version, so I'll be able to get some update URLs and make a prerooted ROM hopefully this weekend.
[Fire TV Original Android Development] Sus_i:
Yeah, it prints all sys messages in that file, you could set filters but I think it isn't necessary. Run the log only up to the failed update screen and then stop the log...

Thank you very much :good:

I've collected three URLs, partial updates from 6.2.3.1 to 6.2.6.5. Let me know if that is helpful in any way, idk.
[Fire TV Original Android Development] rbox:
I'd need a base full image. I can apply a partial to a full, but I can't create a full from only a partial.
[Fire TV Original Android Development] Sus_i:
Yeah, thats what I've expected. I've updated my sticks to latest infront of the unlock... unfortunately there was no way to let the update fail to collect a full, as the stick stores the update bin in cache.

---------- Post added at 09:59 AM ---------- Previous post was at 09:48 AM ----------

Of course.

You can use a otg cable, a usb hub + usb stick and a mouse...

or you have to power the stick with your laptop, boot into twrp with: adb reboot recovery

and then run something like this:

adb push ~/Desktop/Magisk-v19.3.zip /sdcard/
adb shell
twrp install /sdcard/Magisk-v19.3.zip
twrp wipe cache
reboot -p
[Fire TV Original Android Development] Pretoriano80:
Anyone knows how to unpack the boot.img?Never messed with MTK stuff and so far all tools are failing.

My goal is to modify the ramdisk.
[Fire TV Original Android Development] Pretoriano80:
AIK was the first thing to try but it fails.
[Fire TV Original Android Development] k4y0z:
The MTK-Header isn't used and isn't actually needed on most of these devices, I usually leave it out when building boot/recovery-images.

The reason it fails is probably because you are trying to unpack the kamakiri-patched boot-img

Use the following command before trying to unpack it:

dd if=boot.img of=boot.img bs=512 count=2 skip=2 conv=notrunc
[Fire TV Original Android Development] Pretoriano80:
Yep, that did the trick, thank you!
[Fire TV Original Android Development] brick00444:
I have noticed when Firestick goes to sleep I can wake it using the back or select buttons everytime.
[Fire TV Original Android Development] qbasasa:
Unable to root

I have tried to short the CLK and CMD to the metal frame and nothing happened when using kamakiri 1.2 and the iso image provided.

The computer is lenovo t430 and the cable was the one provided with the stick

Any ideas?

My firestick is:

[ro.product.device]: [mantis]

[ro.build.version.all_codenames]: [REL]

[ro.build.version.base_os]: [NHG47K]

[ro.build.version.codename]: [REL]

[ro.build.version.fireos]: [6.0]

[ro.build.version.incremental]: [0003255372676]

[ro.build.version.name]: [Fire OS 6.2.6.8 (NS6268/2315)]

[ro.build.version.preview_sdk]: [0]

[ro.build.version.release]: [7.1.2]

[ro.build.version.sdk]: [25]

[ro.build.version.security_patch]: [2019-09-01]

[ro.build.version.serial]: [2315]
[Fire TV Original Android Development] brick00444:
I would say keep trying, it takes a few tries (sometimes quite a few tries for me) but it does work. It is worth it to keep trying it is a great rom, I love it.
[Fire TV Original Android Development] Sus_i:
Try to use the other 'unmarked' side of the capacitors... i.e. on the picture is the wrong side of the capacitors marked with a red ring ;)
[Fire TV Original Android Development] Skel40:
I opened up the stick with an extra layer of shield. How do I remove it?

I see 7 sticky pieces of tape stuck to it. I also tested out the kamakiri directory in terminal and it says waiting for bootrom still when I plugged in the stick. I need help removing this extra layer of protection so I can successfully root the stick
[Fire TV Original Android Development] qbasasa:
Yup tried it yesterday worked like a charm thanks!
[Fire TV Original Android Development] Sus_i:
Make sure you have 'one' of the sticks with a MTK SOC and/or compare the pictures...
[Fire TV Original Android Development] davinci2798:
Hello, after root i got massage on screen

: android system

There is na internal problem with Your device. Contact Your manufacturer for detalis.

And when im trying to register in Amazon it bringing me back to pairing screen, farest i can go it is wifi connection.

Did i brick my Stick?
[Fire TV Original Android Development] r00tamerica:
I've got a question. Where can I get a patched linux kernel? Will regular Kali Linux do?
[Fire TV Original Android Development] davinci2798:
So now i flashed stock rom and massage gone but Stick is coming back to pairing screen non stop.

What i made wrong?
[Fire TV Original Android Development] luniz7:
I’m having a really difficult time trying to short the capacitor. Which other side are you talking about? I’m trying to do it with foil. Unless there’s something easier.
[Fire TV Original Android Development] Sus_i:
I mean that electrical part (capacitor) has two ends soldered to the board. You may short the side that isn't marked... Bridging both ends with tinfoil will work too, as one side of the capacitor is GND.

https://xdaforums.com/showpost.php?p=80487815
[Fire TV Original Android Development] luniz7:
Thanks for the reply. However in seeing your photo it revealed my idiocy.. I forgot to put power to the Firestick [emoji2359][emoji2359][emoji1787]
[Fire TV Original Android Development] raphael.e:
Thanks a lot for the instructions. Are you guys also facing the issue that the github download speed of the file fireiso-1.0.0.iso is too slow? it takes forever. Is anyone having it on gdrive for example? Thank you!
[Fire TV Original Android Development] dmcfo20:
After getting everything working and twrp installed, I cant connect my fire stick to adb. Whether i boot into twrp or boot normally it wont find my device. I want to flash the prerooted rom, and I still can, but I cant disable updates afterwards. Any ideas of what's going on? Adb debugging and unknown sources are turned on.

EDIT: apparently my OTG cable was preventing my pc from recognizing the fire stick
[Fire TV Original Android Development] luniz7:
Can anyone help me out. I used the live usb and flashed my Firestick. Ran the fast boot script and it said reboot. Nothing showed up on the computer so I plugged it in to the tv and it just sits on this screen. What do I do?
[Fire TV Original Android Development] brick00444:
I would try the unbricking again but have it connected to the tv while you do it.
[Fire TV Original Android Development] luniz7:
I did the process again and now I get std:bad alloc when i push the mantis zip. What now?
[Fire TV Original Android Development] brick00444:
Try "/sdcard" not "/ sdcard" no space between the / and sdcard. Thats what worked for me. Hope that helps.