yashsingh1/xdaforums huggingface dataset:
[Fire TV Original Android Development] LocoMexican:
When I check for updates, the Fire 2d says there is a shortage of storage and suggests I delete some apps. When I check "storaage" it shows 3.1 G of unused storage capacity. Question, how can I get my device to recognise the actual storage space of over 3 G's? I have wiped system and reprogrammed system. Also, I have formated data and then used recovery to put my back up data back on board. The device works fine, but I'd like to allow it to update when a new system update is available. Suggestions appreciated. Thanks in advance.
[Fire TV Original Android Development] Sus_i:
Maybe the OS complains about external storage, i.e. maybe the OS used an usb storage or ext sd card at some point, which may be disconnected now..!? Saw such an issue on the first gen fireTV box, component updates broken with removed storage stick.

Latest for me

Fire OS 5.2.9.5 (686800820)
https://d1s31zyz7dcc2d.cloudfront.prod.ota-cloudfront.net/5b8c7d462f1bea85ba8a4b5d32f4ee14/update-kindle-full_sloane-36.6.8.6_user_686800820.bin
[Fire TV Original Android Development] LocoMexican:
Great call. I removed external SD card, booted into TWRP, wiped System, installed the posted sys img, installed Magist v23 and rebooted system. Reinstalled external SD card and for whatever reason, that fixed my problem. Device now checks for update and runs normally again. Did some de-bloating, and for the last couple of days, all is well with "check for updates". Thanks for your insight and suggestion.
[Fire TV Original Android Development] brick00444:
Ok, Sorry to bother but I haven't played with Sloane in awhile. I try to flash 2 different boxes and get similar results. Either it makes it through the initial flashing and preloader flash and then the terminal window closes or mid flash the terminal closes and seems to end the process. I have tried different pc's different usb a to a cords all with same results. 1 box was 5.2.7.2 and the other was 5.2.8.0. I wanted to update to latest firmware. Any help would be appreciated Thanks
[Fire TV Original Android Development] brick00444:
It is failing during the recovery flashing.

Sending 'recovery_x' (20644 KB). OKAY { 1.161s}

Writing 'recovery_x'. OKAY {. 1.480s}

Finished. Total time: 2.660s

fastboot: core/libsparse/spars.ccp:131: int write_all_blocks(struct sparse_file *, struct output_file *): Assertion 'pad >= 0' failed.

/root/Desktop/amonet-sloane-v1.1/amonet/fastboot-step.sh: line 9: 6439 Aborted.

(core dumped) fastboot flash MISC bin/boot-recovery.bin
[Fire TV Original Android Development] brick00444:
Ok, got them both working. My own fault.
[Fire TV Original Android Development] jonj80:
I'de like to try this on my "original" FireTV which is on OS 5.2.7.2.

Is rooting with this version possible or better asked what in general is possible?
[Fire TV Original Android Development] Sus_i:
If it's a sloane a.k.a. second gen box with sdcard slot, then this will work on any FW version
[Fire TV Original Android Development] jonj80:
You mean microSD?
[Fire TV Original Android Development] Bertonumber1:
Yes he means the model with the MicroSD slot on the rear ..The 2015 FireTV 2nd Generation codenamed sloane is vulnerable to the exploit no matter what firmware you are on as its a hardware mod (Opening case and shorting bootrom clk resistor or dat0 pad in this case ).

Follow the OP and youll be fine but patience is advised as the script doesnt always go through first time.

If you need any help just ask

Regards
[Fire TV Original Android Development] jonj80:
Thanks mate, I appreciate your offer. I've read the first page of this topic. Sounds complicated but I'll give it a try.

As far as I have undestood, I'll have to start with #2, then #1

Is there a picture of how DAT0 with GND is connected? I'v seen this but as I am no electrican that's outside of my frame to understand what exactly to connect.
[Fire TV Original Android Development] Rortiz2:
Just use some paper clip and make sure one end is touching DAT0 and the other GND.​
[Fire TV Original Android Development] hafren:
@Sus_i

Rooted Sloane on fireos 5.2.7.4 and having nag message to update in order to continue using My5 streaming app. I think this may be a drm issue as I no longer have video - only audio. Is it safe to upgrade/flash with a stock rom to fireos 5.2.8.7 and afterwards magisk?
[Fire TV Original Android Development] Sus_i:
Yes, it's safe.

The latest is 5.2.9.5

https://d1s31zyz7dcc2d.cloudfront.prod.ota-cloudfront.net/5b8c7d462f1bea85ba8a4b5d32f4ee14/update-kindle-full_sloane-36.6.8.6_user_686800820.bin
[Fire TV Original Android Development] linuxchick:
Greetings to all,

I had an old FireTV2 Sloane lying around and wanted to use it again - as i recall it was rooted years ago and it had twrp installed. But when wanted to use it now - it had just a black screen, a white LED which switched to orange then white and orange again and again.

So I decided to open up the device and try to revive it with this method. I did everything to the book - but no matter what I try. The device keeps getting stuck in a bootloop with the white amazon logo.

The bootstep process finishes without an error - the last message " Reboot to unlocked fastboot. When flashing via bootstep.sh the device is reported as Mediatek Phone - but after the bootstep.sh, dmesg says that the device is in preloader mode. But no matter what I do I cannot get it to work in phone mode anymore after the bootstep script.

I tried two different linux machines (one with a fresh Linux Mint Install, the other one with an old Lubuntu on an eeepc from years ago, which I used to first root the firetv2).

Any suggestions?

I tried gpt-fix - no changes

I did the script and shorting method at least a dozen times now - but everytime I end up in the bootloop.

I tried starting the fastboot script in parallel to the bootstep script - "waiting for device...." no changes

Greetings from Germany

edit: at my last attempt I managed to rip of the smd component (which has to be shorted) and in the repair attempt I lost it on my workbench - does anyone know what smd component it should be? At least I did not rip of any pads - so I could try to fix it.
[Fire TV Original Android Development] Sus_i:
It's a 47K Ohm resistor.

Something between 10K and 100K may also work, needs to be tested.
[Fire TV Original Android Development] linuxchick:
thx for the reply will try to repair the damage - maybe afterwards the bootstep will work better
[Fire TV Original Android Development] bonezey2525:
i hav the sloane currently at 5.2.9.5 firmware .. never been opened or rooted .. unfortuneatly i hav never touched linux os as well .. is the pin shorting in a linux OS first thing that needs done with the device ?? Sry if i didnt read it right ..
[Fire TV Original Android Development] Johnric001:
Hopefully someone can help me out. I have the DV83YW Amazon Fire TV but the chip requiring shorting looks different to the picture shown here.

I started out with a device with a failed update. Bootup to white Amazon logo -> reboot after a few secs and repeat.

I have got as far as running sudo ./bootrom-step.sh from amonet v1.1 zip

Waiting for bootrom

[2024-01-01 18:58:58.538854] Found port = /dev/ttyACM0

[2024-01-01 18:58:58.539157] Handshake

[2024-01-01 18:58:58.539521] Disable watchdog

[2024-01-01 18:58:58.540700] Waiting for bootrom

waited a long time and nothing happens. lsusb shows 'MediaTek Inc. MT6227 phone'

I again short the pin to get something to happen

[2024-01-01 19:00:25.416273] Found port = /dev/ttyACM0

* * * Remove the short and press Enter * * *

press enter and

2024-01-01 19:01:12.237097] Init crypto engine

[2024-01-01 19:01:12.261099] Disable caches

[2024-01-01 19:01:12.261590] Disable bootrom range checks

[2024-01-01 19:01:12.274633] Load payload from ../brom-payload/build/payload.bin = 0x4760 bytes

[2024-01-01 19:01:12.280999] Send payload

[2024-01-01 19:01:12.870466] Let's rock

[2024-01-01 19:01:12.871090] Wait for the payload to come online...

