FireTV Boot Menu 1.0

Search This thread

vampypang

New member
Aug 6, 2005
4
0
Hrm... My FireTV also loads the rbox boot menu, and won't boot the kernel (it just sits there) and launch recovery will return with the amazon system update not successful screen. Any luck with your FireTV?

I've made some progress... after much persistence of "launching recovering" then pressing (Alt + Prt Sc + i) to reboot it again, then pressing the HOME key, I now have the "Android System Recovery" loaded... I'm now not sure what to do next! Factory reset didn't do much, and I'm not sure how to connect to the firetv when using the "apply update from ADB"... Any tips?
 

bula1ca

Senior Member
Nov 18, 2014
346
63
I've made some progress... after much persistence of "launching recovering" then pressing (Alt + Prt Sc + i) to reboot it again, then pressing the HOME key, I now have the "Android System Recovery" loaded... I'm now not sure what to do next! Factory reset didn't do much, and I'm not sure how to connect to the firetv when using the "apply update from ADB"... Any tips?

Reinstall bueller-51.1.4.0_514006420-rooted+updated, it will remove Boot Menu and you can start fresh. I installed boot menu manually on all my boxes however on the last one I did for a friend I tried to install it using FireTv Utility (could had been an user error) and I ended up with system not being able to boot up, fortunately boot menu saved me.
 
Last edited:

hotterpop

Member
Jul 12, 2014
36
13
Seattle
Also, I don't want to sound like too much of a fanboy here, but being able to use my laptop to control the recovery without having to go dig up my keyboard was a magical experience.
 

Y314K

Senior Member
Dec 29, 2008
1,498
488
Samsung Galaxy A32 5G

hotterpop

Member
Jul 12, 2014
36
13
Seattle
I haven't used FireTV Utility, I've been doing all my installs manually through the terminal. I just rebooted to CWM and then followed the instructions you linked. My only complaint is that I had to switch out of Dvorak to get the proper key orientation :p
 

RoachForLife

Senior Member
Jul 17, 2007
307
16
Orlando
so looks like I bricked mine. I see how I did this. I right clicked the link and hit save on the img file rather than left clicking and downloading from the mega site. This ended up being only 89k but of course I didnt check. The actual file is 6megs.

Anyways after running thru the commands I am stuck on the amazon boot screen. Is there anything that can be done or is this a complete loss? Sucks I just spent an hour or so doing all this stuff only to brick it right at the end. Grr
Thanks
 

chrootz

Senior Member
Apr 9, 2011
397
91
@rbox - thanks for this excellent development and I finally got time to work on my AFTV and everything is charm and smoothly. When I get paycheck in next 2 weeks and promise buy you a beer.
 

Y314K

Senior Member
Dec 29, 2008
1,498
488
Samsung Galaxy A32 5G
so looks like I bricked mine. I see how I did this. I right clicked the link and hit save on the img file rather than left clicking and downloading from the mega site. This ended up being only 89k but of course I didnt check. The actual file is 6megs.

Anyways after running thru the commands I am stuck on the amazon boot screen. Is there anything that can be done or is this a complete loss? Sucks I just spent an hour or so doing all this stuff only to brick it right at the end. Grr
Thanks
Can you still ADB into your FTV. I would try to sideload the bootmenu.img file using the FireTV Utility App to the Download folder & then I would try running thru the commands again. If you can still ADB to your FTV then there might still be hope...
 

chrootz

Senior Member
Apr 9, 2011
397
91
@rbox - is it safe if I am going to format /system partition in the recovery and will I going to lose the boot.img? I was going to re-install the latest pre-rooted rom. Just wanted make sure before I do it. Thanks

PS. I already installed the boot menu.
 

ECEXCURSION

Senior Member
Aug 20, 2010
2,261
521
Minneapolis, MN
www.lego.com
I am having an almost similar situation. The timer counts down to 0 and I am stuck there. I also have a keyboard installed, however it will not enter the boot kernel or launch recovery. It actually doesn't let me do anything from this screen. I have tried 2 different keyboards. They are working as the CTRL ALT DELETE triggers a reboot. I know the the latest version of CWM was installed. Not really sure how to proceed.

Edit: Apparently I got it working now. Not exactly sure what was wrong but it's up and running. Yesterday when I was triggering the recovery at boot via the ALT PrntScreen i it didn't actually boot recovery, but somehow later it did? After doing that it allowed for movement on the boot menu, but at that point I just loaded 4.0 to remove boot menu. Then flashed boot menu again and everything was working.
I've done a few boxes for family and friends and never had this issue, glad it decided to fix itself one way or another.
I too have found myself in a similar situation. Currently trying to remedy the situation.

