yashsingh1/xdaforums huggingface dataset:
[Fire TV Original Android Development] Veg-Meat:
I DID IT! I just kept re-trying lol it seemed that at one point it was Type1 bricked so I followed the steps for that then shorted it again and did the rest!

Thank you so much everyone, especially @Bertonumber1 for all your help and support with all this cool stuff I managed to boot TWRP on my sloane box! I am currently testing FireOS and going to check whether TWRP is still bootable or not and then I am going to try and get it to run either Debian Linux or Arch Linux ARM so I can use it like a Raspberry Pi with more powerful hardware!

This has been a great learning process on how to do this kind of stuff as I have only had experience before with using Xiaomi's Bootloader Unlocker which is much simpler than this!

Thank you @Rortiz2 for making this great tool to unlock the capabilities of my FireTV2. I would like to ask your permission to make a blog post on this with a guide on how I did it as I would like to make it slightly easier for new users to understand how to do this without having to bother forum members on this thread like I have :)
[Fire TV Original Android Development] Rortiz2:
Sure, just mention the original thread.
[Fire TV Original Android Development] LocoMexican:
Veg-Meat, I would like to follow your efforts on running Debian Linux on this kind of device. Sounds like a fun project. Regardless, good luck with your efforts. I hope your pinky healed to your satisfaction.
[Fire TV Original Android Development] meohmy:
I have updated 2 x firetv's in the past using amonet 1.01, magisk and os 5.2.7.6 but upon trying to update

another box today using amonet 1.1 the process has gone wrong.

From a pre rooted rom I booted into twrp and installed amonet 1.1 and did the wipe

as before, then installed SU as opposed to magisk plus os5.2.7.8

The box then rebooted to the amazon interface successfully, I then tried to reboot into twrp using the adb commands

'reboot twrp' which caused the box to reboot back to the amazon interface. I then tried 'reboot recovery'

and the box rebooted to a failure screen - see photo. It appears that twrp has been overwritten by the amazon os.

The box will reboot successfully into the amazon software but I am unsure how to get twrp re-installed.

I have tried to start from scratch and reload a prerooted rom but after chmod of mtk-su the script fails to run,

probably because of the different file structure.

Any help would be gratefully appreciated.
[Fire TV Original Android Development] Michajin:
The prerooted rom disables stock recovery (stock or TWRP if flashed over stock). TWRP from the pre-root runs on 2nd init and disables stock recovery. Likely you disabled the rcovery, wit hthe prerooted rom, then when you wiped you lost TWRP. I would suggest you try the shorting method now, unless you have root access.
[Fire TV Original Android Development] meohmy:
The install of amonet 1.1 was successful and the wipe in the new twrp was also successfully completed

as I read the confirmation of the new file system in the new twrp install after wipe, I am therefor not sure if the pre rooted rom was the cause. If there are no other suggestions then I may have to go down the shorting route but hopefully not.
[Fire TV Original Android Development] Michajin:
If you flashed the pre-rooted rom, it will disable TWRP on the unlocked version.

"Starting with this update, stock recovery will be disabled to prevent stock updates from being flashed. Please refer to the instructions above for managing stock recovery."

Try this....

Managing Stock Recovery

Starting with 5.0.5_r3, stock recovery gets disabled. This means you cannot reboot in to stock recovery manually or automatically because of a system update. This will make it safer for people who forget to disable updates. You should still disable updates though. If for whatever reason, you want to reenable it, or verify it is disabled, you can use the manage_recovery program. Under normal circumstances, you should never need to use manage_recovery.

Connect to adb and start a shell

Switch to root with su

Run manage_recovery (if you do not run su first, it will seem to run, but won't actually be able to do anything)

Code:

manage_recovery

There are 3 different scenarios that manage_recovery will detect and prompt for.

The first is when stock recovery is disabled, it will look like this:

Code:

Checking current stock recovery status... NOT STOCK

Checking for reason... DISABLED

Stock recovery is currently disabled,

Would you like to enable it?

Type 'yes' to enable it, anything else to quit.
[Fire TV Original Android Development] meohmy:
Unfortunately that did not work, says su not found. I also tried 'manage_recovery to see what would happen and that wasn't found either.

Many thanks for your reply but I think I will need to read the whole thread again and resort to the shorting method. I hope my hands will be steady enough, as the wife always says 'age is a bugger'
[Fire TV Original Android Development] Michajin:
I would suggest to use magisk and use a stock rom, then block updates. The shorting method wasn't bad, i had to use it when i installed a prerooted version. Use aluminum foil, it may take a few times. If you can find root access you probably dont need to short.
[Fire TV Original Android Development] meohmy:
When using the shorting method I assume you only short DAT0 to ground?

In post 2 of this thread it says that 'If FireOS is still accessible there are other means of recovery, don't continue.' I can boot up into FireOS with no problems and the box will work, I just seem to have lost my option of booting to recovery. What are the other methods of recovery please as my eyes are are threatening to go on strike from so much reading.:cool:
[Fire TV Original Android Development] LocoMexican:
Sus_i, is there a way an unsophisticated but interested member such as myself can capture future new full stock sloane updates such that it can be installed on my device short of having to ask admins such as yourself to do that job for me? It's probably over my pay grade, but if it's not too complicated, maybe you can post a suggestion. Thanks.
[Fire TV Original Android Development] mekz1:
So I'm a little in over my head and don't want to use this place as a hand-hold section but I had a few small questions as I'm now waiting on a A-A cable to arrive in the mail before I can tinker with any of this. I got the Fire TV 2nd and power cable separately in the past week - can plug it and get the kiosk mode to respond to some keyboard commands with ctrl alt escape + print screen and what not (read somewhere else to do that) - I take it that's a good sign and not a completely dead device if it's opening up other menus still) - I'm unfamiliar with Linux and wondering if I can use win10 virtual environment system for Linux or better off going with a full Linux install - Either way it should be an interesting experience

Secondly I'm a little unsure of whether I'm supposed to actually open the hardware / Fire TV up and maybe "do something" to a chip in there..If so that's completely grey area but in some of the "walkthru's" it looks like there might be more program based solutions where none of that's necessary. My only wish for this Fire TV device anyways is to getting it functioning as just any regular product you'd get directly from Amazon without any extra software btw if that would make the process any easy

Either way I'm not look for all the answers, just a few points in the right direction since I got a couple days before my cord gets here - From what I read it seems like there's some good failsafes built in the software side of things so I can screw it up for hours on end and not have to come back with each little problem (right?)
[Fire TV Original Android Development] mekz1:
Also if my post was bad and this not the right section for it, I'm sorry please throw it out
[Fire TV Original Android Development] Sus_i:
Take a look here:

https://xdaforums.com/t/extract-past-present-fireos-cloud-front-links-for-misc-fire-devices.4259997/

Note: You don't need to mess with the build.prop for new updates, only if you want to pull an older one.
[Fire TV Original Android Development] LocoMexican:
Thanks Sus_i. One more project to try out in my free time.
[Fire TV Original Android Development] Toothless_NEO:
Wiping Data, cache, and Dalvik is understandable, but why do people say you need to Wipe internal Storage? That part just doesn't make much sense to me.
[Fire TV Original Android Development] Rortiz2:
Because the entire partition table changes and userdata is moved to the end of the GPT.
[Fire TV Original Android Development] Veg-Meat:
So far I have not tried many things, I have just been doing a crap ton of research lol. I found that there is a Chromebook device which has the exact same model of CPU as this Fire TV 2 and there is an ArchLinuxARM image for it already with the rootfs only problem is I have not yet figured out how to flash it onto the FireTV2, I need to learn how to make those custom ROM zip files with the boot.img and flash the rootfs and stuff... As for Debian Linux, there does not seem to be much support for this CPU so I have currently focused my efforts on ArchLinuxARM to aim to get a successful bootup...

There is also a Linux distribution called postmarketOS (based on Alpine Linux) which is designed for smartphones and they have some tools which allow you to make a .zip file of their Linux distro in TWRP and someone has already made a succesful port of postmarketOS for their AmazonFireTV 1st Generation Box. I am currently trying to get postmarketOS to boot up on the AmazonFireTV2 in order to see what Linux on this thing would be like. I also got some help from a NixOS Mobile (a Linux distribution for mobile phones based on NixOS) developer who has pointed me in the direction of some resources in order to figure out how to package Linux Distros into TWRP flashable .zip files.
[Fire TV Original Android Development] LocoMexican:
Thanks for the update and good luck.
[Fire TV Original Android Development] phier:
hi is this about Fire TV Cube gen2?
[Fire TV Original Android Development] meohmy:
In post 2 in repect of recovery it says

'If FireOS is still accessible there are other means of recovery, don't continue.'

Given that I have failed miserably to short the board to complete the procedure and I can fully boot into FireOS with the box being fully usable, what is the best way to recover twrp?

Initially I had successfully completed the unlock, installed twrp and then installed os 5.2.7.7 through twrp,

but when attempting to reboot to recovery my twrp recovery had vanished along with stock recovery.

I have asked this question before but never received a reply as to 'the other methods of recovery'.

Any help appreciated
[Fire TV Original Android Development] LocoMexican:
Have you tried using adb command - adb reboot recovery?????
[Fire TV Original Android Development] meohmy:
Unfortunately, yes I have tried that and it doesn't work
[Fire TV Original Android Development] Michajin:
Did you flash the pre-rooted 5.2.7.7? You might need to try running the boot-recovery.sh if that doesnt work boot-fastboot.sh Should be in the amonet folder in the OP download... pre-rooted 5.2.7.7 blocks stock TWRP. If you can't get into twrp with boot-recovery, then if boot-fastboot works, then run the fastboot-step.sh.
[Fire TV Original Android Development] meohmy:
Thanks for the replies, no I did not flash the pre-rooted rom and boot-recovery.sh does not work.

I have not tried boot-fastboot.sh and fastboot-step.sh but I will certainly try tomorrow and report back on the results.
[Fire TV Original Android Development] meohmy:
Tried both boot-fastboot.sh and fastboot-step.sh commands today, boot-fast-boot.sh command says not found.

Wnen I tried sudo boot-fastboot.sh I also go the message that sudo was not found so I tried boot-fast-boot.sh out of curiosity and it showed as waiting for preloader so hopefully the box can be brought back to recovery.

I have the chance to use an electronic microscope on Sunday so hopefully I can go the shorting method route, I just hope I can keep my old hands steady enough otherwise I might get myself an x96 max+ box from here.

https://droix.co.uk/product/x96-max-android-9-pie-smart-tv-box-kodi/
[Fire TV Original Android Development] jbvid:
Hi

Sucessfully unlocked and rooted my fire tv2 and tryng to block updates but getting the java error below, Using Minimal ADB and Fastboot on Windows 10, any advice please.

jb

pm disable com.amazon.device.software.ota

Error: java.lang.SecurityException: Permission Denial: attempt to change component state from pid=10543, uid=2000, package uid=32012
[Fire TV Original Android Development] sconnyuk:
You need to setup magisk apk, grant permissions and use the same command with root privilege
[Fire TV Original Android Development] jbvid:
Thanks, will try that

regards jb
[Fire TV Original Android Development] jbvid:
Hi

Tried to sort this but dont get the chance to grant/accept settings. I have usb mouse and usb keyboard but they wont operate though my USB 3 Hub, how is it done?

Regards jb
[Fire TV Original Android Development] LocoMexican:
If

You say you are unlocked and rooted and using adb in a windows environment. If so, Open a terminal and use adb commands and follow the posted script? For instance:

adb connect 192.168.X.XXX

If you get connection, then:

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

pm clear com.amazon.device.software.ota

exit

exit

If your device is not rooted, you will not get past the command "su". If this is the case, then install Magist (I use v22) from twrp. Reboot system. Go to settings and then "applications" and see if magist is there. If so, open it and it will ask you to download the app (what used to be magist manager). From the installed app, go to app settings and set up your super user permissions. You can change the prompt for su there to "grant" always and not have to deal with your mouse situation. And, if you want to use the mouse, you can change the amount of time you have to respond to the prompt up to I believe 30 or 40 seconds. Regardless, if you set default to "grant", you can then go back to your adb set-up and enter the blocking commands. Hope this helps. Been there done that too. Good luck.
[Fire TV Original Android Development] jbvid:
Hi Guys, thanks for the help and guidance/pointers, found the part in Magisk settings, (Automatic Response to Grant)

Then all commands worked fine, now ota blocked.

Regards jb
[Fire TV Original Android Development] meohmy:
I finally managed to recover my Firetv using the instructions provided, but with a twist.

No matter how hard I tried I could not short dat0 successfully using any type of foil or pin etc so I decided to go the 'hard easy' route.

I soldered some mobile phone speaker wire to dat0 pin and, along with a micro switch from an old satellite receiver which I mounted to a screw hole, I managed with no problems. Should I need to recover the box in future I just press the switch to short, I have now ordered a mobile phone microswitch which I will mount on the rear of the circuit board then drill a hole in the bottom plate so I won't have to open the box again.
[Fire TV Original Android Development] jbvid:
Hi

Nice mod, very lucky you didn't melt the resistor off the board,:rolleyes:

I soldered a thin piece of wire to the circular screw hole and soldered a pin on the other end.

Sharpened the pin to a very small point.

I had my AFTV2 power plugged into a switchable 3 pin socket, with it switched off to start with and USB lead plugged in.

Used a magnifying glass to view and place the pin on the correct Data 0 pin location, then switched the power on and followed the script.

jb
[Fire TV Original Android Development] meohmy:
@jbvid

The solder was made easier because I used an electric microscope with 2 eye pieces which gave greater visibility and 2 hands free. I am fortunate that I have a m8 who designs electronic circuits for a living so has all the correct equipment and he was also looking over my shoulder at what I was doing. It was his suggestion regarding the micro switch. I do not profess to be an electronics wizard, on the contrary, just an ordinary numpty who follows instructions.

I showed the mod in case anyone else wanted to try it but had not thought of the method.
[Fire TV Original Android Development] jbvid:
Hi

Ahh, got the right equipment then for these micro mini components.

Yes me too, just an ordinary numpty who follows instructions, but find it quite satisfying. Also rooted a Firestick 4k using Flakies thread, struggled a few times with the tin foil but got there. I should have used my pin method and spy glass for that.

jb
[Fire TV Original Android Development] crazzzzy:
Fire OS 5.2.8.0 (668694820)

https://d1s31zyz7dcc2d.cloudfront.n...indle-full_sloane-36.6.6.8_user_668694820.bin
[Fire TV Original Android Development] el7145:
Hello,

Im hoping someone can help me with this error...my device appears to be properly bricked as no led lights turn on at all, when i run the script i get a "AssertionError: Partition Table is corrupt

Does anyone know what i should do next, is there any hope or is the garbage the next destination?

Thanks
[Fire TV Original Android Development] Sus_i:
Hi

Maybe try this if you like: :)

Browse to this post here:

[UNBRICK] [ROOT] [TWRP] Fire TV 2 (sloane)

This guide is only for the Fire TV 2 2015 (not stick) codenamed "sloane" with mt8173. This will flash correct partitions and TWRP into it. This WILL NOT clean RPMB neither will unlock the device. I am not responsable of any physical damage in...

xdaforums.com

Download the 1.3 package from the thread and run 'sudo ./gpt-fix.sh' (instead of running the bootrom-step).

Copy/Paste the terminal output in here.

Then try again the bootrom-step from this thread:

https://xdaforums.com/t/unlock-root-twrp-unbrick-firetv-2-sloane.4222331/

Good luck^^
[Fire TV Original Android Development] Rortiz2:
Your partition table is corrupt. Try running gpt-fix.sh instead of bootrom-step.sh. That'll reflash the stock GPT and will unlock the device.
[Fire TV Original Android Development] Sus_i:
Hi :)

Afaik the gpt-fix script is missing in the unlock amonet.zip-files...

Thats why I said, the older 1.3 zip first.

Regards
[Fire TV Original Android Development] el7145:
@Sus_i and @Rortiz2

Thank you guys for the replies, after many attempts I finally got some things in order. It seems that maybe the short is super "finiky" sometimes it will register a short, but the script will fail with different errors (ie input/output), i guess you have to keep doing it (ie over 20x) until it doesnt error.

