yashsingh1/xdaforums huggingface dataset:
[Fire TV Android Development] vladm7:
I have FireTV1 and was running latest-1 fireOS with kingroot. Decided to install pre-rooted image, and followed the guide to downgrade to 51.x version so that I can unlock bootloader (this). Downgrade went fine, but alas, FireTV doesn't boot. Just stays black.

Trying to revive it, following the guide above, but when I connect it to a linux box, instead of disk, it shows up as a modem. Any ideas?

Jul 8 13:46:54 nas kernel: usb 2-2: new high-speed USB device number 11 using ehci-pci
Jul 8 13:46:54 nas kernel: usb 2-2: New USB device found, idVendor=05c6, idProduct=9008
Jul 8 13:46:54 nas kernel: usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Jul 8 13:46:54 nas kernel: usb 2-2: Product: QHSUSB_DLOAD
Jul 8 13:46:54 nas kernel: usb 2-2: Manufacturer: Qualcomm CDMA Technologies MSM
Jul 8 13:46:54 nas kernel: qcserial 2-2:1.0: Qualcomm USB modem converter detected
Jul 8 13:46:54 nas kernel: usb 2-2: Qualcomm USB modem converter now attached to ttyUSB0
[Fire TV Android Development] xenyz:
It looks like the zip file is corrupt. I tried downloading it twice with the same results.

Edit: looks like a mediafire issue, I'll wait a bit and try again...
[Fire TV Android Development] rbox:
You bricked it. This post links to the page for installing recovery, which gives very explicit instructions for what to do if you are rooted with OS5.
[Fire TV Android Development] vladm7:
sorry, I dont get it - which post links?

I followed the guide, installed earlier version of recovery, tried to downgrade and it's bricked now. Connecting to a linux via USB - kernel doesn't see it as a disk, but some modem.
[Fire TV Android Development] rbox:
The first post in this thread:

The recovery is a link to here: http://xdaforums.com/fire-tv/development/firetv-1-bueller-twrp-recovery-t3383286

The first sentence says:

And then it proceeds to explain the process of what to do if you have a locked bootloader.

Unfortunately because you didn't follow the directions, it's bricked.
[Fire TV Android Development] vladm7:
ok, thaks for the reply. I didn't even got that far as instructions on the first page. I posted here becaused I saw your recommendation that it can be reflashed from linux as a disk.

I followed aftvnews guide to downgrade, which says nothing about "dont do that if you are on one of the recent versions (unless I missed it)

So she goes to a garbage can? Can't solder anything to the board and reflash?
[Fire TV Android Development] rbox:
That page is from 2015. There is no page anyway related to installing TWRP or prerooted OS5 that says you should be doing anything like that if you are already on OS5.

I think in theory you could rewrite the partition you flashed with the emmc hack.
[Fire TV Android Development] CtJackHarkness:
[MENTION=3991724]rbox[/MENTION] - what happened to the com.amazon.dcp package for updates?

Did you remove it from your pre-rooted ROMs? I can't disable it or even find it using adb shell pm list packages -d / -e and that shows its not even there.

On the latest one fyi
[Fire TV Android Development] rbox:
They changed the package for doing updates on OS5. There is a guide on aftvnews on how to block it.
[Fire TV Android Development] CtJackHarkness:
Done! Thank you rbox. Also - do you know whats wrong with TWRP -6 as opposed to the -7 image? I was having TWRP black cycling bootloops like crazy on -6.
[Fire TV Android Development] rbox:
Yes. It was a bug in TWRP. That's what was fixed in 7.
[Fire TV Android Development] CtJackHarkness:
1 Last thing - does wiping cache/dalvik cache wipe this setting? Because when I wiped and started my AFTV - it said "Installing System Software". I pulled the plug out of fear :D

guessing it re-enabled OTA?

Also where can we donate to u? - dur just saw the big yellow button. thank u :)!
[Fire TV Android Development] rbox:
Only a factory reset will clear the ota block. The "installing system software" happens precisely when you wipe cache. that's the screen that shows when android is rebuilding the cache.
[Fire TV Android Development] andy_mg2000:
Ok, so I may have bricked my FTV1. Here's what I did:

I was on 5.0.5.1_r1 pre-rooted with unlocked bootloader.

Flashed 5.2.1.0_r1 pre-rooted via TWRP.

Forgot to disable the Amazon update service and left it for around 10 mins connected to the internet. I am blocking 'amzdigitaldownloads.edgesuite.ne', 'softwareupdates.amazon.com' and 'updates.amazon.com' on my router though so wouldn't have expected it to be able to download an update, unless update domains have changed on the new OS...