I've been following AFTVnew's wonderful rooting guide in conjunction with the Amazon FireTV Utility App for basic commands (like launching adb shell, pushing files, or rebooting the FTV.

This morning my AFTV sat with bootloader unlocked, CWM 6.0.5.1.4a, 51.1.4.0_514006420 updated, rooted, busybox installed, updates disabled, and all file checksum's verified before flashing.

Aftering continuing on with the AFTVnews rooting guide it was time to install the custom boot menu. I opted to manually input commands, instead of relying on the FireTV Utility App. After rebooting the AFTV the custom boot menu clock ticked down to 0 and just sat there - unable to select anything. I was able to press Ctrl-Alt-Delete to reboot, at which point I selected recovery, and now have access to adb shell again. The only thing I can think of which deviated from the guide is that I had initially transferred "firetv-bootmenu-1.0.img" to the sdcard before renaming it as the guide suggested. I then decided to rename it by doing "cp firetv-bootmenu-1.0.img bootmenu.img". I'm curious if there would be any permission problems in doing so (I'm somewhat of a Linux novice)?

I'm wondering what the best course of action is. Do I reboot and hope for the best? Do I flash 51.1.4.0_514006420 updated to the AFTV again and flash that to start over? Or should I transfer 51.1.4.1_514013920 fixed instead? I'm currently in the process of transferring both to the SD Card. I assume 51.1.4.0 is the logical choice? What do you guys think?
 

rbox

Recognized Developer
Apr 22, 2011
1,776
2,606
I too have found myself in a similar situation. Currently trying to remedy the situation.

I've been following AFTVnew's wonderful rooting guide in conjunction with the Amazon FireTV Utility App for basic commands (like launching adb shell, pushing files, or rebooting the FTV.

This morning my AFTV sat with bootloader unlocked, CWM 6.0.5.1.4a, 51.1.4.0_514006420 updated, rooted, busybox installed, updates disabled, and all file checksum's verified before flashing.

Aftering continuing on with the AFTVnews rooting guide it was time to install the custom boot menu. I opted to manually input commands, instead of relying on the FireTV Utility App. After rebooting the AFTV the custom boot menu clock ticked down to 0 and just sat there - unable to select anything. I was able to press Ctrl-Alt-Delete to reboot, at which point I selected recovery, and now have access to adb shell again. The only thing I can think of which deviated from the guide is that I had initially transferred "firetv-bootmenu-1.0.img" to the sdcard before renaming it as the guide suggested. I then decided to rename it by doing "cp firetv-bootmenu-1.0.img bootmenu.img". I'm curious if there would be any permission problems in doing so (I'm somewhat of a Linux novice)?

I'm wondering what the best course of action is. Do I reboot and hope for the best? Do I flash 51.1.4.0_514006420 updated to the AFTV again and flash that to start over? Or should I transfer 51.1.4.1_514013920 fixed instead? I'm currently in the process of transferring both to the SD Card. I assume 51.1.4.0 is the logical choice? What do you guys think?

Sounds like you didn't back up the boot.img. Just install 51.1.4.1 and you should be fine.
 
  • Like
Reactions: ECEXCURSION

ECEXCURSION

Senior Member
Aug 20, 2010
2,261
521
Minneapolis, MN
www.lego.com
Sounds like you didn't back up the boot.img. Just install 51.1.4.1 and you should be fine.
I installed 51.1.4.1 and it completed successfully, I'm back up and running! Thanks!

I'm still slightly confused though for root cause; I assume the backup of boot.img in this command?
Code:
dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/system/boot/boot.img
I did run that command the first time and it completed. I can see a file located at /system/boot/boot.img on my AFTV.

Perhaps this isn't the right area, but I was also wondering what the best method would be to start "fresh". It seems that my purchased music from Amazon Music plays back at .05 speed for some reason... Should I clear cache and factory reset in CWM? Factory reset in the Amazon menu perhaps? Sorry for all of the questions.
 

rbox

Recognized Developer
Apr 22, 2011
1,776
2,606
I installed 51.1.4.1 and it completed successfully, I'm back up and running! Thanks!

I'm still slightly confused though for root cause; I assume the backup of boot.img in this command?
Code:
dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/system/boot/boot.img
I did run that command the first time and it completed. I can see a file located at /system/boot/boot.img on my AFTV.

Perhaps this isn't the right area, but I was also wondering what the best method would be to start "fresh". It seems that my purchased music from Amazon Music plays back at .05 speed for some reason... Should I clear cache and factory reset in CWM? Factory reset in the Amazon menu perhaps? Sorry for all of the questions.

Factory reset from recovery is enough.
 

ECEXCURSION

Senior Member
Aug 20, 2010
2,261
521
Minneapolis, MN
www.lego.com
Factory reset from recovery is enough.
Alright, so I'm pretty sure my AFTV has now turned demonic... Even the initial setup video was playing back at 0.25% audio speed. This isn't how E-Fuses manifest themselves, is it? lol?

