FireTV 1 (bueller) Full Bootloader Unlock

[rbox]

I have tried and still stuck on the white screen and this the link for fire tv utility app http://forum.xda-developers.com/showthread.php?t=2736774. I cant run fastboot continue as adb shell as it is not connecting to internet

fastboot has nothing to do with adb

 

[alba1978]

fastboot has nothing to do with adb

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

 

[rbox]

When you get the A to A cable, try running 'fastboot continue'.

Fastboot is over usb.

 

[alba1978]

Fastboot is over usb.

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

 

[rbox]

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

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

 

[alba1978]

thanks for your help

 

[bula1ca]

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.

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.

 

[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?

 

[rbox]

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?

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.

 

[E--Man]

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.

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 ----------

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...

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!

 

[Kramar111]

@rbox
Please answer
http://forum.xda-developers.com/showpost.php?p=58901654&postcount=15

 

[krasny2k5]

@Kramar111 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.

 

[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).

 

[rbox]

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).

Hate to break it to you... but this changes nothing. 24p or otherwise...

 

[Resnoid]

:good:

Worked like a charm on all three of my FireTV's. Thanks Rbox

 

[alba1978]

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

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.

 

[bula1ca]

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.

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?

 

[alba1978]

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?[/Yes I did have boot menu installed but it is stuck on the white logo

 

[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?[/Yes I did have boot menu installed but it is stuck on the white logo

Did you try to remove everything that is plugged into the USB port (if anything), unplug box from the wall for a couple of minutes and then plug it back in? If this does not work then boot loader got somehow corrupted during the unlock procedure and you will not be able to recover through software. I may be wrong.... at least I hope so.

 

[rubinho]

@rbox
Could the same vulnerability also still work with the newer firetv bootloader ?
see here...
http://forum.xda-developers.com/showpost.php?p=59117419&postcount=40
and here...
http://forum.xda-developers.com/showpost.php?p=59129096&postcount=64