After realising I'd not disabled the update service I ran 'pm disable com.amazon.dcp' via ADB shell. This failed as I now realise the service isn't present anymore on this version. Wouldn't have expected this to cause any issues.

Also ran 'pm disable com.amazon.device.software.ota' which worked fine and disabled the service.

Restarted via 'adb reboot'.

Now I have no light on the box, no HDMI output and unable to access via fastboot with USB A-A cable.

Do I have any chance of recovering this? I originally flashed 'su' a long while back via the e-mmc hardware mod so I'm capable of soldering that up again if that helps in correcting whatever may have gone wrong. Also have a linux machine as I've read some bits about possible fixes by mounting the filesystem. Not looking good eh?

Edit: On USB A-A it is mounting as a drive with the following displaying: IMAGE
[Fire TV Android Development] rbox:
You need to dd all the firmware from the 5.2.1.0 stock amazon package. In this thread or the TWRP thread, I explained all the stuff that needed to be dd'ed.
[Fire TV Android Development] cd2022:
My impression is that once you flashed rbox pre-rooted ROM you're blocked from OTA update by TWRP, beside you had the 5.2.1.0_r1 and that's Amazon latest atm so your box can't pull any update .
[Fire TV Android Development] andy_mg2000:
Thank you very much. Found the steps you had posted so will give that a go after work.
[Fire TV Android Development] andy_mg2000:
I have no idea what happened then. It booted fine after flashing 5.2.1.0_r1 initially. It was only after the restart it died. Will attempt rbox's fix and hopefully that will revive it, even if it does mean the loss of the unlocked bootloader.
[Fire TV Android Development] andy_mg2000:
Ok so I tried this. Double checked all files and partitions when I ran the dd commands. All seemed to go ok. However on reboot it goes to the white Amazon logo, it disappears after about 15 seconds, reappears and stays there indefinitely. At one part through the boot (early in the second appearance of the logo) 'sdd' appears on linux mounts for around 20 seconds, then disappears. None of the other mount points are listed. Obviously no fastboot due to the locked boot loader so can't really attempt much. Listing devices using ADB over USB A-A also works for a short while, but attempted a shell launch and it fails. Either way, the ADB device disappears shortly after anyway.

I'm guessing this is now ready for the bin or is there anything else I can attempt? Thanks for your help anyway, it was worth a try.
[Fire TV Android Development] ldeveraux:
did you eject after dd? That's what did it for me !
[Fire TV Android Development] cd2022:
Did you run "sync" 3 times at the end.
[Fire TV Android Development] andy_mg2000:
No. I did eject though as per the instructions and didn't do it immediately after issuing the last dd command. Perhaps that caused it to fail.

Any chance I can get this working by wiring up the emmc adapter again? Can you access the partitions to run the dd's again with that? If I can access the partitions this way, would the mount points match the same numbering as when I accessed previously over usb a-a?
[Fire TV Android Development] rbox:
Yes, if you access the emmc directly, you'll see exactly the same thing you saw with the usb.
[Fire TV Android Development] andy_mg2000:
So I just wired up the emmc adapter and executed all dd commands again, followed by a sync. All appeared to go fine. However no change on boot up, still cycles once on the white amazon logo, then stays on it.

Could there be a problem with TWRP which is causing this? I'm getting to the point where if its the only option, I'd reinstall stock recovery, use it to flash stock software and give up on root. Is this even possible via emmc? Any other suggestions?

Thanks,

Andy
[Fire TV Android Development] rbox:
What did you flash? You could also try flashing the boot and system. To flash system you'll have to use sdat2img.py on the system image from the update. You'll have to use a full stock update and not an incremental.
[Fire TV Android Development] andy_mg2000:
I flashed partitions 3-10 as per this link. The boot.img was included.

Is the image on AFTV news here (51.1.6.3_user_516012020) a full image or incremental? If it isn't the full image, where can I get this? Also which file is the system image as I can't see an obvious dat for this in the AFTV news software extract (perhaps because it is an incremental)?
[Fire TV Android Development] rbox:
That's an ancient version... It looks like the zip linked in the post is good enough. So you an get the dat from there.
[Fire TV Android Development] andy_mg2000:
Ok. Sorry, I hadn't realised how out of date those AFTV news images were and took that latest and was what I was flashing :eek: Probably explains my issues. I've found the full stock for 5.2.1.0 now so will dd that over to partitions 3-10 and I'm guessing that will solve the problems I'm having. Will provide an update once I've done it as need to solder the emmc adapter back up again...

