FireTV Boot Menu 1.0

Search This thread

rbox

Recognized Developer
Apr 22, 2011
1,776
2,606
so I ran the first commands and it looks like I have boot.img in /system:
[email protected]:/system/boot # ls -l
ls -l
-rw------- root root 1675264 2014-11-21 18:19 boot.img

My concern is that I don't have any free space in system at all:
/system 756M 756M 0K 4096

is this normal to be this tight on the 51.1.4.0 prerooted rom?
I have even removed WhisperplayCore.apk when I was trying to get the chromecast receiver app working (sadly looks like that's fruitless at this point, but that's a separate topic)

I haven't copied the bootmenu image over just incase there is an issue with that boot.img that may not have been a full copy or something. Just trying to be extra careful.

No, that's not normal. Are you sure you haven't modified it? You could try deleting the Freetime apk I suppose.

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.

Ah, I'll update it.
 

ImCoKeMaN

Senior Member
Jan 8, 2007
213
54
No, that's not normal. Are you sure you haven't modified it? You could try deleting the Freetime apk I suppose.

.

Well I tried modifying it to run the cast receiver, but that isn't too big. I've had a previous stock image before. Is there any chance it added files to /system instead of flashing the whole partition? I'm not sure what the expected free space is. I've also had the xposed framework for google play store, but if I remember correctly the first thing I did after flashing the rooted image was try the cast receiver and it said I didn't have enough space. then I removed that apk instead of just renaming it.

clearly I can remove that since it's now useless, but I did want to know if it may be something else I should test for first, or reflash etc.
 

rbox

Recognized Developer
Apr 22, 2011
1,776
2,606
Well I tried modifying it to run the cast receiver, but that isn't too big. I've had a previous stock image before. Is there any chance it added files to /system instead of flashing the whole partition? I'm not sure what the expected free space is. I've also had the xposed framework for google play store, but if I remember correctly the first thing I did after flashing the rooted image was try the cast receiver and it said I didn't have enough space. then I removed that apk instead of just renaming it.

clearly I can remove that since it's now useless, but I did want to know if it may be something else I should test for first, or reflash etc.

I would recommend flashing the bootmenu first, then flashing 51.1.4.1+fixed from recovery. That'll wipe /system and install the kernel in the proper location.
 

qwertywarez

Member
Feb 7, 2009
31
0
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)

rbox, I'm having a hell of a difficult time booting into recovery from either stock or CWM. It just sits on the white Amazon logo. I was thinking that flashing this new boot menu might fix that problem. I am currently rooted on 5.1.1.0.1 with CWM latest version. I just never was able to boot into recovery. What do you recommend? Should I attempt to flash this to try to fix the boot to recovery?

Thanks
 

rbox

Recognized Developer
Apr 22, 2011
1,776
2,606
rbox, I'm having a hell of a difficult time booting into recovery from either stock or CWM. It just sits on the white Amazon logo. I was thinking that flashing this new boot menu might fix that problem. I am currently rooted on 5.1.1.0.1 with CWM latest version. I just never was able to boot into recovery. What do you recommend? Should I attempt to flash this to try to fix the boot to recovery?

Thanks

As the OP states... you MUST verify you can boot recovery before even thinking about using bootmenu. If you can't boot into recovery you didn't install it properly and then installing bootmenu will brick your box.

Although your statement "I'm having a hell of a difficult time booting into recovery from either stock or CWM" makes no sense, because CWM is recovery. How can you not boot into recovery from recovery...
 

qwertywarez

Member
Feb 7, 2009
31
0
As the OP states... you MUST verify you can boot recovery before even thinking about using bootmenu. If you can't boot into recovery you didn't install it properly and then installing bootmenu will brick your box.

Although your statement "I'm having a hell of a difficult time booting into recovery from either stock or CWM" makes no sense, because CWM is recovery. How can you not boot into recovery from recovery...

What I meant was that reboot recovery hangs whether stock or CWM is installed. Flashing recovery seems to work though in adb.
 

ImCoKeMaN

Senior Member
Jan 8, 2007
213
54
I would recommend flashing the bootmenu first, then flashing 51.1.4.1+fixed from recovery. That'll wipe /system and install the kernel in the proper location.

I removed freetime.apk for the time being to copy the boot.img over just to test bootmenu works before the new flash, looks bigger now:
[email protected]:/system/boot # ls -l
ls -l
-rw------- root root 10485760 2014-11-22 16:45 boot.img

and I have 13mb free so I'm more comfortable. I'm about to test it and flash the new 51.1.4.1 now.

UPDATE: Flashed and working, the previous space issue was clearly from the cast receiver, not reinstalling as much as I'd love that functionality. Thanks for all your work and support rbox!
 
Last edited:

jessenj

Senior Member
May 2, 2008
75
13
Im stuck but not where everyone else is. My unit boots to the Rbox's Boot Menu screen, shows me both options to boot kernel and launch recovery, and the timer counts down from 5 to 0, but when it reaches 0, it just hangs there. I only have the keyboard installed, and I had just installed completely all the needed steps to update from the last version of CWM to the latest "a" version. What do you think I can do at this point? It's just doing the countdown and then nothing.

