yashsingh1/xdaforums huggingface dataset:
[Fire TV General] playingmax:
thanks for the tips will try n report back.

yes its a loptop and its set up as high performance. and have disabled sleep.

---------- Post added 26th November 2015 at 12:08 AM ---------- Previous post was 25th November 2015 at 11:50 PM ----------

still hangs. question. should I just use the regular win7 drivers. because I have a 64bit and I installed the win764. what do you think?
[Fire TV General] ImCoKeMaN:
Personally that's what I did and can't hurt at this point.
[Fire TV General] playingmax:
Still hangs. I don't know what else to do. Happy thanksgiving!
[Fire TV General] bula1ca:
Use archive from post 207 and post back.
[Fire TV General] playingmax:
Ill give it a try.

question, I select the "Mediatek preloader usb vcom port" is that the right one?

[IMG="drive"]http://img.photobucket.com/albums/v647/bonomax1itpics/111_zpsdcgpozy3.jpg[/IMG]
[Fire TV General] bula1ca:
I installed Android_Gadget_CDC_driver.inf driver,running Windows10 64. After installation reboot your computer.
[Fire TV General] ImCoKeMaN:
the preloader one is good, I have win7 x64, but didn't use the 64 bit driver. I didn't run this from a laptop though. If you have a change to try on a diff pc, especially a desktop I'd try that, but I'd love to see if we can work through your connection issues. I'd love to patch the code to fix it, but it's looking like the code is working and the connection is just resetting for some reason.
[Fire TV General] bula1ca:
I totally agree with InCoKeMan, it is a hardware issue. In my case I used a laptop, running windows 10 (64), I had to install 64 bit driver as 32 bit will not install.
[Fire TV General] memman:
I am having an issue trying to install the VCOM drivers on my Windows 7 desktop. My Device Manager screen shows that the Mediatek driver loaded but was unable to start. I have tried rebooting my desktop and the FiRE TV, all to no avail. My Device Manager also shows a Fire TV device, which also has an error. I'd like to start this process over still nice again, but am unsure if I am using the correct procedure. Any help would be appreciated.
[Fire TV General] ImCoKeMaN:
You may be at the right spot. Run the handshake.py script, as it's connected usb a-a cable to computer. While script is running plug in power to fireTV, that com port will only be available for a short time during boot unless that handshake script is running.

If this works about 5 seconds after you plug in your firetv to power, you should see handshake complete and you can continue with the process.
[Fire TV General] fldash:
Thanks for all the scripts, like the other guy, I'm having issues with it locking up. First it was lockup up on the third patch, then I changed the baud in device manager and in the write_mmc_win.py to 57600. Now it's stuck on patch_17c3e000.img. I've tried different bauds to no avail. I will try to buy a new Male A to Male A cable and see if that's the deal. Outside of that, I'm out of ideas. I'm running Windows 10, tried both the MT6577 USB VCOM and the Android Gadget CDC driver as well.
[Fire TV General] zeroepoch:
Report Root Success

Anyone following this thread who doesn't mind reporting their success rooting the AFTV2, please visit the newly created poll by ImCoKeMan. You can find it here.
[Fire TV General] memman:
I've now managed to work my way through most of the patches, but I've hit the wall with patch_20537400. I've had to nurse the patches by restarting the patching process at the place where the process stops. But the patch in question is so large, the process stops only partway through, so I cannot move on. I've played with baud rates to no avail. I noticed another person above saying that he will try another A-to-A cable. I guess I'll try that, too. Does anyone have another possible solution. Thanks in advance to those of you hepingout the rest of us.
[Fire TV General] Don_Black01:
There is a step missing in stage 4 of [MENTION=5630334]ians325[/MENTION] instructions in Zeroepoch's he downloads thee aftv2-tools this is not in Ian's instructions. In addition are you in adb when starting this stage Yes or no
[Fire TV General] zeroepoch:
[MENTION=394912]ImCoKeMaN[/MENTION] and I have some ideas to improve resuming so it can start intra-patch. You could also try an Ubuntu 14.04 live CD if you feel comfortable doing that. We've had one person report success doing that.
[Fire TV General] ImCoKeMaN:
I just did a quick test with a mountain lion machine and I didn't use the git command to get the aftv-tools and didn't need to install command line tools for the handshake, device is already rooted so there is a chance it could be needed for further steps, but I'm not sure it would be needed. Also, I skipped the adb stuff as it's nice, but not required for the patching itself

Here's what I did:

Download python 3.5 from python.org and install

install pyserial with terminal:

sudo pip3 install pyserial (enter password)

