yashsingh1/xdaforums huggingface dataset:
[Fire TV Original Android Development] Michajin:
"your" and "Response"

Thank you for you contribution. Be well!
[Fire TV Original Android Development] Michajin:
Thanks! Enjoy the free labor put into freeing your device.
[Fire TV Original Android Development] Michajin:
It is not about about a donation to society, but to the free exploit you used.

It isn't a view and it isn't free to the people who expose the exploits. It is a fact you are pushing for another route (VIA VM) on install. This is confusing to some. Unless you are willing to troubleshoot and assist others with your install option. I am sorry a offended you. Many people reap the rewards of the developers who create and assist with these hacks, without anything but mostly a thank you. Yes, I am sad I guess because I care about the development community. But since you feel you must have the last post regarding this argument, this is not the forum to debate, I hope you enjoy your unlocked Mantis. Take care!
[Fire TV Original Android Development] Flakie:
I wrote a free ADB app. Lots of people are using it. A couple have asked for my paypal and I said no.

Not fantastic but allows you to connect to devices and save them in a config file for each device with the settings for it.

APK install, update, uninstall and apk information etc.

Reboot device, links into scrcpy with no tryping. Enter the IP address and port once and save the config and call it up next time you want to connect (to do lots of adb stuff without touching a keyboard).

I provide them support with connnecting to their devices over the internet (router port forwarding etc).

I accept feature requests.

The new version will be given to them soon too. It has much much more. Even more so now I am adding in rooting features.

Yes, if anyone wanted help with a VM then I would assist. No problems with that at all :)

Update: I know me using the VM method did not go down too well here, but if anyone does want to try it, then I have put together a video of how to.

There is no real need to use this method, in most circumstances, but if like me it will be a great help or you want to give it a try, just ask.

For me it became a necessity. Space is limited here and I have to run the boot usb on a laptop on the floor.

My back is killing me and I will be running this on 50 firesticks.

Because that is how many I support and its growing by an average of 2 a week. I do this because I love helping others and sharing the knowledge.

I wrote a guide to running the exploit and atatched it to this thread. Designed for Linux newbies like me.

Also, here's a screenshot of my ADB app:

[IMG="Flakie ADB GUI"]https://flakie.co.uk/downloads/flakie-adb.jpg[/IMG]

If anyone wants to use it, just ask and I will send the link. It is a simple C# Windows-only app (with a couple of gui bugs) but the updated version in a month or so will have so much more :)

It is and will always be freeware and no ads :)
[Fire TV Original Android Development] xionbunny:
sure id like to use it, been looking for a solution like this.
[Fire TV Original Android Development] Flakie:
PM sent :)
[Fire TV Original Android Development] nJoy-Android:
Could someone plz explain how to update the FireOS with TWRP?

Im not noobish with TWRP, but with Fire TV Stick.

Just read about the new Profiles for Amazon like Netflix.

Rooted FireTV stick 4K with Magisk present. Updates disabled through adb commands.Also OTG USB cable,but no powered usb-hub...

Are the new files online?

Problems with installed apps after flashing new OS?
[Fire TV Original Android Development] Michajin:
What OS are you on now? This is the latest i have seen, rename .bin to .zip to flash. I havent had any update issues...

https://xdaforums.com/fire-tv/general/official-stock-image-fire-tv-stick-4k-6-t4088247
[Fire TV Original Android Development] nJoy-Android:
Thx for replay.

One with Fire OS 6.2.6.8

And one with 6.2.7.1 ( I was sitting on the remote and any combo does properly factory reset)

So just flashing after renaming within TWRP? That's all? Sounds easy - will test tomorrow.

By the way. Could I also flash newest Magisk 20.4 in TWRP?

Because of Problems with updating through the magisk manager...
[Fire TV Original Android Development] Michajin:
Yes, you could also install the prerooted one from here.

