FORUMS
Remove All Ads from XDA

FireTV Boot Menu 1.0

1,590 posts
Thanks Meter: 1,969
 
By rbox, Recognized Developer on 15th November 2014, 10:20 PM
Post Reply Email Thread
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)
The Following 23 Users Say Thank You to rbox For This Useful Post: [ View ]
 
 
16th November 2014, 12:21 AM |#2  
Member
Thanks Meter: 6
 
More
Hmm, tried this and didn't seem to do anything. It did sit at the black screen for a while but then no boot menu comes up. Tried rebooting normally and to recovery but either way no boot menu come up, just boots straight to recovery or to XBMC (I've set XBMC as my launcher).

I'm using your 6.0.5.1.4a recovery, bootloader partially unlocked etc.
16th November 2014, 12:28 AM |#3  
OP Recognized Developer
Thanks Meter: 1,969
 
Donate to Me
More
Quote:
Originally Posted by AQKhanTheOne

Hmm, tried this and didn't seem to do anything. It did sit at the black screen for a while but then no boot menu comes up. Tried rebooting normally and to recovery but either way no boot menu come up, just boots straight to recovery or to XBMC (I've set XBMC as my launcher).

I'm using your 6.0.5.1.4a recovery, bootloader partially unlocked etc.

It's completely blank? I timed from 'adb reboot' to when the menu showed up and it was 24 seconds. Then you should see *something* on the screen, and then 5 seconds later it should reboot the firetv and then the kernel should start loading. 25 seconds after adb reboot, try hitting the down arrow and then waiting a few seconds. It should boot into recovery. Does that work? Also, are you using overscan in recovery?
16th November 2014, 12:49 AM |#4  
Member
Thanks Meter: 6
 
More
Yes completely blank. Actually it only sat at the blank/black screen the first time it rebooted after the install. After that each reboot to either recovery or to XBMC does not result in the long blank screen at all. Though there is the briefest lightening of the screen right before the white amazon logo comes up. And no, I'm not using overscan. The result of the install is below if that helps. It's likely I've made a mistake.

Code:
shell@android:/ $ 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
smount -o remount,ro /system
u
dd if=/sdcard/bootmenu.img of=/dev/block/platform/msm_sdcc.1/by-name/bootmount -
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
root@android:/ # mount -o remount,rw /system
root@android:/ # mkdir /system/boot
dcc.1/by-name/boot of=/system/boot/boot.img                                   <
20480+0 records in
20480+0 records out
10485760 bytes transferred in 1.939 secs (5407818 bytes/sec)
root@android:/ # mount -o remount,ro /system
root@android:/ # exit
16th November 2014, 01:01 AM |#5  
OP Recognized Developer
Thanks Meter: 1,969
 
Donate to Me
More
Quote:
Originally Posted by AQKhanTheOne

Yes completely blank. Actually it only sat at the blank/black screen the first time it rebooted after the install. After that each reboot to either recovery or to XBMC does not result in the long blank screen at all. Though there is the briefest lightening of the screen right before the white amazon logo comes up.

Well it has no effect on recovery, just the main system. It should do it every time. Not quite sure why you aren't seeing it though.
16th November 2014, 01:04 AM |#6  
Member
Thanks Meter: 6
 
More
Quote:
Originally Posted by rbox

Well it has no effect on recovery, just the main system. It should do it every time. Not quite sure why you aren't seeing it though.

I did rename the downloaded file to bootmenu.img to avoid having to change the name in the shell command. Don't know if that makes a difference.
16th November 2014, 01:15 AM |#7  
OP Recognized Developer
Thanks Meter: 1,969
 
Donate to Me
More
Quote:
Originally Posted by AQKhanTheOne

I did rename the downloaded file to bootmenu.img to avoid having to change the name in the shell command. Don't know if that makes a difference.

No, the name doesn't matter. Try this version. It should have a solid blue background to start and then if you hit the down arrow it'll switch to red. Blue will boot the kernel, red will boot recovery.

EDIT: Okay. I reread your post and saw you included the output from the shell. Don't copy paste it all at once. Do the commands one at a time.
16th November 2014, 01:49 AM |#8  
Member
Thanks Meter: 6
 
More
Quote:
Originally Posted by rbox

No, the name doesn't matter. Try this version. It should have a solid blue background to start and then if you hit the down arrow it'll switch to red. Blue will boot the kernel, red will boot recovery.

EDIT: Okay. I reread your post and saw you included the output from the shell. Don't copy paste it all at once. Do the commands one at a time.

Okay, that did the trick! Now I get the colorful Rbox's Boot Menu with two options, Boot Kernal and Boot to recovery.

Thanks as always for all your great work!
16th November 2014, 05:06 AM |#9  
Senior Member
Flag Around Town
Thanks Meter: 43
 
More
Well this looks like its going to be handy.
In with no issues Rbox and countdown

Idea: Press and hold key on the remote or keyboard to get to boot-menu (unsure if this can be done)
Press nothing boots to FTV

Thanks
16th November 2014, 05:43 PM |#10  
Senior Member
Flag Sarnia
Thanks Meter: 34
 
More
Works perfect here, the remote doesnt work tho right? need to use a keyboard?
16th November 2014, 09:21 PM |#11  
OP Recognized Developer
Thanks Meter: 1,969
 
Donate to Me
More
Quote:
Originally Posted by nhumber

Works perfect here, the remote doesnt work tho right? need to use a keyboard?

Yeah. Just like recovery it needs the keyboard.
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes