yashsingh1/xdaforums huggingface dataset:
[Fire TV Android Development] Sus_i:
Ok, the script output looks good, although I think you haven't copied all of it. Furthermore you haven't add the 'clearing data' commands from my last post into your script.

No matter, from what I see, System, Boot, Recovery and Cache should be OK.

Data seems to be corrupt. We can try to fix that with TWRP, but I don't know if it will work, i.e. the partition table from the emmc could be corrupt.

Boot TWRP, select Wipe.

Go to advanced Wipe.

Select Data, click Repair or Change File System button

Select Repair File System (if it won't work do the next)

Select Data, press Change File System

Select Ext2 + swipe/confirm

Change back to Ext4 + swipe/confirm

Check your partitions, should be 6 (Dalvik Cache, Cache, Data, Internal, System, USB), if you can mount all of them (except usb) or not.

If not, do the same with Internal partition (Internal Storage).
[Fire TV Android Development] Sus_i:
That has nothing to do with resizing, it changes the filesystem, i.e. it formats the partition you select with ext2 or ext4.

Don't try that in future with system, or you can solder the cables back again, as it deletes all of the selected partition...

If you click on Mount button, which partitions can you see?

Which partitions under advanced wipe?

What do you know about this fireTV? How is the box bricked?
[Fire TV Android Development] LocoMexican:
OK, I'll reconnect to the computer and reflash. That is easy to do since the wires are locked down solid. My understanding is that this device was, at some point in it's life, connected to prime video and a pin number was established for that purpose. With a pin in place, the device would not allow anything without the pin first. Could not reset to factory defaults, or deregister, or watch or use any app without first entering a pin. When I received it, I decided that if it had root access and twrp recovery, then a person might be able to reflash the device after a twrp factory wipe and re-load with a fresh copy of pre-rooted rom, thus taking the pin out completely. But, I flashed the device as though it had a unlocked bootloader thinking merely changing the script from"locked" from no to yes. Of course the boot loader was actually locked. AFTER the fact, I posted about the bootloader edits, but by that time, the device was already flashed with bad instructions on my part. I simply thought I could edit the flash.sh file to fix the problem, but it looks like the files are totally corrupted. If you think it's toast, just let me know, and I'll consider it a lesson learned. If I can basically format the operating system and reload with a pre rooted rom, that's what I would like to do, and what I actually thought I was doing. Hope this helps. Thanks again for your help. At this point, I'll reconnect and reflash, but I'm going to shorten the wiring, thinking the existing set-up may have distorted the process.
[Fire TV Android Development] LocoMexican:
OK, shortening the soldered wires and dropping the ubs extension seems to have done the trick. The wires are about 1 and 1/2 inches long. The adapter is now plugged directly into the computer (no ubs extension). Reflashed with "flash.sh" script and it ran perfectly. Removed adapter, reconnected jumper wire where resistor was and plugged into TV. Booted into twrp, after 5 seconds, went to black screen and then booted into the aftv system. Device took about 10 minutes to re-orient itself and then started the set-up procedure. Unfortunately, it was not able to connect to the wireless router, so I had to stop for the night. If I can figure out the internet connection (which has never been a problem in the past) it should work as it is suppose to. In the meantime, the old compact computer seems to be going on the blink, so I was unable to copy the terminal read out. Thanks for your help, and I'll get back with you after I have time to work on the connectivity issue.
[Fire TV Android Development] Sus_i:
Congratulations :good:

Take your time, I bet you get sorted that out.
[Fire TV Android Development] LocoMexican:
Ok, all is good. I had set up my router anticipating a good result, and forgot to unblock the internet from the device. A brain fart on my part. Has to do with age I think. Anyway, it now boots into twrp recovery, then boots into 5.2.7.0, and connects to internet. Followed you instructions on blocking updates thru twrp, restarted and it ran fine. I rebooted several times just to make sure it was doing what it was suppose to do. Reconnected everything to my tv system, and all is fine.

In post 1419 you commented that "...the partition table from the emmc could be corrupt." In one of my first readouts on this device, I mentioned the error message I got when connecting to the computer. It said: "Unable to Mount 6.1 GB Volume". Yesterday when I started working on this, that error message was not present even though nothing had changed on my setup. Again, this inconsistency was when I first connected to the computer. You had already cautioned about keeping the wires short. So, that's why I decided to shorten the connecting wires. Apparently that is what was wrong from the get go. Thanks again for your help. You're the best.
[Fire TV Android Development] Sus_i:
:good:

That volume is userdata. The script formated that automatically with the "clear data" section I mentioned in post #1417

Don't worry about that, all good, the partition table is fine :good:
[Fire TV Android Development] LocoMexican:
Sus_i, in my lastest effort to salvage a 1st gen aftv, I relied on some of your posts in my first effort with my original aftv. In particular, the last 3 lines of Post number 1336, mentions a guide which you provide a link for, but the discussion ends with the following: "This guide is almost complete, but don't forget to chmod 755 the lastly pushed build.prop file (with twrp filebrowser), that's missing in the guide. Can you provide me with a proper script command to accomplish what you are describing? I think I was successful simply by virtue of luck. I was transferring the build prop by way of a usb for editing and then back to the device. An actual command to achieve the chmod 755 with twrp might prove helpful for myself as well as other who might want to try this in the future. Thanks for everything.
[Fire TV Android Development] Sus_i:
Thats easy. Boot into TWRP, take a look in Mount Tab, check System. Go back, select Advanced, select File Manager... in System scroll down and you find the build.prop file. Hook that file on, click permissions and if isn't already set to 755, click that 755 button. You see, if you push and replace a file from windows, file permissions gets lost. Ubuntu may keep the permission, but it isn't a mistake to take a look at the permission with the file manager.

You may do that with adb too, if you haven't did that already.

adb shell
su
pm disable com.amazon.device.software.ota
pm disable com.amazon.device.software.ota.override
pm clear com.amazon.device.software.ota

But since you have an emmc adapter, you can easiily root your box in case of an accidentally OTA update. You can use the script from #1340 to root a working box (it doesn't flash boot/system).
[Fire TV Android Development] codyppc:
Download link for 5.2.6.9 r1 no longer working. Anyone have a working link?

Thanks, Cody
[Fire TV Android Development] codyppc:
Can i use the 5.2.7.0 on Fire Tv 1?

currently on 5.2.1.1. with twrp 3.0.0-7

Thanks, Cody
[Fire TV Android Development] Sus_i:
Yes, of course
[Fire TV Android Development] codyppc:
Smooth install last night. Thanks everyone for the awesome work.
[Fire TV Android Development] rocker0:
thanks a lot
[Fire TV Android Development] Sus_i:
Hello rbox, I've captured two links... ;)

mPackageName='com.amazon.bueller.android.os', mNetworkType=WiFi,
mPackageVersion=646581820, mPackageVersionName='Fire OS 5.2.7.1 (646581820)',
mRemoteUri=https://d1s31zyz7dcc2d.cloudfront.net/a6ae0b9daed6058b4803fbd5fe923cb8/update-kindle-bueller-51.6.4.6_user_646581820.bin
mMetadata={binaryType=full, md5Sum=dee72791897d06a2587167ad0a819637}

mPackageName='com.amazon.bueller.android.os', mNetworkType=WiFi,
mPackageVersion=648594820, mPackageVersionName='Fire OS 5.2.7.2 (648594820)',
mRemoteUri=https://d1s31zyz7dcc2d.cloudfront.net/46279ca165796f56ed8083b0f07c79e3/update-kindle-bueller-51.6.4.8_user_648594820.bin
mMetadata={binaryType=full, md5Sum=befd9bf6d6b7cfd867cc492a8e253582}
[Fire TV Android Development] Jhya:
It would be awesome if we can get the latest software version of the FireTV 1 to use with the apple tv app!

I've sideloaded the apple tv app and added it to my amazon account. The only obstacle right now is that the apple tv app asks for the latest software version on the fire TV.
[Fire TV Android Development] rbox:
I updated the OP with 5.2.7.2._r1.
[Fire TV Android Development] Jhya:
Thank you [MENTION=3991724]rbox[/MENTION]! Updated successfully to the latest version for the Fire TV 1.

Still not able to get Apple TV version 1.2 to work. The app still require the latest software update. I'm guessing that version "Fire OS 5.2.7.2 (648594620)" is not supported by Apple TV, and it is looking for Fire OS 6.2.6.8 (3255372676) or higher in the build.prop.
[Fire TV Android Development] rbox:
Well 6.2.6.8 is only for the stick 4k and other devices. The older devices are on the 5.2. But you can make the build.prop say whatever you want.
[Fire TV Android Development] loplo:
It looks like I managed to brick my Fire TV (?)

Yesterday I had some issues with the box, and I made a factory reset from TWRP, formatting everything. Since then, my box is stuck at the black Amazon logo.

If I connect the box to my PC with a USB A to A cable, it gets recognized as a Kedacom USB Device (Android Bootloader interface). adb devices does not return any device connected.

Is there a way to recover my box, or is it gone forever?
[Fire TV Android Development] kywildcat:
wifi issues after latest update
[Fire TV Android Development] Matt_7:
Solved.
[Fire TV Android Development] Matt_7:
The 1st Gen FireTV box is very hard to brick, use the USB keyboard trick or you can try to reset the unit directly just by using the FireTV remote (see attached).
[Fire TV Android Development] loplo:
Thanks, I've already tried the usb keyboard trick, didn't work, gotta do some more research what I'm doing wrong. My remote died years ago, lately I was using their android app as remote.
[Fire TV Android Development] nycelitemaster:
Solved-
[Fire TV Android Development] Sus_i:
If I see this correct, three unlocked devices bricked just after installing 5.2.7.2.

Whats wrong? Maybe 'big A' implemented a new way to trigger the efuse, same as back then with 5.0.5?

At least Matt_7 was able to fix it yesterday with the dd / a-a cable solution. Clear sign for efuse kernel related issues?

---------- Post added at 01:22 PM ---------- Previous post was at 01:03 PM ----------

Hi

Take a look here, same issue solved yesterday ;)