https://xdaforums.com/fire-tv/development/fire-tv-stick-4k-mantis-prerooted-stock-t3983091

Yes you can update magisk through twrp. But there is some risk, i am on 20.0, not sure if there is a benefit from updating. Seems like i have 20.4 on one of mine... Just always have a back up.
[Fire TV Original Android Development] tsynik:
No any risk with Magisk 20.4. It's suggested as latest Magisk Manager which works OK with FTV Remote. Just flash stock fw zip and Magisk-v20.4 zip after in TWRP (can be done in one session). And you'll have current fw with root.
[Fire TV Original Android Development] Pat1981:
I would like to clean /sdcard via twrp from my firetv stick. there is no twrp wipe command for sdcard. Any tipps how to cleanup /sdcard? (I would like to reset firetv completely with no "temp old datas)

thanks

(wipe cache / dalvik resets only firetv, doesnt remove old appdata from kodi ,.. and other apps.)
[Fire TV Original Android Development] Sus_i:
There is a wipe button for /sdcard in TWRP, it is 'Internal storage'

For a factory reset, wipe data too.
[Fire TV Original Android Development] Pat1981:
sorry, I need this as twrp command... (no usb otg cable available)

thanks for your help!
[Fire TV Original Android Development] Sus_i:
From TWRP shell, reboot into hacked fastboot:

adb shell reboot-amonet

Then run:

fastboot devices

and in case there is your device, run:

fastboot erase userdata

That will wipe data and sdcard.
[Fire TV Original Android Development] BLACKPHOENIXRIZIN:
[MENTION=4563980]Flakie[/MENTION]. Just need 2 know how u got ur screen shot into ur post #940? I need 2 do the with a pic on my phone but don't know how 2 do it. Could u plz tell me how u did urz? Thx.
[Fire TV Original Android Development] Flakie:
I am not sure I follow you. How did I attach the image to the post? I just uploaded the image using ftp and then used the Insert Image button to enter the URL of it.

Hope thats what you mean :)
[Fire TV Original Android Development] BLACKPHOENIXRIZIN:
Yeah, that answerz most of it, ftp? I used it briefly I believe last yr, so again how does it work, & u uploaded the screenshot 2 where?
[Fire TV Original Android Development] Pat1981:
tried it and can confirm, it works!

finally you need to enter

fastboot reboot

as last command and FireTV will reboot and wipe all data.
[Fire TV Original Android Development] Flakie:
PM sent.
[Fire TV Original Android Development] brick00444:
I'm having a problem unlocking a 4k stick. I can short it and remove short and hit enter then it starts the process. Problem is when it gets to the part

[2020-07-20 11:27:12.518253] Check GPT

Traceback (most recent call last):

File "main.py", line 119, in <module>

main(dev)

File "main.py", line 33, in main

switch_user(dev)

File "/root/Desktop/kamakiri-mantis-v1.2/kamakiri/modules/functions.py", line 114, in switch_user

raise RuntimeError("what's wrong with your GPT?")

RuntimeError: what's wrong with your GPT?

Any ideas

---------- Post added at 12:19 PM ---------- Previous post was at 11:41 AM ----------

is there a way to fix the gpt? I've seen a gpt fix for the "tank" version but not "mantis".
[Fire TV Original Android Development] Pretoriano80:
Take a look here - > https://xdaforums.com/fire-tv/orig-development/unlock-fire-tv-stick-4k-mantis-t3978459/post82629101
[Fire TV Original Android Development] brick00444:
Sorry for missing that. I tried it and get this after it starts Flashing GPT it gets to 3/34 and then fails:

root@sysresccd ~/Desktop/kamakiri-mantis-v1.2/kamakiri]# ./gpt-fix.sh

[2020-07-20 13:17:01.077357] Waiting for bootrom

[2020-07-20 13:17:05.097808] Found port = /dev/ttyACM0

[2020-07-20 13:17:05.098137] Handshake

