yashsingh1/xdaforums huggingface dataset:
[Fire TV Original Android Development] k4y0z:
I did miss that, thanks for clarifying.

However even if you want to go back to stock, I would suggest leaving GPT untouched which will make it easier should you decide to unlock again.

boot_x and recovery_x will just remain unused on a locked device.
[Fire TV Original Android Development] DanielF50:
Yeah, I forgot about the gpt repartition. I retract my statement about that then, but everything else still stands - that method is my go-to; it removes twrp when needed.
[Fire TV Original Android Development] Toothless_NEO:
But the Bootloader is still locked? If I flash Magisk it'll brick, that's what the old guide said, isn't there something I have to do regarding the bootloader?
[Fire TV Original Android Development] DanielF50:
What you originally quoted was referencing updating Magisk to the latest version? You shouldn't have Magisk installed if you're BL is locked.
[Fire TV Original Android Development] Michajin:
You can't flash magisk if you are locked. The guide said to only flash magisk from TWRP, do not update from magisk. Flashing magisk from the app puts you into a boot loop. What are you trying to do?
[Fire TV Original Android Development] Bertonumber1:
I don't know wtf is happening here man ....I'm lost :Dall these issues can't keep up:p

Use the search function for Amazon firetv / magisk . Remember not to update the ramdisk patch from the manager app.
[Fire TV Original Android Development] LocoMexican:
I tried the gpt-fix, but ran into computer issues. So, I have come to the conclusion this particular device will not allow a return to stock. It is my "practice device" which was a "demo" with a revolving Alexa commercial when I got it. This morning, I ran the shorting brick hack v1.01 again. In twrp, I formated data and wiped dalvic cache. Then, I went to advanced wipe and wiped dalvic, cache, internal storage, system; i.e. everything I could except usb. Then I formated data followed by install pre-rooted rom. Still in twrp, I deleted recovery and install full sloan image posted in post 13 here. Then wipe dalvic cache I rebooted system. This got rid of twrp, but device still shows to be up to date. Streamed for a couple of hours, and when I checked update, still showed to be up to date.

Started over with shorting brick hack v1.01 and now running latest stock update. And, I have a perfectly functioning device which will not update, but which otherwise falls right in line with what this thread was intended to do. When a new update comes down the pike, I'll simply go into recovery and install it just like Rortiz2 intended. Thanks Rortiz2, Sus_i and everyone else for your input. I hate to give up, but I learned a lot and enjoyed every minute. Thanks again.
[Fire TV Original Android Development] Toothless_NEO:
I rooted with the old Guide that uses SuperSU in system mode and doesn't unlock the Bootloader. I would like to have the unlocked Bootloader without disassembling my Fire TV and doing the exploit again so I can get Magisk.

If that's too much I at least want to know how to stop SuperSU from crashing whenever I open it.
[Fire TV Original Android Development] Rortiz2:
lol read the first post. flash the zip with twrp
[Fire TV Original Android Development] Michajin:
You shouldn't have to. Are you running a r-box pre-rooted rom? You have twrp? short steps...

(warning-unlocking wipes all data)

Download unlock zip

download stock rom

download magisk

Boot into twrp

flash zip

format and type yes

factory reset

flash stock

flash magisk

reboot....
[Fire TV Original Android Development] Bertonumber1:
As an added note to michajins post remember when you format data you'll have to adb push/download your stock and magisk files to the device again..(unless you have the files placed in external storage/otg)
[Fire TV Original Android Development] Veg-Meat:
Hey there!

So I've been lurking on this thread for a while and finally decided to try and unlock my Amazon Fire TV 2 (2015) Sloane device. Unfortunately for me, my firmware version is already above 5.2.7.7 so the only way for me is to short the pin.

I have a couple of questions about this;

