yashsingh1/xdaforums huggingface dataset:
[Fire TV Original Android Development] Sus_i:
Well, this feels really weird. Someone develope a hack to root, but doesn't take care at all to figure out a way for updates... :confused:

What is with fastboot? Is that aviable for your bricked fireTVs?

I've read a bit in the exploiteers blog here

Don't know, is this only for the initial rooting process? What the hell is flashboot?

Edit: [MENTION=3597813]xXhighpowerXx[/MENTION]
[Fire TV Original Android Development] Diazz72:
Does it work on 2nd gen cube and will Netflix play in FHD&4K ( a.k.a. do we lose Widevine L1 )?
[Fire TV Original Android Development] Michajin:
no the exploit only worked on a 1st gen cube and pendant, and it was blocked by amazon.
[Fire TV Original Android Development] Darkfact5249:
Any exploit for amazon cube second generation?
[Fire TV Original Android Development] Michajin:
No, there isn't any exploit for 2nd gen cube.
[Fire TV Original Android Development] phier:
still no update for 2nd gen cube? Also is there a way to do something if 2nd gen cube is blacklisted by amazon? thanks
[Fire TV Original Android Development] Michajin:
No, i haven't seen anything. I can only suggest contacting amazon and see what they will do. Play stupid, maybe they will swap it out. Usually their customer service is pretty fast to please the customers. You never know....
[Fire TV Original Android Development] phier:
So i can basically trash the device? No, they are saying that GIFT sender reported it as stolen; even tracking says delivered and also i can proof i own it. they rejected any further discussion and kept it blacklisted - idiots.
[Fire TV Original Android Development] Michajin:
That is up to you. You can store it away for years and hope a exploit is found, Throw it away, or try and sell it on eBay with the note it is blacklisted. I don't think anyone can get past the setup with a blacklisted device, but likely someone would buy it and try.
[Fire TV Original Android Development] phier:
hm seem then device is gone; unusable anymore ... :(
[Fire TV Original Android Development] Finnzz:
@phier @Darkfact5249 @Diazz72

There is this for the 2nd gen Cube but it's only temporary root right now:

https://xdaforums.com/t/temporary-unlock-root-twrp-magisk-firetv-2nd-gen-cube-raven.4445971/
[Fire TV Original Android Development] JedidroidX:
Considering just buying an nvidia shield instead of buying a linux box and other hardware to hack a cube. Just wish it was less troublesome as bricking the cube seems likely with just one mistake. Nvidia shield has a lot of development support and even offer the roms on their support website incase of bricking. Its a no brainer, just wanted to share my opinion...peace!!
[Fire TV Original Android Development] AZImmortal:
Thanks for taking the time to write all that up, it's incredibly helpful. I have a question about the Arduino needed. Is the DUE completely necessary, or can an UNO (or other variants) work? And if other variants can work, then do the instructions need to be adapted in any way?
[Fire TV Original Android Development] retyre:
The Uno should work (I do not have one to confirm). Use A4 for SDA and A5 for SCL.
[Fire TV Original Android Development] PeterLustig:
Can anyone tell me how I can be sure that the arduino uno was flashed correctly? I can't get it to work with one. The FTV just shows up as an Lab 126 device.
[Fire TV Original Android Development] ldeveraux:
Also having this issue! I'm pretty sure the sketch flashed correctly, I'm not sure I have the HDMI wired correctly. I know not recommended, but I'm using an Elegoo Mega 2560 R3 instead of an Arduino Due. I'm also using this HDMI adapter: amazon.com/gp/product/B071X4GX2B

These are the wires: (Elegoo - HDMI)

SCL 21 - SCL 15

SDA 20 - SDA 16

GND 52 - DDC/CECG GND 17

EDIT: It's not the Elegoo. I got a Arduino Due and it still won't enter DFU

EDIT2: Weird, for some reason it found the AMLogic this time, randomly. Backing up now, hoping it works!
[Fire TV Original Android Development] PeterLustig:
I'm using an arduino uno. SDA wired to A4, SCL to A5. OS is ubuntu 18.04. HDMI breakout adapter is from Delock. But FTV3 won't go into DFU Mode. Is there any way to debug this?
[Fire TV Original Android Development] ldeveraux:
I got through the backup and the exploit. Once the flash is successful, what exactly am I supposed to unplug? The HDMI from the HDMI adapter? Or the USB? I unplugged the HDMI from the adapter and it says it reset. Then after "Fastboot flash patched boot image" after pressing enter, it just sits at "waiting for device". How do I get this thing into fastboot?
[Fire TV Original Android Development] retyre:
If it's waiting for the device in fastboot, it's most likely an issue with permissions. Have you added the udev rule for fastboot? Does the fastboot device show up in lsusb (as Google Inc. Celkon A88)? When you type fastboot devices, I'm guessing it says it doesn't have permissions for your device?

And yes, you unplug the AFTV3 from the HDMI breakout before reset into fastboot.
[Fire TV Original Android Development] ldeveraux:
So I got it back to fastboot made where the lsusb said "Google, Inc". I manually flashed the recovery, but completely forgot to flash the boot.img. Now I can't get the device back to fastboot mode to flash the boot. If I hook up to a TV, it's stuck on the FireTV screen. Can I get back to fastboot mode to flash the boot img or did I brick it?

I'm going to try installing the exploit again from the sh without backing up this time, see if I can't get back to fastboot. Then manually install boot,recovery if I need to.

EDIT: This time it worked! The exploit installed, then rebooted to fastboot and I was able to root. Checked Magisk and root access granted. Thanks all for the help, this was more complex than I first thought!
[Fire TV Original Android Development] xXhighpowerXx:
FYI: to get back into fastboot mode, you just need to enter DFU mode with the HDMI dongle (Arduino) attached then unplug the dongle when it entered DFU mode (check with lsusb) run the reboot tool ("$ aml_reboot fastboot"). Now it should be in fastboot and you can flash your boot / recovery image.
[Fire TV Original Android Development] PeterLustig:
Congrats! Did you use the due or what did you change? Can't get it to work with an uno R3.
[Fire TV Original Android Development] ldeveraux:
Yeah, I figured that out pretty early on just by searching through the code

I did use the Due, not the Elegoo. I don't know enough about the exploit to know how to determine the correct IDs for the Elegoo, or whether it's Amlogic or not. My guess is not. I could try a few quick tests to see, but it might be chasing my tail. Has anyone gotten this to work fully without a Due?
[Fire TV Original Android Development] retyre:
What do you mean? The Elegoo is a clone. It will have the same ATmega2560 as the Arduino it's based on. Just like the genuine Due and all its clones have the SAM3X8E.

Amlogic is the chip in the AFTV3, not the Arduino.
[Fire TV Original Android Development] ldeveraux:
brain fart, sorry. Though the interface is different; the Elegoo is USB A-B and the Due is microUSB. Doubt that would have any ill effect, it's just different. I had to retry the DFU procedure many times before it would kick in, so persistence is key here. :good:
[Fire TV Original Android Development] BRICK0044:
I get as far as trying to install exploit then clickk on the y all 4 times then it doesnt back up anything. It says Error: Fail to backup boot1. Any help would be appreciated. Will keep trying and see what happens.
[Fire TV Original Android Development] BRICK0044:
when you create the "70-firetv3.rules" file does it only have SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", ATTR{idVendor}=="1b8e", ATTR{idProduct}=="c003", MODE:="0666"

SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", ATTR{idVendor}=="18d1", ATTR{idProduct}=="0d02", MODE:="0666" in it? I can't seem to get it recognized in lsusb.

I was able to upload and verify in Ardunio in windows, i wanted to try it in linux but could'nt get it to upload.

I hate to ask but can someone send me their rules file? Maybe I'm screwing something up creating it.

---------- Post added at 07:09 PM ---------- Previous post was at 06:58 PM ----------

When you say retry the DFU procedure many times, what exactly are you doing when you retry? Is it as simple as just unplugging the usb and replugging it back in. I have tried completely rehooking the jumpers and then powering up the arduino and then plug in the usb to pc. I have also tried soldering the jumpers on so I would have a good connection. Sorry for rambling on but I'm pulling the little bit of gray out of my head.
[Fire TV Original Android Development] ldeveraux:
Once I got my Due, I was fairly confident in the script flashing, and I had the leads connected properly to the HDMI adapter. So I never killed power to the Arduino. I just kept unplugging the microUSB from the Fire until I saw AMLogic in the lsusb. From there it went fairly smoothly. Although at one point I needed to enter the flash commands manually.
[Fire TV Original Android Development] BRICK0044:
Thanks for your response.

Does your rules file look exactly like this?

SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", ATTR{idVendor}=="1b8e", ATTR{idProduct}=="c003", MODE:="0666"

SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", ATTR{idVendor}=="18d1", ATTR{idProduct}=="0d02", MODE:="0666"
[Fire TV Original Android Development] ldeveraux:
If that's what the wiki says, then that's what my rules file says. It should have been created automatically assuming you ran the scripts correctly.
[Fire TV Original Android Development] retyre:
Are you using Ubuntu 16.04 (if not, the rules syntax may be different)? Do you have the Due? In post #34, you indicated you were able to run the exploit (at least, initially). Did lsusb list Amlogic at that point? In general, the Amlogic device should be detected if the sketch was uploaded successfully and the jumper wires are connected as described. The udev rules are for permission rather than detection.

It will help if you indicate clearly (in one post) your hardware/software setup, connections, shell commands, and output.
[Fire TV Original Android Development] xXhighpowerXx:
The device should still enumerate even if you didn't create the udev rules, the rules are just for setting the permission. You can just skip the udev rule step if you just run the script as root. :o

I never try with a Arduino Uno so I don't know if it work or not. If you have a logic analyzer or oscilloscope you can check the bus and see what went wrong.
[Fire TV Original Android Development] BRICK0044:
Thank you for the help, now I can narrow it down to the jumpers or flash to Arduino. I have this: https://www.amazon.com/gp/product/B00A6C3JN2/ref=oh_aui_detailpage_o03_s00?ie=UTF8&psc=1 and this: https://www.amazon.com/gp/product/B071X4GX2B/ref=oh_aui_detailpage_o03_s00?ie=UTF8&psc=1

I did have Amlogic once but can't get it anymore. Now I get Lab126, Inc. I'm using Ubuntu 16.04 LTS

My connections are:

HDMI	Arduino

PIN 15 (SCL)	I2C SCL

PIN 16 (SDA)	I2C SDA

PIN 17 (GND)	I2C GND
[Fire TV Original Android Development] retyre:
-- Power down the Due and the AFTV3.

-- Unplug all the connections completely and start again.

-- Are you using M/M jumper wire? If yes, unscrew pins 15, 16, and 17 all the way out on the breakout, insert one end of the jumper wire into each (make sure the connector end sits snugly in between), and tighten the screw all the way in. Try to gently move the connector around and check it stays put.

-- With the HDMI breakout connected to the Due as described, plug the Due into the Windows or Linux box.

-- Upload the sketch (choose the correct board and port) and watch the bottom for progress. Confirm it's successfully verified. (For Linux, run the IDE as root.)

-- Reboot to the Linux side if not already there.

-- Insert the Due's USB cable into the Linux box's USB port (if you unplugged it after the sketch upload).

-- Connect the AFTV3's HDMI to the breakout.

-- Connect the micro USB end of the AFTV3's cable into the AFTV3.

-- Connect the other end of the micro USB cable into a port on your Linux box.

-- Run lsusb and see whether Amlogic appears.

-- If the udev rules are as you wrote earlier, you don't need to run ./install_exploit.sh needle as root. Otherwise, you should. (You should have rebooted the Linux box once after creating the rules.)
[Fire TV Original Android Development] BRICK0044:
When I run lsusb without putting anything in udev rules it shows up as Bus 001 Device 008: ID 2341:003e Arduino SA. Is that normal? I'm not going to give up. Will keep trying all day.

---------- Post added at 07:41 AM ---------- Previous post was at 07:38 AM ----------

Ok will start over again and let you know.
[Fire TV Original Android Development] BRICK0044:
A friend brought his Arduino over and it worked fine with every step. So I'm returning the one I have and getting this: https://www.amazon.com/SAM3X8E-32-bit-Cortex-M3-Arduino-Compatable/dp/B077GNMQ17 then try again because I have 2 more pendants to do.
[Fire TV Original Android Development] xXhighpowerXx:
I used a teensy 3.1 / 3.2 it work quite well. I think it cheaper than the due?
[Fire TV Original Android Development] BRICK0044:
Thank you will check it out.
[Fire TV Original Android Development] bspunker:
Hi!

I tested on Mega (clone), 2 unos (clone), Esp8266 NodeMcu...

Logic Analyzer shows nothing on SDA and SCL , why?

Is the sketch wrong ?

EDIT: I think i have found the solution...make a mistake and try to test only on arduino XD.

Now i have a signal but lsusb is wrong.

greetz bspunker
[Fire TV Original Android Development] xXhighpowerXx:
I never try it with Arduino Mega/Uno before but can you try adding 2 pull up resistor (1 - 2Kohm) on SDL and SDA to 5V? Maybe it will help ?
[Fire TV Original Android Development] bspunker:
Okay i will try it in the evening!

Thanks.
[Fire TV Original Android Development] thomasorr:
Hi all,

Firstly amazing work finding this exploit, I've been stuck on unrooted Fire TV 2's for too long now so it would be great to have a rooted Fire TV 3.

However I am having problems getting the pendant into DFU mode, my setup is as follows:

Ubuntu 18.04

Arduino Mega ADK (Pin 20 and 21)

The following HDMI breakout - amazon.co.uk/dp/B07FYGPFR5/ref=cm_sw_r_cp_apa_yLt7BbGZWN4GY

A female to female HDMI adapter

The latest version of Arduino IDE

No matter what I do the device that shows up in lsusb is Lab126. I've added in some serial printing to the Arduino sketch and can see the receive and request command happening. I have also tried adding a 1k resistor to 5V on each of the SCL and SDA pins and also tried a 4k7. I've left the Arduino powered and unplugged/plugged the FTV in multiple times to no avail. Any help will be greatly appreciated! I'm going to see if I can borrow a Arduino DUE of someone if for some reason that's the problem although don't see why it is since the I2C communication is the same.
[Fire TV Original Android Development] ldeveraux:
Not sure if anyone has gotten this to work on anything other than an Arduino branded board. Certainly didn't work for me. I'm not sure all commands translate to the latest Ubuntu, so would suggest using 16.04 like it says in the OP. And you never mentioned it, but you have a ground connection between breakout and board, yes?
[Fire TV Original Android Development] thomasorr:
Yes I'm grounding the breakout to the Arduino. I don't see why the Ubuntu version would make a difference for the DFU stage though, maybe it would for the Linux script stage but I can't get to that bit :crying:
[Fire TV Original Android Development] bspunker:
Any here with Arduino Due can use a logic analyzer or oszilloscope and show the signal?

i think on the other board is something wrong.

Tested with 2 Unos , 1 Mega and 4 esp 8266 node mcu and no DFU.

greetz bspunker
[Fire TV Original Android Development] thomasorr:
Ok so I've now borrowed a DUE and it worked first time so I can confirm this does not work with the Mega.
[Fire TV Original Android Development] AZImmortal:
This is unfortunate (for me). I was hoping to be able to avoid buying a Due since I already have an Uno, but glad you got it working and for confirming what does or doesn't work for you.
[Fire TV Original Android Development] bspunker:
Can you grab the signal ?

or what voltage comes out on the Due 3,3 or 5v? i mean in the moment the fire tv goes into DFU?

Edit: i ordered a Due and test by my self! comes tomorrow and when i find the error i posted here!

this Due clone runs fine https://www.amazon.de/gp/product/B07B65JYWK/ref=oh_aui_detailpage_o00_s00?ie=UTF8&psc=1
[Fire TV Original Android Development] PeterLustig:
Got a due clone frome ebay today. Worked instantly!
[Fire TV Original Android Development] ldeveraux:
A "due clone" could be just about anything. Is it a MEGA, or something else?
[Fire TV Original Android Development] bspunker:
a Mega not runs... I have a Due clone too this one look at my last post. #56

22€ on amazon and runs fine!

I think we need on Mega and Uno a Bi-Directional Logic Level Converter but i not sure.

Can anyone testing this?
[Fire TV Original Android Development] PeterLustig:
It's this one.
[Fire TV Original Android Development] ldeveraux:
I successfully rooted my pendant last week and it's still going strong. I rooted my Cube last night and everything was OK until this AM. I came back and the front blue light was flashing and it can't complete the boot sequence. I disabled OTA, but I think it had downloaded the latest update and tried to install it through recovery and blew up. I'm going to try to reroot and try this again, but how can I reset to factory if I can't even get it to boot? Should I have installed the latest update before rooting? How woudl I go about retoring the backups I made during the root process, especially the recovery?

EDIT: Weirder, I went through the root process and once it rebooted it applied the downloaded update. So now it's on 6.2.5.5 and still rooted. But the system can check online for an update, so disabling didn't work for me. Every time I try to adb in, it will connect and then not show the Cube in the list of connected devices. Essentially I can't use adb for some reason...
[Fire TV Original Android Development] 2WhlWzrd:
Which version of 6.2.5.5? There has been another version rolled out, since this exploit was discovered.

See here.
[Fire TV Original Android Development] ldeveraux:
Oh hadn't even seen that. I have build 1628 in my Cube.
[Fire TV Original Android Development] Pix12:
Can this work on the Fire TV Stick 2 (Tank)?
[Fire TV Original Android Development] 2WhlWzrd:
The Fire TV Stick 2 has different firmware, I'm fairly certain that if this type of exploit would work on that device it would have already been revealed.
[Fire TV Original Android Development] AZImmortal:
Any confirmation if this update patched the exploit?
[Fire TV Original Android Development] enigma1400:
I got my Fire TV pendant Monday and can confirm it worked. I fully updated not realizing there was a revision of the latest FW. It took literally 10 hours for some reason but it worked.

Had a similar issue, adb was showing ?????????? and no permissions. Fixed it by running adb kill-server then adb start-server.
[Fire TV Original Android Development] ldeveraux:
I had the question marks too, but I was on Ubuntu and just thought it was another peripheral I had plugged in. I didn't think it was the cube.
[Fire TV Original Android Development] AZImmortal:
Thanks for confirming. If you only got it on Monday, then I'm not sure that there's anything that you could have done to avoid updating because part of the initial setup is checking for updates (unless there's some way around this that I'm not aware of?).
[Fire TV Original Android Development] enigma1400:
The updates were incremental. It did an initial update to 6.0.x or something like that and then I allowed it to perform the 6.2.5.5 update not realizing there were multiple revisions.
[Fire TV Original Android Development] xXhighpowerXx:
The exploit can be make to work on the manufacturing firmware. But I only test on 1 build version so if you want to try it, I recommend wire up UART port to debug if anything go wrong. After got the exploit working, we still need to find a way to bypass the initial update screen. I haven't look into that yet but it should be simple?
[Fire TV Original Android Development] AZImmortal:
I'm far from an expert on this subject, but does only the manufacturing firmware have the initial update check? If it does, then would it be possible to overwrite it with a pre-rooted ROM similar to the other rooted devices?

http://www.aftvnews.com/pre-rooted-...ilable-for-the-fire-tv-1-and-fire-tv-stick-1/
[Fire TV Original Android Development] Michajin:
ok i got it to connect once and rooted one of mine, I cant seem to get it to boot into DFU mode 99.99% of the time. I keep seeing it show up as Lab126. I keep rebooting the fire, then both, but nothing. I can not get it to connect and boot into DFU. What am i missing?been through every step like 4 times each. then tried other things... nothing. using a board model DUE r3.
[Fire TV Original Android Development] brick00444:
I'm having problems getting past the part where you unplug the hdmi and click continue. When I click it just says waiting for device. I check lsusb and it shows "18d1:0d02 Google Inc. Celkon A88" , That means it is in fastboot right? Not sure what to try next.

Itry the "fastboot devices" command and it says "no permissions fastboot". Almost seems like its stuck somewhere in between normal and fastboot. I'm nervous about bricking the cube if I unplug or shut down anything.
[Fire TV Original Android Development] xXhighpowerXx:
Look like you forgot to set the udev rule for fastboot. You can either setup udev rule for fastboot. Or run fastboot as root.

Your deive is already in fastboot mode. Now you just need to flash the modified recovery and boot.
[Fire TV Original Android Development] brick00444:
Thank you for the help. I thought if it showed 18d1:0d02 Google Inc. Celkon A88 in lsusb that I had the right rules in place, Linux is very new to me. For those having the same issue I used the commands "sudo fastboot flash boot patched_boot.img" and "sudo fastboot flash recovery patched_recovery.img" . Thanks again
[Fire TV Original Android Development] Michajin:
Oddly, it seems to work every time now. But oddly i had to do it from fastboot (fastboot reboot-bootloader) then the amlogic showed up...

---------- Post added at 11:08 AM ---------- Previous post was at 11:07 AM ----------

i haven't looked, but do you know where the back-up files are being saved. I don't know much about ubuntu...
[Fire TV Original Android Development] brick00444:
Mine were saved to the "dist" folder
[Fire TV Original Android Development] puppinoo:
Hi,

I've finally got a HDMI Breakout but the only Arduino I can use right now is a Arduino Mega. Since I've read of many who tried the procedure with it and failed can anyone confirm it can be used or I have definitely try to find a Due / Due clone?

Thanks.
[Fire TV Original Android Development] ldeveraux:
Again, this hasn't worked for anyone using a MEGA. Try it, I hope it does for you.
[Fire TV Original Android Development] brick00444:
For those that are getting Lab126 instead of Amlogic, I was only able to get Amlogic a couple times and had to manually flash the patched boot and recovery. I tried several different power supplies for the Arduino, usb from the pc and several different wall jacks. I finally tried my Samsung wall charger and now I get Amlogic everytime and it also flashes everything like it was supposed to. Try different usb wall chargers until you find one that works. Hope this helps someone.
[Fire TV Original Android Development] Michajin:
Now you say this, i did change power supply ports on the Arduino and change from usb to the iso power. Seem like i had better luck with the native port not the programming also. You know if anyone looking into making a recovery?