Don't know if a virtual machine is reliable, may be a live iso started from usb is better!?
[Fire TV Android Development] kywildcat:
solved my issue, by wiping cache and dalvik
[Fire TV Android Development] jbl0ggs:
Hi,

I've dusted off my Fire TV Gen 1, its been rooted and currently running rooted version 5.2.1.1. I have about 800MB of free space left on it.

I wanted to update to December 7, 2019 - 5.2.7.2_r1 version (I presume this is the latest version available for Fire TV Gen 1).

Do I need more space to be able to install the latest version?

Once I move the .zip file to the Fire TV, do I just need to boot into TWRP and install ?

Thanks for any help provided with this!
[Fire TV Android Development] Y314K:
Any update on getting the latest Amazon Fire OS v5.2.7.3 (652613820) PreRooted FW ??
[Fire TV Android Development] Y314K:
Would advice you to use a Fat32 USB Stick to update from. Just better option.
[Fire TV Android Development] jbl0ggs:
Thank you! I will attempt it this weekend.
[Fire TV Android Development] Y314K:
Any word on getting a PreRooted 5.2.7.3 FW release please...
[Fire TV Android Development] nycelitemaster:
lol counting on rbox hahaha
[Fire TV Android Development] andrelecomte:
I too would greatly appreciate an updated prerooted ROM. My FireTV 1 has been serving my household well for five years.
[Fire TV Android Development] Sus_i:
Captured the url for 5.2.7.3, maybe useful, idk.

mPackageVersionName='Fire OS 5.2.7.3 (652613820)',
mRemoteUri=https://d1s31zyz7dcc2d.cloudfront.net/73e43763291e8e0c74482adb45497a0d/update-kindle-bueller-51.6.5.2_user_652613820.bin

[MENTION=3991724]rbox[/MENTION]
[Fire TV Android Development] Y314K:
Nice ,ty

Btw, had not realized AFTVNews.com is back online... So scene should be much easier to track.
[Fire TV Android Development] Sus_i:
Don't know, nothing heard about, seems that domain is for sale..
[Fire TV Android Development] Y314K:
Sorry, meant AFTVNews.com .
[Fire TV Android Development] nycelitemaster:
I don't think it is going to happen. Maybe RBox doesn't have the box anymore since it is discontinued.

On the other hand i'd like to know how can I revert to stock. Because all tutorials are for clockwork. This way should there is another patch It can auto update.

I don't use root anymore on this box
[Fire TV Android Development] Sus_i:
Doesn't mean nothing :p

Almost all fireTV's are discontinued, except the two cheapo sticks and that overpriced ugly box ;)

Besides that there are still ota updates for all fireTVs incl. the old stick one...

In case your box is unlocked, I 'assume something like dd the stock recovery out of a stock bin to the recovery partition and then enable ota updates in settings should work...

Maybe try a reboot recovery with adb, if the stock revovery comes up, an update should work fine. That will kill the unlock for sure and blows the efuse in the SOC.

Edit: Maybe you need to remove the unlock code from idme too, idk.
[Fire TV Android Development] nycelitemaster:
I read somewhere and did it. It blew the efuse. Then I had to dd all that stuff and Matt helped that time. LoL no simple process to revert anymore.
[Fire TV Android Development] Sus_i:
I see, your efuse is already blown and the unlock is gone.

That should make things easier.

If you really like to unroot, make sure that the stock recovery is in place and that you can reboot into it with adb.

Then enable updates and take a look in the settings, what OS version is ready for download...