download the tools from:

https://gitlab.com/zeroepoch/aftv2-tools (just click download zip)

extract/rename to aftv2-tools (it has a long hash at the end of the name when you dl this way)

open terminal and:

cd aftv2-tools (may need to look in downloads folder)

Download the img files and extract:

curl -O http://download.zeroepoch.com/aftv2/5.0.3.1/system.root.img.gz

curl -O http://download.zeroepoch.com/aftv2/5.0.3.1/system.diff.gz

gunzip system.root.img.gz

gunzip system.diff.gz

Now connect aftv2 with usb a-a cable, but not power.

start handshake.py (I'm not using the adb commands as it wasn't installed, so that's why it's not on power yet):

./handshake.py

it will show "Waiting for preloader..." if you have the current (updated about 10 minutes before this post) tools version.

plug in the aftv2 to power. If all went well it will find the port and say:

"Handshake complete!"

Now you can follow with the last step which patches the image on the device to have root:

./patch_mmc.sh 0x00000000058e0000 system.root.img system.diff # takes ~2 hours

# last address is 0x50dce600

(if for some reason this last step doesn't yet work without the xcode tools, just wait, future versions this will be a py script too. Also, resuming will be improved shortly)

Additional note for Windows users:

the README_WIN.txt from the repo is now updated for the interim improvements to the process. You no longer have to manually edit files with com ports. Further simplification and what appears to be a very needed granular auto resume function will be coming [MENTION=3411776]zeroepoch[/MENTION] has good ideas there.
[Fire TV General] playingmax:
pics of my install w/ no success. I will be replacing usb cable and reporting back.

[IMG="1"]http://img.photobucket.com/albums/v647/bonomax1itpics/1_zpsfvgcfogv.jpg[/IMG]

[IMG="2"]http://img.photobucket.com/albums/v647/bonomax1itpics/2_zpsuje3vjst.jpg[/IMG]

[IMG="3"]http://img.photobucket.com/albums/v647/bonomax1itpics/3_zpsadrbycqp.jpg[/IMG]

[IMG="4"]http://img.photobucket.com/albums/v647/bonomax1itpics/4_zpsu3wcm1e5.jpg[/IMG]

[IMG="5"]http://img.photobucket.com/albums/v647/bonomax1itpics/5_zpsweg176no.jpg[/IMG]

[IMG="6"]http://img.photobucket.com/albums/v647/bonomax1itpics/6_zpskrdh9doh.jpg[/IMG]

[IMG="7"]http://img.photobucket.com/albums/v647/bonomax1itpics/7_zpssjmnnkkt.jpg[/IMG]

[IMG="8"]http://img.photobucket.com/albums/v647/bonomax1itpics/8_zpsbbwiemeo.jpg[/IMG]
[Fire TV General] ImCoKeMaN:
Yeah, I don't think you're doing anything wrong, you might want to try a usb live cd (usb) though as you could do that without buying anything new.

Also, the new resume in development would help you continue where you left off even if it takes multiple restarts.
[Fire TV General] playingmax:
how do I get the resume in development? is this in windows or would I have to do the ubuntu?
[Fire TV General] ImCoKeMaN:
you have to wait until it's developed, but [MENTION=3411776]zeroepoch[/MENTION] might have some progress tonight to post.

It would be cross platform, but trying a VM or live USB is really zero risk and who knows you may like Linux =)
[Fire TV General] playingmax:
I think ill wait for [MENTION=3411776]zeroepoch[/MENTION] becaue i know 0 about Linux. but on a good note I downloaded ubuntu-14.04.3-desktop-amd64.iso just dont know where to start other then burning to cd. and booting from cd. Im a lost poppy after that.
[Fire TV General] Don_Black01:
[MENTION=394912]ImCoKeMaN[/MENTION], how do you start handshake.py
[Fire TV General] ImCoKeMaN:
type it from the terminal/command prompt or double click it

You will have to have installed python and pyserial of course, but it should be that easy.
[Fire TV General] Don_Black01:
Says command not found

---------- Post added at 05:06 AM ---------- Previous post was at 04:56 AM ----------

Does the two system files need to be in the aftv2-tools folder
[Fire TV General] ImCoKeMaN:
in terminal you have to be in the aftv2-tools folder (assuming you renamed it to that after extracting the zip) and type it as ./handshake.py

and yes the .img files need to be in that same folder

Also a step I didn't mention (but was mentioned by others) was to take that port and edit write_mmc.py to use that port. (This step is currently still needed until, but a future improvement is planned)
[Fire TV General] Don_Black01:
Ok, so the two system files that are download after the aftv2-tools need to be inside that folder

