yashsingh1/xdaforums huggingface dataset:
[Fire TV General] DigitalBobby:
I tried all three ports on my windows 7 laptop, same results error: serial protocol mismatch, i used the same laptop to root 5.0.3 version with success.

I tried rooting version 5.0.4 with the first method, using the the 5.0.4 orig.img and 5.04 diff.img and it patches for less than a minute and said completed, but it wasn't rooted, i went back and tried using your new method ./root_aftv2.py, with no success still getting error: serial protocol mismatch

Found port = /dev/ttyACM0

Handshake complete!

Extracting build.prop...

ERROR: serial protocol mismatch
[Fire TV General] zeroepoch:
That's very unusual since the new method is mainly merging all scripts into one. The build.prop check stores the file in memory vs disk but that's it. It uses the same function for the read of the mmc. You are seeing it finish quickly because lastaddr.txt is present and at the end. Looks like it might be a good idea to remove it in the script if it gets to the end without an error.
[Fire TV General] ImCoKeMaN:
did you extract the zip or just try to click into it and run the file? Make sure you extract the entire zip to a folder.
[Fire TV General] go2xraj:
I extracted the folder and did but still same error..
[Fire TV General] rutinh:
My Fire TV 2 (runs on 5.0.4 FW) keeps stuck on Addr: 0x1d54a600, I do not know how to do next. Would some one help me out?
[Fire TV General] ImCoKeMaN:
Do you see version.txt in that folder you extracted? What os? Permissions ok? Running the script from that folder?

---------- Post added at 03:48 PM ---------- Previous post was at 03:47 PM ----------

Restart the process and see if it works on second try it has resume built in to the process.
[Fire TV General] go2xraj:
Yeah version. Txt was there in the folder.

I tried in Windows Linux and Mac

All says the same error
[Fire TV General] DigitalBobby:
ROOT success on 5.0.4 firmware after removing lastaddr.txt and using the first method to gain root, OTA also disabled

Patching patch_4b4e5400.img...

1024+0 records in

1024+0 records out

1024 bytes (1.0 kB) copied, 0.0208536 s, 49.1 kB/s

Addr: 0x50dc5400

Addr: 0x50dc5600

Conclusion:

I was only able to root using the first method, by removing the lastaddr.txt script and using the 5.0.4 system.root.img, 5.04 system.diff.img and running the ./patch_mmc.sh 0x00000000058e0000 system.root.img system.diff # process took about 2 hours.

I was not able to root using the second(newest) method, after running numerous times the sudo ./root_aftv2.py , i keep getting error: serial protocol mismatch

THANKS again [MENTION=3411776]zeroepoch[/MENTION]
[Fire TV General] ultimate_spy_binns:
Thanks worked great for me.

Here is a mini tutorial of the commands i used, bearing in mind I was pre-rooted on the older firmware 5.0.3.1

so I first had to return my box to stock and enable updates again.

After you have entered the following commands your box will reboot, next you will need to do a factory reset of your box, and then click on settings/system/about/and then click on "check for system updates"this will update your firmware to 5.0.4 the latest one.

Now I used this in a virtual machine in linux.

http://download.zeroepoch.com/aftv2/5.0.4/root-aftv2-5.0.4.zip
Execute sudo ./root_aftv2.py

This successfully worked for me
[Fire TV General] sidlas:
not working on dell laptop always stop at different addresses with no messages or with writing time out error.

connected to desktop running with out problems.
[Fire TV General] thecrock:
Follow the instructions

Cant be easier thank you..
[Fire TV General] shimonm:
thank you

work grain with mac
[Fire TV General] zeroepoch:
We've had a number of reports from people using laptops (especially Windows) where it will hang and you have to run it a few times, but desktops seem to mostly work. Thanks for the report it adds a bit more evidence to that claim.
[Fire TV General] efaden:
Are there instructions for returning to stock on 5.0.4?
[Fire TV General] sidlas:
not a few times good thing its have resume,and not briking... you need restart bat file and power off on unit,i did that 20 times,after moved to desktop,it stoped 1 more time anyway but just once. now everything ok,watching movies on kodi . :) don't use laptops! thanks zeroepoch.
[Fire TV General] spotmark:
I just started the root process, will it wipe my FTV? Will I need to reinstall Kodi?
[Fire TV General] deanr1977:
When I done It I done straight from a fresh box, but as far as I know/read about it no it won't, you should be able to carry on but with all your data intact still
[Fire TV General] luv2rip:
Hi Guys,

Need some help.

I got a brand new Fire TV 2. Got it updated to 5.0.4 and followed instructions from, https://gitlab.com/zeroepoch/aftv2-tools/wikis/macosx on my MacOSX with El Capitan.

No progress from "Waiting for preloader..."

Installed the Python, pyserial, disabled csrutil (SIP) ..

I also tried same on Mint Linux/Ubuntu (vm / no VM) with appropriate instructions for the 5.0.4, nothing

Can see the Fire TV connected via USB (adb devices shows the fire tv)
[Fire TV General] spotmark:
Took 2hrs. 10min. and all went well. Kodi remained, but I did have to redo the repo. Thanks for such a simple root method.
[Fire TV General] zeroepoch:
Make sure you don't have a data transfer cable with circuitry in the middle. It should be straight wires. That's the most common problem when it won't handshake.
[Fire TV General] Largewoodenspoon:
Am an hour into rooting 5.0.4. Fingers crossed it all goes well using windows method.
[Fire TV General] spotmark:
Just did it on my Windows 10 machine last night. Worked like a charm.
[Fire TV General] luv2rip:
Hi Zeroepoch,

This is the cable I picked up from Fry's last evening.

http://www.frys.com/product/8070764

I was just excited to receive my new AFTV2 , that I might have not been careful. I will check posts to see if I miss something.

If u happen to have any links to the right cable , Amazon, BesBuy (sucks !!), Fry's , Walmart I would appreciate it.

Thanks

l2r
[Fire TV General] liam080888:
I was just about to root my Fire TV and GITLAB is down. My cable arrived this morning and my body was ready for 2+ hours of staring at a blank screen.
[Fire TV General] wadisnake:
hmm gitlab is up and running just fine :)
[Fire TV General] liam080888:
It was down, I'm rooted now. :)
[Fire TV General] Ganjaware:
about Root...

Is this the right way to stopp the "OTA-Softwareupdate by Amazon" ?

Code:

_______________________________

adb shell

su

pm disable com.amazon.device.software.ota

________________________________

