yashsingh1/xdaforums huggingface dataset:
[Fire TV Original Android Development] rbox:
As the OP states "If you already have CWM installed, you can skip this." As for what this gives you.. Not much really. If you do something stupid, you have to ability to boot into recovery with fastboot. That's about it.
[Fire TV Original Android Development] retroben:
I am in a special case where I am already on 51.1.0.2 but I don't have CWM installed yet.

So,should I install CWM,and then what do I do since I am already on the right firmware version?
[Fire TV Original Android Development] rbox:
What special case? The ONLY mention of CWM in the OP is that if you already have it, you can skip the downgrade. Otherwise it says nothing of CWM. The first step is downgrade to 51.1.0.2. If you are already at 51.1.0.2, then there is nothing to do. Go on to step 2.
[Fire TV Original Android Development] E--Man:
Rbox,

Thanks for your prompt replies here. One quick question: If I perform this, and down the line I somehow manage to accidentally take an Amazon update which takes away my root completely, then can I use the fact that my bootloader is fully unlocked to my advantage to re-root via USB? Or, would that Amazon update be able to relock the bootloader once again?

Thanks again,

E.
[Fire TV Original Android Development] rbox:
There are no "accidental" updates. You have to royally screw up to get an update. This unlock is dependent on the bootloader version. If you do stupid things and screw up and get an update, then the new bootloader will not recognize the unlock.
[Fire TV Original Android Development] E--Man:
Thanks RBox, so as I understand an Amazon update includes a bootloader which will be locked and not recognize this unlock. I have multiple layers of prevention from somehow taking an update including disabling dcp but trying to be as safe as possible just in case.

I really can't wait for a full stable non-Amazon ROM to be released for this box; the fact that they are so hard at work preventing us from enjoying the devices we have purchased makes me want to disassociate from them even more.

Thanks again...
[Fire TV Original Android Development] Zaaap72:
Can some one please provide an original and an unlocked bootloader image.

Thank you.
[Fire TV Original Android Development] rbox:
There is no separate original and unlocked bootloader image... The unlock doesn't modify the bootloader.
[Fire TV Original Android Development] alba1978:
my fire tv is stuck on fastboot I thin as it is on white amazon logo and black screen and I have rebooted several times via power lead and still stuck .is there another way of getting out of fastboot
[Fire TV Original Android Development] rbox:
What did you do to get there? Is anything plugged in to the USB? What version were you on? Do you have a USB A to A cable?
[Fire TV Original Android Development] alba1978:
used the fire tv utility 39 to unlock and I am on you latest custom rom . I have a Logitech k400 keyboard pluged in the usb port. I have ordered an Ato A cable and will be with me Friday.
[Fire TV Original Android Development] rbox:
What if you don't have anthing plugged in to the USB? When you get the A to A cable, try running 'fastboot continue'. But I don't know what the fire tv utility 39 does...
[Fire TV Original Android Development] alba1978:
I have tried and still stuck on the white screen and this the link for fire tv utility app http://xdaforums.com/showthread.php?t=2736774. I cant run fastboot continue as adb shell as it is not connecting to internet
[Fire TV Original Android Development] rbox:
fastboot has nothing to do with adb
[Fire TV Original Android Development] alba1978:
you have to excuse me for my ignorance but how do I run fastboot continue without adb or do I need to wait for my Ato A lead
[Fire TV Original Android Development] rbox:
Fastboot is over usb.
[Fire TV Original Android Development] alba1978:
Thanks for your help and once my lead comes on Friday I will see if can get it to work. is there a link or instructions on how to send commands on fastboot as I have been googling and searching the forum but cant get to it
[Fire TV Original Android Development] rbox:
Step 1. Plug in cable

Step 2. Install drivers (tons of documentation on installing amazon drivers) OR get a real os and don't need to mess around with drivers

Step 3. Run 'fastboot whatever' where whatever is the command you want
[Fire TV Original Android Development] alba1978:
thanks for your help
[Fire TV Original Android Development] bula1ca:
Not sure what happened however you should only be in fast boot if your box is connected to the computer through an A to A cable and the command "adb reboot bootloader" was sent., once you disconnect your cable and reset your box it should start back normally. I do not know if FireTv Utility sends multiple commands and something got screed up in the process, I always like to use adb to send commands one by one.
[Fire TV Original Android Development] E--Man:
Hi RBox,