How do I physically open the device? This is the step I've been stuck on lol... I searched online and haven't found any teardowns of the second edition of the device. I tried using a knife (sliding it in the gap between the bottom rubber and the outer shell but I just ended up cracking one side of the box a bit, not opening anything and cutting my pinky...

What and how do I short on the board? Reading the other posts on this thread, I assume that the script will tell me to basically poke some copper wire on the DAT0 solder pad in order to short it (please correct me if I'm wrong)
[Fire TV Original Android Development] Bertonumber1:
@Veg-Meat

1.Just use a flat metal pry tool such as a precision flat headed screw driver.

Flip the box and start at the rear right side. Gently prise it open by moving around the underside of box until the cover pops off (there are no wires or anything connected to the cover). Next.. you will have to unscrew the board from the topside frame just unscrew the little screws and then just lift the board out carefully.

2. Refer to the picture in the OP and locate the dat0. Use a thin piece of copper wire or roll a long piece of tin foil up and use this to short the little pad you see in photo.

You can attach one end of your piece of wire or foil using sticky tape to one of the silver metal shields you see on board (this will serve as your gnd point) .. Be sure to make you're wire or foil long enough to comfortably reach the location of the dat0.

3. The two above steps are the easy part. You will require patience as sometimes it takes a few attempts to short and get the script to run. Some succeed instantly others take many tries. But just let us know and we'll help you if your unsure.

Regards
[Fire TV Original Android Development] LazorBlind:
I originally used the smallest sized flathead screw bit I had, but it chews up the plastic a little. If you dont mind d spending a few bucks I would suggest buying an iSessmo opening tool/spudger. Its made of a thin flexible metal and is intended for opening devices that are held together with internal clips, like the Fire devices.
[Fire TV Original Android Development] LocoMexican:
LMAO Veg-Meat. Someone should have told you that bleeding is a normal first step/condition imposed by this device (not this thread). Hopefully, when you get it opened and shorted, your device will not be contrary, and do what is expected. Have fun.
[Fire TV Original Android Development] DanielF50:
Easiest/least destructive way that I've found to open these is to use a guitar pick - just push a thick pick between the bottom panel/side, just below the USB port & once it's in, just push the pick downwards, making the bottom panel release.

Visual example:

👍
[Fire TV Original Android Development] LocoMexican:
Couldn't stand it. Hate to give up. Got computer problem worked out. It's called follow directions (computer environment). Ran GPT-fix. Script took about 15 minutes to run, but ended up with twrp. Formated data, wiped dalvick cache and installed full stock udate posted in post 13 of this thread. Rebooted system, and it runs fine, but alas, still no update. In my humble opinion, this particular device was manufactured in a way to prevent any update since it was made to be operated as a demo. Regardless, after short and v1.1 hack, it's now rooted and running current update. For what it is worth, I only ran the gpt-fix.sh from amonet version 1.3 and not the bootrom.sh. Thanks again everyone for your help.
[Fire TV Original Android Development] Toothless_NEO:
What about the Advanced Wipe option?

Any specific reason why you can't use that?
[Fire TV Original Android Development] Bertonumber1:
Because you have to format data to ensure the partition is ready for boot. A normal wipe won't suffice.

Regards
[Fire TV Original Android Development] m1steron:
I managed to succesfully install the unlock and had working Magisk root in Fire OS version 5.2.7.7. I noticed there was a pending OTA update which I foolishly let install (Had a few too many drinks I'm afraid!). Upon reboot I had lost root access and had no TWRP recovery menu during boot. However I can still get to TWRP by using ADB commands. Upon first boot after the OTA update I had a prompt to alllow write access so is TWRP still unlocked? Can I just reinstall the TWRP and Magisk zips from here?

In regards to the original unlock guide. Is it necessary to downgrade the rom if using rbox's latest rooted rom version 5.2.7.6_r1?

Thanks.
[Fire TV Original Android Development] DanielF50:
I'm kind of unsure what you're saying, but asssuming you're saying you flashed rbox's pre-rooted rom & Magisk during the unlock process (instead of an official Amazon update), then somehow allowed a official OTA update to install over the rbox rom?

If my assumptions are correct; as quoted below, rbox's pre-rooted rom disables the unlocked twrp from this thread - it seems you've taken an official update over the pre-rooted rom, which has removed rbox's rom completely & (probably?) re-enabled the unlocked twrp.

From what I can gather, you seem to be running a stock rom with an unlock bootloader, as are most of us & doesn't seem like there should be any issues.
[Fire TV Original Android Development] m1steron:
Thanks for the info but let me elaborate:

My Fire TV started on version 5.2.7.6_r1 of rbox's rooted rom.

After reading the guide from page 1 I decided to downgrade to version 5.2.7.3_r1 before proceeding with the unlock. Is this a necessary step?

I then did the following using information provided by Michajin

Download unlock zip

download stock rom

Fire OS 5.2.7.7 (662663720).

https://d1s31zyz7dcc2d.cloudfront.n...indle-full_sloane-36.6.6.2_user_662663720.bin

download magisk

Boot into twrp

flash zip

format and type yes

factory reset

flash stock

flash magisk

reboot....

From here I installed the Magisk Manager APK and had full root access. I then mistakenly allowed the device to install OTA updates which rebooted to TWRP and flashed something to do with chmod?

Now back to my original post:

What do you think?
[Fire TV Original Android Development] Sus_i:
Thats ok.

After an OTA update, just boot TWRP and flash magisk again. Done.
[Fire TV Original Android Development] m1steron:
Great thanks.

What about getting the TWRP menu back during boot. Presenlty it's only available by using an ADB command.

Should I reflash the TWRP zip?
[Fire TV Original Android Development] Sus_i:
Thats fine.

It's recommended to boot/use the unlocked TWRP from the recovery partition (accessible via adb command or via button in magisk manager).

Don't use the bootmenu-TWRP, as it's the one for the prerooted roms with locked bootloader...
[Fire TV Original Android Development] m1steron:
Oh OK. So it's normal behavior to have it boot up without displaying TWRP count down menu.

Good to know.

Thanks.
[Fire TV Original Android Development] LocoMexican:
That's the way mine works. Twrp is there, it just doesn't advertise itself on boot-up. And, mine updated to the latest and greatest 5.2.7.8. Seems to be doing what it's suppose to.
[Fire TV Original Android Development] m1steron:
My mistake. I was so used to seeing the TWRP menu when booting rbox's rooted roms over the years I thought it would be the same. Like you I am now on v5.2.8.8 with Magisk root.

FYI, a good app worth sideloading for disabling bloatware and unused apps in Fire OS:

App Disabler [root]

App Disabler [root] – Apps on Google Play

App Disabler allows you to enable / disable user-installed and built-in apps.

play.google.com

I've used this to disable the stock launcher, system updates, security, etc.

Thanks to everyone for your help and patience.
[Fire TV Original Android Development] meohmy:
This is probably a stupid question but when I unlocked I used "amonet-sloane-v1.01zip" is there a benefit of me now loading "amonet-sloane-v1.1zip"?
[Fire TV Original Android Development] Rortiz2:
No, you can stay with the 1.0.1 version. The changes between those are related to the unlock process.
[Fire TV Original Android Development] dovedescent7:
Hey Rortiz GREAT WORK!

May i ask why you didnt at least write a brief description in OP stating what this is, and its purpose? Even a few words?

There are MANY folks just like me that only come back to the boards here annually or even less, for maintenence. Personally i dont keep up much, have kids now and so busy.

I read in another thread that this will Unlock Bootloader for my FTV 2 sloane box unless i am mistaken.

Is the purpose of this to unlock the bootloader of the device?

Is unlocking bootloader even possible with sloane box? I thought the contrary

Lastly, what advantages for this vs staying with the systemless root i already have? (BESIDES the annoying auto-rebooting and "update su binary" msg) - btw i'm on 5.2.7.3

Some of us oldies, are so scarce around here we forget terms like what "unlock" in title actually means..Is that unlock bootloader? or something else like root? In many, many cases our old brains are cloudy and filled with years of bong resin. Hard to remember, nuh what i mean?
[Fire TV Original Android Development] m1steron:
Yes it is.

1. You can install Magisk and it's modules rather than use SuperSU.

2. Use MagiskHide for any apps that detect root.

3. Install Latest version of Fire OS v5.2.7.8.

Personally, I am on Fire OS v5.2.7.8 with Magisk root. FYI, you will not see the TWRP menu when booting (thanks for confirming this LocoMexican) but you can get to it through the Magisk reboot menu or via an ADB command.

My mistake:

v5.2.7.8 not v5.2.8.8

;)
[Fire TV Original Android Development] meohmy:
According to Amazon the latest software update is Amazon Fire TV (2nd Generation): Fire OS 5.2.7.8 (664657320) not 5.2.8.8.

but I haven't found a link for it yet.
[Fire TV Original Android Development] LocoMexican:
Me too. Where to find link for full stock Fire OS 5.2.7.8 (664657320)? I'd like to keep my practice demo up to date.
[Fire TV Original Android Development] Sus_i:
Fire OS 5.2.7.8 (664657620) for sloane:

https://d1s31zyz7dcc2d.cloudfront.net/6e68ae0674faaf85093c704caaa63b66/update-kindle-full_sloane-36.6.6.4_user_664657620.bin

md5: 087cef3f082b0017231e8b938feaeec7
[Fire TV Original Android Development] higogo:
Hi there,

I have a FireStick 4k, one of those that serial # starts with G070VM1190xxxx.

It is stuck on Amazon white logo screen.

I tried adb but I get unauthorized. Tried OTG cable with keyboard and no luck.

Device is not rooted.

Any sugestion?
[Fire TV Original Android Development] Sus_i:
I think for magisk users, the stock.bin's are the way to go.

But if you 'skip the magisk flash' and if you like to use supersu instead of magisk, then the prerooted works fine too.

The bootmenu will come up everytime you boot, rbox bootmenu/TWRP works like expected.

Also the OPs new TWRP will work fine too (apart from the installed rom), i.e. adb reboot recovery or the boot-recovery script from OP will boot the new TWRP... and the bootmenu of the prerooted rom boots the old TWRP.

Too much of a hassle, I use magisk and a stock rom (until rbox decides to upgrade his prerooted from supersu to magisk).

lol, I don't think so^^

They don't even know that sloane got an unlock :D
[Fire TV Original Android Development] Bertonumber1:
Yeah I totally agree dude, I did the unlock and had to go back to install playstore etc. But this unlock is the bollocks, best thing that's happened for a while.

Haha I was only messing, the amazon devs aint gonna be bothered about this unlock I don't think, as Rortiz2 said they don't even sell this device now. Still... It's a helluva device and probably the best to have unlocked with regards to development arm64 etcetera
[Fire TV Original Android Development] LazorBlind:
Well done! With bootloader finally unlocked, the possibilities are much more favorable for this device. I'm excited to see what custom ROMs will be thought up. Maybe we can get this thing up to a higher version of android?
[Fire TV Original Android Development] Rortiz2:
Yes I'm working in LineageOS 14.1(android 7) but it'll take me a while to get it working, also I can't really promise anything.
[Fire TV Original Android Development] retyre:
You should bundle the older preloader (perhaps from rbox's 5.0.5 ROM that can be found on this forum) with this exploit. With a preloader that allows read/write commands, someone familiar with the commands (read32, write32) should be able to fix any brick without having to open up the device to short.

Is there a reason you used the newer preloader?
[Fire TV Original Android Development] Rortiz2:
That was just a precaution. There may be incompatibility issues when using the new TZ and the old PL (i.e: DRM). Also, the PL downgrade would require erasing RPMB and that would mean that the zip method will not work as is (you would need to erase RPMB via bootrom).
[Fire TV Original Android Development] brick00444:
First thing Thank you for everything! I am trying to revive a problematic box. I can get to TWRP and when I try to flash amonet or anything else for that matter I get Failed to mount '/data' (invalid argument). I have been trying for 2 days before I decided I need help (in more ways than one). Any suggestions?

update: I can now flash with no errors and enter twrp flash anything without errors but when I reboot it goes to black amazon screen then twrp then black amazon screen and then no signal.
[Fire TV Original Android Development] LazorBlind:
I am having a similar problem. Anytime I try to flash a OTA or prerooted stock image, I get an error about not being able to mount /data. It says there is no directory. I also cannot get into twrp anymore. I run the boot-recovery.sh and it seems to work, but when the Sloane restarts, it just sits in fastboot.

Update: so I managed to fix the problem. I used fastboot-step.sh to get into twrp and then did "Format Data" under the Wipe menu. Then I was able to flash an OTA update with no issue.
[Fire TV Original Android Development] Bertonumber1:
Hi guys,

After you've ran the first steps you have to remember to :

When you are on the hacked fastboot screen

sudo ./fastboot-step.sh

After that, the device will reboot to the unlocked TWRP.

(This part is really important) In Unlocked TWRP

Select Wipe

Then

Format Data

Type : YES

You can now install Prerooted, Supersu or Magisk from there on out.....

But you have to Format data

Regards

Please note : Anyone doing this unlock must follow OP to the letter. It looks a lot to do but it isn't really, it's just cos it's hard to explain on forum..
[Fire TV Original Android Development] brick00444:
I have been at it all day, sometimes I can get it to finish with the command ./bootrom-step.sh. When it does finish then I use ./fastboot-step.sh and it reboots to twrp. I then select wipe and then format data and type yes and it wipes it fine. Then I flash the rom in post #13 all seems fine. So that completes step #9. Shouldn't it now boot to fire tv if thats all I want to do? It doesn't boot after flashing a rom. Maybe I'm missing something. Sorry for all the questions but just want it working again if possible.
[Fire TV Original Android Development] Sus_i:
Maybe wipe cache and dalvik too.

Have you tried a rom from post #15? The one from #13 is rather old.

Magisk is installed?
[Fire TV Original Android Development] Bertonumber1:
Maybe hardware issue if you're getting to twrp and then wiping correctly, have you scraped something else when shorting perhaps?

Try using windows fastboot to flash the boot.img and recovery.img instead of twrp.

Maybe Roger will be able to assist you further mate.
[Fire TV Original Android Development] LazorBlind:
Assuming the issue is the ROM like the others have suggested, try what I did.

In twrp go into wipe and format everything system, data, all of it. Then format data and try flashing a ROM.

By doing this you will completely delete whatever ROM is already installed and have a clean slate to put whatever ROM you want in there with no worry of a conflict. I really don't see why it would matter but hey, its worth a shot.
[Fire TV Original Android Development] brick00444:
Could have scraped something I guess. I'm a 60 something (half blind) guy that just likes playing with this stuff. I will try again tomorrow. Not sure what you mean by windows fastboot . If I can't get it going I will donate it to one of you guys to play with. Thanks
[Fire TV Original Android Development] brick00444:
Yeah I will give it a go tomorrow. Thanks
[Fire TV Original Android Development] Bertonumber1:
Yeah I've done this with the tank model before, broke a neighboring resistor and when I tried the bridge repair I soldered all the resistors together lol.

My eye sight is pretty crap too. As I said Roger may know what the problem is if it's software related. I think you should try fastboot wipe and start from scratch first though mate

Regards
[Fire TV Original Android Development] Rortiz2:
Linked your post to the OP
[Fire TV Original Android Development] brick00444:
I think I figured it out. I ended up knocking 2 of the resistors off. Thanks for the help and all you guys do.
[Fire TV Original Android Development] LazorBlind:
Damn sorry to heat that. That's the risk we take though yeah? This is exactly why I soldered a button between the pin and ground, so I didn't have to fiddle with the short anymore. Not that there wasn't a major risk with that too. (I almost melted the chip...)
[Fire TV Original Android Development] brick00444:
Oh well, live and learn.
[Fire TV Original Android Development] DanielF50:
Yes, use the correct unlock process to fix it - this thread is for the 2nd gen FireTV box, not the 4k FireTV Stick.

Follow the process laid out here: https://xdaforums.com/t/unlock-root-twrp-unbrick-fire-tv-stick-4k-mantis.3978459
[Fire TV Original Android Development] Veg-Meat:
Thank you for your and everyone else's responses! (Sorry I'm replying quite late, I had exams)

I successfully opened my Fire TV 2 and unscrewed the motherboard PCB. I have made an interesting discovery though; the layout of the location of the dat0 pin from the picture is different from what I have; there is a SanDisk chip instead of the chip shown in sloane.jpg and there are more pins on my board than in the picture...

EDIT: I'm an idiot... I wasn't looking closely enough, the pin right below the pin I circled in red on my uploaded picture is dat0... The chip might be different but the pin layouts appear to be the same... ignore this post lol

I successfully opened my Fire TV 2 and unscrewed the motherboard PCB. I have made an interesting discovery though; the layout of the location of the dat0 pin from the picture is different from what I have; there is a SanDisk chip instead of the chip shown in sloane.jpg and there are more pins on my board than in the picture...

So I decided to not short the pin that I have circled in red (I think it might be dat0 although I am unsure if that is the same dat0 pin as the one in sloane.jpg)

Could this be due to a regional variant using different components?

I have attached a few pictures of how the layout looks on my sloane device.

The box says the model number is DV83YW, is that the same one everyone else on this thread has?
[Fire TV Original Android Development] Bertonumber1:
SanDisk and Mediatek are all good mate, they do the same job some but other models of emmc tend to be less flash friendly with regard to efuse.

Glad you succeeded in unlocking this beautiful speedy device. 😎
[Fire TV Original Android Development] Bertonumber1:
Wanted to enquire about something but didn't want to sound like a nipple asking outright :p

What's the story with the Amazon 6.2.7.8 ota on mantis do you think they will try this with Sloane eventually.

I'm guessing we'll be okay as long as we keep ota disabled?
[Fire TV Original Android Development] Bertonumber1:
Jeez, sorry man, I take it the sloane was one of those export/display devices?

You should keep trying .. Don't give up 👍