Update: Well after all of the times I've wired up the emmc, it had to be this time the CLK pad came off. There is no hope for it now. So annoying since I'm pretty sure it would have worked. Never mind, these things happen. Thank you for your help anyway.
[Fire TV Android Development] ldeveraux:
Don't give up! Can't you solder the wire directly to the chip? Or whatever the clk pad connects to?
[Fire TV Android Development] andy_mg2000:
Apparently not. I read around about others having had the CLK pad lift off and there are no other connections/pads available on the board. The line from the lifted pad goes straight into the emmc, and this line runs within the second layer of the PCB. The emmc itself has no visible connections/pins to solder to, the connections are all underneath the chip. People have attempted to scrape the board to expose the line that runs to the lifted pad, but I have not seen any stories of success from anyone attempting this. I actually had a go myself last night having accepted it was the last possible option. All around the lifted pad there is a connection layer but this isn't the one for the CLK. There are no visible lines running to the pad, just one big area of copper surrounding it. I expect the actual line is somewhere below this. There is no way I can scrape beyond the top layer, actually find the line and then solder to it, whilst at the same time avoiding a connection to the top layer too. I've have quite sensibly given up. The box has served me well over the years and to be honest is a little surplus to my needs. I have another unlocked bootloader FTV in my main room which is where I am the majority of the time anyway.
[Fire TV Android Development] ldeveraux:
Haha, well not for lack of trying! You've certainly gotten further than I would have.
[Fire TV Android Development] Tech456:
Hi I've got the fire tv box (first Gen) when I plug it in it goes to " optimizing system storage and applications..." Screen and I can't get off it. It hasn't been rooted or been unlocked. Any help would be appreciated.
[Fire TV Android Development] zroice:
dafuq - my firetv 1 with prerooted stock image 5.0.5_r2 did update itself and remove all my customizations... thought this prerooted roms did have the update functionality removed?! garh
[Fire TV Android Development] Atlasstorm:
Nope, you have to do it yourself.
[Fire TV Android Development] sirxdroid:
Is there a (safe) way to manually install the new grid launcher without losing root? Does anyone have a zip that we could flash via TWRP? Or is there a new pre-rooted ROM in the works that will include it?
[Fire TV Android Development] rbox:
In theory, you just need someone to pull the updated apk and you can do 'adb install -r' to replace it.
[Fire TV Android Development] sirxdroid:
Thanks.

Someone who has the updated apk, please stand up ...
[Fire TV Android Development] cbarre:
No internet!

Got an issue with my FTV1. Its rooted and i have previously installed one of the rbox roms (maybe a year ago - running 51.1.6.3 on OS3). Now decided to update to OS5. Followed the instructions, uploaded the latest version rom (5.2.1.0_r1) and all worked except now amazon home screen wont connect - it says cant load - looks like it has no internet. Tried rebooting etc, checking ethernet but seems all good. No dramas playing files off my nas via xbmc but streams dont work either. Any ideas?
[Fire TV Android Development] CtJackHarkness:
This very same thing happened to me. I believe I just restarted the box a few times. If that's not working for you try to reflash the ROM.
[Fire TV Android Development] ImCoKeMaN:
When it first loads it needs to connect to amazon for your account verification, many of the software update block steps have you block some amazon sites that are needed for this first connection. Check router blocking and try again, or connect to your phone as a hotspot for a second just to confirm, you should be good after that.
[Fire TV Android Development] phistyle:
I'm trying to find clear cut instructions on how to update from os3 to os5 on my rooted, bootloader fully unlocked 1st gen fire tv and wanted to know if these are the right steps. I'm on twrp 3.0.0.6, so would all I need to do is download the latest pre-rooted 5.2.1.0-r1, push it to my fire tv, and install it? Or there others steps involved?
[Fire TV Android Development] ldeveraux:
sounds right, why not just follow the guide in the 2nd post of this thread?
[Fire TV Android Development] phistyle:
Aren't those guides outdated though?
[Fire TV Android Development] ldeveraux:
I think the method to upgrade would still be safe. Check aftvnews' site for sure, that's where the guides are.
[Fire TV Android Development] litoturtle:
I am flashing from 5.1.1.4.0 to 5.2.1.0_r1 (md5sum: c465bbbddaf3254f805bddbf2d162637), I had CWM mod then I installed TWRP. Do I need to install a bootmenu? I keep seeing it on the other versions so I want to ensure before I flash straight to 5.2.1.0 without bootmenu.

TYIA

---------- Post added at 01:09 PM ---------- Previous post was at 12:38 PM ----------

Nvm, I went ahead and did it. It worked
[Fire TV Android Development] iniro:
I am on 5.0.5.1_r1, is recommeded to install 5.2.1.0_r1?