I just performed this via ADB over my LAN, and it finished successfully by saying "Rebooting...", but I am noticing that the networking of this device now behaves slightly differently. For example, before this update, ADB was communicating via UID 2000 (Linux shell), whereas now it appears to be communicating through UID 0 (root).

Might you know why this has changed?

Lastly, when I reconnected via ADB I did not get a root prompt after running ADB shell. Could this be because I already connected via ADB and granted it root when I rooted previously?
[Fire TV Original Android Development] rbox:
adbd runs as root when the bootloader is unlocked, thats just how they set up their adbd. Hence the 2000 vs 0. If adb is uid 0, then you have root so not sure what you are talking about in the 2nd part.
[Fire TV Original Android Development] E--Man:
Thanks RBox for the quick reply. I did not know that ADB will use "root" UID as opposed to "Linux Shell", and I did not expect that would switch to UID 0, good to know this and glad to hear this change is normal.

Now to test the USB functionality...

---------- Post added at 01:45 AM ---------- Previous post was at 01:14 AM ----------

RBox, I think I'm good:

C:\Users\Administrator\Desktop\FireTV>fastboot oem device-info

...

(bootloader) Device tampered: false

(bootloader) Device unlocked: true

OKAY [ 0.006s]

finished. total time: 0.007s

Thanks again!
[Fire TV Original Android Development] Kramar111:
[MENTION=3991724]rbox[/MENTION]

Please answer

http://xdaforums.com/showpost.php?p=58901654&postcount=15
[Fire TV Original Android Development] krasny2k5:
[MENTION=5728225]Kramar111[/MENTION] To recovery your box you flashed new (updated) bootloader into your box, so now you have a rooted 51.1.4.1 but with a non vulnerable bootloader. With that update they burn an efuse so you can´t boot with vulnerable bootloader. So no, the full unlock won´t work for you.
[Fire TV Original Android Development] onlinespending:
this is excellent news. Hopefully this paves the way to 24 Hz (24p) video output, so we can enjoy films in their native frame rate without judder (still a head scratcher how Amazon, Apple, Google, and the rest of them release a media box and don't support this).
[Fire TV Original Android Development] rbox:
Hate to break it to you... but this changes nothing. 24p or otherwise...
[Fire TV Original Android Development] Resnoid:
:good:

Worked like a charm on all three of my FireTV's. Thanks Rbox
[Fire TV Original Android Development] alba1978:
my A to A lead come but I have had no joy as It will not allow me to connect to fire tv but I am stuck in white logo. it was good whilst it lasted but it looks like time to get a new one.
[Fire TV Original Android Development] bula1ca:
See post 47.

Your box should had reboot when powered off and back on if you were in fastboot.

Have you had boot menu installed prior unlocking boot?
[Fire TV Original Android Development] rubinho:
[MENTION=3991724]rbox[/MENTION]

Could the same vulnerability also still work with the newer firetv bootloader ?

see here...

http://xdaforums.com/showpost.php?p=59117419&postcount=40

and here...

http://xdaforums.com/showpost.php?p=59129096&postcount=64
[Fire TV Original Android Development] rbox:
Well anything is possible. Try it and see.
[Fire TV Original Android Development] rubinho:
I dont have a new bootloader, sry.

Von meinem LG G3 getippelt
[Fire TV Original Android Development] gamer765:
You can always flash the new bootloader, just take the new img and flash to aboot partition.
[Fire TV Original Android Development] rubinho:
is this supposed to be a joke?

I change not an unlocked bootloader, against a locked bootloader the may not can be unlocked.
[Fire TV Original Android Development] papars:
I would like to know if there is any gain in doing this in a hardware rooted box.

Will actually be possible to do it anyway in such box?
[Fire TV Original Android Development] bula1ca:
It is not possible.
[Fire TV Original Android Development] Zaaap72:
Tested by me and is not working on FireTV with stock 51.1.4.3

"oem unlock" shows ... forever.

D:\adb>fastboot -i 0x1949 oem unlock unlock.img
...
^C

D:\adb>fastboot -i 0x1949 oem device-info
...
(bootloader) Device tampered: false
OKAY [ 0.000s]
finished. total time: 0.000s

"flash unlock" seams to be patched by amazon.

D:\adb>fastboot -i 0x1949 flash unlock unlock.img
sending 'unlock' (0 KB)...
OKAY [ -0.000s]
writing 'unlock'...
FAILED (remote: Unlock code is NOT correct)
finished. total time: 0.016s

Who can find out how to generate a correct unlock code? :)
[Fire TV Original Android Development] goodbye hppalm:
Strange thin rbox, I was able to install recovery but when I do the adb shell command its still show $ not #, im wondering how that is
[Fire TV Original Android Development] bula1ca:
Did you full unlock boot loader or just partially? CWM only requires a partial unlock.
[Fire TV Original Android Development] marlowe310:
I'm a bit puzzled -- I have a rooted AFTV, running 51.1.3.0_user_513011520. I can confirm root because AdAway is still able to download and install new host files (which I believe means I AM rooted).