[2020-07-20 13:17:05.098436] Disable watchdog

* * * If you have a short attached, remove it now * * *

* * * Press Enter to continue * * *

[2020-07-20 13:17:07.106316] Load payload from ../brom-payload/stage1/stage1.bin = 0x27C bytes

[2020-07-20 13:17:07.133253] Let's rock

[2020-07-20 13:17:07.139917] Waiting for stage 1 to come online...

[2020-07-20 13:17:07.142050] All good

[2020-07-20 13:17:07.142129] Load 2nd stage payload

[2020-07-20 13:17:07.142190] Load payload from ../brom-payload/stage2/stage2.bin = 0x36D4 bytes

[2020-07-20 13:17:07.142225] Send 2nd stage payload

[2020-07-20 13:17:07.166192] Party time

[2020-07-20 13:17:07.167495] Waiting for stage 2 to come online...

[2020-07-20 13:17:07.293855] All good

[2020-07-20 13:17:07.296005] Flashing GPT

Traceback (most recent call last):

File "main.py", line 119, in <module>

main(dev)

File "main.py", line 29, in main

flash_binary(dev, "../bin/gpt-mantis.bin", 0, 34 * 0x200)

File "/root/Desktop/kamakiri-mantis-v1.2/kamakiri/modules/functions.py", line 69, in flash_binary

flash_data(dev, data, start_block, max_size=0)

File "/root/Desktop/kamakiri-mantis-v1.2/kamakiri/modules/functions.py", line 58, in flash_data

dev.emmc_write(start_block + x, data[x * 0x200:(x + 1) * 0x200])

File "/root/Desktop/kamakiri-mantis-v1.2/kamakiri/modules/common.py", line 199, in emmc_write

raise RuntimeError("device failure")

RuntimeError: device failure
[Fire TV Original Android Development] 2smok3d:
Im having a problem with twrp guys.

To start I already have magisk installed and have su access but now when I boot to twrp im stuck on the "swipe to allow system modifications" screen. Ive tried connecting through tcp and usb and my adb connection freezes as soon as twrp boots and that "swipe to mod" screen pops up. I even grabbed an old usb hub for mouse support but nothing. Is there a special way to get into the twrp menu?

edit: im dumb. I wasnt using shell
[Fire TV Original Android Development] bird333:
Are you saying there is a way to enable ADB wirelessly over TWRP? If so how?
[Fire TV Original Android Development] BLACKPHOENIXRIZIN:
Linux live exploit iso

I have been able 2 download & burn the (ISO) file 2 flashdrive, but when I attempt 2 boot into it, it makez it almost 2 the end then I get an error msg. I'm hoping someone on the site will be able 2 decipher the error msg & help me find a fix so I can complete the rooting process 4 my firestick.

https://www.flickr.com/photos/189468486@N04/50152959298/in/dateposted-friend/
[Fire TV Original Android Development] this.guy.lol:
NEED HELP

im slow amd need help rooting.

how do i boot the iso on my win10?

wehat format do i make the usb? im on x64 on my win10

how do i do evertthing? noobie here with fs4k
[Fire TV Original Android Development] Sus_i:
google: rufus.ie
[Fire TV Original Android Development] JustInXDA89:
I have installed the iso on a flashdrive via rufus.

When I boot from the drive I get the same error as BLACKPHOENIXRIZIN.

Is there any way to fix this problem?
[Fire TV Original Android Development] Skel40:
Try using Etcher. This is what I used to get the Iso to load properly after pressing f12 and making Windows boot from a USB.

https://www.balena.io/etcher/
[Fire TV Original Android Development] gb160:
Guys, apologies if this has already been asked.

Can someone point me in the direction of uninstallation steps, so the stick is completely back to stock.

Im giving this device to a family member who wont require any of these bells and whistles.

