yashsingh1/xdaforums huggingface dataset:
[Fire TV Android Development] Zero_Shadow:
So I did a clean flash of 5.2.6.9 and the problem of Kodi stopping and locking up remains. I updated to Leia 18.2 to see if that helped form SPMC 17.1 and no dice. I have my files on a NAS and connect to Kodi via NFS which has never been a problem until recently. I am going to see if this is a network issue or does this happen even with a external device (Usb Drive) Ill give that a try a report back my findings.

*Update: If I can figure out how to get the USB port to work, I installed StickMount but it is not mounting the USB drive anybody know what I can try to get it to mount correctly.

I do notice to get Kodi back working if I clear the cache and force close the app it will work again after it locks up.
[Fire TV Android Development] xdause:
I tried going through this thread but can someone answer a simple question for me. For a firetv 1st gen with bootloader unlocked on 5.2.1.1 rooted rom and twrp 3.0.0.7: what is the steps to update the 5.2.6.9_r1? Just overwrite it with twrp install and wipe cache/davik like normal roms? Thanks for any info.
[Fire TV Android Development] Free4ever2:
I have the exact same setup, 1st gen firetv with unlocked bootloader, 5.2.1.1 rooted rom and twrp 3.0.0.7 and also want to upgrade to newest prerooted rom. Did you manage to upgrade without issues? Thanks.
[Fire TV Android Development] xdause:
unfortunately no because I already bricked an old device this year and the only reason I want to update is because of kodi but the issue does not seem to be related to firetv firmware. Since this device can only do 1080p; I probably will not update anytime soon.
[Fire TV Android Development] Free4ever2:
I went ahead and did the upgrade to 5.2.6.9 by booting to TWRP and wiping cache/dalvik cache and installing the image. Rebooted and after 10 mins of optimizing apps everything worked fine. So it should be straightforward if you ever do decide to upgrade.
[Fire TV Android Development] godlike1984:
can someone mirror the latest fw to gdrive or mega or zippyshare? its slow from mfire thanks
[Fire TV Android Development] rbox:
I updated the OP with 5.2.7.0.
[Fire TV Android Development] realbbb:
Loading this one now. Thanks!

update: Worked like a charm! Thanks again!

BBB

Paper Spot
[Fire TV Android Development] Zero_Shadow:
Thank You for your help rbox, really appreciate your hard work.
[Fire TV Android Development] LocoMexican:
I've been updating roms since 2011 with rbox pre-rooted. I downloaded pre-rooted bueller 5.2.7.0 and checked for a good match code. Copied rom to usb thumb drive, and installed thru TWRP. It erred out before completing the update. Could not get twrp back to its home, so I unplugged device power and restarted. On restart, I only get the white Amazon fire logo on and off and on and off, etc. Is there any way to get back into twrp and try this again, or is the device now bricked? Any help is appreciated.
[Fire TV Android Development] Sus_i:
Bootloader of the box unlocked? If yes, maybe fastboot is an option.

If no, I would think it's bricked, only an emmc adapter with soldering helps you out...
[Fire TV Android Development] LocoMexican:
Unfortunately, I remembered that bit of info after the fact. However, the bootloader was fully unlocked. Can you refer me to a post on the fastboot recovery?? Thanks for the info. Loco
[Fire TV Android Development] Sus_i:
Don't know this at all :D

I would try: fastboot reboot recovery

and if it won't work, I would try to boot the unlocked recovery image from rbox thread, i.e. fastboot boot unlockedboot.img

but please ask [MENTION=3991724]rbox[/MENTION] first before you try this, I really don't know details for the bueller box.
[Fire TV Android Development] LocoMexican:
Tried fastboot reboot recovery, but no banana. I was able to flash bueller-twrp_3.0.0-7.img. It didn't seem to help. I wanted to use the test.img 8 mentioned earlier in this thread. But, since the download address no longer works, I'm at a loss as to where I might find the test.img. It seems I can flash the device with fastboot, but I need to know what flash to use. Thanks for your help.
[Fire TV Android Development] Sus_i:
:D

OK, thought it's worth a shot on an amazon non-standard android system :D

That's not what I meant, I would try to boot the recovery image file from rbox, without any flashing. Put the image in the same folder together with adb/fastboot on your PC, connect the bueller and try: "fastboot boot recovery.img" But don't forget to adjust the name of the image. ;)