And did you try to connect a USB-Harddrive which is formated in NTFS, I have heard the AFT/2 will only accept (ex)Fat?
[Fire TV General] deanr1977:
Pretty sure that command is right mate (just checked yes that's right)
[Fire TV General] Ganjaware:
OK, thank you.

It would by VERY nice if you test a NTFS-hardrive on your rooted AFTV/2.
[Fire TV General] deanr1977:
I've heard its possible but not tried myself. Look through the forum mate because I'm sure I've read about this already.
[Fire TV General] xokol2lvox:
The ftv2 does not natively support ntfs, however stickmount from playstore will be easiest way to automount ntfs drive. I'm still trying to figure out how to get rid of ftv nag telling me it's not fat32 for 10 seconds or so at startup.
[Fire TV General] MicrosoftBug:
I was getting that too and then I realized that the wording in the guide is wrong, it's the .exe you have to run, not the .bat file. Once I realized that, it began rooting right away after power cycling my AFTV.
[Fire TV General] briansparrish:
To remove root from 5.0.3 do I just do a factory reset?
[Fire TV General] nav.jot:
5.0.4 Is Android Lollipop . I want to downgrades FTV 2 to any KITKAT based OS... Beacuse some apps stuck on loading in 5.0.4 ...Any solution
[Fire TV General] ImCoKeMaN:
no, factory reset just wipes /data and /system will remain unchanged. you would need to dd the system.orig.img file per some other post/guides around here for reverting to stock. Also, out of curiosity, what do you want to revert for?
[Fire TV General] briansparrish:
Thanks for the reply. There seems to be an issue with my fire tv's micro sd slot. Need to send it back to Amazon and I thought root may be frowned upon.
[Fire TV General] laidbackcloud:
I'm having trouble rooting this. here is what i get:

Waiting for preloader...

Found port = /dev/ttyACM0

Traceback (most recent call last):

File "./root_aftv2.py", line 413, in <module>

handshake()

File "./root_aftv2.py", line 378, in handshake

c = write8(b'\xa0')

File "./root_aftv2.py", line 100, in write8

in_str = dev.read()

File "/usr/lib/python3/dist-packages/serial/serialposix.py", line 453, in read

buf = os.read(self.fd, size-len(read))

BlockingIOError: [Errno 11] Resource temporarily unavailable
[Fire TV General] zeroepoch:
I bought my cable at Fry's as well.

http://frys.com/product/5289237

The cable you bought should be fine. I don't know if being USB 3.0 would cause any issues but I wouldn't think so.
[Fire TV General] zeroepoch:
Looks like the serial port was dropped. Try again with a different computer or different port.
[Fire TV General] zeroepoch:
You don't need to, but you should be running the .bat file. It's a wrapper around the .exe that has some instructions and when it exits gives you a chance to see the error messages. It sounds like you have something wrong with your python installation. It's really odd that the .exe would though when the .bat didn't.
[Fire TV General] met152:
Worked great for me. Thanks!

I was using my laptop and it did hang fairly regularly and I had to restart. Fortunately it resumed where it left off each time.
[Fire TV General] nozebleed:
No problems with USB 3.0. Im lucky enough to have a "monoprice-like" warehouse right up the road - paid 3 bucks for mine.

firefold(dot)com/3ft-usb3-aa-blue
[Fire TV General] MicrosoftBug:
I don't have python installed, the new method doesn't say anything about it being required.
[Fire TV General] stangri:
Thank you for the files and instructions at wiki. Using this dirt-cheap cable: http://www.aliexpress.com/item/Blac...ctor-Adapter-Cable-Cord-Wire/32520344931.html I was able to root the 5.0.4 with a Mac.
[Fire TV General] luv2rip:
Hi Zeroepoch,

I got a USB 2.0 cable and the MT65xx Preloader was detected on my Mac (El Capitan) but the root script failed with similar messages about Resource Not available (sort of), but then I connected to BOOTCAMP Windows (with earlier configured drivers etc), and it worked.

It got stuck many times , but just restarted and it resumed (it was scary though). Hope there is a faster way in future, but great work.

Just FYI, On my Mac it did not detect the preloader initially couple of times, then I reduced the time.sleep(0.25) to (0.01) , and then it detected.

I am rooted now. Installed my Busybox Pro and all good.

Thanks

l2r
[Fire TV General] dismalisdead:
5.0.4.

10 ft. Cables to go usb 3.0 male a to male a I picked up at a local shop for an overpriced $12

Rooted using Windows 7 pc, trouble with 2 separate windows 8 laptops.

It is listed elsewhere, but it is worth repeating in case anyone gets stuck: There are two folders for the VCOM drivers that are in the tut/walkthrough. Only install the drivers that are in zeroepoch's respective firmware folder. The 65xx is a dodgy link and should you actually install can complicate this process. It should also be mentioned that all of the drivers should be installed, not just the top vcom one. I'm not sure if that is necessary per se, but I didn't have any luck until I installed all five manually using the outlined method.

I'm reasonably sure that additional toying around with windows 8 laptops would have provided root result, but disabling driver signing or any walkthrough process requiring restarts on windows 8 are cumbersome to the point I felt it was unnecessarily risky to continue. As also previously mentioned, the process frequently stopped/stalled at the end of a patch. First couple of times it was scary, but the patching resumes just fine. The time estimates listed are accurate, but please note that the restarts are going to require your passive attention every ten minutes or so. (Mine started and I walked away thinking it would just run on it's own and added some time I wished I had back after the kid and Mrs. returned from the grocery.)

Stickmount is showing my 3tb hard drive that was impossible to format in FAT32. That alone is reason enough to root. :good: Thank you so much to all involved.
[Fire TV General] zeroepoch:
You're right. Somehow I was thinking because of the python backtrace that you were running the .py script. I tried to tweak the build to include encodings but encodings was already in the python library zip file so I'm not sure it will help. I updated the zip file already. My best guess why it didn't work is maybe you have a non-english language selected for your OS? Maybe only utf-8 gets built-in?
[Fire TV General] MicrosoftBug:
I'm running Windows 10 Enterprise x64 in English so not sure what it could be. It seemed to work just fine with the .exe except that I can't get SuperSU to open. It grants me access just fine via the prompt but I want to get in to customize it. Is there a way to update it to the latest version?
[Fire TV General] dtortora:
FTV2 setup Question

I have tried to root FTV2 using my Vaio Pro running Win 10 Pro. I keep getting stuck on "Waiting for Preloader". Nowhere in zeroepoch's instructions is an indication of the state of the FTV2 regarding developer options. Should ABD debugging, USB debugging and Apps from UNknown.. be on or off? I have tried them all on and all off. Both times getting stuck on "Waiting for Preloader". Since there are 9 permutations for these options to be on or off, a little heads up would be helpful, especially if this procedure needs to be run multiple times as the thread seems to suggest. BTW: when I turn on USB debugging I can see the fire tv drives on my laptop. Does that mean that I got the drivers right? Does this mean my cable is OK? I have tried these cables from amazon 1)Your Cable Store 15 Foot Black USB 2.0 High Speed Male A To Male A Cable and 2)C2G / Cables To Go 54171 USB 3.0 A Male to A Male Cable. Both are less then 5 bucks. Both let me see FTV2 on my vaio. Could someone do a video of this process? Thanks

