yashsingh1/xdaforums huggingface dataset:
[Fire TV Original Android Development] Michajin:
So you can flash from fastboot? Sorry, im not sending my userdata (no offense).

Yes, i posted the Cube/Stark image.

A few posts before that, retyre converted my full .bin download into a system image for needle/ pendant at post 24. If you have fastboot flash access, you can boot into twrp. i would have made a backup as soon as i had a working twrp recovery.
[Fire TV Original Android Development] vasir13:
I know, I am pulling it from a different unit .. that was just for sarc.

yes, it was late and I skipped a step.

:)
[Fire TV Original Android Development] Michajin:
That is where I am at, mine updated from 6.2.5.5 to 6.2.5.8 and bricked. The expoit only worked for me on 6.2.5.5. everything I have had been updated to 6.2.6.0 including the downloads in the twrp thread. I think everything had to match up to boot. But I'm guessing...
[Fire TV Original Android Development] fpena06:
Hello everyone and thank you for such an amazing site. With the help of the forum I have been able to root Fire TV Stick 2nd gen (tank). However I'm having a hard time getting this one to work. I have bricked two devices which both stay in waiting for device after fastboot. Any help getting these devices back and running would be appreciate it. When I connect the firetv's to the television I get no image whatsoever. Thanks in advance
[Fire TV Original Android Development] Michajin:
Restore the reserved.bin backups it made while running the script. The script doesn't work on 6.2.5.8 and newer.
[Fire TV Original Android Development] fpena06:
Thanks for your quick reply. But how if I can't get the device in fastboot?

Thanks

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

I was able to get one up and running thanks.

./aml_usb_mmc -p 0 -w -s 0x12000 -c 6 -f backup-needle-20190505-175521/backup_reserved.bin
[Fire TV Original Android Development] Michajin:
yes, through DFU mode. I had to restore 2 of mine doing that.
[Fire TV Original Android Development] fpena06:
I have a 6.2.6.0 and 6.2.1.2. Will it work on either?
[Fire TV Original Android Development] Michajin:
no, this script wont work on neither... If you could upgrade the 6.2.1.2 to 6.2.5.5, but when you update it will go right to 6.2.6.0.
[Fire TV Original Android Development] fpena06:
So I have a firetv3 that currently stays stuck on the firetv boot logo, never tried rooting it. I connected UART to see logs and it stalls on

bootconsole [earlycon0] disabled

. I can backup using firefu method. I was wondering if there's a way to bring this one back? Thanks
[Fire TV Original Android Development] vasir13:
That means that you have updated to a version that is already patched. The console I/O gets disabled to prevent people to see the message and/or to "roam" around.

Did you backup your boot files prior and know what version they were?

If you are already at 6.2.6 then you are toast for now. They have done a few things to make the hack more difficult and patched the exploit.

If you have your original resrved partition then you can write it back and get it going.

I have been told by the guys here that the stick 4k is a better deal to focus all your brain power to.
[Fire TV Original Android Development] fpena06:
Unfortunately I'm not sure what version this one is on. I don't have the original reversed but do have from other sticks. This one belonged to a friend who gave it to me. I don't think it was rooted.
[Fire TV Original Android Development] vasir13:
If you have the backup files then you can revert back to working state assuming that it worked before you tried to patch it. 6.2.1.2 is the gateway now to 6.2.6 and is already patched.
[Fire TV Original Android Development] fpena06:
When trying to restore I get the following error.

sudo ./aml_usb_mmc -p 0 -w -s 0x12000 -c 6 -f backup-needle-20190519-114404/backup_reserved.bin
[sudo] password for fpena06:
Chipid: 7e8ed0e0259feed94ad93362
EMMC init:
aml_priv->desc_buf = 0x0x5574ecf6e9a0
aml_priv->desc_buf = 0x0x5574ecf709b0
emmc/sd response timeout, cmd8, status=0x1ff2800
emmc/sd response timeout, cmd55, status=0x1ff2800
[mmc_init] mmc init success
SDIO Port B: 0,
SDIO Port C: 1
Switching HW partition to: 0
Device: SDIO Port C
Manufacturer ID: 11
OEM: 100
Name: 008G3
Tran Speed: 52000000
Rd Block Len: 512
MMC version 4.0
High Capacity: Yes
Capacity: 7818182656 B
mmc clock: 12000000
Bus Width: 8-bit
emmc/sd write error, cmd24, status=0x1ff2100
mmc write failed