If you're lucky, twrp boots up and you can flash the prerooted again.
[Fire TV Android Development] LocoMexican:
Tried this with fastboot, but no help. There was a mention in the original comment to my post regarding soldering, etc. At this point, I'm pretty sure the device is bricked, so I have nothing to lose by trying to open up the device. I think I probably lost root access when I tried to update the rom, since Rbox puts SU in his updated roms. The device never completed the update, so SU was never put back into the device. Do you have a link to a possible solder schematic or other info on how I might try to give this a try? Thanks again for your comments and help.
[Fire TV Android Development] Sus_i:
OK, take a first look here, you see the 4 pads on the bueller that needs a soldered wire to the also needed emmc reader. Without this emmc reader and the advised sdcard reader, don't open the box. ;)

Here is the corresponding xda thread, called hardware root.

Next thread to watch (in order to unbrick) is soldering-method-how-disable-se-linux-t3533617. In there you find a script to flash a prerooted rom with the connected emmc reader (linux PC).

You see, a lot of work, but a possible solution if you get this reader from exploiteers (or build your own pcb like I did). ;)
[Fire TV Android Development] kywildcat:
Thanks [MENTION=3991724]rbox[/MENTION], yet another flawless update.
[Fire TV Android Development] tnkrer:
updated from 2.6.0 prerooted to 2.7.0 after wiping cache/dalvik and twrp install.

Install succeeded, it asked me to log in again to amazon and all my applications (ssh server, downloader, kodi) are gone.

Is that to be expected? Are they hiding in there and just not showing on the UI? I will check with adb .. (Always used ssh before, now have to deal with adb :( )

ETA: Looks like Android/Data folder does have those apps still .. so how do I actually get to use those?

ETA: reinstalled the basic minimum - ssh server, busybox and miXplorer

ETA: reinstalled all the apps I needed .. so now back to normal.
[Fire TV Android Development] LocoMexican:
I just saw this! I can't tell you how much I appreciate your setting this up for me. The bricked fire is my original fire. It would be a real coup to bring it back to life. I've already ordered a reader from exploiters. Even though I'm over 70 years, I can still solder. I've never actually used a Linux system, so I'll have to really work hard to figure out the "script to disable and allow flash prerooted rom. Thanks again for your help.
[Fire TV Android Development] Sus_i:
Let me know when you get your emmc adapter. I've done this multiple times and can tell you a few hints. In advance, take only really fine enameled copper wire for soldering (maybe slaughter a coil in an old power supply). Cut the wire into 2-3 inches long pieces (avoid cross-talking thru long cables) and tin both ends with solder. Also for setup the linux system & using the mentioned scripts, let me know if you have questions. I've split the unbrick/root script in four scripts, one does a backup, the second script copys the sparse rom image to an ext-image file, another script copys the ext-image (and if you want boot/recovery image too) onto the emmc in order to unbrick and the last script does the rooting stuff.
[Fire TV Android Development] LocoMexican:
I'll let you know when I get the reader. Also, I'm going to have to order the enameled copper wire, I think it calls for .02 enameled. The wire I have is insulated, so I have to strip off the outer insulation before tinning or attempting a solder connection. The Linux commands are going to be a challenge for me more than the soldering, but I have patience too. Maybe this will happen. Thanks again for your help.
[Fire TV Android Development] LocoMexican:
OK, I have the emmc adapter. Still waiting on the enameled wire and referenced card reader. Both of those should be here before the end of this week. I think I can do the soldering without to many problems. I've been looking at your post, as well as the script to unbrick. Keep in mind I am a complete Linux novice. The "backup" part, seems to be included in the referenced in the unbrick script, so I'm a bit confused with the sequence. The "second script" (copy sparse rom image to ext-=image file) seems to require a python download which is not part of the main script. The rooting part is the subject of a separate thread, and the copying of ext-image and boot/recovery is part of the main script. So, do I try to unroot first or is that the last step? Does the wired (soldered) connection stay the same thru the entire process? I assume I'll be using Ubuntu Linux throughout (except for where it calls for python). In the various posts, there was a comment about using Windows 10 for some part of the process. As you can see, I'm totally confused, so any hints, tips, or other help in advance will really be appreciated. Thanks for your help.
[Fire TV Android Development] LocoMexican:
Thanks for the info. At this point, I am going to attempt the Ubuntu computer set-up as you have recommended since it will have to be done at some point. Second step will be to attack the soldering part. I have the wire and the adapter in hand, just waiting for the card reader. I can then start with the rest of the process. I'll let you know what it looks like as I progress. It may be a day or two, but I'll be back. Thanks again for your help.
[Fire TV Android Development] Sus_i:
Yeah, take your time, play a bit with ubuntu and do the sdat2img thing. :good:

Don't attempt to run the full script mentioned above, we have to edit it for your unlocked device and there is also a error in if I correct remember.

Please tin the wire on both ends before start a soldering attempt, this enameled wire takes solder badly ;)
[Fire TV Android Development] LocoMexican:
I remember why I never tried too hard to learn Linux. It's too hard. Regardless, I have hit a roadblock on the Sparse image segment. Everything seemed to run correctly until the last command. Here's part of what my terminal showed:

locomex12@locomex12-Presario-C700-Notebook-PC:~/Desktop/Folder$ sudo apt install dos2unix

[sudo] password for locomex12:

Reading package lists... Done

Building dependency tree

Reading state information... Done

dos2unix is already the newest version (6.0.4-1).

0 upgraded, 0 newly installed, 0 to remove and 499 not upgraded.

locomex12@locomex12-Presario-C700-Notebook-PC:~/Desktop/Folder$ sudo apt install pv

Reading package lists... Done

Building dependency tree

Reading state information... Done

pv is already the newest version (1.6.0-1).

0 upgraded, 0 newly installed, 0 to remove and 499 not upgraded.

locomex12@locomex12-Presario-C700-Notebook-PC:~/Desktop/Folder$ sudo dos2unix sdat2img.sh

dos2unix: converting file sdat2img.sh to Unix format ...

locomex12@locomex12-Presario-C700-Notebook-PC:~/Desktop/Folder$ sudo chmod u+x sdat2img.sh

locomex12@locomex12-Presario-C700-Notebook-PC:~/Desktop/Folder$ sudo chmod u+x sdat2img.py

locomex12@locomex12-Presario-C700-Notebook-PC:~/Desktop/Folder$ sudo ./sdat2img.sh

Converting system.new.dat to img format... ./sdat2img.sh: 31: ./sdat2img.sh: /home/locomex12/Desktop/Folder/sdat2img/sdat2img.py: not found

Done!

locomex12@locomex12-Presario-C700-Notebook-PC:~/Desktop/Folder$ sudo ./sdat2img.sh

Converting system.new.dat to img format... ./sdat2img.sh: 31: ./sdat2img.sh: /home/locomex12/Desktop/Folder/sdat2img/sdat2img.py: not found

Done!

So, it seems everything ran fine until the last command. I have no idea where to look for the problem. Any input from your end is appreciated. Otherwise, I have everything in hand except i"m still waiting for the card reader. Maybe tomorrow or Sat. As always thanks for your help.
[Fire TV Android Development] Sus_i:
I think your path in the script to the sdat2img.py is wrong. Open the folder with that file in, click right, open terminal and check/compare the path...

EDIT: I looked at your terminal output, it seems that your sdat2img.py is in the Folder on Desktop.

I would edit the path in the sdat2img.sh script like that:

SDAT2IMG=~/Desktop/Folder/sdat2img.py
[Fire TV Android Development] LocoMexican:
OK, here's the latest:

locomex12@locomex12-Presario-C700-Notebook-PC:~/Desktop/Shared Files$ sudo dos2unix sdat2img.sh

dos2unix: converting file sdat2img.sh to Unix format ...

locomex12@locomex12-Presario-C700-Notebook-PC:~/Desktop/Shared Files$ sudo chmod u+x sdat2img.sh

locomex12@locomex12-Presario-C700-Notebook-PC:~/Desktop/Shared Files$ sudo chmod u+x sdat2img.py

locomex12@locomex12-Presario-C700-Notebook-PC:~/Desktop/Shared Files$ sudo ./sdat2img.py

Usage: sdat2img.py <transfer_list> <system_new_file> [system_img]

<transfer_list>: transfer list file

<system_new_file>: system new dat file

[system_img]: output system image

Visit xda thread for more information.

Press ENTER to exit...

Unfortunately the "system_sdat2img.img" is not in the unzipped 5.2.7.0 folder. I don't have a clue as to where it might be. I told you, I'm a novice at best using Linux/Ubuntu. Since I'm having this much trouble with this script, I don't know if there is a way to get through the main scripts Help again please. Thank you.
[Fire TV Android Development] Sus_i:
Yeah, it isn't there, because the error above. Most likely the path to the unzipped rom folder is wrong. Maybe you have unzipped the rom without the folder...

ZIP="${SHARED}/bueller-5.2.7.0-rooted_r1"

That was the path in my case,. I've extracted the bueller-5.2.7.0-rooted_r1.zip into the folder bueller-5.2.7.0-rooted_r1 and that folder is placed my shared path, which was in my case an usb stick.

As I said, don't worry about this to much, you are not the only one who has problems with ubuntu at first time. We only need to adjust the given paths in this little script with the correct ones. For the other segments this path doesn't change, you can copy/paste it to the next script.