Thx!
[Fire TV Android Development] LivinOne:
Looking for help, my SSH login connects and immediately kills the session.

- connect without issue using ADB via ethernet

- verified Busybox is installed (I reinstalled it too) and SSH is running; even tried changing from port 22 to 2222

WinSCP log...

. 2016-08-14 21:02:18.240 Looking up host "192.168.2.15"

. 2016-08-14 21:02:18.241 Connecting to 192.168.2.15 port 2222

. 2016-08-14 21:02:18.293 Server version: SSH-2.0-dropbear_0.52

. 2016-08-14 21:02:18.293 Using SSH protocol version 2

. 2016-08-14 21:02:18.293 We claim version: SSH-2.0-WinSCP_release_5.7.7

. 2016-08-14 21:02:18.294 Using Diffie-Hellman with standard group "group1"

. 2016-08-14 21:02:18.294 Doing Diffie-Hellman key exchange with hash SHA-1

. 2016-08-14 21:02:18.393 Verifying host key rsa2

. 2016-08-14 21:02:18.399 Host key matches cached key

. 2016-08-14 21:02:18.399 Host key fingerprint is:

. 2016-08-14 21:02:18.399 ssh-rsa 1040

. 2016-08-14 21:02:18.399 Initialised AES-256 SDCTR client->server encryption

. 2016-08-14 21:02:18.400 Initialised HMAC-SHA1 client->server MAC algorithm

. 2016-08-14 21:02:18.400 Initialised AES-256 SDCTR server->client encryption

. 2016-08-14 21:02:18.400 Initialised HMAC-SHA1 server->client MAC algorithm

! 2016-08-14 21:02:18.400 Using username "root".

. 2016-08-14 21:02:18.453 Prompt (password, "SSH password", <no instructions>, "&Password: ")

. 2016-08-14 21:02:18.453 Using stored password.

. 2016-08-14 21:02:18.505 Sent password

. 2016-08-14 21:02:18.512 Access granted

. 2016-08-14 21:02:18.512 Opening session as main channel

. 2016-08-14 21:02:18.520 Opened main channel

. 2016-08-14 21:02:18.556 Started a shell/command

. 2016-08-14 21:02:18.608 --------------------------------------------------------------------------

. 2016-08-14 21:02:18.608 Using SFTP protocol.

. 2016-08-14 21:02:18.612 Doing startup conversation with host.

. 2016-08-14 21:02:18.612 Server sent command exit status 1

. 2016-08-14 21:02:18.612 Disconnected: All channels closed

* 2016-08-14 21:02:18.716 (EFatal)
[Fire TV Android Development] bobbofire:
aftv1 - bricked, no lights, still available on USB

I can't fastboot.

I had an unlocked, rooted system.

- Updated to 5.2.1.0_r1_rooted from earlier rooted 5.0. Got some errors (roommate "helped" by playing with the TV while I was updating), and it didn't go well.

- no big deal, fastboot on USB worked. Started with the recover image, the re-did the main OS. Looked good, soft-booted to recovery, then back to OS.

- Left it a bit. I didn't turn off the auto-updates (didn't realize they were back on). This is my best guess on what went wrong.

- Came back, turned it off and plugged it back into the main TV, and walked away. Roommate tells me: no led, blank screen. Roommate think he saw something about configuring on the screen (I'm assuming it was applying the latest OTA update if he did see anything) before it powered off. Never came back again.

- No fastboot option this time. Power supply voltage is good.

I still see the drive partitions on USB though. I gather I'm stuck with locked now.

I see unbrick recovery options by manual dd's to overwrite partitions.

older recovery instructions: http://xdaforums.com/showpost.php?p=66961740&postcount=676

Somewhat current, but the latest official OTA update isn't available on the main page yet: http://xdaforums.com/showpost.php?p=67776513&postcount=855

What firmware package do I need? Which partitions? The old write-ups are out of date.

edit

I don't see sbl1.mbn, sbl2.mbn, sbl3.mbn, only tz.img (instead of tz.mbn) and there's no rpm.mbn in the 5.2.0 build 550145120 stock update bin archive.

edit 2: All the files are in the older 5.0.5 build, not the latest. Just ran out of space in /tmp when I opened the archive. I'm going to try writing the 5.2.0 stock files now and see what happens. Any mapping of what goes where from the 5.2.0 build?

---------- Post added at 08:15 PM ---------- Previous post was at 07:28 PM ----------

Where did you find the mapping instructions for 5.2.1.0? I'm not seeing this?
[Fire TV Android Development] bobbofire:
Just a follow-on to my previous post:

- My Fire TV 1 was bricked. No led. Blank screen. Looked dead.

--> I check the power supply, still 6.25V and pulling apart the FTV, nothing was fried.

- But with an USB A to USB A cable, I could see the drive and partitions (sdf1 to sdf18 on my system) and could mount/overwrite them as needed.

So I followed the Rbox's instructions from post 676, and used the stock version 5.0.5 linked to in the post.

http://xdaforums.com/showpost.php?p=66961740&postcount=676

That was good enough to get the led back on and some booting progress. That got me as far as the colorful yellow amazon fire ftv.

From there, I was stilling having trouble. I wasn't getting a fastboot option to recover (I might have had the timing off, I didn't test a lot because my boot menu came back).