Cheers.
[Fire TV Original Android Development] Donphillipe:
Just search here for "factory ROM" of the version you want and load in the ZIP from TWRP like you did with the original rooting you did.
[Fire TV Original Android Development] gb160:
Cheers buddy, only problem is im not finding any factory rooms as .zip files when I search...just a couple of .bin files
[Fire TV Original Android Development] Donphillipe:
Try Google for one of these:

update-kindle-mantis-NS6268_user_2315_0003255372676.zip

update-kindle-mantis-NS6271_user_2493_0003590962564.zip

**** maybe here?

https://xdaforums.com/fire-tv/general/official-stock-image-fire-tv-stick-4k-6-t4059777

---------- Post added at 06:13 PM ---------- Previous post was at 05:35 PM ----------

I don't know what happened to

update-kindle-mantis-NS6268_user_2315_0003255372676.zip

I wasn't able to find this either. It must have been taken down or replaced with the 6271. I'd go with the 6268 personally and let the new owner of it download the update if they want it. if you can't find it, let me know and I'll try to upload it somewhere. Looks like the most recent stock rom may have some issues.
[Fire TV Original Android Development] gb160:
Cheers, as you say it looks like its been taken down...lots of mentions of it, but no file to download.

If you could upload it that would be great.
[Fire TV Original Android Development] Donphillipe:
Perhaps someone with a better connection can share. the file is over 600M and I am currently out of the country on a 1M upload connection and Google drive says 349 hours to upload and has already failed twice.
[Fire TV Original Android Development] 0815hoffi:
https://d1s31zyz7dcc2d.cloudfront.n...dle-mantis-NS6271_user_2495_0003590963076.bin
[Fire TV Original Android Development] Donphillipe:
I finally had to ask a friend to upload it but here you go. Not sure how long the link will be alive ....

https://drive.google.com/file/d/1yMgX9pA9J4E8r_9g2Jh3QOrU8kinvqoJ/view?usp=sharing
[Fire TV Original Android Development] gb160:
Cheers for your assistance buddy, all done!
[Fire TV Original Android Development] Skel40:
I have 2495 of 6.2.7.1 somewhere on my computer so if that link gets taken down, I got a backup of the .zip
[Fire TV Original Android Development] tsynik:
Hi k4y0z, looks like preloader, lk and tz changed in 6.2.7.3 version of fw (in 6.2.6.8/6.2.7.1 they are the same). Will you release kamakiri-mantis-v1.3.zip with them to have option of twrp install for it?
[Fire TV Original Android Development] Donphillipe:
Would you explain this a little further, is there a new firmware that can't be hacked?
[Fire TV Original Android Development] k4y0z:
Have you experienced any issues with the old pl/tz ?
[Fire TV Original Android Development] tsynik:
Personally, I prefer to stay on 6.2.7.1 fw. Some guys who installed new fw over TWRP told me Prime Video still works.

But I remember old days when it was needed to sync fw 6.2.6.5+ with corresponding keys after update from twrp as those parts not written with it.
[Fire TV Original Android Development] sam7323:
Brilliant work, guys!

Any chance to fix playback interlaced videos? The problem is well described here: github.com/amzn/exoplayer-amazon-port/issues/94
[Fire TV Original Android Development] kigba:
I personally have no way to restore the capacitor. But I have a friend who understands this and repairs mobile phones. Later I go to him and he carefully examines the damage under a microscope. I visited him yesterday and we soldered the condensate from a mobile phone (donor), but that did not help. After three unsuccessful attempts to recover with the capacitor already soldered, I again poked the needle and tore it off again. But that is no longer important. Today we will try again more carefully. For reference, the contour frame is soldered to the board; it cannot be removed. Therefore, I just gently torn off the corner of the frame to have access to the soldering point.