ERROR: write block fail
[Fire TV Original Android Development] vasir13:
Seems you are in DFU, I would write the whole file. Also, If you are using OTG cable, are you supplying the unit with enough power? or are you directly connecting to your PC? seems that you have cabling/power issues.

What is the usb device ID before you start the write?
[Fire TV Original Android Development] fpena06:
The firetv is directly connected to the PC and the usb device ID is

Bus 002 Device 004: ID 1b8e:c003 Amlogic, Inc.

I thought I was already writing the whole file. Do you mind pointing out how to? thanks
[Fire TV Original Android Development] vasir13:
n

Ok, device is in DFU based on the id.

what it needs to be:

aml_usb_mmc -p 0 -w -s 0x12000 -c 0x4000 -f ./reserved.bin

what you had:

/aml_usb_mmc -p 0 -w -s 0x12000 -c 6 -f
[Fire TV Original Android Development] fpena06:
Unfortunately I still get the mmc write failed error.

---------- Post added at 02:12 AM ---------- Previous post was at 02:10 AM ----------

Is there a way to recover via fastboot?
[Fire TV Original Android Development] vasir13:
If it is locked, then no.

If you are getting write errors, as a few suggested before then you have either damaged your mmc during the rs232 cable installation OR your current supply is low.

You can just get a refurb from ebay for $17 and then backthem up BEFORE you register to amazon. Make sure that you name the backup something meaningful and -w the whole directory in case you had to many drinks for that evening.

Why I suggest it? I have a google directories with different backups like spaghetti and have no idea what is what.

Hope this helps.
[Fire TV Original Android Development] ldeveraux:
I think I'm on 6.2.5.X and the yellow/orange light on the front keeps moving back and forth. I have wired network and a FLIRC hooked into a USB hub. Even if I unplug the hub and go WIFI, the light still goes. This seemingly started a week ago randomly. I feel like it's telling me there's a new update, even though it errors out when checking in Settings. Is there a way to update the Fire Cube software once rooted through DFU?
[Fire TV Original Android Development] Michajin:
I updated mine to 6.2.6.0 by writing in TWRP open recvoery. See post #25 here

https://xdaforums.com/fire-tv/general/fire-tv-3-needle-twrp-t3903578/page3

I have the system img here post #35

https://xdaforums.com/fire-tv/general/fire-tv-3-needle-twrp-t3903578/page4

Use at you own risk, and dont forget to disable updates as soon as you boot up. i dont think this has anything to do with the lights though...
[Fire TV Original Android Development] ldeveraux:
Awesome, I'll check it out. I see the cube also has 6.2.6.4 released, could I use the img from that to update to the latest? Can you even get the images for the cube to extract it? Now that AFTVnews is gone it's tough to keep up with the latest...
[Fire TV Original Android Development] Michajin:
You can, but you have to enable updates download then disable the updates. Extract the bin from the update folder and extract the system.img. i have a cube that i barely use and take the risk if you want, but it might not be until sunday.... There is some moderate risk involved.
[Fire TV Original Android Development] ldeveraux:
Yeah I don't feel like being the guinea pig! The second tester, I can handle :o What about the yellow light across the front of the cube, any clue? I thought network issues, but it's very connected to the network. It doesn't seem to do it with the official Amazon network adapter, though can't figure out how to use that with OTG.
[Fire TV Original Android Development] Michajin:
No idea about the yellow light, doesnt that have something to do with Alexa? I am pretty sure i am using a OTG on mine without issues. Let me get mine back online this weekend, enable updates and capture the update. Once i get that i will update and test update as previous updates worked. Then i will look at my lights and see what mine does with the lights. I got mine for cheap and moved on to the supported rooted fire devices. So few people did this root, no one supports it and im a novice at best...
[Fire TV Original Android Development] ldeveraux:
Curious to see what you get, as updating didn't stop the light. Can I disable Alexa somehow? That might do it.

How to disable updates? I entered these 2 in elevated shell:

pm disable com.amazon.dcp

pm disable com.amazon.device.software.ota
[Fire TV Original Android Development] Michajin:
i will have to look back. I use a app called package disabler for android to disable apps and keep track. without always doign the a shell and keeping it standalone. im not sire about the pm disable com.amazon.dcp, i dont recall that. I know i disable anything that has OTA in it from the package disabler. i think you can turn off alexa from settings.
[Fire TV Original Android Development] Michajin:
Curious, where did you see 6.2.6.4 rolled out?