Actually - I wanted to update this. I was able to get to the Recovery option, it's the booting into Kernel option, so I put the latest custom rom zip on a usb drive, and as long as I booted with just the keyboard connected to the usb hub, CWM loads fine, and then I was able to pop my usb drive into another port and CWM recognized it as a storage device, so now I'm installing the latest custom zip and will say a little prayer in the meantime.

---------- Post added at 03:42 PM ---------- Previous post was at 03:27 PM ----------

Im stuck but not where everyone else is. My unit boots to the Rbox's Boot Menu screen, shows me both options to boot kernel and launch recovery, and the timer counts down from 5 to 0, but when it reaches 0, it just hangs there. I only have the keyboard installed, and I had just installed completely all the needed steps to update from the last version of CWM to the latest "a" version. What do you think I can do at this point? It's just doing the countdown and then nothing.

Actually - I wanted to update this. I was able to get to the Recovery option, it's the booting into Kernel option, so I put the latest custom rom zip on a usb drive, and as long as I booted with just the keyboard connected to the usb hub, CWM loads fine, and then I was able to pop my usb drive into another port and CWM recognized it as a storage device, so now I'm installing the latest custom zip and will say a little prayer in the meantime.

Well - I answered my own question. The install from zip on usb drive WORKED LIKE A CHARM and now I'm getting the system to install the updates. I figured rather than delete this, I'll leave it here in case anyone else has the same issue.
 
Last edited:

mroneeyedboh

Senior Member
Feb 14, 2008
1,865
490
That happened to me. I needed to flash his boot menu and then boot to recovery then mount and copy over the new FW. Flash that, then it worked.

The new FW tells the boot menu where the kernel is or something...
 

mastermind278

Senior Member
Nov 29, 2006
104
65
NJ
Im stuck but not where everyone else is. My unit boots to the Rbox's Boot Menu screen, shows me both options to boot kernel and launch recovery, and the timer counts down from 5 to 0, but when it reaches 0, it just hangs there. I only have the keyboard installed, and I had just installed completely all the needed steps to update from the last version of CWM to the latest "a" version. What do you think I can do at this point? It's just doing the countdown and then nothing.

Actually - I wanted to update this. I was able to get to the Recovery option, it's the booting into Kernel option, so I put the latest custom rom zip on a usb drive, and as long as I booted with just the keyboard connected to the usb hub, CWM loads fine, and then I was able to pop my usb drive into another port and CWM recognized it as a storage device, so now I'm installing the latest custom zip and will say a little prayer in the meantime.


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.
 
Last edited:

Tenny

Senior Member
Jul 10, 2007
688
27
38
Houston, TX
www.tenfpv.com
It looks like I'm stuck on this one...

I have 51.1.0.1 installed.
I have CWM 6.0.5.1.4a installed

Now I just installed this boot menu, and it gets to the selection screen. Unfortunately I have tried three different keyboards and none of them seem to be working at all for me. I cannot move the item down to "Launch Recovery" to install 51.1.4.1.

They keyboards at least slightly work as when I press ctrl-alt-delete it does reboot the FireTV. Although that's about all I can do at this point. It obviously won't boot (as it's running 51.1.0.1) and I can't select recovery.

ADB won't connect (didn't think it would, but it was worth a shot).

Any suggestions?


EDIT:
Duh, not sure what it was but after enough alt control deletes and alt i prt screens the keyboard starting working... So if you get stuck in the same spot maybe try those two combos (it seemed the later was the better one).
 
Last edited:

rbox

Recognized Developer
Apr 22, 2011
1,776
2,606
They keyboards at least slightly work as when I press ctrl-alt-delete it does reboot the FireTV. Although that's about all I can do at this point. It obviously won't boot (as it's running 51.1.0.1) and I can't select recovery.

ADB won't connect (didn't think it would, but it was worth a shot).

Any suggestions?

If you had followed the instructions it would have no problem booting 51.1.0.1... Are you sure you are pressing the correct arrow keys?

Using the sysrq trick enough times would probably trigger it to go in to recovery.
 
  • Like
Reactions: Tenny

philo_enyce

Member
Feb 10, 2006
38
3
bricked it...

sorry to be the chowderhead who posts this, but i'm hoping against hope that i'm not boned here.

i managed to get the boot menu installed prior to getting cwm installed. i was using imtiaj meah's firetv utility app and did the steps out of order. when the firetv boots it gets to the rbox boot menu, but won't boot the kernel, it just sits there and if i try and launch recovery, i get the amazon system update unsuccessful screen. is there any way of getting around this?
 

rbox

Recognized Developer
Apr 22, 2011
1,776
2,606
any chance the USB can be used to receive adb commands? i can get to the android system recovery menu as described here - http://www.aftvnews.com/how-to-unbr...ry-mode-and-factory-reset-the-amazon-fire-tv/ - but don't have the right usb cable to connect from my computer. i tried to use my nexus 5, but don't know how to get the usb into the right mode to connect to the firetv, if i do an adb devices command nothing is listed.

The Fire TV doesn't support ADB over USB.
 

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.