---------- Post added at 08:15 AM ---------- Previous post was at 08:10 AM ----------

I have tried to root FTV2 using my Vaio Pro running Win 10 Pro. I keep getting stuck on "Waiting for Preloader". Nowhere in zeroepoch's instructions is an indication of the state of the FTV2 regarding developer options. Should ABD debugging, USB debugging and Apps from UNknown.. be on or off? I have tried them all on and all off. Both times getting stuck on "Waiting for Preloader". Since there are 9 permutations for these options to be on or off, a little heads up would be helpful, especially if this procedure needs to be run multiple times as the thread seems to suggest. BTW: when I turn on USB debugging I can see the fire tv drives on my laptop. Does that mean that I got the drivers right? Does this mean my cable is OK? I have tried these cables from amazon 1)Your Cable Store 15 Foot Black USB 2.0 High Speed Male A To Male A Cable and 2)C2G / Cables To Go 54171 USB 3.0 A Male to A Male Cable. Both are less then 5 bucks. Both let me see FTV2 on my vaio. Could someone do a video of this process? Thanks
[Fire TV General] deanr1977:
Yes usb debugging should be on, if you can see the drives via your computer that's good, if your cables are correct too they should be male a to male a cables, I know it's hard but one of the devs will answer you soon mate just keep reading through the posts until someone gets back to you. The only thing I can think of is what Ultimate binns video Of 5.0.3.1 said that he types sudo at the start with the first command? (Check his video) or someone also said there anti virus wasn't letting them go any ferther? Try disabling that & retry maybe?
[Fire TV General] dtortora:
Cables are both male a to male a. USB debugging is on but what about the other two settings in developer options. ADB bebugging needs to be on to see USB bebugging so both are on. Just figured that out. So i am left with App from Unknown? ON or OFF? Or does it matter? I am a writer so i am willing to write up a detailed account of how to do this once I can figure out "HOW TO DO THIS". Can someone comment on the driver part of my question? More specifically, IF I see the Fire TV paths on my laptop does that mean that the drivers are OK? I did the Vcom procedure on my Vaio (win 10 PRO) but did not do it on my HP Envy 360 (win 10). AS soon as I plugged in the FTV2 to my HP it recognized the FTV2 and installed drivers automatically and the FTV2 became visible on my HP. I can see the FTV2 and its microsd card on both. I can write directly to the microsd card on both. But I have failed to root using each laptop getting stuck on "Waiting for Preloader" on both. IS IT AS SIMPLE AS JUST REPEATING THE THE BAT FILE AND RESTARTING THE FTV2 UNTIL IT WORKS? How long should I stare at "Waiting for preloader" before I restart? 5 min. 1 hr? This is not clear to me?
[Fire TV General] ImCoKeMaN:
waiting for preloader is a fast step that happens within ~5 seconds of power cycling your box if the drivers are set properly. you should here the usb dings and if you are looking in the device manager you might even see the vcom drivers load while it does the preloader step. you may need to double check the driver install. use the ones from the zip file, but follow the procedure linked in the instructions.
[Fire TV General] dtortora:
How long do you wait for pre-loader befor restarting the process ?
[Fire TV General] ImCoKeMaN:
If it isn't finding the port restarting won't help and adb settings don't matter. Does USB ding when resetting fire TV in first 5 seconds? Try drivers, disable antivirus, other/desktop pc, vm method Many many had this work but the handshake waiting for preloader isn't more than a 10 second step
[Fire TV General] Rokkasho:
Windows 10

I was having an issue where the .bat file would sit at "Waiting for preloader...".

I ended up having to set the compatibility of the .exe to always run as admin and leaving the .bat file as standard.
[Fire TV General] Darkkeep:
The second it stops loading a new line. I usually counted to 10, closed cmd, unplugged power from aftv2, re-ran batch, plugged power back in. The second the script hit patch_25e17400.img, that's when the rebooting of the script started. Once it finishes this patch, everything went fairly quick.

---------- Post added at 07:04 AM ---------- Previous post was at 07:00 AM ----------

How do you know when the process is finished and you have root? Is there a special way to tell on the AFTV? Like SU installed?