https://www.amazon.com/gp/help/customer/display.html?nodeId=201497590
[Fire TV Original Android Development] ldeveraux:
I remember I saw a more Amazony list, but this: https://www.amazon.com/gp/help/customer/display.html?nodeId=201452680
[Fire TV Original Android Development] Michajin:
Well it was 6.2.6.5. I downloaded it and tried to installed the system image (from 6.2.6.0) and it bricked. Sorry, im bootlooping with unauthorized adb access...
[Fire TV Original Android Development] retyre:
Was it a full system image or a diff? Can you upload the file?

Are you not able to boot to TWRP to write back a backup system image?
[Fire TV Original Android Development] Michajin:
I don't know of a way to get into TWRP from boot. i extracted the system from the upgrade and installed. there may be options from the exploit, but i don't know how to get into recovery after boot.

Here is the system img i used...

https://drive.google.com/open?id=19SO3aRsuKDTdGt5oXwOiN1uh-spxeYUy

Here is the full update...

https://drive.google.com/open?id=1-WWMpdS15E-H6TIziGc01SKjxrfF0gVa

I dont really use my cube, but was trying to help others... If you have any thoughts on how to boot into TWRP from boot it would be great...

Thanks!
[Fire TV Original Android Development] retyre:
I am assuming you wrote the system.img in TWRP and did not update from inside FireOS. With the device in DFU mode:

sudo ./aml_reboot fastboot
sudo fastboot boot /path/to/twrp.img

Restore your backup and reboot.
[Fire TV Original Android Development] Michajin:
correct. i used dd from terminal. i will pull out the aduro tomorrow and dig into it more.. I think i had a back up! lol
[Fire TV Original Android Development] ldeveraux:
When I updated to 6.2.6.0, I copied the img to /sdcard and transferred in TWRP terminal. Would that make a difference?
[Fire TV Original Android Development] Michajin:
ok im into TWRP, i have a backup available. But somehow i can not get a mouse to work or keyboard to work. I connect a computer and it shows up as a media device. I have tried OTG's, hubs seems like i am forgetting something. It has been a while
[Fire TV Original Android Development] ldeveraux:
No clue why it wouldn't work. I have a crummy logitech wireless mouse/keyboard combo and the dongle was instantly detected. That's weird. You may have to restore via the DFU route?
[Fire TV Original Android Development] Michajin:
No idea, i gave up. the cube is going back in the drawer.... I can't even get into fastboot now... live and learn! i hated the thing anyways, big and slow.... I like the fireTV1 better.... lol
[Fire TV Original Android Development] ldeveraux:
I like a Roku better...
[Fire TV Original Android Development] Michajin:
nice, but i still love freedom unlocking...
[Fire TV Original Android Development] Sus_i:
There is no mouse emulator in this TWRP that works over USB/ADB, like it does for the old fire stick? Just wondering... don't own this FTV, I dislike the design ;)
[Fire TV Original Android Development] thomasorr:
Hi,

I have 4 fire tv 3's (pendants) which have all been rooted on 6.2.5.5 build 1268, i am keen to update to the latest version keeping root. I have seen your posts detailing it can be done using TWRP and enabling updates and capturing the diff update file, successfully updating to 6.2.6.0. However I have seen you have bricked going to the newer version. If i try the method now I assume I will get the 6.2.6.4 update rather than the 6.2.6.0, is it likely that this update will brick my units?
[Fire TV Original Android Development] Michajin:
6.2.6.5 was what i downloaded. It is very possible that i screwed up the system image extracting it. It is hard to say, i posted the files here in hopes that it was my error and not some update poison pill.
[Fire TV Original Android Development] ldeveraux:
If you really have the desire to update, then do so to 6.2.6.0 as Michajin and I have done:

https://xdaforums.com/showpost.php?p=80077109&postcount=251
[Fire TV Original Android Development] thomasorr:
That's the problem, if i try enable updates and pull the update file it will probably be the latest update and not 6.2.6.0. If I use the update file posted in that link would that brick my unit if it's not updating from the exact same version? What version was that updated from?
[Fire TV Original Android Development] ldeveraux:
It doesn't matter what version you start on, as long as it's <= 6.2.6.0, and is rooted with TWRP installed. You don't have to bother with pulling the OTA update, that work has already been done in that post.
[Fire TV Original Android Development] thomasorr:
I thought the updates were incremental diffs as stated in Michajin's post so the version you're on mattered but if that's not the case I will update using his attached img file.
[Fire TV Original Android Development] ldeveraux:
I believe they are inclusive, but if you're concerned, you should wait for someone much smarter than me to confirm before flashing.:)
[Fire TV Original Android Development] thomasorr:
Did you use Michajin's file to update and if so what version did you update from?
[Fire TV Original Android Development] ldeveraux:
I definitely used the file in that post I linked earlier. The difference was in flashing. I pushed via adb the file to the cube's /sdcard/ then booted to TWRP and copied the file over in terminal. I think the previous user may have used the DFU method which is hackier when I already had TWRP installed. I don't know what I updated from, I want to say 6.2.5.5 but I'm can say positively. Maybe [MENTION=4914529]Michajin[/MENTION] or [MENTION=3497316]retyre[/MENTION] could tell if you need to update incrementally.
[Fire TV Original Android Development] thomasorr:
Thanks for your reply, unfortunately mine are pendant's not cube's so I assume there would be slight subtleties in the update file and wouldn't want to risk it, so would need to do the full re-enable updates and pull from cache then extract image.
[Fire TV Original Android Development] ldeveraux:
Don't know how you made that assumption, maybe someone already has done the legwork for you.
[Fire TV Original Android Development] thomasorr:
I haven't seen anyone in these posts that has updated the pendant, only the cube. Hopefully someone will say otherwise and has done the legwork like you say.
[Fire TV Original Android Development] Michajin:
For pendant 6.2.6.0 use this

https://xdaforums.com/fire-tv/general/fire-tv-3-needle-twrp-t3903578/page3