- My boot recovery menu started coming up again when the USB-A to USB cable was plugged in at power-on (didn't work if just the keyboard was there, though).

- So I booted, waited for the menu, swapped the USB keyboard, and selected recovery boot.

- Re-installed my 5.2.1.0 rooted image.

- tested a couple cycles, powered it on with the internet disabled.

- Then I disabled OTA updates before re-enabling my gateway.

- power cycled again. All good.

No issues this time.

Maybe it's in the instructions somewhere, but disabling automatic OTA updates in the rooted image would go a long way. They stayed off for a lot of my previous updates, and I stopped checking. A lot of the bricked messages I read were similar complaints...and some of the instructions say OTA updates will stay off if you update, which is misleading. People can easily turn them back on, and it's much less damaging if you forget to turn them on, vs forgetting (or not knowing) you have to turn OTA updates off.

Cheers!
[Fire TV Android Development] catman2005:
Reset Factory ?

Hello,

Thank you for your wonderful work.

I followed the guide from CWM to TWRP and to the latest rom.

Everything worked fine.

Now, question, I had XPOSED, FireStarter bunch of games from kids installed and uninstalled and I am about 1.2 Gb free on my Fire TV (one), Can I do a factory reset on this ROM and not loose root?

Thank you again for all your work!

Cat
[Fire TV Android Development] iLLNiSS:
I just tried unbricking mine, but had 1 to 20 for partitions.... Does this make sense?

Regardless, flashed 3 through 10 and cycled power and I no longer have access to the partitions in /dev/ despite the usb device still showing under lsusb.

Good thing I have the eMMC adapter already on its way :o

And for future reference, is there no way to recover from a brick with the A-A or eMMC method and retain the bootloader unlock?
[Fire TV Android Development] cbarre:
Weird twrp issue

Hi all

I updated to a rooted 5.2.1.0 and havent had issues for the past couple of weeks but now all of a sudden after a period of non use, the system finds it self back in twrp's main screen. I have to unlug the fire tv or plug in the keyboard to navigate to reboot and all is good again. I havent seen it go into twrp as such, generally i find its happened in the morning, or in the evening after not using the fire tv for a few hours.

Anyone had this issue before? Anyone know a solution?

Cheers
[Fire TV Android Development] E--Man:
Hi [MENTION=3991724]rbox[/MENTION], I see so many people having issues during or after upgrading to OS5 here and on other threads. Is this due to a flaw in the posted upgrade procedure or ROM? Or, are these people not following the instructions appropriatly?

I am on OS3 rooted with unlocked bootloader and boot menu as per your following, and hesitant to upgrade because of all these issues we hear about and I want to ensure I will remain rooted and my bootloader will remain unlocked without issue.

Anyone have anything to add?
[Fire TV Android Development] xenyz:
Generally speaking, there's no reason to post in the forums if everything is working. You'll only find posts from those having issues; everyone else is busy watching their TV.

I personally have never found one flaw with any rbox release, and the single problem I've ever had (flashing TWRP) was a bizarre case involving certain models of TVs, and sorted itself after 48 hrs of booting.
[Fire TV Android Development] rbox:
You aren't blocking updates.
[Fire TV Android Development] iniro:
What is the difference between 5.0.5.1_r1 and 5.2.1.0_r0?
[Fire TV Android Development] cbarre:
oh, didnt realise this could cause an issue like this.
[Fire TV Android Development] iLLNiSS:
Is this method still applicable assuming the box was bricked while running 5.2.1.0_r1 ?

I updated to 5.2.1.0_r1 and things went well. During the OS boot while it was optimizing apps/etc I believe I reboot it over adb (trying to update another box). It bricked. No light/etc.

But following your post using the eMMC adapter I still get no light. Was wondering if perhaps things would be different after 5.2.1.0_r1.

UPDATE: disregard. After many attempts at flashing, the thing that fixed it was not running in a VM. Native Linux did the trick. Finally got a flashing light and yellow amazon logo. Progress :)