I realize this is a n00b question...but I'm hammering around in adb and cannot achieve adb root in command prompt. Is that normal?
[Fire TV General] Rokkasho:
Stuck...

I seem to be stuck at "Found port = COM8" :(

Edit: Nevermind. Restarted the bat twice and the FTV once.

Started root sequence over. Fingers crossed.
[Fire TV General] Darkkeep:
I ran into this by installing the wrong driver. I installed the first in the list when the second one was what actually worked.

Update on my previous post, didn't realize that the permission to run SU on the aftv2 was that short. That was why I couldn't get SU to work under adb shell. All in all, it's a painless process. I now have kodi moved to the sdcard as well. Kudos and excellent work [MENTION=3411776]zeroepoch[/MENTION]
[Fire TV General] papabong:
I have a similar situation here - I´m on a AFTV 2 - I did upgrade to 5.0.4 then i performed the root-aftv2-5.0.4 procedures without any problems.

Tried to install the system tools in adbFire 2.0.1 and received an error stating "Systeme Tools not installed"

Did i missed anything ?

thx a lot in advance for some advise

cheers

papa
[Fire TV General] klofisch:
Hello,

i cant get past to "waiting for preloader". Bought just a simple cable and lsusb shows a Device with Vendor Lab126. This is my FireTV but it doesnt work. :(

What to do?

Peter

---------- Post added at 10:11 AM ---------- Previous post was at 09:40 AM ----------

ok,..with Windows7 it starts the process,.... lets see.

My first try had been with Ubuntu.
[Fire TV General] Darkkeep:
I used adb.exe from the android SDK installation. Granted, you need java jdk as well...somewhere around 300mb total download. Once you get it installed, I followed zeroepochs guide for disabling ota updates is what I followed for the adb usage...that and some hammering and hashing code/switches. Make sure you get you IP Address of you AFTV2. If you follow the guide on how to bring up the command prompt inside the Android SDK folder, type: adb connect {IP Address}. I stink at side loading apk's, so you're on your own. I'll have to spend some more time playing with the software.
[Fire TV General] klofisch:
Rooting with Windows 7 was successful.

I installed Google Play but it shows that it cant connect. :(
[Fire TV General] Fruchttiger00x0:
If I may personally give you a piece of advice, be a bit more patient before you get into trouble... Like me and my first device quick-fire solution ;)

rbox is working on the twrp recovery. after this we getting serious

btw. first App to install should be busybox
[Fire TV General] chu2tw6:
I had follw your guide ,then got my fire TV rooted and su command in adb shell.

Because I'm testing something so I decided to restore to original stock.

But after I follow the guide to restoring back to stock, then did root again.

Root_aftv2.bat finish in only a few second and show Congrats..." power cycle one more time.

At this time I didn't get su command in adb shell.

Does anyone get the same problem??
[Fire TV General] ImCoKeMaN:
redownload the files, older versions kept the lastaddr.txt file after completion. that is fixed in the latest.

Alternatively if you only want to root this one more time or do manually, you can delete lastaddr.txt
[Fire TV General] chu2tw6:
I'll try it when I get out of work.

I think this will solve my problem.

Thanks a lot!
[Fire TV General] mongolx:
Worked great, rooted. Updates blocked. Thanks.
[Fire TV General] Patrick_445:
[MENTION=3411776]zeroepoch[/MENTION],

A couple of very quick feedback points on how to make the wiki more user friendly.

1) The wiki suggests getting adb as part of the Android SDK. This is several hundred megs of software for just a tiny utility. Minimal ADB and Fastboot works just as well and is about 2MB in size. I've been using it for adb operations with the FTV1 and FTV2 without any problem.

2) Some Windows users may have trouble using ADB over USB if they don't have the right drivers. This happened to me. As a resource the wiki could point to the download link for the official ADB USB drivers for Amazon Fire devices. That driver is referred to here and here.

3) Several people seem to have trouble with inadequate USB wires. It might be useful for the wiki to have a list of confirmed-to-be-working USB A-to-A cords for this rooting process. I used this one. Below are other successful cords reported:
[Fire TV General] zeroepoch:
[MENTION=5910180]Patrick_445[/MENTION], this is all great advice. When I get a chance I'll add it to the wiki. I think I'll also include the adb drivers for Windows in the repo as well. I've been meaning to do that anyways.
[Fire TV General] liam08:
You've got a better Tesco than me. The only place around here with Male to Male was Maplin and they wanted £15.

Ended up with a USB 3.0 from Amazon, hoping it would speed things up a little. Only about £6.

Edit: This cable to be exact