I upgraded all mine to 6.2.6.0 on both the cube and pendants. I bricked trying to update to 6.2.6.5 on the cube. I copied to /sdcard and ran the file from terminal in TWRP (read post #25 above). If you download the update, it will be 6.2.6.5 and unless i pulled the system image wrong (it is possible i screwed that up) you could brick. I wouldnt touch the updates until someone who is an expert and look at it and tell me where i screwed up.
[Fire TV Original Android Development] thomasorr:
Thanks for confirming you updated a pendant as well. I will give it a go with your file!
[Fire TV Original Android Development] Michajin:
[MENTION=3497316]retyre[/MENTION] did the pendant 6.2.6.0 system pull and i used the file. I did the cube 6.2.6.0 and it worked also.
[Fire TV Original Android Development] retyre:
Don't give up that easily. Doesn't inspire confidence in the Wolverines' season.

You should be using a USB A-A cable with the OTG as follows:

-- OTG cable (male microUSB end) to FTV3

-- USB A-A cable to (USB A end of) OTG cable

-- FTV3's HDMI end to (HDMI on) the breakout board (jumper-cabled to the Arduino)

-- Power to the Arduino

-- (Other end of) USB A-A cable to computer's USB port

-- Confirm with lsusb that Amlogic, Inc. is present

-- Disconnect FTV3's HDMI from the breakout board

-- sudo ./aml_reboot fastboot from a terminal

-- fastboot devices to confirm FTV3 is present

-- Connect USB charging cable to (female microUSB end of) the OTG cable and other end to wall outlet

-- fastboot boot twrp.img to boot into TWRP; as soon as this completes in the terminal, disconnect FTV3's end of the USB A-A cable from the OTG and plug in the USB receiver for keyboard/mouse

-- Restore the TWRP backup from internal storage

-- Wait for it to complete and restart

You can also use a hub (USB2) if your TWRP backup is not on internal storage:

-- Insert USB stick into hub

-- Go to Mount in TWRP and mount USB-OTG and Select Storage

-- Restore the TWRP backup from USB-OTG and restart
[Fire TV Original Android Development] Michajin:
I tried all this. No matter what OTG i plugged in the mouse or keyboard would not work. From fastboot i decided to do a wipe (erase data erase cache) and i also did a -w. All in all, i made bad choices.... Now, it no longer boots into the white amazon screen and i no longer have fastboot access from aml_reboot fastboot. I can however still get into the bootrom and run aml commands. I should have held off and thought about the wipe more, but i got frustrated and had too much to drink. It happens, but i still have the pendants to play with...

Go Blue...
[Fire TV Original Android Development] ldeveraux:
It amazes me that you can direct me to upgrade software in TWRP, then completely destroy yours a few days later! Your madness is greatly appreciated!:silly:
[Fire TV Original Android Development] Klava_Z:
Any help....
[Fire TV Original Android Development] yosdmie:
I'd be interested in a picture and any info, have a pendant at 6.2.1.2. Thank You again for sharing im scared it will update when I go to put an account on it.
[Fire TV Original Android Development] ldeveraux:
I have my cube still rooted with 6.2.6.0. With AFTVnews gone, I don't know what the latest software version available for the cube is, but I'd like to upgrade. I STILL have that stupid yellow light across the front of my cube and it's annoying as hell. I can't figure out how to get rid of it, I have no notifications, etc. Maybe a software update would fix it?
[Fire TV Original Android Development] Sus_i:
Fire OS 7.2.0.6 (17683470212) is the latest for the cube

Edit: Seems there are two generations of the cube. 7.2.0.6 is the latest OS for the second gen cube... The first gen is probably Fire OS 6.2.7.1.
[Fire TV Original Android Development] ldeveraux:
I'm in the US and I have a Cube version 1. This page says differently:

https://www.amazon.com/gp/help/customer/display.html?nodeId=201497590

Regardless, where can I download a different version to update via TWRP?
[Fire TV Original Android Development] Sus_i:
You should be able to capture an URL to the latest update bin, in case you enable the OTA updater and run: adb logcat > logcat.txt

As soon the URL is printed in the log, disable the OTA updater and run: pm clear com.amazon.device.software.ota

in order to delete all downloaded stuff...

During that, keep the FireTV busy, play a prime video, to prevent a reboot.
[Fire TV Original Android Development] ldeveraux:
OK so I got a ~733MB bin file that I think is 6.2.6.8. I disabled the OTA and cleared the download so I hope it won't update on reboot? How would I apply this bin file as an update? I would normally flash a system.img in TWRP, but that file doesn't exist in the bin. There's a system.new.dat that's over 1GB in size, but don't quite know what to do.:confused:
[Fire TV Original Android Development] Michajin:
I will warn you, extracting the system.img and flashing it is what bricked mine. It worked on some of the updates, been then i crashed and burned.. See post #30 here for links to tools...

https://xdaforums.com/fire-tv/general/fire-tv-3-needle-twrp-t3903578/post79288482#post79288482

---------- Post added at 01:44 PM ---------- Previous post was at 01:41 PM ----------

on amazon fire tablets, you just rename the bin to zip and you can flash them... But i will warn you that i think it could be a poison pill!
[Fire TV Original Android Development] ldeveraux:
But in that thread it looks like you converted the dat to img and it worked for you? Which image version DIDN'T work then? I don't really see the benefits of keeping root here, so even if I have to take the OTA and sacrifice root, I'd rather get rid of that silly blinking light than have root!
[Fire TV Original Android Development] Michajin:
i upgraded successfully to 6260, i believe 6261 bricked me. Flashing the bin (as a zip) will flash, it will likely kill root and TWRP (i believe). I just dont know if flashing it from TWRP will cause a brick. You might have to go back and restore the old reserved, recovery and boot. I am considering trying this on my pendants cause they are all stuck on 6260.
[Fire TV Original Android Development] Sus_i:
I don't know how to create a safe update for this device.

Flashing the renamed file and magisk.zip behind won't work??? :confused:

As [MENTION=4914529]Michajin[/MENTION] said, flashing only system.new won't work, the kernel needs an update too.

There are some tools on xda, which extract/repack OTA files fine.

Maybe take a look in the old update file, and compare the stuff inside with the new file.

Maybe some img files inside needs to be removed? Take a look into the old/new update script...
[Fire TV Original Android Development] ldeveraux:
This is all getting more complicated than I wanted on a Saturday afternoon! Maybe I'll just drop it until someone gets this sorted. I don't want to brick the cube, but don't really use it much (Roku ftw) so once someone gets a proper image, I'll give it a go.
[Fire TV Original Android Development] Michajin:
i dont think anyone is working on these and rooting them was short lived, i would say only a handful of people have these rooted (even less for the cube). If i get bored tomorrow or later i will pull a pendant out and try flashing the full bin (as a zip) in TWRP. I already sacrificed one cube and one pendant, i'll test it. I moved on to the stick 4k. I am sure there is a way, but i think XDA dev support is dead for these devices... :(
[Fire TV Original Android Development] Michajin:
Well it is confirmed... You can rename it and flash it, but because of the hack in the reserve/boot/recovery partitions- it bricks it. You will need to restore the exploited partitions in this hack to upgrade. I dont think anyone is looking into modifying a custom version of this. Sorry, tried to help... another pendant for the trash! But what do i know, im just a hack! lol, good luck!

[MENTION=5213625]Sus_i[/MENTION]
[Fire TV Original Android Development] ldeveraux:
Ugh, of course. I wonder what happens if you convert the dat to img and flash that in TWRP? Meh.
[Fire TV Original Android Development] Michajin:
That is how i bricked my Cube... Maybe i should give me the alias as "The FIRETV Bricker"