[2024-01-01 19:01:12.874839] all good

[2024-01-01 19:01:12.875019] Clear preloader header

Traceback (most recent call last):

File "/root/Downloads/amonet-sloane-v1.1/amonet/modules/main.py", line 146, in <module>

main()

File "/root/Downloads/amonet-sloane-v1.1/amonet/modules/main.py", line 37, in main

switch_boot0(dev)

File "/root/Downloads/amonet-sloane-v1.1/amonet/modules/functions.py", line 39, in switch_boot0

block = dev.emmc_read(0)

File "/root/Downloads/amonet-sloane-v1.1/amonet/modules/common.py", line 199, in emmc_read

raise RuntimeError("read fail")

RuntimeError: read fail

so it seems as though although it can detect my device it cannot communicate with it. Although it said it sent the payload I'm not sure it actually has.

I no longer get the white Amazon logo just no output from the HDMI connector.
[Fire TV Original Android Development] Sus_i:
Sounds like you have maybe damaged somehow the part during shorting, no eMMC r/w access. The box should be always in phone mode and the script will start right away without any short... but fail as soon as a read/write attempt to the eMMC starts.
[Fire TV Original Android Development] Johnric001:
Not impossible that I have damaged something but I used a microscope camera and fine tipped soldering iron to attach a very fine wire to the DAT0 connection as shown in the diagram on page 1. I then shorted that to GND as described following "Unbricking / Unlocking with non-rooted Firmware" for the symptoms I am having -

It doesn't show any life (screen stays dark)

You see the white amazon logo, but cannot access FireOS.

It is the first time I have tried this so although I read the whole article as suggested I am in the dark about this hardware and what the scripts are actually doing.
[Fire TV Original Android Development] Sus_i:
So you see the white logo and then just blackscreen? :unsure:

If yes, then follow the unbricking/shorting. Most people need some/many attempts to get it to work. Sloane is harder to short than the fireTV sticks, because it gets power via power brick and usb cable.
[Fire TV Original Android Development] bonezey2525:
The only response when trying the boot rom script is waiting for bootrom .. when I tried the above , command not found ..
[Fire TV Original Android Development] Johnric001:
I only quoted those phrases to confirm which part of the process in the posts I was following.

I started out by having the repeating white Amazon logo following a failed OTA update which is why I started down this route.

I then attached Fire TV via an A-A usb lead to a PC running Ubuntu.

I used the 1.1 set of files. The scripts run - they have a+x privs.

**See my original post above for all the errors I was getting in detail - Monday 7:06pm. **

Some of the sript must have run I assume as it is now 'bricked' - i.e. no white Amazon logo but the scripts error out as shown.

Someone else has jumped in with a different comment about command not found - that was not me (that is usually becuase you need to put ./ before the command and or run as root using sudo)
[Fire TV Original Android Development] morchu:
Scanning throught this thread it seems like it maybe a good idea to edit the first post in this thread and make it clear that it is recommended to use OTA roms (and not rbox pre-rooted rom) after this unock process. (Plus magisk for root).

Of course if you know the caveats of using the rbox rooted rom, after unlocking, there is no issue. But most unsuspected users continue to use the "TWRP" included with the rbox, when they try to update to a different version, and end up zeroing out the unlocked TWRP, and possibly also overwriting preloader/tz/lk. Essentially end up removing all unlock modifications.

This is because the rbox twrp message comes up on every boot, vs to use the unlocked TWRP you need to do "adb restart recovery" to properly do a recovery boot. rbox roms had a real purpose in the pre-unlock times, since that was the only way to boot TWRP. But beyond unlock, the signficance of it diminished, and that is probably the reason rbox stopped releasing rooted roms.

Infact I would actually suggest that rbox release one last "rooted rom" for the post-unlock era and place it on top of his thread (clearly stating to use that ONLY if they have already unlocked and have unlocked twrp). This may partially help to stop unsuspected users from doing wrong things when mixing latest rbox roms after unlock.
[Fire TV Original Android Development] morchu:
My mistake. So it is already clearly mentioned in the first post.
[Fire TV Original Android Development] Rortiz2:
[UNLOCK][ROOT][TWRP][UNBRICK] FireTV 2 (sloane)