[IMG="stik-2"]https://s8.hostingkartinok.com/uploads/images/2019/10/c0bd2c9fefce0fc5aa8d575f46649a1a.jpg[/IMG]
[Fire TV Original Android Development] Velcro31:
First of all thank you very much for the unlock! I ended up just soldering a small 30 awg wire to the capacitor and to a ground point. It felt like a red ribbon store opening ceremonial, using my cutting pliers to snip the wire when the script told me to "release the short" and seeing all the magic happen.

This is probably my only android device in years so i lack a bit of experience. I installed Magisk and root is now running and after that disabled ota updates. Can't wait to tweak the gui since hijack launcher has some quirks tbh but it served its purpose well. My main wish is to install Disney+. Can i just flash OpenGapps tv-stock ARM/ARM64 (which one do i need? ARM right?) to get the Google Play Store working. Or am i missing something?
[Fire TV Original Android Development] Sus_i:
OK, had a look, you're missing a ceramic capacitor. I measured that two pads. One side is ground, the other side is a power line from about 1.1v. Consequently that can't be the CMD line (as the picture from OP states, i.e. labeled wrong).

I guess that is the power node for the core regulator, VDDi., common voltage is 1.1v.

You can try to repair that, simply solder a 0.1uF capacitor to the pads, i.e. connect a 0.1uF capacitor from VDDi to ground. No guarantee, as I have to guess the value, I haven't got any schematics, but it's a common value! Good luck!

---------- Post added at 02:21 PM ---------- Previous post was at 02:17 PM ----------

Don't flash any Gapps Package! There isn't a stock rom available until now.
[Fire TV Original Android Development] falldaemon:
The device works, I don't play :) tnx
[Fire TV Original Android Development] kigba:
Thank you for your support and finding a solution to my problem. From your message, you can conclude that 1.1v power for flash memory does not come. Actually, the presence or absence of a condenser can not be a big problem, since this is just an additional filter from interference from the power supply of the microcircuit. However, we assumed that it was a data line of flash memory, but not power. Thank you again, let's try to check the voltage at this point.
[Fire TV Original Android Development] Sus_i:
No. ;)

Most emmc chips have three power domains, VCC, VCCQ and VDDi.

VDDi is the 'internal' regulator connection to an 'external' decoupling capacitor.

If I guess right, then this capacitor has a value about 0.1uF

You see, the voltage is still there, only the capacitor is gone. The internal to external connection is lost. That renders the internal regulator unstable.

---------- Post added at 03:26 PM ---------- Previous post was at 03:14 PM ----------

Data or CMD lines doesn't need capacitors.

Manufacturers connect usually CMD and DAT0-7 lines with a resistor to VCCQ.

Only CLK is a independent line (with a resistor in that line).
[Fire TV Original Android Development] k4y0z:
Yes, you are correct, the picture is wrong, only the DAT0 should be correctly labeled.

I took the picture from [MENTION=4381075]hwmod[/MENTION] who guessed the labels and hence marked them with a "?".

The points still work fine for shorting, which would also indicate that a missing capacitor at these points would be fatal.
[Fire TV Original Android Development] Sus_i:
Yes, of course. I know hwmod doesn't own that stick and guessed points for shorting. And for sure, his suggested points have an impressive reliability to get into bootrom. :good: Many thanks to him.

I don't checked any points with an oscilloscope, I'm also only guessing ;)
[Fire TV Original Android Development] cristimnt:
Haven't tried the unlock yet but waited for it for months! Thanks a lot!

I have an uninitialized 4k stick. Would it make sense to update it to latest version and unlock it afterwards?

Or it is better to unlock it without being updated?
[Fire TV Original Android Development] Sus_i:
I updated to latest (6.2.6.5 + two or three additional system component updates) and did the unlock afterwards. worked just fine.
[Fire TV Original Android Development] kigba:
Today I was not able to solder the capacitor, I hope I will do it tomorrow or later. However, the circuit board was examined - everything is in order with it, there is no damage. At the second contact there is 1.1v. I definitely know two people, the stick works without this capacitor. Still, I have doubts that the problem is in the hardware, perhaps an error occurred while executing the first Unlock script. Are there any options to fix the bootloader?
[Fire TV Original Android Development] k4y0z:
The script flashes the bootloader, so if it went through without errors, the bootloader isn't the issue.
[Fire TV Original Android Development] Sus_i:
No damage except you ripped a capacitor from the board ;) :laugh:

Edit: Forget about the scripts. Your stick stucks into bootrom, caused by the missing mlc. I've told you that earlier this day.

I think it isn't possible that a stick is working without a propper VDDi connection. Trust me, the manufacturers will know how to connect their chips :p
[Fire TV Original Android Development] kigba:
this is how the script works for me. This process starts immediately after power is supplied (insert the USB cable), without any short circuits of point 1.1V. In the process of running the script, I press "enter" again. Screen of the script below

[IMG="screen"]https://s8.hostingkartinok.com/uploads/images/2019/10/efb89612263c7193378eae3737a8b258.jpg[/IMG]

Please tell me if there are errors in the script?
[Fire TV Original Android Development] asislife20:
I actually ended up breaking the same capacitor, and my firestick worked fine untill I messed it up trying to flash gapps.
[Fire TV Original Android Development] kigba:
that's what I’m talking about, that a failure of the capacitor should not lead to a brick, as in my case. Maybe there is some kind of full rom .img for the firmware of the device? Or another method for revitalizing a brick? Is it possible to flash, by analogy with the unlock boot, another boot from the backup twrp or stock boot?
[Fire TV Original Android Development] Sus_i:
My thoughts about it:

1. The first script needs that you connect a shorted 4k stick. That short to ground renders the emmc unaviable, the SOC stops into bootrom, can't boot at all at this point.

2. Your stick goes into bootrom without a short, see your posts about this.

3. The script finds the bootrom, but needs that you remove the short to go on, as it wants to write to the emmc. It tells you : Remove the short and press enter.

4. Question is, how do you remove a short, even though you never shorted???

5. As the emmc isn't aviable, because of the permanent shorting, how would any kind of stored firmware on the emmc play a major role? Isn't it like you ripped of the whole emmc?

Maybe I'm wrong and someone could explain this to me?

Edit: Admittedly, that short isn't that permanent, you can see this on your picture with the script... but at least, I bet it renders the emmc very unstable, you can't use it without a repair.
[Fire TV Original Android Development] k4y0z:
That looks fine, only this line would suggest it never booted up after flashing:

rpmb looks broken; if this is expected (i.e. you're retrying the exploit) press enter, otherwise terminate with Ctrl+C"

Which is confirmed by the fact that it apparently goes straight into bootrom.

It's not an issue with flashing... It doesn't even load up the preloader.

The EMMC actually seems to be accessible, since it is able to read the GPT and flash all the partitions fine.

If EMMC was indeed inaccessible you would get an error like the following right after "Check GPT":

Traceback (most recent call last):
File "main.py", line 114, in <module>
main(dev)
File "main.py", line 28, in main
switch_user(dev)
File "/home/chaosmaster/kamakiri/modules/functions.py", line 111, in switch_user
block = dev.emmc_read(0)
File "/home/chaosmaster/kamakiri/modules/common.py", line 180, in emmc_read
raise RuntimeError("read fail")
RuntimeError: read fail

Try connecting it to a power brick instead of powering it through USB.
[Fire TV Original Android Development] kigba:
Everything is logical! I agree with you. Then you need to examine the board in more detail, but today it was examined carefully. There is nothing superfluous for a short circuit on the capacitor contacts. When power is applied, the second pin has 1.1V. When checking with a tester, there is a resistance between the capacitor contacts. Nothing indicates a shorted contact. This is also a fact. If possible, tomorrow I will try to check the second capacitor nearby, along the board's tracks it is very likely that they have a common contact with a torn capacitor. Visually, it is not damaged (microscope), but it will have to be checked more thoroughly.