Slight brick risk, I guess. ;)
[Fire TV Android Development] Sizzlechest:
All you need to do to get rid of root is to extract the boot_unlocked.img file and flash that in TWRP. No more su.
[Fire TV Android Development] nycelitemaster:
So you are saying, if I download the rooted firmware and extract the boot_img and just flash that. It should take care of root removal?
[Fire TV Android Development] Sus_i:
How is that supposed to work? ;)

If someone flash boot_unlocked.img onto a locked box, its a nice brick... :p

su is installed in systemmode (/system/xbin), not in the boot.img.

The bootmenu and TWRP runs out of a ramdisk, placed also on /system.

That changes on system needs to be reverted in order to get rid of them.

Since [MENTION=483068]nycelitemaster[/MENTION] 's box is locked, while it was formerly unlocked, he also needs to make sure, that TWRP isn't anymore at /recovery, must be replaced with the stock recovery.
[Fire TV Android Development] rbox:
I updated the OP with 5.2.7.3_r1.
[Fire TV Android Development] nycelitemaster:
Awesome. Thank you sir
[Fire TV Android Development] LocoMexican:
Thanks for the update. Installed it last night and it is running fine.
[Fire TV Android Development] guido1138:
Many thanks! Updated my FTV v1 last night and all is well.
[Fire TV Android Development] fido14dido:
updated with the latest and no issues so far. Is the Amazon News App now available on Gen1? Cant seem to find it/launch it.
[Fire TV Android Development] Y314K:
You are not really unrooting this way. But you can run as not rooted. I think TWRP will still block any FW updates. But any apps that detect root won't trigger. I run my rooted FTV1 Boxes this way. I delete the SU folder from the zip before installing it.

I think any method to really unroot will start with going back to stock recovery. Never seen a walk-thru for it though. I know AFTVNews.com was recently asked about it & he mention looking into it but nothing has been posted so far. So keep an eye there for a possible guide.

---------- Post added at 02:56 PM ---------- Previous post was at 02:52 PM ----------

