yashsingh1/xdaforums huggingface dataset:
[Fire TV General] Pat1981:
root@sloane:/ # md5 /dev/block/mmcblk0?*

md5 /dev/block/mmcblk0?*

0070b21c65e57327efab59e5d7299fe6 /dev/block/mmcblk0boot0

da257620d2c9279c471b31e526958dd3 /dev/block/mmcblk0boot1

f9b5ef697fde92c42bbbec35e5a6cad4 /dev/block/mmcblk0p1

59071590099d21dd439896592338bf95 /dev/block/mmcblk0p10

50f24ce4c7ac388b33310bff6f79636a /dev/block/mmcblk0p11

a3ad800f012a153953b403ef1fa36e14 /dev/block/mmcblk0p12

ac82741df950e4b7517cdad089dc401f /dev/block/mmcblk0p13

61d3211a689d320e2e46bb5de4c84328 /dev/block/mmcblk0p14

a543eb1847e759be243b1f8d8f15420f /dev/block/mmcblk0p15

93db18d71677e16872021099130d24b6 /dev/block/mmcblk0p2

8a9d058f87711c2e8ccc698647f5026b /dev/block/mmcblk0p3

8a9d058f87711c2e8ccc698647f5026b /dev/block/mmcblk0p4

fbd20aa58cd63c07392080cad7627e18 /dev/block/mmcblk0p5

97a2ccdb7a02838b26b9a57e4f31d51d /dev/block/mmcblk0p6

74f0bac463bae8141acf20594987a559 /dev/block/mmcblk0p7

2e7467f2ded54b3e57e58ecc31079e6b /dev/block/mmcblk0p8

28cd64b57dd7ea7d9b993123598f2978 /dev/block/mmcblk0p9

a26f0b56848b1bdbb350f70141b58098 /dev/block/mmcblk0rpmb

FireTV2 with 5.0.3.1 rootet via VMware / Ubuntu
[Fire TV General] Patrick_445:
FireTV 2015 firmware 5.0.3.1

C:\>adb connect 192.168.1.38
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
connected to 192.168.1.38:5555

C:\>adb shell
shell@sloane:/ $ su
root@sloane:/ # md5 /dev/block/mmcblk0?*
0070b21c65e57327efab59e5d7299fe6 /dev/block/mmcblk0boot0
ddacaa66b543eb66e651e5910ed567df /dev/block/mmcblk0boot1
f9b5ef697fde92c42bbbec35e5a6cad4 /dev/block/mmcblk0p1
59071590099d21dd439896592338bf95 /dev/block/mmcblk0p10
50f24ce4c7ac388b33310bff6f79636a /dev/block/mmcblk0p11
a3ad800f012a153953b403ef1fa36e14 /dev/block/mmcblk0p12
6827f521a6eba4c6814da6ab27220e26 /dev/block/mmcblk0p13
b7cc901d721e3b4deb5ce6d9ae4ef008 /dev/block/mmcblk0p14
690fc9219dedb7509c671650b66caa80 /dev/block/mmcblk0p15
f9d33442bf5ea148be843f76b21cc9f5 /dev/block/mmcblk0p2
8a9d058f87711c2e8ccc698647f5026b /dev/block/mmcblk0p3
8a9d058f87711c2e8ccc698647f5026b /dev/block/mmcblk0p4
fbd20aa58cd63c07392080cad7627e18 /dev/block/mmcblk0p5
97a2ccdb7a02838b26b9a57e4f31d51d /dev/block/mmcblk0p6
74f0bac463bae8141acf20594987a559 /dev/block/mmcblk0p7
5dc0fc5b2df84c50cc45c4a271dccca0 /dev/block/mmcblk0p8
11bac21f84bbcda14db16f7dd503f277 /dev/block/mmcblk0p9
a26f0b56848b1bdbb350f70141b58098 /dev/block/mmcblk0rpmb
root@sloane:/ #

I don't know whether this matters but my hosts file has been modified (by the app AdAway)