Read this whole guide before starting. This is for the 2nd gen Fire TV (sloane) Current relase: amonet-sloane-v1.1 NOTE: This process does not require you to open your device if you're already rooted or you have TWRP. NOTE: If something goes...

xdaforums.com
[Fire TV Original Android Development] bonezey2525:
After a day of trying , I finally got the short right ... My sloane completed the fastboot-step.sh part of the script as well .. To where the TV displayed a mostly light blue screen with partition info or options possibly ..??? The reason I unsure is , 15 seconds after fastboot-step was done , a breaker tripped and powered of a section of my house , knocking sloane out as well ... I powered bk up , and sloane is stuck on amazon fire tv logo ... Do I have to start by shorting again ??? I tried adb reboot recovery command , and the fastboot -step.sh and is still stuck ...
[Fire TV Original Android Development] Rortiz2:
Use sudo ./boot-recovery.sh to boot into TWRP mode. Then, flash the stock firmware.​
[Fire TV Original Android Development] bonezey2525:
Fantastic Man !!! I back in TWRP ... Thank U .... b4 the flashing of a stock fw , don't I need 2 wipe & fact reset or something first in twrp ??? Sry , complete noob with these devices ...
[Fire TV Original Android Development] Rortiz2:
Yes, you need to wipe data & cache.
[Fire TV Original Android Development] bonezey2525:
thank man .. i did the wipe , format data , stock rom , magisk , etc .. when the system reboot was finished , it threw sloane to the optimizing screen [ make take 10 mins ] then to the searching for remote display [ tap the home button to connect ] as if a factory reset had been done .. " Now Here Could Be The Kick In My Johnson " , i've never had a fire tv remote for this unit ... always had used the phone app , which works great , i might add .. and i've had to do several factory resets in the past , which sloane could always pair my phone with the fire tv app installed , as the remote after displaying the four digit code ... Now that sloane is modded , its not pairing my phone up after i enter the 4 digit display code .. Stuck on trying to pair remote for 2 days ... and i've tried everything Imagineable .. would this be a case of i need an authentic 2nd gen remote to complete the startup process ???? or is there a known workaround for this senario ??? thanks 4 ur input ...
[Fire TV Original Android Development] Sus_i:
USB Keyboard maybe?
[Fire TV Original Android Development] bonezey2525:
What keys would u possibly hit ???? What key would u think represents home button on the AFTV Remote
[Fire TV Original Android Development] Sus_i:
Sry, can't recall details, if you've got a keyboard arround try some of the keys like space, enter, backwards, delete and the direction arrow buttons as a workaround until you get the app working.
[Fire TV Original Android Development] bonezey2525:
Will do... And , Thank U ..
[Fire TV Original Android Development] LocoMexican:
If you have a usb keyboard that has a built in mouse-pad, you should be able to hover and click the appropriate information. Good luck.
[Fire TV Original Android Development] navin23:
Hi, when I try to wipe data via twrp I getting error "Unable to mount /data"

I also tried via shell same error. I ran a few other commands and the output is below. I also, tried to repair the partition in twrp no go. Thanks

~ # twrp wipe data

Formatting cache using make_ext4fs...

Formatting Data using make_ext4fs...

Failed to mount '/data' (No such device)

Failed to mount '/data' (No such device)

Unable to recreate /data/media folder.

Done processing script file

# fdisk -l /dev/block/mmcblk0p17

Disk /dev/block/mmcblk0p17: 6131 MB, 6131383808 bytes

4 heads, 16 sectors/track, 187114 cylinders

Units = cylinders of 64 * 512 = 32768 bytes

Disk /dev/block/mmcblk0p17 doesn't contain a valid partition table

~ # ls -ld /cache /data