---------- Post added at 05:39 AM ---------- Previous post was at 05:35 AM ----------

I am re-downloading them now into the aftv2-tools folder

---------- Post added at 05:48 AM ---------- Previous post was at 05:39 AM ----------

Is this correct
[Fire TV General] zeroepoch:
That's almost right. The reason it's saying command not found is because you need "./handshake.py" instead of "handshake.py". It's a shell thing. Also when you gunzip'd the diff file you accidentally included "adb reboot" at the end so it couldn't find the file.
[Fire TV General] zeroepoch:
OK... I've added resume support to the windows branch of the repo. If you don't want to bother with the git commands just use the zip download from https://gitlab.com/zeroepoch/aftv2-tools/repository/archive.zip?ref=windows. Nothing in the procedure has changed but when it hangs now just run handshake again, reboot the device, the run the patch script again. You won't need the continue version of the batch script anymore. It should quickly skip ahead to where it last left off when you killed it. Please let us know if that works for you.
[Fire TV General] ImCoKeMaN:
I just updated the windows branch so the bat files run write_mmc.py and no longer write_mmc_win.py as the changes were added to the primary script.

Also, when you got it working again did the new handshake.py work? It's been updated too. I tested it on windows and it should work for all OSes now.

redownload and try again =)
[Fire TV General] Don_Black01:
Says waiting for pre-loader
[Fire TV General] fldash:
Did you change anything else? All I did was download the new package and mine is flying through, hasn't gotten stuck yet (not to say it won't, but it's much farther than I ever got before)...
[Fire TV General] Don_Black01:
My other terminal where I inputed ls: /devcu.usbmodem*: No such file or directory is that suppose to have a number at the end where the * is because I did not get a number

---------- Post added at 05:25 PM ---------- Previous post was at 04:52 PM ----------

I am on IMac running Mavericks

---------- Post added at 05:53 PM ---------- Previous post was at 05:25 PM ----------

That is the current problem I am having ls: /devcu.usbmodem* does not do anything, can someone tell me what I am doing wrong here
[Fire TV General] zeroepoch:
Actually if you update to the latest copy of the repo the handshake script should automatically figure out the port for you. It should print "Waiting for preloader..." and then you reboot the device (or plug it in at that point). [MENTION=394912]ImCoKeMaN[/MENTION] tested the new handshake script on a Mac environment and at least the new handshake should work.
[Fire TV General] ImCoKeMaN:
You need to connect usb a-a cable to firetv and computer.

Start ./handshake.py it will say waiting for preloader...

Then plug in power to the firetv.

in ~5 seconds it should see the preloader and move to handshake complete.

that usbmodem command will only find something for ~3 seconds during firetv bootup.
[Fire TV General] Don_Black01:
I am re-downloading repo system files as Zeroepoch suggested. Then I will plug in usb a-a cable and proceed

---------- Post added at 06:34 PM ---------- Previous post was at 06:32 PM ----------

In the second terminal window where I am running devcu.usbmodem cmd should I also be In th aftv2-tools folder

---------- Post added at 06:39 PM ---------- Previous post was at 06:34 PM ----------

How would I know if the AFTV is communicating with iMac when I plug in USB A-A cable. What indicator should I look for. Then once preloaded message comes up then I need to plug in power cord is this correct.
[Fire TV General] fldash:
Dumb question, mine just completed... Does that mean it's done? I don't do anything with all these IMG files?

Patching patch_4b4ee400.img...

rawwrite dd for windows version 0.6beta3.

Written by John Newbigin <jn@it.swin.edu.au>

This program is covered by terms of the GPL Version 2.

skip to 1263461376

1024+0 records in

1024+0 records out

Addr: 0x50dce400

Addr: 0x50dce600

Done!

Press any key to continue . . .
[Fire TV General] Don_Black01:
Now it is asking me to overwrite gunzip but it won't let me

---------- Post added at 06:50 PM ---------- Previous post was at 06:48 PM ----------

I manually did it

---------- Post added at 07:01 PM ---------- Previous post was at 06:50 PM ----------

Still saying waiting for preloader what am I doing wrong.

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