Thanks again for the great update.. :good:
[Fire TV Android Development] feegus:
Is there any reason that a rooted 1st Gen Fire TV (using rbox's latest custom ROM) would not allow VPN's to spoof Netflix in other regions?

Specific to the root or custom rom - any issues in how they work vs a non-rooted box? Thanks vm
[Fire TV Android Development] Sus_i:
No. The prerooted rom is 100% stock (except the supersu files and the TWRP ramdisk).
[Fire TV Android Development] iniro:
Hello. Thx for updates.

Some time ago I bricked my aftv. With your help, linux and usb to usb cable, finally manage to unbrick.

Now, can I update to your latest prerroted stock rom?

Thx in advance.

---------- Post added at 07:30 PM ---------- Previous post was at 07:18 PM ----------

Im from Spain and I cant manage to work prime video on my aftv. I desregister, register, reboot... Any chance?

Thx!
[Fire TV Android Development] iniro:
If I do a full wipe, revert to stock and update to latest stock rom, I can install Kodi?
[Fire TV Android Development] Sus_i:
Probably yes, but a revert to stock is also a brick risk (you won't be able to fix anything with the stock recovery).
[Fire TV Android Development] iniro:
Im on restore Linux rom after brick. Can I update to latest rbox rom?

Im on this rom and situation:

https://xdaforums.com/showpost.php?p=78043554&postcount=1248
[Fire TV Android Development] Sus_i:
In case the guide worked for you and the box is up running again, you should be able to update to the latest...

There are a few reports from people using this unbrick guide and all went well (back then, 5.2.7.2 was the latest).
[Fire TV Android Development] iniro:
And how can I update? Normal update? Download and install from twrp? I think that I dont have unlocked bootloader.

Thx!
[Fire TV Android Development] Sus_i:
If you followed the unbrick guide from rbox, you should still have a working bootmenu and twrp!?

If yes, download 5.2.7.2 or -.3 from the OP,

adb push it to /sdcard (or use an usb stick) and then install the zip with twrp.
[Fire TV Android Development] iniro:
Thx I will try!
[Fire TV Android Development] iniro:
I updated successfully and all goes fine, but when i was watching a tv show on prime video, suddenly it reboots...

It spends 10 minutes on boot. Optimizing storage and system apps... And then reboots again.

What Im doing wrong?

I tried to install latest rom again but again I enter in a bootloop.

I have twrp. Any chance?

Thx in advance.
[Fire TV Android Development] Sus_i:
Sounds like a power issue, maybe check the power cable for damages.

If you have an USB power brick and an A-to-A cable, you could try to 'add' some power to the box via the USB A port, just to see if that helps somehow...

If it helps, your power brick is maybe too weak for a stable operation.
[Fire TV Android Development] iniro:
If I revert to previous version (bueller-5.0.5-rooted_r2). Then it works :(

Its very strange.

Edit: I plug an usb with power, but nothing...

Edit2: I can reproduce these steps:

1.Go to TWRP

2.Install and boot normally bueller-5.0.5-rooted_r2

3.Go to TWRP

4.Install 5.2.7.3 and change build.prop version on TWRP

5.Reboot. It boot ok. I can see a tv show for a while. Then it suddenly reboots.

6.Bootloop until I power off - power on and enter on TWRP.

What Im doing wrong?

I dont know if I have unlocked bootloader or not.

Can I wipe?
[Fire TV Android Development] Sus_i:
Yeah, why not :)

Wipe cache and dalvik.

You can wipe data too, but then the setup/logon will wait for you at the reboot.

If you wipe data too, you should edit the build.prop in order to block updates, or root is probably gone...

IDK if it helps you, but its good if you enable adb debugging, call su in adb shell, allow su access for shell on TV, then block updates with:

pm disable com.amazon.device.software.ota
pm disable com.amazon.device.software.ota.override
pm disable com.amazon.tv.forcedotaupdater.v2

PS: The bootloader is locked (due the unbrick), but that doesn't matter, it's still rooted and twrp is there.
[Fire TV Android Development] iniro:
I follow steps again. Only step that I dont realize was wipe data. It has working perfectly for 45 minutes aprox. Then it suddenly reboots and now is in bootloop :'(
[Fire TV Android Development] papars:
I run into a similar problem. I was on 5.2.7.0 and tried to update to 5.2.7.3

Now the box is in bootloop. I've done wipe data too without any change.

When I power up (cold boot) I see this order of logos:

-White amazon

-Colored animated amazon fire tv

-White amazon

-The twrp boot screen

and back again from the beginning.

If I leave it to reboot several times, I see a "optimising system storage and applications" that takes several minutes to complete. But after that I still get the boot loop.

I have tried to load 5.2.7.0 and 5.2.7.2 but got into the same loop. So box now is unusable.

Edit : the problem was the power supply.
[Fire TV Android Development] Sus_i:
If you like, you can try a clean install:

Make sure you have the latest prerooted installed, then go to twrp wipe and wipe cache and dalvik, then go back to wipe section and press the 'format data' button, type yes. Reboot.

In case it wont help, I guess it's a hardware issue.

A clean install should fix your box...

Boot TWRP, install 5.2.7.3, then go to twrp wipe and wipe cache and dalvik, then go back to wipe section and press the 'format data' button, type yes. Reboot (to the setup/logon screen).
[Fire TV Android Development] kywildcat:
alot of apps now popping up, system update needed. Is this the end of prerooted roms for FTV1?
[Fire TV Android Development] iniro:
And can be update?
[Fire TV Android Development] Sus_i:
I don't know if there is a new full update, last time I checked 5.2.7.3 was the latest...

I didn't like it (for an unknown reason, you cannot see anymore what **** you've already played with prime) and since then my two FTV1 are back on 5.2.7.2, running fine.

This will stop the updater:

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
[Fire TV Android Development] kywildcat:
Latest firmware via amazon (1st Generation): Fire OS 5.2.7.4 (656638920)

Apps I've noticed so far = ESPN, NBC and Thursday Night Football schedule on Prime Video throws this system update error
[Fire TV Android Development] Sus_i:
Ok, if you like these apps, maybe annoy [MENTION=3991724]rbox[/MENTION] a bit... :p

maybe he has some time to make a new prerooted^^

I'll try to catch the url for the update (but IDK if the update is out for my country).
[Fire TV Android Development] kywildcat:
Really appreciate it. I'll probably just end up buying a 4K cube, I've certainly got my money out of this device. Thanks [MENTION=3991724]rbox[/MENTION]
[Fire TV Android Development] Sus_i:
Seems 5.2.7.4 is pending in my country too, I got the update URL for 5.2.7.4:

mPackageVersionName='Fire OS 5.2.7.4 (656638920)

mRemoteUri=https://d1s31zyz7dcc2d.cloudfront.net/82273debe4fa84469809a5105ce182a0/update-kindle-bueller-51.6.5.6_user_656638920.bin

mMetadata={binaryType=full, md5Sum=4b330ac4720bf25756a540f30f58672c},

Lets hope [MENTION=3991724]rbox[/MENTION] get some time^^
[Fire TV Android Development] iniro:
Really? The problem was the power supply? How did you test it? Maybe is my issue too. Thx!

---------- Post added at 09:50 AM ---------- Previous post was at 09:25 AM ----------

Maybe I have a different partitions size and when cache partition fills it reboots? I dont know.