However both the AFTV news guide and this thread don't mention my software version specifically, and if I'm reading right what they DO say is that my version 1) can't be rooted and therefore 2) cannot use this unlock. Is that correct? Since I am rooted, can I still make use of this tool? If so, do i need to downgrade versions first? I'm honestly not sure if I ever installed CWM -- is there a quick SSH command I could use to check?

Thanks very much for any help!
[Fire TV Original Android Development] rbox:
Since you hardware rooted, you can still follow all the guides on aftvnews. Just make sure you downgrade the recovery like the guide mentions before attempting to downgrade the rom. The point of no return is 51.1.4.1. As long as you are on 51.1.3.0, you can still do it all.
[Fire TV Original Android Development] marlowe310:
Thanks very much for the response. Just to confirm: you said since I 'hardware rooted' -- did you mean since my hardware IS rooted? I ask because I definitely didn't do any sort of hardware/mechanical root, I just used TowelRoot.

What is also weird is that I can't LAUNCH SuperSU, but it still seems to be capable of granting root access. Very odd.
[Fire TV Original Android Development] rbox:
If you didn't hardware root and you have root on 51.1.3.0, then you most definitely have CWM.
[Fire TV Original Android Development] KLit75:
It maybe odd because i dont know why exactly but thats the way supersu works for all of us. Think when i originally rooted aftv supersu could launch and settings could be accessed but somewhere along the way that changed. Theres no real downside to it that i can see.
[Fire TV Original Android Development] bpugliese:
Hello

I'm trying to recover from brick via fastboot

So far, i'm stuck at this problem:

: C:\adb>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
OKAY [ 0.007s]
finished. total time: 0.008s

C:\adb>fastboot flash recovery recovery.img
sending 'recovery' (8360 KB)...
OKAY [ 0.373s]
writing 'recovery'...
FAILED (remote: flashing not allowed for locked hw)
finished. total time: 0.396s

Anyone have any help to give?
[Fire TV Original Android Development] rbox:
You never did the full unlock. You can't use fastboot with the partial unlock.
[Fire TV Original Android Development] bpugliese:
Thanks for the reply. Up until now, I thought I had the full unlock, at least now I know for sure now that I didn't.

If by any chance you have some suggestion of procedure I could still try, in order to reverse the brick, I'd be happy to know. From what I've learned so far, this unit seems to be gone forever.
[Fire TV Original Android Development] rbox:
Well it really depends on how you are "bricked".
[Fire TV Original Android Development] bpugliese:
When I turn the device on, it gets stuck on the white amazon logo. Supposedly can't connect via adb. Fastboot is as I've already posted. I've tried using keyboard Alt + Sysreq + i to get to recovery but it didn't work. I think that sums it up.

If there's any other relevant info I can still provide, please let me know.
[Fire TV Original Android Development] rbox:
Depends on how you got there, but if you have CWM, you're best bet is to just try the sysrq.
[Fire TV Original Android Development] bpugliese:
I do have CWM, but I had no luck trying sysreq, it seems the keyboard doesn't even get to the point of being powered on. I'll try searching about sysreq and see if there are any other tips about that, but I think that if my best shot is that, this unit is already lost.
[Fire TV Original Android Development] dk1keith:
I have CWM and have installed your custom rom. How can I tell if I have a fully unlocked or partial unlock? is it the root prompt when in adb shell? that prompt says root@android:/ #
[Fire TV Original Android Development] rbox:
Yes. If when it's booted and you do adb shell and get a root prompt, that means it's got the full unlock.
[Fire TV Original Android Development] TROJAN4EVR:
Connect via fastboot when at the white amazon logo screen.

Type the following 3 commands:

fastboot devices

fastboot continue

fastboot continue