drwxrwx--x 5 system cache 4096 Mar 22 2020 /cache

drwxr-xr-x 2 root root 0 Jan 1 00:02 /data

cat /etc/fstab

/dev/block/mmcblk0p14 /cache ext4 rw 0 0

/dev/block/mmcblk0p17 /data rw 0 0

/dev/block/mmcblk0p13 /system ext4 rw 0 0

/dev/block/mmcblk1p1 /external_sd vfat rw 0 0

/usb auto rw 0 0

fdisk -l /dev/block/mmcblk0

Found valid GPT with protective MBR; using GPT

Disk /dev/block/mmcblk0: 15269888 sectors, 3360M

Logical sector size: 512

Disk identifier (GUID): c2f6c11f-12a6-486d-8e97-4fd979bbe292

Partition table holds up to 128 entries

First usable sector is 34, last usable sector is 15269854

Number Start (sector) End (sector) Size Code Name

1 1024 1277 127K 0700 PRO_INFO

2 2048 12287 5120K 0700 NVRAM

3 12288 22527 5120K 0700 TEE1

4 22528 32767 5120K 0700 TEE2

5 32768 34815 1024K 0700 lk

6 34816 86015 25.0M 0700 boot_x

7 86016 137215 25.0M 0700 recovery_x

8 137216 139263 1024K 0700 KB

9 139264 141311 1024K 0700 DKB

10 141312 142335 512K 0700 MISC

11 142336 158719 8192K 0700 LOGO

12 158720 182015 11.3M 0700 EXPDB

13 182016 2659615 1209M 0700 system

14 2659616 3171615 250M 0700 cache

15 3171616 3233055 30.0M 0700 boot

16 3233056 3294495 30.0M 0700 recovery

17 3294496 15269854 5847M 0700 userdata
[Fire TV Original Android Development] Rortiz2:
You need to Format Data, not Wipe.
[Fire TV Original Android Development] navin23:
It's still failing to format data in TWRP with the same error "unable to mount /data". I also tried fastboot format userdata via fastboot.

Is there anything else i can try?
[Fire TV Original Android Development] Sus_i:
Maybe run the gpt-fix, then format again.

Maybe switch userdata to ext3, format, reboot and take a look what happens, then format back to ext4.
[Fire TV Original Android Development] navin23:
I also tried changing to different extensions and it still failed to mount data.

I ran the gpt fix and it fails at the location below.

sudo ./gpt-fix.sh

[2024-01-16 16:43:55.272595] Check boot0

[2024-01-16 16:43:55.581676] Check rpmb

[2024-01-16 16:43:55.788337] Downgrade rpmb

[2024-01-16 16:43:55.790550] Recheck rpmb

Traceback (most recent call last):

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

main()

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

raise RuntimeError("downgrade failure, giving up")

RuntimeError: downgrade failure, giving up
[Fire TV Original Android Development] Sus_i:
Try disabling rpmb recheck in the main.py, # infront of the lines (rpmb and images are already downgraded via amonet).
[Fire TV Original Android Development] Sus_i:
There is an old thread for unbricking sloane. If you run the gpt-fix from it, you get the old full stock GPT back.