Once I got into twrp, I flashed one of the update.bin (zip), booted into OS, made sure I had my developer options in order, rebooted back into twrp to flash magisk, and now all good...might disable updates tomorrow, although that doesn't seem as important now that I'm fully unlocked.

So the moral of the story, if after 15x of trying, after failed scripts with various errors...keep trying! Eventually you will hit everything at the exact time. Someone suggested using a smart plug to power on the fire TV, and omg that worked wonders

So, thanks again for the help!
[Fire TV Original Android Development] Rortiz2:
That's correct, my bad... I will add the gpt-fix.sh ASAP
[Fire TV Original Android Development] Rortiz2:
Glad to hear you made it work. Yes, definitely, shorting Sloane is one of the hardest things in the world. Like you said, you just have to keep trying until it works.
[Fire TV Original Android Development] sleepymaxx:
Is it possible to run your description on a (sloane) Fire TV gen2 if there is the stock version 5.2.7.6 alredy installed?

PS Thank you for your awsome work
[Fire TV Original Android Development] Bertonumber1:
Yes it should be ran as normal .You will be able to flash the firmware + root method in TWRP recovery when the script has finished anyhow.

Regards
[Fire TV Original Android Development] sleepymaxx:
Hallo Guys & Girls ... as you promised - it worked Flawlessly - with some (minor??) issues - and ive got some tipps for anyone who will do this in future...