If you have boot loader fully unlocked and you have rbox's boot kernel installed the 2nd command above will hopefully boot you into the boot kernel and if you're quick enough you can connect a usb keyboard so you can select recovery. Otherwise entering the third command will hopefully boot you into the amazon home screen. Let us know if it works. Good Luck.
[Fire TV Original Android Development] dk1keith:
Great thanks
[Fire TV Original Android Development] TROJAN4EVR:
Have you tried fastboot continue command? Also with regard to entering "Alt + i + Sysreq",...you need to be sure youre pressing all keys at the same time and just keep pressing in unison at a steady rate....I've had to press all three keys in unison at least 10 or more times before the screen flickers to boot into cwm. I use a basic dell usb keyboard: At the same time, I press the "alt" key with my left thumb, the "i" key with my left index finger and the "SysRq" with my right index finger. The sequence has to be done at exactly the same time and at a constant rate. You can't mess it up as once you do it correctly...the screen will tell you because it will flicker and then boot into CWM. Good luck!!!
[Fire TV Original Android Development] moeduss:
Sorry Found answer to question. Thanks.
[Fire TV Original Android Development] schybiorz:
is there also a chance to fully unlock the bootloader from the aftv2 devices?
[Fire TV Original Android Development] Y314K:
Bootloaders have been locked for a long while. There is no method to software unlock them on FTV Gen1 with newer FW & none of the FTV Gen 2 or FTVS's have ever been unlockable. Getting it unlocked is probably even harder then finding an exploit for root.