[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

Ofc the unlock, hacked fastboot and the new TWRP gets lost, best to flash the latest prerooted rom from rbox as a first step before doing the old gpt-fix.

FireTV 2 (sloane) Prerooted Stock Images [5.2.7.6_r1]

Here are prerooted stock images for use with my recovery. Note that these contain addon.d support, so any 3rd party things you install to /system need an addon.d script to be retained between flashes. Managing Stock Recovery Starting with...

xdaforums.com

Idk if this will help, but maybe worth a shot... i.e. try the stock GPT together with the old rbox prerooted TWRP.
[Fire TV Original Android Development] Michajin:
A while back i was told that older firetv2's that had samsung memory (it was switched over to different later) had some defects that made them fail. I know k4y0z mentioned it to me a few years ago. I am not sure of the details though....
[Fire TV Original Android Development] Sus_i:
Yes, @Rortiz2 got such a box with a dead eMMC (switchs whole eMMC to read only), but @navin23 is able to format cache fine, only userdata isn't formatting which is odd. :unsure:
[Fire TV Original Android Development] navin23:
Thanks, I suspected it was a hardware issue..

This is the info on the chip.

Samsung 543

KLM8G1WEPD-B031

S2ZAY00A

It seems other people has issue with this chip too.

Replace a BGA with a PCB - Page 1

Replace a BGA with a PCB - Page 1

www.eevblog.com

The file /dev/system does not exist - LibreELEC Forum

I have installed libreelec on a lot of Nexbox A95X, but a new box now with a strange problem, hope there is someone who can adress this issue. As you can see below, I could not install 8.2. Nexbox A95X S905X 1GB 8GB SSH - 8.2: Type "yes" if you know…

forum.libreelec.tv
[Fire TV Original Android Development] hafren:
Can someone provide a link to where the stock roms can be downloaded
[Fire TV Original Android Development] Bertonumber1:
5.2.9.4

https://d1s31zyz7dcc2d.cloudfront.prod.ota-cloudfront.net/725b18adc2a05a85e45842e11ba158d1/update-kindle-full_sloane-36.6.8.5_user_685791120.bin

5.2.9.5

https://d1s31zyz7dcc2d.cloudfront.prod.ota-cloudfront.net/5d7a6e4bc1c76e60ba3cceb871ded639/update-kindle-full_sloane-36.6.8.6_user_686800020.bin

Here is a couple Sus_i posted a while back, to be honest the latest UI is absolute adware and breaks things such as custom launchers so earch around this thread for more firmwares . You can get older pre rooted ones on aftvhacks and i think rbox done some too but just refer to the OP for assistance.

Regards
[Fire TV Original Android Development] hafren:
Thanks so much. I'll probably try 5.2.9.5 to see if it solves my video/sound issue. However I've seen on the forum a repository list of stock roms, not just for FTV2, but cant find my link. Do you know that members name of have the link?
[Fire TV Original Android Development] SK4G:
I'm not aware of a central repo that covers all Amazon devices. The OP in this post has links for mantis and raven.

The stock roms are mostly scattered throughout posts. They can be found using "Search This thread" and searching for "https://d1s31zyz7dcc2d.cloudfront.net/" in the [UNLOCK][ROOT][TWRP][UNBRICK] respective device threads.
[Fire TV Original Android Development] Bertonumber1:
Hi ...@bonezey2525

Try renaming on computer first as sometimes twrp can mess up renaming large files.

In windows/Linux

Right click and rename

Name_of_your_firmware.bin

and rename to

Name_of_your_firmware.zip

Use adb push or an extarnal USB / sdcard to get the files to you internal storage for flashing

adb shell

twrp flash Name_of_your_firmware.zip

twrp flash Magisk-vxx.zip

both below are optional

twrp wipe cache

twrp wipe dalvik

twrp reboot system

Regards
[Fire TV Original Android Development] Michajin:
@Rortiz2 so I bought a few demo sloane's off eBay. I am planning on unlocking them. Once I got into the stock room on the device it is version 5.5 (yes only 5.5). Fire OS is version 6.0.0.0. 5.5 seems to the demo version of the rom promoting alexa devices (it was looping a alexa demo on boot). I am assuming I can root, unlock and flash full stock. My questions, do you have any interest in this 5.5 version? Also, can I directly install 5.2.7.7 one into twrp? 5.5 doesn't require updates, and boots right into home. I plan on checking into this more. But I was curious if anyone has had this version before.
[Fire TV Original Android Development] Michajin:
Very little risk in my opinion. Use a live disk. A live disk is booted from a usb flash drive, ubuntu is fairly common.
[Fire TV Original Android Development] LazorBlind:
Google FireIso
[Fire TV Original Android Development] brick00444:
Here is the iso, https://github.com/amonet-kamakiri/fireiso/releases