I still have access to CWM, so I guess I will try flashing 51.1.4.0_514006420 updated tomorrow and see if it fixes anything (unless you have another idea). Thanks for the help, rbox!.\

// EDIT: It turns out my LG LA6200 HDTV was at fault, not the AFTV... demonic TV.
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 23
    This is a boot menu that will allow you to select if you want to boot a kernel or reboot in to recovery. I highly recommend everyone install this so you always have a way to boot in to recovery in case of problems. Just like recovery, it will sit at a black screen for an abnormal amount of time before showing. It's something like 20 seconds. But once it shows, you will have 5 seconds to make a selection. It defaults to booting the kernel, but you can use the up down keys to change the selection. Once it hits 0, it will do whatever option is selected. You can also hit enter and it will do that right away.

    Right now, this is a very rough version 1.0. I plan to add some more features to it and would like to hear feedback from people to see what they think about it.

    As usual, this WILL void your warranty and I am NOT responsible for anything you do with this. Installing it properly won't brick your Fire TV. Of course, this requires root and unlock.

    Installation

    Install CWM version 6.0.5.1.4 or higher. You MUST VERIFY CWM is at least 6.0.5.1.4 and it works BEFORE proceeding. You WILL BRICK your Fire TV if you are not properly unlocked, and verifying 6.0.5.1.4 or higher is working will do that.

    For the following instructions, replace bootmenu.img with whatever filename you downloaded from this post, for example firetv-bootmenu-1.0.img. Copy bootmenu.img to /sdcard (via adb or whatever). Then from adb shell run this: DO NOT COPY PASTE THE WHOLE THING, DO EACH COMMAND ONE AT A TIME.

    Code:
    su
    mount -o remount,rw /system
    mkdir /system/boot
    dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/system/boot/boot.img
    mount -o remount,ro /system
    dd if=/sdcard/bootmenu.img of=/dev/block/platform/msm_sdcc.1/by-name/boot

    Once you have verified it is working, you can replace /system/boot/boot.img with whatever kernel you want. Whether it be the overclocked kernel, or a Fedora kernel, or something else. And you never have to worry about bricking or getting back in to recovery.

    Notes

    Flashing anything that updates boot.img will cause you to loose bootmenu support. All pre-rooted roms 51.1.4.0 and lower will do this. Anything past 51.1.4.0 will only support booting their kernels through this method. When flashing 51.1.4.0 or lower when using bootmenu, you must repeat the entire bootmenu installation procedure because those roms will overwrite the bootmenu.

    Changelog and Downloads:

    • Nov 15, 2014 - 1.0 (md5sum: a8a3c28baafe43f354d92e6cc8b392d3)
    2
    @rbox - is it safe if I am going to format /system partition in the recovery and will I going to lose the boot.img? I was going to re-install the latest pre-rooted rom. Just wanted make sure before I do it. Thanks

    PS. I already installed the boot menu.

    You should *NEVER* format /system. There is never any reason to do that.
    1
    Thanks a lot rbox. This works as described though I am not sure at this point what to do with it. I just installed it as you said it would be useful :)

    My main goal with it was to always be able to get to recovery. Secondary goal is to easily use alternate kernels without risk of not being able to get back to recovery. Which really gets back to the main goal. A side effect is that people can load fedora kernels easy without having to screw around with their partitions.
    1
    That's very much correct. I think I'm going to make all my future prerooted images put their boot.img in /system/boot and not flash it to the boot partition.
    Thanks for your quick reply. Glad I'm on the same page .. I'm working on a custom ROM and was thinking that was something i would address the same way but then thought for a sec maybe you had moded the newer cwm to just do that instead of flashing the boot.img.

    EDIT
    might want to put some more thought into doing that for the newer pre-roots as someone may flash back to an older one then flash forward and screw themselves.. maybe include some sort of checking in cwm? And maybe include a warning in the OP if they flash any pre-root they loose the safetynet of the bootmenu.img until applied again.
    1
    One tiny suggestion: Change the wording in your post "When flashing 51.1.4.0 or lower when using bootmenu, you must reflash bootmenu." to "When flashing 51.1.4.0 or lower when using bootmenu, you must repeat the entire bootmenu installation procedure."

    The reason: After setting up bootmenu on my test device, I realized it was on 51.1.3.0 when I thought it was on 51.1.4.0. I installed 51.1.4.0 then re-read your note to "reflash bootmenu". I thought "ah simple, i'll just re-run the last dd step since everything is still in place." Of course, I forgot that installing 51.1.4.0 wiped out /system/boot/boot.img so when I put bootmenu in place I no longer had a stock boot image on the box. It was a simple fix (I just used bootmenu to get into recovery and reinstalled 51.1.4.0), but probably best to be explicit with the above sentence.