All files updated as we'll from Zeroepoch repo
[Fire TV General] zeroepoch:
That looks good! Connect it back to an HDMI port, setup adb, and try running "su". You can just delete the patch files they are just temp files.
[Fire TV General] Don_Black01:
Ok, what do I need to do this on windows I will do it from my laptop
[Fire TV General] zeroepoch:
That looks right. The output on the left window would change around the same time it gets past the Waiting for preloader on the right. It's not detecting the device at all. Did you try power cycling it while it's doing that?
[Fire TV General] zeroepoch:
I'm not actually sure. I've never connected this device with adb on Windows. But the process would be to install the adb driver and download the Android SDK tools or find a copy of just adb.exe. I think ADBFire includes some of these tools. [MENTION=394912]ImCoKeMaN[/MENTION] would know better.
[Fire TV General] ImCoKeMaN:
To do the basics on windows you still don't need adb. You can follow the steps from my others posts, or check the newly created wiki that has some info for each OS:

For windows:

https://gitlab.com/zeroepoch/aftv2-tools/wikis/windows

for other OSes:

https://gitlab.com/zeroepoch/aftv2-tools/wikis/home
[Fire TV General] Don_Black01:
Just tried adb fire I can't not use she'll unless I connect to network and power on
[Fire TV General] ImCoKeMaN:
I wouldn't mess with ADBFire yet unless [MENTION=2718012]jocala[/MENTION] says it's ready for firetv 2.
[Fire TV General] Don_Black01:
Ok

---------- Post added at 07:27 PM ---------- Previous post was at 07:26 PM ----------

I just looked at your instructions for Mac, and I did all of that and It is still not moving

---------- Post added at 07:28 PM ---------- Previous post was at 07:27 PM ----------

I know it is not my USB A-A I just used that to root a Ouya a couple weeks ago

---------- Post added at 07:32 PM ---------- Previous post was at 07:28 PM ----------

@IMCokeMan In your windows instructions in the wiki you say extract files to same directory is that "aftv2-tools" or some other directory
[Fire TV General] ImCoKeMaN:
everything always needs to be in the same directory tools and image files.
[Fire TV General] playingmax:
it stopped at Addr: 0x25b65c00 am I close to the end?
[Fire TV General] ImCoKeMaN:
You still have a way to go

# last address is 0x50dce600
[Fire TV General] playingmax:
Thank u. I don't understand why it keeps stopping. Sounds like ill be at this all night too.
[Fire TV General] ImCoKeMaN:
know anyone else with a computer you could try?

or Linux livecd ;)

otherwise, probably...
[Fire TV General] playingmax:
I have a desktop n wife a mac. But I'm too far into this to start over.
[Fire TV General] ImCoKeMaN:
well, it shouldn't take long to get started, and if you copy over the lastaddr.txt file it will start from where you are now.
[Fire TV General] playingmax:
I think I'm going to take u up on that. Because I'm at Addr: 0x25c43600
[Fire TV General] fldash:
Yes, I'm good with SU. Thanks again, everyone.
[Fire TV General] playingmax:
ended up using PC. guess problem was with laptop.

Patching patch_4b4ee400.img...
rawwrite dd for windows version 0.6beta3.
Written by John Newbigin <jn@it.swin.edu.au>
This program is covered by terms of the GPL Version 2.

skip to 1263461376
1024+0 records in
1024+0 records out
Addr: 0x50dce400
Addr: 0x50dce600

Done!
Press any key to continue . . .

---------- Post added at 11:15 PM ---------- Previous post was at 10:54 PM ----------

question. does this mean my update is blocked?

C:\Users\Morris\Desktop\adbFire>adb connect 192.168.1.111

* daemon not running. starting it now on port 5037 *

* daemon started successfully *

connected to 192.168.1.111:5555

C:\Users\Morris\Desktop\adbFire>asb shell

'asb' is not recognized as an internal or external command,

operable program or batch file.

C:\Users\Morris\Desktop\adbFire>adb shell

shell@sloane:/ $ su

su

root@sloane:/ # pm disable com.amazon.device.software.ota

pm disable com.amazon.device.software.ota

Package com.amazon.device.software.ota new state: disabled

root@sloane:/ #
[Fire TV General] zeroepoch:
Yep
[Fire TV General] Jay794:
Don't suppose there has been a windows tool developed for us idiots out there has there?
[Fire TV General] BagiMT:
Has anybody been able to get the Google Play Store working on the rooted Fire TV 2? I loaded the required apps but Play Store gives a connection error. Will this still require the Xposed script?
[Fire TV General] Antieco:
Hi, is it possible to root amazon fire stick?
[Fire TV General] playingbball20:
Have you checked the firestick root? It's on the forum
[Fire TV General] playingmax:
I too would like to know this.
[Fire TV General] puppinoo:
Hi,

Just rooted a UK Fire TV 4K bought on Ebay.

After first handshake I waited for about half an hour for something to happen but prompt was still.