...It's now 17 days later and I have gone from 5.0.3.1 rooted to 5.0.4 rooted. The hosts file has changed since the original post. Below are the MD5 hashes as of today:

root@sloane:/ # md5 /dev/block/mmcblk0?*
53649663ee0fa2f7c434b5acdbfddcda /dev/block/mmcblk0boot0
59eb8a1982a1ba1581b4c7044b42982e /dev/block/mmcblk0boot1
f9b5ef697fde92c42bbbec35e5a6cad4 /dev/block/mmcblk0p1
59071590099d21dd439896592338bf95 /dev/block/mmcblk0p10
50f24ce4c7ac388b33310bff6f79636a /dev/block/mmcblk0p11
a3ad800f012a153953b403ef1fa36e14 /dev/block/mmcblk0p12
2f3988483f637d0cb1ca0b8381e131e7 /dev/block/mmcblk0p13
b929ea22a705993680b378162da228f8 /dev/block/mmcblk0p14
f4cb53e7f47b60451f528e582334a002 /dev/block/mmcblk0p15
c80745be3a72c3e133350351644ef84f /dev/block/mmcblk0p2
8a9d058f87711c2e8ccc698647f5026b /dev/block/mmcblk0p3
8a9d058f87711c2e8ccc698647f5026b /dev/block/mmcblk0p4
f0b05f68cbcecb96722a4637eb06a8a0 /dev/block/mmcblk0p5
4cc42c5a4ded1eb4d9529b2aede1dfb7 /dev/block/mmcblk0p6
3aa70baba1bbb8b29f7d2fa7428e4e1e /dev/block/mmcblk0p7
5dc0fc5b2df84c50cc45c4a271dccca0 /dev/block/mmcblk0p8
11bac21f84bbcda14db16f7dd503f277 /dev/block/mmcblk0p9
a26f0b56848b1bdbb350f70141b58098 /dev/block/mmcblk0rpmb
[Fire TV General] retyre:
I have a nicely working rooted 5.0.3.1 with FlashFire and TiBU backups. Does anyone have a changelog for 5.0.4? It would be nice to know whether there are improvements, if any, from 5.0.3.1 that justify the need to upgrade.
[Fire TV General] Xedos9er:
Somebody mentioned that DTS and DD Passtrough is working now in Kodi. But he has only a 4k Av Receiver without HDCP 2.2. I could not verify it, since i don´t get any update :( I have a HDCP 2.2 and HDMI 2.0a Receiver.

Also i looks like you can choose now with 5.0.4 in sound settings between DD+ and DD output.
[Fire TV General] BagiMT:
DTS and DD passthrough have been working fin for me with Kodi on 5.0.3.1. My receiver is an older Pioneer with HDMI 1.3. The biggest news seems to be that sideloaded apps now show up in the apps list according to aftvnews which by itself is worth the update.
[Fire TV General] BagiMT:
Double posted by accident, sorry.
[Fire TV General] Xedos9er:
With my old HDMI 1.3 Receiver i also didn´t have any problems with passtrough. The new 4k Receivers have issues.
[Fire TV General] ultimate_spy_binns:
Just finished setting up a box, I've got five more to set up tonight and will post the md5 output as I go along setting them up.

Here Is the first one for you, FireTV2 with 5.0.3.1 rootet via VMware / Ubuntu.

root@sloane:/ # md5 /dev/block/mmcblk0?*
0070b21c65e57327efab59e5d7299fe6 /dev/block/mmcblk0boot0
583cdf67d73fe50b3122dd1061e9991f /dev/block/mmcblk0boot1
f9b5ef697fde92c42bbbec35e5a6cad4 /dev/block/mmcblk0p1
59071590099d21dd439896592338bf95 /dev/block/mmcblk0p10
50f24ce4c7ac388b33310bff6f79636a /dev/block/mmcblk0p11
a3ad800f012a153953b403ef1fa36e14 /dev/block/mmcblk0p12
f092fcb9d0ba27224e8ffbe2f0458567 /dev/block/mmcblk0p13
e2613a2d8bcf843f85638059a9ffaffd /dev/block/mmcblk0p14
d21bd84d0f16d0850265cb5435a6cfd3 /dev/block/mmcblk0p15
9772e05aacc59bfc21f3569a1f3ed0ba /dev/block/mmcblk0p2
8a9d058f87711c2e8ccc698647f5026b /dev/block/mmcblk0p3
8a9d058f87711c2e8ccc698647f5026b /dev/block/mmcblk0p4
fbd20aa58cd63c07392080cad7627e18 /dev/block/mmcblk0p5
97a2ccdb7a02838b26b9a57e4f31d51d /dev/block/mmcblk0p6
74f0bac463bae8141acf20594987a559 /dev/block/mmcblk0p7
b20c62e22b335b9c7e5eb1e5aa6fe428 /dev/block/mmcblk0p8
185250b650ebb39d66e54e39dd70b2c4 /dev/block/mmcblk0p9
40109dcc5c4e151070dd5a8af7c81d1c /dev/block/mmcblk0rpmb
[Fire TV General] zeroepoch:
I only really need 2 to see what is unique per device but 3 to double check. I have 3 or 4 now so don't worry about the others :)

I'll need a few on 5.0.4 as well once I get that out mainly to double check things. Then we'll know what needs to be dd'd to update until a better method is out.

I was dumb and didn't md5 before updating which would have really helped.

[MENTION=7078058]ultimate_spy_binns[/MENTION] since you have so many devices if you could take one rooted one that you hashed at 5.0.3.1 revert to stock then update to 5.0.4 root and do the hash again that would be cool. Mainly to see many angles. Don't want people to not flash something we didn't notice and get out of sync.
[Fire TV General] ultimate_spy_binns:
I'm more than happy to do that, but not on the current boxes since they are for customers and need to get shipped out tomorrow, due to Christmas rush.

I should have two more boxes arriving on Saturday, so I will do that for you then if that's okay.

Quick question, regarding the new boxes do you want me to root 1st with 5.0.3.1 and then resort back to stock firmware, and perform the update to 5.0.4, or Do you want me to just plug it in without rooting and update to 5.0.4, and then do the hash, or doesn't it really matter ?

Edit, I just read your post properly, you want me to hash first on 5.0.3.1, then on the same box, revert back to stock update to 5.0.4, and then perform the hash again for comparison, correct ?
[Fire TV General] zeroepoch:
Root 5.0.3.1 first so we can compare root between versions. Goal here is to mainly see what remains unchanged throughout the process. I'd do it except now I can't go back to 5.0.3.1

1. Root 5.0.3.1

2. Hash partitions

3. Revert to stock

4. Update to 5.0.4

5. Root 5.0.4

6. Hash partitions

Then we'll see what changed. That should be better than trying to compare a few devices to see what is device specific but it's still a good double check.
[Fire TV General] D-an-W:
Is the 5.0.4 root as "safe" as the 5.0.3.1 one is as I can try and do that now for you (My box is a rooted 5.0.3.1 with updates blocked)?
[Fire TV General] zeroepoch:
Yeah just mainly free time to create the patch files. It's automated but need to package it all up. Should be soon. I'll be using the new single zip file approach of course.
[Fire TV General] ultimate_spy_binns:
Okay I will do that on Saturday for you.

One more question lol sorry, what image am I using to root 5.0.4 with, because the current one is only for 5.0.3.1
[Fire TV General] D-an-W:
The restore procedure looks to have changed slightly since I made my notes, can I please confirm...

This:

cat /data/local/tmp/system.orig.img > /dev/block/platform/mtk-msdc.0/by-name/system

Changed to this:

dd if=/data/local/tmp/system.orig.img of=/dev/block/platform/mtk-msdc.0/by-name/system bs=1m
[Fire TV General] zeroepoch:
The dd is much faster (1-2 min) and also the proper tool for the job. If there is a problem with cat like source file not found weird things might possibly happen.
[Fire TV General] zeroepoch:
Here are the 5.0.4 hashes for my own reference:

53649663ee0fa2f7c434b5acdbfddcda /dev/block/mmcblk0boot0
5dba59324ba3db0391a7c5db9ece6eab /dev/block/mmcblk0boot1
f9b5ef697fde92c42bbbec35e5a6cad4 /dev/block/mmcblk0p1
59071590099d21dd439896592338bf95 /dev/block/mmcblk0p10
50f24ce4c7ac388b33310bff6f79636a /dev/block/mmcblk0p11
a3ad800f012a153953b403ef1fa36e14 /dev/block/mmcblk0p12
4736323bd867a1509d8f91d1f8e7f002 /dev/block/mmcblk0p13
96a8482c4727b322b9fe794a23abace0 /dev/block/mmcblk0p14
074cbda959d1e0c1e0e6c42427b9797b /dev/block/mmcblk0p15
4b8abd1dba969196fecf79d5e3e26a5f /dev/block/mmcblk0p2
8a9d058f87711c2e8ccc698647f5026b /dev/block/mmcblk0p3
8a9d058f87711c2e8ccc698647f5026b /dev/block/mmcblk0p4
f0b05f68cbcecb96722a4637eb06a8a0 /dev/block/mmcblk0p5
4cc42c5a4ded1eb4d9529b2aede1dfb7 /dev/block/mmcblk0p6
3aa70baba1bbb8b29f7d2fa7428e4e1e /dev/block/mmcblk0p7
c14b0b1088c28aab5a4a3460fceb3239 /dev/block/mmcblk0p8
7574d2c5ce52e9f9b8a61578a9ef9f04 /dev/block/mmcblk0p9
40109dcc5c4e151070dd5a8af7c81d1c /dev/block/mmcblk0rpmb
[Fire TV General] D-an-W:
This is my UK AFTV2 running 5.0.3.1 rooted:

0070b21c65e57327efab59e5d7299fe6 /dev/block/mmcblk0boot0
71833931557de0b659dcff7ee65f413f /dev/block/mmcblk0boot1
f9b5ef697fde92c42bbbec35e5a6cad4 /dev/block/mmcblk0p1
59071590099d21dd439896592338bf95 /dev/block/mmcblk0p10
50f24ce4c7ac388b33310bff6f79636a /dev/block/mmcblk0p11
a3ad800f012a153953b403ef1fa36e14 /dev/block/mmcblk0p12
e1d0473fa8c85fe8f0faccc66e5631a0 /dev/block/mmcblk0p13
d287ba1f23d56bd19fa3d00f0cac96cf /dev/block/mmcblk0p14
9238f4c865ed449cc19f69587e57bb11 /dev/block/mmcblk0p15
ee26a7f4d605c56a7ec76125cf90f152 /dev/block/mmcblk0p2
8a9d058f87711c2e8ccc698647f5026b /dev/block/mmcblk0p3
eda2733e1d0214873d9cb9d78c68425f /dev/block/mmcblk0p4
fbd20aa58cd63c07392080cad7627e18 /dev/block/mmcblk0p5
97a2ccdb7a02838b26b9a57e4f31d51d /dev/block/mmcblk0p6
74f0bac463bae8141acf20594987a559 /dev/block/mmcblk0p7
e6fa93ab5b287add2fbec77be781801c /dev/block/mmcblk0p8
776130b5e39610fcf1fb4b30c7ec9650 /dev/block/mmcblk0p9
40109dcc5c4e151070dd5a8af7c81d1c /dev/block/mmcblk0rpmb
[Fire TV General] ultimate_spy_binns:
Was just browsing your FTP server for the new images for 5.0.4

http://download.zeroepoch.com/aftv2/5.0.4/system.root.img.gz

http://download.zeroepoch.com/aftv2/5.0.4/system.orig.img.gz

Is this correct, the new pre-rooted images for 5.0.4 two patch ?
[Fire TV General] D-an-W:
This was the method I used to root 5.0.3.1 on the Pi 2:

git clone https://gitlab.com/zeroepoch/aftv2-tools.git
cd aftv2-tools
wget http://download.zeroepoch.com/aftv2/5.0.3.1/system.root.img.gz
wget http://download.zeroepoch.com/aftv2/5.0.3.1/system.diff.gz
gunzip system.root.img.gz
gunzip system.diff.gz
adb reboot ; ./handshake.py
./patch_mmc.sh 0x00000000058e0000 system.root.img system.diff

Can I please confirm what the method to use for 5.0.4 is as I don't (Yet) see a system.diff file, sorry if this has been posted but things are moving fast here at the moment!:

git clone https://gitlab.com/zeroepoch/aftv2-tools.git
cd aftv2-tools
wget http://download.zeroepoch.com/aftv2/5.0.4/system.root.img.gz
gunzip system.root.img.gz
adb reboot ; ./handshake.py
./checkver.py
./patch_mmc.sh 0x00000000058e0000 system.root.img
[Fire TV General] retyre:
One is the rooted image, the other is the original. You have to diff the two and generate the system.diff to flash.
[Fire TV General] zeroepoch:
If you want to jump ahead the diff is generated using:

cmp -l system.orig.img system.root.img > system.diff

You can run this from a Ubuntu machine. The latest scripts in the master branch will work with the new root image and diff. When I get some free time I'll prepare a zip with pregenerated patches inside like the test I released recently. That's the next step for me for people who want to wait.
[Fire TV General] D-an-W:
My Pi 2's SD card ran out of space creating the .diff file so starting again with a 32Gb one!
[Fire TV General] retyre:
The diff appears to be much smaller than in 5.0.3.1. Not much needed to be injected to root?
[Fire TV General] edwhardo:
Stuck at White Amazon Logo

I received 2 new 2nd Gen FireTV this week. They were both 5.0.3.1

Something went wrong with the first one and its is stuck on the white amazon logo. checkversion.py returns nothing and there seems to be nothing on the partition. The second one worked perfectly.

Can I just confirm that the above command with the 5.0.3.1 system.orig.img should get things back to original condition? Or will I need to write_mmc.py the kernel and bootloader too?

Thanks
[Fire TV General] zeroepoch:
You're right just system. If the checkver just hangs every time in the first but the second worked fine that is strange. Maybe hardware issue?
[Fire TV General] Patrick_445:
Is the space between "system.root." and "img" intended or a typo?

I am currently rooted on 5.0.3.1. Would steps 3, 4 and 5 delete my apps and data?
[Fire TV General] zeroepoch:
I was also noticing the byte difference is smaller. I didn't look at the number of non-sequential chucks but it might just mean more bytes are the same. Maybe just alignment is better with the previous data. It was a dd of my device after the install of su. I even wrote it back again and root still worked.
[Fire TV General] edwhardo:
I didn't try checkversion.py until after it was stuck in the boot loop. I made sure to identify the version on first boot from the system menu. After the first rooting fail, I ran the process again with a couple of different cables. Didn't see any errors, but if all we are doing is patching and the partition was empty/borked, we aren't patching anything.

If anything I blame dodgy soldering. I made a usb male A to male A cable out of a couple of spares and I was in a bit of a hurry. It did work for the second unit I tried, but I've tossed that cable and using a store bought one now.

It is hinted at a few posts back that the write_mmc process takes a while, so I'll just sit back and wait. If it is a hardware issue, I'll send it back.

Thanks for all of your efforts!
[Fire TV General] zeroepoch:
Typo.

No it keeps your data.
[Fire TV General] Patrick_445:
[MENTION=3411776]zeroepoch[/MENTION], Thanks. Do you think it would be a good idea for you to edit the Ubuntu Live USB instructions (https://gitlab.com/zeroepoch/aftv2-tools/snippets/11117) to add the version check (checkver.py) at the start of the process? Or at least add comments at the right position within the file with instructions to run the check and what condition should be met before proceeding to with the patch?
[Fire TV General] zeroepoch:
Thanks for the suggestion. Added a few lines.
[Fire TV General] gazdaman.:
Hi,

Just curious, what version of Titanium Backup are you running?

And are you able to enter the preferences menu?

On my AFTV2 when I try to enter preferences to change backup directory, the app force closes
[Fire TV General] retyre:
This is a problem with many apps on the FireTV (Titanium Backup, SuperSU, ...). Two ways to solve the Titanium Backup preferences issue: (1) Install Titanium Backup on another Android device, make the changes to your preferences in the GUI, and copy the preferences file to the FireTV (the file is located here: /data/data/com.keramidas.TitaniumBackup/shared_prefs/com.keramidas.TitaniumBackup_preferences.xml). (2) If you know what changes to make and the associated syntax, you can directly edit the aforementioned preferences file. Even so, you will find that the top row (with the check for batch actions) is missing in the FireTV interface. Right-click will bring up a menu.

When I do a batch backup in Titanium Backup, it breaks FireStarter (because of notifications, perhaps?). Uninstall and restore of FireStarter fixes it.
[Fire TV General] Pat1981:
I've enabled updates, installed the original 5031 firmware via dd, updatet via online update to 504 and createt the diff file from rooted and original 504 firmware.

The handshake is okay, but checkver.py doesn't find the build.pro at the right address. Do you have any Infos for guys howto root 504?

thanks!
[Fire TV General] ImCoKeMaN:
Take a look at the 5.0.4 branch on the GIT. It has the updated version.txt for 5.0.4 with the new address.
[Fire TV General] zeroepoch:
Check out the 5.0.4 branch or download a zip from the gitlab website. You need the updated version.txt for the check to pass properly.
[Fire TV General] Pat1981:
it's running - thanks! :)

md5 will come later
[Fire TV General] zeroepoch:
I think I have a pretty good idea which ones changed from looking at the scripts and diff of checksums from yours and mine. Would be nice to get your feedback before confirming it. I'll try to get that root zip out for you. Or do the diff yourself and use the old modular method.
[Fire TV General] ultimate_spy_binns:
I apologise I won't be able to do it tonight now, since I have been swamped with orders, I apologise, the earliest i can do it for you is Monday or Tuesday when I get a new shipment of boxes in, I apologise for any inconvenience.

And if possible can you send me the root zip, thanks.
[Fire TV General] Xedos9er:
I still have no 5.0.4 update notification !?!?! What´s wrong here? Any way to update manually?
[Fire TV General] Patrick_445:
Did you disable updates?
[Fire TV General] zeroepoch:
I got the new zip prepared. Follow the link below for those who know what to do with it.

http://download.zeroepoch.com/aftv2/5.0.4/root-aftv2-5.0.4.zip

I'll get the guides updated some time in the near future. This is for going from stock. Need a bit more info before we suggest the way to update without reverting to stock.
[Fire TV General] Pat1981:
works, 5.0.4 rooted - thx!
[Fire TV General] bula1ca:
Worked very well. Thank you
[Fire TV General] D-an-W:
The batch file calls the exe file with additional parameters and prompts so thats what you need to run.
[Fire TV General] zeroepoch:
[MENTION=7079005]D-an-W[/MENTION] is right it's just a wrapper that prints some instructions before calling the exe and pauses before ending so you can read the output.
[Fire TV General] zeroepoch:
Do you by chance have the md5s for 5.0.3.1 on the same device? Maybe I missed it if you already posted them.
[Fire TV General] AFTVnews.com:
Awesome work.

Not sure if this has been posted yet, or if it's of any use, but here is the OTA update package for 5.0.3.1 to 5.0.4: http://amzdigitaldownloads.edgesuit...sloane_full_sloane-534011720-to-536116920.bin
[Fire TV General] Xedos9er:
Any chance to force this update by copy it to the temp folder? Still got no update. I'm going crazy
[Fire TV General] Patrick_445:
[MENTION=1164016]Xedos9er[/MENTION] Maybe factory reset does not undo the OTA disable (pm disable com.amazon.device.software.ota). In that case, as [MENTION=3411776]zeroepoch[/MENTION] suggested, you may have to root, then re-enable OTA, then revert back to stock.
[Fire TV General] Patrick_445:
(double-post)
[Fire TV General] Xedos9er:
Just startet root. See tomorrow after it finished if it helps to activate ota.
[Fire TV General] gazdaman.:
Now that 5.0.4 has been rooted I have a question.

Although custom recovery has not been created or released yet, I hope that someone is working on this.

So, is there a preferred FW to be on for any potential custom recovery in the future?

[MENTION=3991724]rbox[/MENTION]
[Fire TV General] AFTVnews.com:
No, there's no way to force the update or manually install it. Just be patient. 2 out of my 3 Fire TV 2's have not updated yet. It usually takes at least a full week from when the 1st FIre TV gets the update to when all have been updated.
[Fire TV General] zeroepoch:
You probably need to set SELinux to permissive to do certain operations.

setenforce 0
getenforce # should return Permissive
[Fire TV General] zeroepoch:
I think at this point that might be the only option. Someone already rooted can dd the new rooted image to upgrade using their existing root. Someone new will need to apply the diff method from their base version. I would need to create the original and rooted pairs for any new versions released. I'm not sure if I will be able to scale it as you said since it's time consuming.
[Fire TV General] T0m93:
Confused using Mac

Hey i just ordered my new fire tv 2 and gonna sell my fire Tv first generation.

I will use my Mac to Root the Fire tv.

I'm not sure if i understand the Rooting process.

1.Connect the USB ports via cabel.

2. Install Python and Pyserial.

3. Change Handshake Port

How do i do this? I have my Mac Terminal. Python 3.5 installed.

And then i need to start to look for the Device.

How do i look in the /dev directory to find the right USBmodem?

I'm a little bit confused. The Handshake.py do i change it after the "gunzip system.diff.gz" command or before i start entering the commands.

Where/How do i change the Port? With some Terminal Command? Do i use the Python launcher and than enter the commands in Terminal?

To verify if i found the Right Device i use this command? while true ; do ls -l /dev/cu.usbmodem* ; sleep 1 ; done

and look what happends. Will the Fire tv go to sleep or will just the USB Device disappear.

Another Question do i use Python 3.5 Launcher or what. I'm pretty much confused.

4. Run First Commands etc.

6.Verify Root

Edit: Great Work by the Way :) I'm so excited :D
[Fire TV General] BBLT78:
Uk amazon fire tv rooted. Thanks

Xposed module doesn't seem to work, will there be an alternative way to do this.

Thanks again
[Fire TV General] bubbanc:
If it doesn't spit out like 5-10 lines and say handshake successful within the first 3 seconds of powering the unit up or rebooting, then your handshake failed.

---------- Post added at 08:54 AM ---------- Previous post was at 08:44 AM ----------

Thanks for the update. Appreciate your time to do this.

So, any way to make side loaded apps show up on the main screen (like on my Fire Stick w/ Llama). FireStarter appears to mess with the home button which sorta sucks. I'd rather keep things simple so my kid can maneuver around much like on the FireStick (to Kodi).
[Fire TV General] BBLT78:
Can I proceed to put clock work recovery on this one rooted?

Regards
[Fire TV General] rbox:
Chaining xposed and SuperSU together is a little complicated because they both hijack app_process. Are you sure you are using the lollipop version of xposed?

There is no clockwork for this yet, so that would be a no. Putting my version for the original fire tv will defintely not work. The bootloader is locked and we don't have a way to unlock yet, so recovery is going to be a little tricky on this. But I have some solid ideas and I'm going to start playing around with them.
[Fire TV General] BBLT78:
Great, thanks for your reply.

In regards to xposed, do I not need to flash a zip in recovery first ?

Regards
[Fire TV General] T0m93:
Need some help

Hey, when you are a mac User and want to enter the Wget lines usw curl -O instead of wget. Worked for me. dont just use curl... Something Weird will happen :D

And can somebody explain how to change the Handshake.py? Where is it and how do i change the Port. I know how the right Port is called .