First things first ...

ive done the bricking method - and did this more than twenty times one after the other- because mostly of my own faults .. so i did it with the second box in the follwing work-row:

After the first attempts - i waited after every step really long - till the wished outputs of your script arrived!

1. Bricking Device (with non-rooted Firmware)

2. Prepairing Environment

2.a Prepairing Environment extrA: made a micro - Sd -Card fit with the datas which are needet in TWRP:

2.b - amonet-sloane-v1.1.zip

2.c - Magisk -v20.1.zip

2.d - sloane-5.2.7.6-rooted_r1.zip

(all data incl. the md5 checksums)

2.e - Fiddled the micro sd in the Port

3. Run your Code I (sudo apt update ....................)

4. Run your Code II (sudo systemctl stop ..................)

5. opend 2. terminal in the amonet directory - entered Code (./fastboot-step.sh)

6. opend 1. terminal in the amonet directory - entered Code (sudo ./bootrom-step.sh)

7. Waited for Reboot in TWRP

8. made a full wipe: Data / Dalvik - ART Cache /Cache

9. made a second wipe Data

10. Installed in TWRP

10.a flashed amonet-sloane-v1.1.zip

10.c flashed sloane-5.2.7.6-rooted_r1.zip

10.b flashed Magisk

11 let TWRP reboot

Thanked to god and YOU GUYS AND GILRS

mY Problems:

1- i did´t know wich pin i should use (in the first picture there are 3 marked - ) (after reading - the whole post i figuerd it out - i had to take the DATO pin!

2- HELL NO THIS BOARD IS TOOO ****ING NARROW TO DO ANYTHING ON IT--- so i took a helping hand with a sewing- needle to point on the DATO - Pin (pictures downstairs)

3. After the 6. attempt somthing went horribly wrong - an very very tiny chip broke of from dat0 Port - (and downwards) - i thougt i broke the Board

4. Anyway i tried it again - and what should i say (in reality i dont understand it anyways) it funcioned also without the tiny chip

Thank you for your work -- ( if you are interested - i offer a short translation to german - as big Thankyou)
[Fire TV Original Android Development] Sus_i:
The rooted rom isn't recommended, see the OP for details.

It's best if you flash a stock rom instead.

The flashing magisk part is always the last step, just after any rom update...

Steel is a little too hard for the tiny resistor ;)

The box should not boot at all with a broken resistor at DAT0. Maybe a bit of the resistor is still there ;)

Value is 47k ohms, if I remember correct.
[Fire TV Original Android Development] sleepymaxx:
last question: must i block the Amazon Updates trough my router furthermore or is the TWRP existent on all future Updates?

BY the way - i bought myself 2 additional boxes through eb.y (in Germany they are at 10 € one piece today) - will flash them also for my kids -

(so i will go to stock perhaps - what are the limitations of the amonet prerooted rom??? )
[Fire TV Original Android Development] Sus_i:
TWRP is always there (the new one at recovery partition, not the old bootmenu-TWRP) and it depends on you. If you like automatic OTA updates, let the app do it's thing. It will work just fine.

Most people disable the updater I guess, because the OTA app pulls additionally crap and bloat, even if the box is already on the latest OS.

Really only 10€ ?

It will work too (disadvantage would be the bootmenu with the old TWRP + the old system-install of supersu).