If there ever is a way to do it you will probably see a new thread here in Fire TV Original Android Development since it would be a huge deal.
[Fire TV Original Android Development] cmlusco:
I got excited whet i ran this on my ftv2. It looks like it works, but remains locked. :(
[Fire TV Original Android Development] Jcagley:
I rooted my gen 2 firetv only to find it absolutely ridiculous to do so. Many apps on the Amazon side (i.e. uverse app with log in credentials) wouldn't play due to "unsecured device". The ONLY benefit I see from root, is the ability to stop forced updates. Big deal I say, as I don't believe Amazon is going to stop side loading. That works just fine without root. I unrooted my FireTV, and am now back to " normal". Another issue I see, is its constantly said that if your internet is not "fast" enough, kodi stuff won't play well. My question is why does amazone side streaming actually work beautifully, with HD sound and all, but in kodi, I struggle to keep many channels alive for more than 3-5 minutes? I'm of the belief that it's hack programming of the builds....just my opinion.
[Fire TV Original Android Development] TROJAN4EVR:
Bro...use the guide for rooting on aftvnews.com....and if you don't like pre rooted rom 5.0.5.1 you can downgrade to 5.0.5...And as for kodi...are you running a build or just kodi with your favorite addons? Try official kodi jarvis 16.1 release. With the right addons and a good internet connection...everything runs great. Try schismtv moonshine build....runs great on fire tv/stick
[Fire TV Original Android Development] Jcagley:
I did use the guide! I just don't see any benefit at all to root. I lost functionality on the Amazon side with the only gain being blocking auto updates. Just don't see the benefit.
[Fire TV Original Android Development] TROJAN4EVR:
You did something wrong. Guide allows you to have pre rooted 5.0.5 or 5.0.5.1 roms and amazon and kodi runs fine. As for the benefits of rooting...well that depends on what you want from your device...sorry it didn't work out for you.
[Fire TV Original Android Development] Jcagley:
It worked fine. I had root, confirmed. Look it up, uverse apps and others with log in credentials will NOT run on rooted devices.

---------- Post added at 12:55 PM ---------- Previous post was at 12:54 PM ----------

I was running the prerooted ROM. Most Amazon stuff would work. But having the uverse credentials from my parents, gave me a lot more TV options. But 90% of those channels will not run on root.
[Fire TV Original Android Development] ldeveraux:
Try running xposed without root, see how far it gets you!
[Fire TV Original Android Development] Jcagley:
Why run exposed? What's that going to get me? I run xposed on my bl unlocked phone, love it for what it does on my phone. Unless xposed is going to get me TV channels, which is what my FireTV is for....don't see a need. Still haven't heard a single "good" reason for root....js. See absolutely no benefit whatsoever.

---------- Post added at 03:06 PM ---------- Previous post was at 02:49 PM ----------

I am using 16.1. Have tried several builds, from beast, Royalist, forget one I have now. It's always the same issues with the live channels. Horribly pixelated most channels. Dropped feeds constantly. If my connection were not fast enough, how can I stream 1080 AND dolby sound on Amazon side just fine...for days on end, and never even buffer?
[Fire TV Original Android Development] ldeveraux:
OK well good for you I guess? Are you looking for someone to explain the benefits of root? Or for someone to give you a convincing reason to root? Because you've clearly made a decision against it and are, for some reason, trying to convince others you're correct. I don't see why it matters to you that much, just let everyone else root in peace. ;)
[Fire TV Original Android Development] Jcagley:
No, I get your point, for lack of a better word. Root away! I thought forums were to discuss and ask questions, and yes, I was looking for a convincing reason to root. I see no benefit in it with the side loading available. So that was the crux of my statements.
[Fire TV Original Android Development] the_chinaman:
Mate, then don't root!

People here trying to offer advice as you have obviously fecked things up on your device, your issues are not widespread and many are enjoying a hassle free root.

So, keep walking, nothing for you to see here!
[Fire TV Original Android Development] Jcagley:
I f'd up what? I don't get the gd hostility here at all. I offered my OPINION that i saw no benefits to rooting, and have been waiting patiently for a reason "why". There was nothing at all f'd up with my root. It rooted, I could do whatever I wanted with the device. The problems are with apps that will NOT function on a rooted device. That was not a problem of mine, other than I LOST functionality. Uverse, ESPN, a&e, to name a few, would not work with root. So I ask again, what exactly does root accomplish? I can run kodi without it, I can see a LOT more content without it, so THAT is why I wanted to get others OPINIONS on why root was so special.[emoji16]
[Fire TV Original Android Development] Y314K:
A Rooted FTV means you own your FTV. UnRooted FTV means your renting your FTV until Amazon decides to take an option away or change how it works.

The Att-Uverse app Rooted device block has already been bypass...

So just by removing the SU directly in the PreRooted ROM. You get the best overall solution. You get to run the latest Pre-Rooted version without having to stop updating each time Amazon blacklists something. And by removing SuperSU before flashing. You can run ATT-Uverse fine.

UnRooted you are stuck at whatever ROM version Amazon decided to blacklist whatever. While Rooted folks can wait for a Rooted ROM that gets rid of the blacklist. Or where you can at least run ADB code to freeze or remove the blacklist. FULL CONTROL OF YOUR AFTV.
[Fire TV Original Android Development] Jcagley:
Thanks for that tid bit of info. I'm all for rooting, believe me. Won't buy a phone that can't be min rooted, prefer bl. Had not heard of this bypass for uverse app. I noticed it on my phone first (fully bl unlocked), then once I rooted, I couldn't watch a lot of channels. That was a deal breaker. But I will reattempt this with removal of su pre flash. Thanks for that. I searched high and low, and only answers I saw were "try root cloak"! Ha-ha that app doesn't work.
[Fire TV Original Android Development] Y314K:
np, I've been tempted a bunch of times since last year to UnRoot my 1st Gen FTV's since the wait for a PreRooted FireOS 5 ROM has been this long. I almost rewarded Amazon for the blacklist by purchasing a FTV2 although the hardware upgrade is not warranted. But was able to stop myself.

Just about every root cloaking app is so old that I doubt it will work. Seems all those projects where abandoned. As for the apps. I would highly recommend that you turn off Auto-Updates for apps. That way you can just manually update the app only after you know they haven't introduce something like a Root checker. I myself have never had root problem when using the ESPN app. I've updated it a few times. But have never had that problem on an FTV. Might be something new on a newer APK version. It's always a must & very easy to backup the current APK on ES File Explorer before manually updating. Or even if you prefer to run Auto-Update. You can backup the latest APK version once a month to make sure you have a backup plan in case something bad is introduce.

The only apps that I've had problems with Root has been ATT Uverse & XFinity. Other then that, nada. But I have not been testing those lately. Wanted to wait until the FireOS 5 to retest them again.
[Fire TV Original Android Development] cmlusco:
There are tons of reasons to root. Smb, change dns servers, disable blocking of firestarter or any other app they try to blacklist, change device name, backup apps, use recovery to back up the entire system, add back adb support, set selinux permissive, and the list goes on. With root you get to make it the way you like, not the way amazon likes it. I didnt pay $99 for a box someone else has complete control over.