Best is if you post your sdat2img.sh here, please copy/paste it between code tags, you find the code button if you press the reply button and then use the # sign in the xda editor.

Also please post the path to your shared folder and to the folder with the unzipped rom, you see the system_new file in there,

and I'm going to look over it...
[Fire TV Android Development] LocoMexican:
Believe it or not, I've been working on this for 3 days. I've tried so many different combinations with script changes and file changes, I'm totally lost. I think I should just walk away for a while. In the meantime, my card reader finally showed up, so I have everything in hand. Maybe I can work on soldering and then get back to working with Ubuntu scripts. If I can't get the soldering done, then there is no point in going forward. And, should that be the case, I'll be glad to donate my new card reader as well as my emmc adapter to a person you might think would benefit. Thanks again for all your help.
[Fire TV Android Development] LocoMexican:
I got the case opened with no problem. The resistor came off cleanly. The pads look great and are solidly intact. I don't know what happened to the resistor, but I understand that's not too important for now. Tomorrow, I'll see if I can solder the four wires in the appropriate place. Then, I'll connect it to the computer and see if anything shows up. I don't plan to attempt doing any more than just seeing if the computer, card reader, emmc adapter, and my soldering skills work. No programing planed until I get a grasp on Ubuntu and make the edits you said need to be made. Thanks again for all your help.
[Fire TV Android Development] LocoMexican:
The soldering seems to be complete. All four wires are connected and show good continuity on my ohm meter. Going to bed now, but will pick up again in the morning.
[Fire TV Android Development] Sus_i:
OK, thats fine :good:

Ofcourse you can test it with ubuntu. Plug in the power supply of the FTV (and wait about two seconds), then plug in the usb from the card reader into the laptop. The led from the emmc adapter should flash a few times, then it should glow solid blue. In case all is good, there are many pop up windows onto your screen, as the emmc has about 18 partitions. Some of them are mountable, some not... so you get filebrowser windows with i.e. system or data partition... but also a lot of error messages (could not mount errors). Thats fine! ;)

If the emmc adapter don't glow solid blue, there is an error anywhere, look for errors onto your screen.

No matter what, please let me know the result of your test...
[Fire TV Android Development] LocoMexican:
My soldering skills must be OK. Plugged in FTV power cord and then the emmc adapter/card reader. Got solid blue on the adapter and multiple windows/folders (7 total) came up. Four of the seven had several files contained inside. 1st window had several files. 2nd only had 1 file. 3rd had several files. 4th only had 2 files. 5th had several including xbin. 6th only had 3 files including data. 7th had several files. Is there enough left on the device to actually bring it back to life, assuming I can figure out Ubuntu? Reason I ask is because after the update failure, I tried flashing recovery, etc hoping to bring it back to life. I may have bricked it beyond recovery in that process. Just thinking out loud.

I'm going to delete everything on my old compact except for the operating system and start over. Question, in following your "how to", I'm not sure whether I need two working folders (one for shared files and one for the script-sparse img files) or just one folder containing all of the files. Thanks again for your help.
[Fire TV Android Development] LocoMexican:
Ran the 1st script (sparse img) and ended up with the following.

locomex12@locomex12-Presario-C700-Notebook-PC:~/Desktop/Folder$ sudo ./sdat2img.sh

Converting system.new.dat to img format... sdat2img binary - version: 1.2

Traceback (most recent call last):

File "/home/locomex12/Desktop/Folder/sdat2img.py", line 143, in <module>

main(TRANSFER_LIST_FILE, NEW_DATA_FILE, OUTPUT_IMAGE_FILE)

File "/home/locomex12/Desktop/Folder/sdat2img.py", line 68, in main

version, new_blocks, commands = parse_transfer_list_file(TRANSFER_LIST_FILE)

File "/home/locomex12/Desktop/Folder/sdat2img.py", line 35, in parse_transfer_list_file

trans_list = open(TRANSFER_LIST_FILE, 'r')

IOError: [Errno 2] No such file or directory: '~/Desktop/Folder/bueller-5.2.7.0-rooted_r1/system.transfer.list'

Done!

locomex12@locomex12-Presario-C700-Notebook-PC:~/Desktop/Folder$