So I read advice to reboot the device as I did. There was no need to reboot my linux box and "Addr" prompts started. 2 hours later I disabled OTAs using root :)

Thanks a lot Zeroepoch.
[Fire TV General] Antieco:
You mean the one involving soldering?

Is any software way to root fire stick?

Enviado desde mi OnePlus One
[Fire TV General] bula1ca:
You need Xposed script for Google Play Store and at the moment it is not available for aftv2.........yet

---------- Post added at 12:50 PM ---------- Previous post was at 12:47 PM ----------

No such of thing at the moment.
[Fire TV General] frellin:
I have also the same issue, also the problem that my K400 QWERT keyboard will only be identified as a QWERTY one. No chance to change settings somewhere.

I know that this keyboard layout issue was once a problem until a AFTV1 OS upgrade was distributed. So I do not really know if this keyboard thing is now an additional root phenomenon or a general software bug?!?
[Fire TV General] Don_Black:
Instructions need to be more in Detail

[MENTION=394912]ImCoKeMaN[/MENTION] and [MENTION=3411776]zeroepoch[/MENTION],

I too tried this on OS X Mavericks and Windows, on Imac I did everything instructions said to do just hangs at "waiting on preloader." Plugged in, plugged out, no change. I believe there is a communication problem between Imac and fire tv cable checked on 1st gen fire tv and it connected. Please provide explanation as to how to ensure device is communicating.

Tried on Windows first you should restate the prerequisites for install python and pyserial. This can only be done in cmd prompt if you change your environment variables in advanced settings in windows. even after this was done still not able to download pyserial.

Guys, I understand you are more proficient in software rooting and development. Some of us are newbies, I know how to open up a terminal and run a few simple commands, but unless you think about all the non-developers and software developers. Then this beautiful script will only be enjoyed by a few. I am not trying to insult anyone, but if this community is poised by teaching then teach with detail and descriptive so that all can understand and not just the advance users.

Thank you for all your help you have done thus far.

regards,
[Fire TV General] ultimate_spy_binns:
add me for help

add me on Skype antspy11, if you would like I'm happy to help you, I've managed to route 13 devices so far successfully.
[Fire TV General] playingmax:
I too have done 7 w/out any problems under windows. just waiting on Roms to be released.
[Fire TV General] zeroepoch:
Wow! That is a lot of devices! I'm glad I could be of assistance with your mass rooting :)

I'm very sorry that our guides have not been easy to follow. We both have kids and don't have a lot of time to write detailed guides. We assume you have a certain base understanding of the components involved. Until this has been nicely documented on blogs and other sources you can assume XDA is for active development and early adopters. This is why I provided low-level details on how I rooted the device so you will know what is going on and decrease your risk of breaking the device. Also to allow other developers to help streamline the process. Once rooted you should expect things to become more technical based on the advanced features you are trying to implement. We are working on simplify the process to a single script that can eventually be converted to an exe and remove the need for dd or python at all. Also the download will decreased from 500 MB to 3 MB. This has been slow because we haven't had enough time to finish it and make it safe. You should consider rooting at this point still in development and why there is no single zip with everything you need but instead a git repo you clone. While many have been able to root the device successfully, it's not the simplest procedure and we're not even sure it will work for future versions yet. [MENTION=394912]ImCoKeMaN[/MENTION] has some concerns about an update arriving (could be sooner or later) and someone rooting after updating, so we're looking to add an additional step in the instructions to check the version in case someone doesn't know how to do that themselves. This would be trivial to check with adb but since people have issues with that additional step we're going to rely on checking a known block of the flash the contains the version. Don't feel too concerned about not being able to root the device. The hope is it will become easier. The best you can do for now is to update and then use some debloating guide to disable updates. I haven't debloated myself since once I had root I didn't need to use that method.
[Fire TV General] zeroepoch:
You must already have python with pyserial working otherwise you wouldn't see "Waiting for preloader...". For Windows you also need to install drivers. I haven't done this myself, but I was hoping to test the procedure in the near future. Mac OS X you shouldn't need drivers just plugin and power on the device. There must be some sort of hardware issue because once that message appears you plugin the USB cable then plugin power and that's it. Maybe you also need to enable all the developer options first in the settings menu? I really don't think that should matter but I've never tested it with those options off. There are some ways to debug it on Mac OS X but it involves using the command line or timing refreshes on the system information like tool.
[Fire TV General] Don_Black:
Need Help

I will add you when I leave work, [MENTION=7078058]ultimate_spy_binns[/MENTION]

thanks,