I extracted the folder and did but still same error..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.
I extracted the folder and did but still same error..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.
Do you see version.txt in that folder you extracted? What os? Permissions ok? Running the script from that folder?
Restart the process and see if it works on second try it has resume built in to the process.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?
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.
wget http://download.zeroepoch.com/aftv2/5.0.3.1/system.orig.img.gz
gunzip system.orig.img.gz
adb push system.orig.img /data/local/tmp
adb shell
su
pm enable com.amazon.device.software.ota
dd if=/data/local/tmp/system.orig.img of=/dev/block/platform/mtk-msdc.0/by-name/system bs=1m
sync
reboot
http://download.zeroepoch.com/aftv2/5.0.4/root-aftv2-5.0.4.zip
Execute sudo ./root_aftv2.py
work grain with macNOTE: This procedure is only for stock devices. The safest way to upgrade rooted devices is still being worked out.
This is an updated thread for rooting the Amazon Fire TV 2. A newer and simpler rooting procedure has been developed and tested by a number of users, but the guides were not updated until now. We have decided to publish the guides on the wiki section of the repo website since it allows other primary contributors to edit the guides as well so we can share the work (currently just @ImCoKeMaN). For those interested in jumping straight to it follow the link below:
https://gitlab.com/zeroepoch/aftv2-tools/wikis/home
I have also uploaded the associated zip files to this thread as sort of a mirror. The above guide provides support for Windows, Mac OS X, and Linux. As of right now the procedure supports 5.0.3.1 and 5.0.4, but a unique zip file is required for each version. It does check the version when starting the root procedure so you'll have a chance to grab the correct one just in case. The original scripts are all located and will continue to be maintained in the git repo located here:
https://gitlab.com/zeroepoch/aftv2-tools
This new thread will serve as a place to ask questions and discuss the newer rooting procedure while the old thread will be more historical or for advanced users who are trying some new things using the preloader interface.
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.
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.
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 stillI just started the root process, will it wipe my FTV? Will I need to reinstall Kodi?
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)
Am an hour into rooting 5.0.4. Fingers crossed it all goes well using windows method.
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.
Once I've rooted, will the root access persist through subsequent automatic system updates?
This is what I did to build ADB on the Pi 2 which someone might find useful if they are carrying out the root procedure on one, please feel free to add it to the Wiki if you think it's relevant.
Makefile:
Code:SRCS+= adb.c SRCS+= adb_client.c SRCS+= commandline.c SRCS+= console.c SRCS+= file_sync_client.c SRCS+= fdevent.c SRCS+= get_my_path_linux.c SRCS+= services.c SRCS+= sockets.c SRCS+= transport.c SRCS+= transport_local.c SRCS+= transport_usb.c SRCS+= usb_linux.c SRCS+= usb_vendors.c SRCS+= adb_auth_host.c VPATH+= ../libcutils SRCS+= socket_inaddr_any_server.c SRCS+= socket_local_client.c SRCS+= socket_local_server.c SRCS+= socket_loopback_client.c SRCS+= socket_loopback_server.c SRCS+= socket_network_client.c SRCS+= load_file.c VPATH+= ../libzipfile SRCS+= centraldir.c SRCS+= zipfile.c VPATH+= ../../../external/zlib/src SRCS+= adler32.c SRCS+= compress.c SRCS+= crc32.c SRCS+= deflate.c SRCS+= infback.c SRCS+= inffast.c SRCS+= inflate.c SRCS+= inftrees.c SRCS+= trees.c SRCS+= uncompr.c SRCS+= zutil.c CPPFLAGS+= -DADB_HOST=1 CPPFLAGS+= -DHAVE_FORKEXEC=1 CPPFLAGS+= -DHAVE_SYMLINKS CPPFLAGS+= -DHAVE_TERMIO_H CPPFLAGS+= -DHAVE_OFF64_T CPPFLAGS+= -D_GNU_SOURCE CPPFLAGS+= -D_XOPEN_SOURCE CPPFLAGS+= -DWORKAROUND_BUG6558362 CPPFLAGS+= -I. CPPFLAGS+= -I../include CPPFLAGS+= -I../../../external/zlib CFLAGS+= -O2 -g -Wall -Wno-unused-parameter #LDFLAGS= -static LIBS= -lrt -lpthread -lcrypto -lssl TOOLCHAIN= CC= $(TOOLCHAIN)gcc LD= $(TOOLCHAIN)gcc OBJS= $(SRCS:.c=.o) all: adb adb: $(OBJS) $(LD) -o $@ $(LDFLAGS) $(OBJS) $(LIBS) clean: rm -rf $(OBJS)
Got the info from the two links below and tweaked it a little...
http://xdaforums.com/showpost.php?p=55619695&postcount=70
http://torifuku.blogspot.co.uk/2015/08/raspberry-piandroidadbandroid-debug.html