When I open the "Desktop/Folder" and then open the /bueller-5.2.7.0-rooted_r1 file, the system.transfer.list' is IN the bueller-5.2.7.0-rooted_r1 file. So, I'm doing something wrong. I'll see if I can figure out how to unzip the bueller zip into my Folder. Seems that has to be the problem. With your spoon feeding, I thought I was almost there. I hope there aren't too many people watching me be dumb. But maybe it'll help someone else avoid my mistakes. Thanks again.
[Fire TV Android Development] Sus_i:
Yeah, you are almost there. Copy the bueller-5.2.7.0-rooted_r1.zip into the 'Folder' on desktop. Right click on it and look for extract... it should create a folder with the name of the zip in your Folder. You can open a terminal in the unzipped bueller-5.2.7.0-rooted_r1 folder and compare the path, it must be ~/Desktop/Folder/bueller-5.2.7.0-rooted_r1
[Fire TV Android Development] LocoMexican:
Checked and re-checked, and the path is ~/Desktop/Folder/bueller-5.2.7.0-rooted_r1. Any other thoughts? Maybe I should try using another version of Linux instead of Ubuntu? Don't know if that would help.
[Fire TV Android Development] Sus_i:
No. Don't do this, please. ;)

Yes. Unfortunately you didn't posted your terminal output, so I have to guess...

You managed to extract the bueller-5.2.7.0-rooted_r1.zip to

~/Desktop/Folder/bueller-5.2.7.0-rooted_r1

and checked this twice with the terminal, right?

Only thing I could think of, is that you don't get back with your terminal to your folder with the script, rather then trying to run the script from ~/Desktop/Folder/bueller-5.2.7.0-rooted_r1.

You see, the command sudo ./sdat2img.sh doesn't work at all, if you try that outside the corresponding folder with that script in, which is ~/Desktop/Folder

You can close the terminal and open a new one in ~/Desktop/Folder or you can use change directory. If you are in ~/Desktop/Folder/bueller-5.2.7.0-rooted_r1 you can type cd .. and you get back in the folder above.

Please go to ~/Desktop/Folder and open a terminal. Run this:

sudo ./sdat2img.sh

If you get errors, please do also the following:

Check if your terminal is in: ~/Desktop/Folder

Type the following commands line by line and press enter.

ls -la

cd bueller-5.2.7.0-rooted_r1

ls -la

Then please copy the whole terminal output and post it here and I'm going to look over it...
[Fire TV Android Development] Sus_i:
Sorry, was late yesterday, I'm about 8 hours infront of you... one path in the script above was incorrect, I have edited it now.

I'll also attach both scripts to this post, see the attachment.

I've set the correct path for you, should work fine.

Delete your old *.sh scripts. Extract the attachment with ubuntu, then copy both scripts in your Folder on Desktop as discussed.

Then simply run it with

sudo ./sdat2img.sh

Edit: In addition... The sdat2img thing works placed on desktop much faster than from an old usb stick. Duration only a few seconds. You can run this script a few times if you want, it will tell you if the image is extracted. Take a look at the file in the unzipped folder as discussed.

If you got no problems, you can connect your emmc. Close all popup windows for now. Go to the terminal and run the second script with

sudo ./flash.sh

If the script asks about clearing the cache partition, you have to press Y onto your keyboard.

Please post all printed output here.
[Fire TV Android Development] LocoMexican:
YES YES, I think. Here's the result.

locomex12@locomex12-Presario-C700-Notebook-PC:~/Desktop/Folder$ sudo ./sdat2img.sh

[sudo] password for locomex12:

Converting system.new.dat to img format... sdat2img binary - version: 1.2

Android Lollipop 5.0 detected!

Skipping command erase...

Copying 32767 blocks into position 0...

Copying 32767 blocks into position 32768...

Copying 32767 blocks into position 65536...

Copying 32767 blocks into position 98304...

Copying 18247 blocks into position 131072...

Copying 32767 blocks into position 163840...

Done! Output image: /home/locomex12/Desktop/Folder/bueller-5.2.7.0-rooted_r1/system_sdat2img.img

Done!

And, the file named 'system_sdat2img.img' is now in the unzipped 5.2.7.0 folder. I couldn't begin to understand what changes you made, but they worked and I really appreciate it. Should I now continue with the new scripts you posted in post 1325 above?
[Fire TV Android Development] Sus_i:
:good: :highfive:

There is only one script left. You can take it from my attachment or your other option is to do the copy paste thing with the second script from post 1325., which I posted above... both named flash.sh

If you take the copy/paste script, you have to run the sudo dos2unix thing and the sudo chmod, as descriped above.

Place the script in the same folder as the first one, connect your emmc. Wait about a half minute, then close all popup windows...

Open a terminal in your folder and run the second script with

sudo ./flash.sh

If the script asks about clearing the cache partition, you have to press Y onto your keyboard...

That script should do all the stuff in order to unbrick and root your device. It flashs the unlocked bootloader, recovery and system.

Please post the results and I look later on it...