Fire TV Rbox boot - Fire TV Q&A, Help & Troubleshooting

I made a mistake somewhere and now I'm at the rbox boot screen and I can get to pick a kernal or anything,so my question, is there a alternative to get back to the main TV screen without a USB keyboard?

droidkill3r said:
I made a mistake somewhere and now I'm at the rbox boot screen and I can get to pick a kernal or anything,so my question, is there a alternative to get back to the main TV screen without a USB keyboard?
Click to expand...
Click to collapse
If, after the boot menu timer ends, you are not taken to the Fire TV home screen, then you're only option is to use a USB keyboard to select "Recovery" on the boot menu. Once in recovery, you should re-install the 51.1.4.1 pre-rooted ROM.

On thank you

droidkill3r said:
I made a mistake somewhere and now I'm at the rbox boot screen and I can get to pick a kernal or anything,so my question, is there a alternative to get back to the main TV screen without a USB keyboard?
Click to expand...
Click to collapse
From v34 of the Amazon FireTV Utility App BootMenu will be installed by a couple clicks of the mouse. But first you need to reflash PreRooted bueller-51.1.4.0_514006420-rooted+updated.zip to get rid of the bad BootMenu installation.
http://forum.xda-developers.com/showpost.php?p=57598814&postcount=629
http://forum.xda-developers.com/showpost.php?p=57604431&postcount=638

Y314K said:
From v34 of the Amazon FireTV Utility App BootMenu will be installed by a couple clicks of the mouse. But first you need to reflash PreRooted bueller-51.1.4.0_514006420-rooted+updated.zip to get rid of the bad BootMenu installation.
http://forum.xda-developers.com/showpost.php?p=57598814&postcount=629
http://forum.xda-developers.com/showpost.php?p=57604431&postcount=638
Click to expand...
Click to collapse
yes well I don't have cwm recovery , just stock.. I tried a factory reset but still get kicked into rbox boot menu

droidkill3r said:
yes well I don't have cwm recovery , just stock.. I tried a factory reset but still get kicked into rbox boot menu
Click to expand...
Click to collapse
Requirement to install RBox's BootMenu:
Root with SuperSU & BusyBox.
Partially Unlock Bootloader.
Install latest Custom Recovery - v6.0.5.1.4a
Install PreRooted FW bueller-51.1.4.0_514006420-rooted+updated.zip
THEN YOU CAN START TO ATTEMP TO INSTALL RBOX's BOOTMENU. IF YOU ARE TRYING TO INSTALL IT WITHOUT THIS REQUIREMENTS. YOU ARE JUST GONNA BRICK YOUR FTV.
rbox said:
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)
Click to expand...
Click to collapse

Y314K said:
Requirement to install RBox's BootMenu:
Root with SuperSU & BusyBox.
Partially Unlock Bootloader.
Install latest Custom Recovery - v6.0.5.1.4a
Install PreRooted FW bueller-51.1.4.0_514006420-rooted+updated.zip
THEN YOU CAN START TO ATTEMP TO INSTALL RBOX's BOOTMENU. IF YOU ARE TRYING TO INSTALL IT WITHOUT THIS REQUIREMENTS. YOU ARE JUST GONNA BRICK YOUR FTV.
Click to expand...
Click to collapse
I did brick it, just try to unbrick it

droidkill3r said:
I did brick it, just try to unbrick it
Click to expand...
Click to collapse
To be able to help will need to know more about where you are at. Did you at least meet the first 2 requirements ? What Stock FW was your FTV @ when it begin to loop ??

I am rooted and installed supersu and partially unlock bootloader. use the firetv utility app. in rbox menu I click boot kernel and it just freezes. I can get to stock recovery to factory reset and can use the sideload option but vant connect pc to firetv via adb

droidkill3r said:
I am rooted and installed supersu and partially unlock bootloader. use the firetv utility app. in rbox menu I click boot kernel and it just freezes. I can get to stock recovery to factory reset and can use the sideload option but vant connect pc to firetv via adb
Click to expand...
Click to collapse
Never encounter one that wouldn't ADB. Maybe @rbox will know the best way forward.

Y314K said:
Never encounter one that wouldn't ADB. Maybe @rbox will know the best way forward.
Click to expand...
Click to collapse
well I read once you factory reset you lose adb. so its looking like its gonna be a paper weight

Related

[Q] REMOVING TWRP software

I have just downloaded the twrp software today on my kindle fire. It wont download any of the custom ROMs so I am just stuck on this screen. I even called Amazon and they couldnt help me...
Does anybody know how to remove TWRP from the kindle and set it back to the default system and its normal setup??
You called amazon and asked about twrp? Lol.
Sent from my Kindle Fire using XDA
mtdulmag said:
I have just downloaded the twrp software today on my kindle fire. It wont download any of the custom ROMs so I am just stuck on this screen. I even called Amazon and they couldnt help me...
Does anybody know how to remove TWRP from the kindle and set it back to the default system and its normal setup??
Click to expand...
Click to collapse
I'm sure that for you, this is not amusing. But for me, its funny for so many reasons. We'll fix you up, don't worry. But first let me explain a few things.
When you make any alterations to Amazon's proprietary Kindle Fire interface such as rooting or installing custom recovery, you void your warranty and in the process waive certain benefits like Amazon customer service.
But since you have already done that, you want to make sure you have good fail safes to protect your investment. Of course one of those fail safes is custom recovery (TWRP). Removing it at this point with the skill level you are at right now is a VERY BAD IDEA.
The good news is, your Kindle is not broken. In fact, its doing exactly what it was designed to do, although its pretty hard for you to see that at the moment.
So the first thing you need to do is read this
http://forum.xda-developers.com/showthread.php?p=23747567
And come back when you are done
Sent from my Amazon Kindle Fire using xda premium
mtdulmag said:
I have just downloaded the twrp software today on my kindle fire. It wont download any of the custom ROMs so I am just stuck on this screen. I even called Amazon and they couldnt help me...
Does anybody know how to remove TWRP from the kindle and set it back to the default system and its normal setup??
Click to expand...
Click to collapse
I'm guessing thousands of people have used TWRP successfully to get ROMs installed, so I suspect something else is going on. Maybe you'd like to give this a read...
http://forum.xda-developers.com/showthread.php?t=1552547
so you can get an idea of how things work. Then if you want to explain...
1) what you did so far and how you did it
2) how you are trying to install ROMs
3) exactly what your Kindle Fire is doing
I or someone else here can help you get where you are going. Whether that's flashing a new rom or going back to stock, that's up to you.
As a side note, calling Amazon to tell them you've voided the warranty by flashing unauthorized software and then asking for help is probably not a good idea.
EDIT: There were no replies yet when I started typing.
Next Step
Alright I have read the thread from that link, now what is the next step?
It could be the cable. When you download stuff, always try at least 5 times. I always have to anyway.
Haha to calling Amazon by the way.
mtdulmag said:
I have just downloaded the twrp software today on my kindle fire. It wont download any of the custom ROMs so I am just stuck on this screen. I even called Amazon and they couldnt help me...
Does anybody know how to remove TWRP from the kindle and set it back to the default system and its normal setup??
Click to expand...
Click to collapse
Lol, to calling Amazon. Stick in there buddy a few months ago I was also a totl noob. It gets easier and there are lots of peeps here that can help you with pretty much any problem. A little bit of searching help too. What I do before I even start downloading ROM's, mod's or, add-ons, I do a bit of research. That way I where to look again if I bork something.
kindle gen 1 twrp
Hey I have a KF 1st gen that I have rooted. Currently it is I guess stuck in twrp. It is holding the blue and white KF logo. I can use the power button to go into boot mode/twrp to reboot. However once past that area it will immediately power down. And truly I would liketo go back to stock rom.
lonnia said:
Hey I have a KF 1st gen that I have rooted. Currently it is I guess stuck in twrp. It is holding the blue and white KF logo. I can use the power button to go into boot mode/twrp to reboot. However once past that area it will immediately power down. And truly I would liketo go back to stock rom.
Click to expand...
Click to collapse
Your in Bootloader, and Twrp is not working correctly
You will need to flash twrp to fix.
See How to flash twrp and firefirefire with a Fastboot cable
http://forum.xda-developers.com/showpost.php?p=53652317&postcount=2
Shows basic steps, you have Bootloader, so don't need the fastboot cable, so download adb files, and twrp.IMG
And use
Code:
fastboot flash recovery twrpfilename
Fastboot reboot
Sent from my Amazon OtterX using Tapatalk
KF1 flashed with TWRP 2.2.21-blaze/CM11 OtterX Nightly
Successfully flashed the above TWRP on a KF1, and then used it to install CM11 OtterX Nightly the latest (10-04-2015) build.
Now it's stuck in boot loading.
Reentering TWRP console, which I can do--I have full TWRP, but I no longer have any Zips to install from. (My SDCard was wiped.)
I've tried to use ADB to push (after struggling with the drivers) the build back to my KF1, but I find I don't have permissions set up correctly.
I did reflash TWRP as is recommended below, but that did not help the boot load freeze.
Can I use ADB to push the build back for a reinstall? Can I use fastboot to push it?
What is the proper course to recover this KF1?
BTW, I do not have a factory cable.
Thanks for the help!
sd_shadow said:
Your in Bootloader, and Twrp is not working correctly
You will need to flash twrp to fix.
See How to flash twrp and firefirefire with a Fastboot cable
http://forum.xda-developers.com/showpost.php?p=53652317&postcount=2
Shows basic steps, you have Bootloader, so don't need the fastboot cable, so download adb files, and twrp.IMG
And use
Code:
fastboot flash recovery twrpfilename
Fastboot reboot
Sent from my Amazon OtterX using Tapatalk
Click to expand...
Click to collapse
rustynail33 said:
Successfully flashed the above TWRP on a KF1, and then used it to install CM11 OtterX Nightly the latest (10-04-2015) build.
Click to expand...
Click to collapse
TWRP 2.2.21-blaze is not compatible with any roms with "OtterX" , CM11, or CM12
"Otter" CM 11 requires Twrp 2.7.1.0 or newer
see Kindle Fire Flashable Recoveries/FFF TWRP/COTR/CWM
OtterX roms require OtterX bootloader, and OtterX Twrp
see [How To] Fix Otter X Install Errors, Partition sizes, Unable to Mount System.
---------- Post added at 06:33 PM ---------- Previous post was at 06:26 PM ----------
I no longer have any Zips to install from. (My SDCard was wiped.)
I've tried to use ADB to push (after struggling with the drivers) the build back to my KF1, but I find I don't have permissions set up correctly.
Click to expand...
Click to collapse
what commands are you using? what error are you getting?
BTW, I do not have a factory cable.
Click to expand...
Click to collapse
Factory cable is not needed if you have a custom bootloader
Thanks to your help SD I was able to install the Otter CM 11!
Now, I'm trying to install the ZIP of Open Gapps Nano for 11, and TWRP is reporting that I don't have enough space.
More investigation!
rustynail33 said:
Successfully flashed the above TWRP on a KF1, and then used it to install CM11 OtterX Nightly the latest (10-04-2015) build.
Now it's stuck in boot loading.
Reentering TWRP console, which I can do--I have full TWRP, but I no longer have any Zips to install from. (My SDCard was wiped.)
I've tried to use ADB to push (after struggling with the drivers) the build back to my KF1, but I find I don't have permissions set up correctly.
I did reflash TWRP as is recommended below, but that did not help the boot load freeze.
Can I use ADB to push the build back for a reinstall? Can I use fastboot to push it?
What is the proper course to recover this KF1?
BTW, I do not have a factory cable.
Thanks for the help!
Click to expand...
Click to collapse
rustynail33 said:
Thanks to your help SD I was able to install the Otter CM 11!
Now, I'm trying to install the ZIP of Open Gapps Nano for 11, and TWRP is reporting that I don't have enough space.
More investigation!
Click to expand...
Click to collapse
what's the full file name? size?
So, SD, I was able to install the pico Open Apps after installing gaps-kk. When that had me hanging in boot, I entered TWRP again and then did a wipe. On a whim, I rebooted into TWRP after the wipe, and tried to install the PICO OpenGapp zip. And, it installed!
I rebooted, and now I have GAPPS!
Can't explain it, but now it works. Thanks for all your help!
sd_shadow said:
what's the full file name? size?
Click to expand...
Click to collapse

[Q] TWRP Help.

Hello:
I have an Amazon Kindle fire that I rooted with KFU 0.9.5 and am running CWM Recovery, FireFireFire v1.4, and MoCaDo (Current Version: 6.3_user_4019920 (MoDaCo Custom ROM Gr8).
I want to try another ICS ROM. I was told that I need to flash TWRP 2.1 to get the later ICS ROMS to work correctly.
So my questions are:
1) Do I really need TWRP?
2) How do I flash TWRP? (All the pages are assuming your running unrooted stock)
3) Do the ICS ROMs update the Kernel version, or is it still andriod 2.3.whatever
Thank you
Kyle
kylebenton said:
Hello:
I have an Amazon Kindle fire that I rooted with KFU 0.9.5 and am running CWM Recovery, FireFireFire v1.4, and MoCaDo (Current Version: 6.3_user_4019920 (MoDaCo Custom ROM Gr8).
I want to try another ICS ROM. I was told that I need to flash TWRP 2.1 to get the later ICS ROMS to work correctly.
So my questions are:
1) Do I really need TWRP?
2) How do I flash TWRP? (All the pages are assuming your running unrooted stock)
3) Do the ICS ROMs update the Kernel version, or is it still andriod 2.3.whatever
Thank you
Kyle
Click to expand...
Click to collapse
1. Yes, you really need TWRP.
2. Check this thread. Post #2 has the command you can use to flash TWRP after you've downloaded it. http://forum.xda-developers.com/showthread.php?t=1621208
3. Most of the ICS ROM's right now are using Hash's latest 3.0 ICS kernel.
kylebenton said:
Hello:
I have an Amazon Kindle fire that I rooted with KFU 0.9.5 and am running CWM Recovery, FireFireFire v1.4, and MoCaDo (Current Version: 6.3_user_4019920 (MoDaCo Custom ROM Gr8).
I want to try another ICS ROM. I was told that I need to flash TWRP 2.1 to get the later ICS ROMS to work correctly.
So my questions are:
1) Do I really need TWRP?
2) How do I flash TWRP? (All the pages are assuming your running unrooted stock)
3) Do the ICS ROMs update the Kernel version, or is it still andriod 2.3.whatever
Thank you
Kyle
Click to expand...
Click to collapse
You do need TWRP for the newer ICS roms to install properly.
Depending on your comfort level, there are generally two ways to install recovery; command line method in fastboot mode or from within the working rom using either scripts or the Terminal Emulator app.
The command line method is easiest but can be troublesome if your drivers aren't in working order, plus you need to have a clear understanding of how to use fastboot.
To use the fastboot method turn your device off and with your command prompt ready to accept fastboot commands, enter:
Code:
fastboot flash recovery /path/to/twrp2.1.img
...when you see "waiting for device", turn it on and TWRP will be installed. You must use TWRP 2.1 with that command or it won't work.
To install it from within the rom, the safest method is using a script. User smirkis has created a tool called "Smirkit" that will do the work for you. Follow the instructions on his thread to install, reboot, and it should be installed.
The method from within the rom, which is significantly less safe than the others, is through the Terminal Emulator. It is less safe because it involves using a command to directly overwrite a particular partition. Writing the command incorrectly, or choosing the wrong partition number can seriously brick your device. But if this is the route you want to take, place the twrp2.1.img on your sdcard, open the Terminal Emulator app and enter:
Code:
su
dd if=/sdcard/twrp2.1.img of=/dev/block/mmcblk0p5
...then reboot.
--Edited to fix stupidity--
soupmagnet never sleeps, ever vigilant. I picture him watching over the forums in a costume, with a cape and a big "S" on the chest...you know, for "soupmagnet man."
soupmagnet said:
You do need TWRP for the newer ICS roms to install properly.
Depending on your comfort level, there are generally two ways to install recovery; command line method in fastboot mode or from within the working rom using either scripts or the Terminal Emulator app.
The command line method is easiest but can be troublesome if your drivers aren't in working order, plus you need to have a clear understanding of how to use fastboot.
To use the fastboot method turn your device off and with your command prompt ready to accept fastboot commands, enter:
Code:
fastboot flash recovery /path/to/twrp2.1.img
...when you see "waiting for device", turn it on and TWRP will be installed. You must use TWRP 2.1 with that command or you'll lose FFF1.4
To install it from within the rom, the safest method is using a script. User smirkis has created a tool called "Smirkit" that will do the work for you. Follow the instructions on his thread to install, reboot, and it should be installed.
The method from within the rom, which is significantly less safe than the others, is through the Terminal Emulator. It is less safe because it involves using a command to directly overwrite a particular partition. Writing the command incorrectly, or choosing the wrong partition number can seriously brick your device. But if this is the route you want to take, place the twrp2.1.img on your sdcard, open the Terminal Emulator app and enter:
Code:
su
dd if=/sdcard/twrp2.1.img of=/dev/block/mmcblk0p5
...then reboot.
Click to expand...
Click to collapse
Thank you guys.
I took the Terminal Emulator route (I live on the edge )
Downloaded the app, moved the .img to my device, entered the code as Soup wrote it
... and rebooted.
It booted in normal mode and was like wth?!? So I rebooted again and pressed the power key to get to recovery.
That did it, I am now looking at TWRP v2.1.1
Backing up now, Then rom testing time
Thanks again!
Kyle
Oh, one more,
Do I need to uninstall GO Launcher EX before I flash a new ROM?
When I flash MoCaDo from CWM before I got TWRP, the ROM flashed fine, but it still booted up GO Launcher.
Or do I just tell the Device no to autostart GO Launcher?
Thanks,
Kyle
koop1955 said:
soupmagnet never sleeps, ever vigilant. I picture him watching over the forums in a costume, with a cape and a big "S" on the chest...you know, for "soupmagnet man."
Click to expand...
Click to collapse
Koop, Truer words were never spoken
Kyle
kylebenton said:
Oh, one more,
Do I need to uninstall GO Launcher EX before I flash a new ROM?
When I flash MoCaDo from CWM before I got TWRP, the ROM flashed fine, but it still booted up GO Launcher.
Or do I just tell the Device no to autostart GO Launcher?
Thanks,
Kyle
Click to expand...
Click to collapse
MoDaCo probably came with GO Launcher EX, which is why it was there when you started up.
koop1955 said:
soupmagnet never sleeps, ever vigilant. I picture him watching over the forums in a costume, with a cape and a big "S" on the chest...you know, for "soupmagnet man."
Click to expand...
Click to collapse
I'm not sure if I should be offended by that or not.
soupmagnet said:
I'm not sure if I should be offended by that or not.
Click to expand...
Click to collapse
It's a compliment. If I could give you more than one "thanks" per post, I would.
You're like Batman.... for Android
Kyle
Strike 1
I tried AOPK and when I flashed it, the firefirefire came up and the screen went black....
I got back into recovery and did a restore so I'm back on MoCaDo.
TWRP works LOL.
I flashed the zip and wiped the cache before I rebooted. Did I miss a step?
Kyle
When switching to a different rom, especially one that's completely different; "factory reset", wipe system, wipe cache, and wipe dalvik, then install.
Gapps will likely need to be reinstalled as well.
soupmagnet said:
When switching to a different rom, especially one that's completely different; "factory reset", wipe system, wipe cache, and wipe dalvik, then install.
Gapps will likely need to be reinstalled as well.
Click to expand...
Click to collapse
Will that wipe my backup too?
I have all the .apk files for Google play and such on my PC, so I'm not worried about that. I just don't want to wipe my backup and have something go wrong.
Kyle
kylebenton said:
Will that wipe my backup too?
I have all the .apk files for Google play and such on my PC, so I'm not worried about that. I just don't want to wipe my backup and have something go wrong.
Kyle
Click to expand...
Click to collapse
No. There's another option for wiping the sdcard.
Awesome! ICS looks delicious.
However, I cannot get google play to work.
I installed the vending.apk, and it's in my app menu, but when I open it it just flashed real quick and I'm back at the home screen.
Kyle
kylebenton said:
Awesome! ICS looks delicious.
However, I cannot get google play to work.
I installed the vending.apk, and it's in my app menu, but when I open it it just flashed real quick and I'm back at the home screen.
Kyle
Click to expand...
Click to collapse
Forget about the vending.apk. You need to flash gapps while in recovery.
[Edit:] http://wiki.cyanogenmod.com/wiki/Latest_Version/Google_Apps
Oh, I forgot, I need to copy googleserviceframework into the /system/app folder.
I just can't get it to change to r\w so I can change the permissions and paste the file. What am I missing?
soupmagnet said:
Forget about the vending.apk. You need to flash gapps while in recovery.
[Edit:] http://wiki.cyanogenmod.com/wiki/Latest_Version/Google_Apps
Click to expand...
Click to collapse
...
soupmagnet said:
Forget about the vending.apk. You need to flash gapps while in recovery.
[Edit:] http://wiki.cyanogenmod.com/wiki/Latest_Version/Google_Apps
Click to expand...
Click to collapse
Sorry, I didn't get your first reply until now.
So I need the latest Cyanogenmod9.zip to flash GPlay in TWRP?
I was using APOK, but I restored back to MoCaDo so I'd have a functioning tablet until I had the time to sit down and really get into it.
Kyle
Sent from my Kindle Fire using XDA
kylebenton said:
So I need the latest Cyanogenmod9.zip to flash GPlay in TWRP?
Click to expand...
Click to collapse
Actually the filename should be "gapps-ics-20120317-signed.zip".
...and, yes.

Root attempt failing

I purchased a Kindle Fire for my wife, I want to root it to allow Google Play to be installed
I dl'd the KFU v0.9.6, got the ADB driver, installed, showing as a android composite device
I run the utility following these instructions
from the liliputing.com
it gets to this point, screen cap attached
and dies, it leaves me at the TWRP screen, I have recovered several times using this site here
rootkindlefire.com hot to /how-to-unrootunbrick-rooted-kindle-fire
I must have read 100 threads today but nothing seems to help
Any suggestions or should I just wait for a utility update?
I'm no expert but I have rooted my phones in the past and installed custom ROMs, I'm no developer by a long shot but I'm not out in the woods clueless either.
Thanks
Hopefully you have the latest FFF installed (blue Kindle Fire logo?). If so, when you see it, hold the power button until you see the boot options appear. Select normal or reset boot mode.
soupmagnet said:
Hopefully you have the latest FFF installed (blue Kindle Fire logo?). If so, when you see it, hold the power button until you see the boot options appear. Select normal or reset boot mode.
Click to expand...
Click to collapse
At the moment I am back to stock, kind of skittish as it seems I am not the only person having a similar issue
Well, looking at screenshot, I see that TWRP was installed successfully. As long as have that, you're good. You can use TWRP to install FFF and a new rom which fixes just about everything. When TWRP first installs it will reboot and leave your device in fastboot mode (stuck at boot logo). To fix it, simply change your bootmode. Using the latest FFF (blue Kindle Fire logo) is the easiest way, but it can also be done via command line.
Being "stuck" at the boot logo is a normal process of modifying the KF, it doesn't mean it's bricked. I suggest you take the time to read up on some Kindle Fire basics before you proceed.
http://forum.xda-developers.com/showpost.php?p=23747567
Read it, not to identify your exact problem like so many do, but to educate yourself on how this thing called Kindle Fire/Android works. If you've already read it, read it again. Doing so will help you and those trying to help you, tremendously.
I got the same screen last night as well. TWRP is installed as I can reboot into Normal/Recovery/Reset Boot..
I can use the KFU to reset the bootloader as well (normal/fastboot, etc)..
but for some reason, KFU doesn't seem to root my device when selecting option 2. I get the blue KF boot logo, can access TWRP, but then what? Do I need to install some other software?
I am soo confused...
I want to root my device so I can install programs. I would also like to install custom ROMs (which I understand that I do not NEED to be rooted to do this), but to install other programs I do.
iRock48 said:
I got the same screen last night as well. TWRP is installed as I can reboot into Normal/Recovery/Reset Boot..
I can use the KFU to reset the bootloader as well (normal/fastboot, etc)..
but for some reason, KFU doesn't seem to root my device when selecting option 2. I get the blue KF boot logo, can access TWRP, but then what? Do I need to install some other software?
I am soo confused...
I want to root my device so I can install programs. I would also like to install custom ROMs (which I understand that I do not NEED to be rooted to do this), but to install other programs I do.
Click to expand...
Click to collapse
Transfer the ROM you want to your sdcard and use TWRP to install it. Be sure to "factory reset" (wipe) before you install the ROM or there will be conflicts. It is usually a good idea to wipe cache and dalvik after the ROM installation. There's no need to root a custom ROM.
soupmagnet said:
Well, looking at screenshot, I see that TWRP was installed successfully. As long as have that, you're good. You can use TWRP to install FFF and a new rom which fixes just about everything. When TWRP first installs it will reboot and leave your device in fastboot mode (stuck at boot logo). To fix it, simply change your bootmode. Using the latest FFF (blue Kindle Fire logo) is the easiest way, but it can also be done via command line.
Being "stuck" at the boot logo is a normal process of modifying the KF, it doesn't mean it's bricked. I suggest you take the time to read up on some Kindle Fire basics before you proceed.
http://forum.xda-developers.com/showpost.php?p=23747567
Read it, not to identify your exact problem like so many do, but to educate yourself on how this thing called Kindle Fire/Android works. If you've already read it, read it again. Doing so will help you and those trying to help you, tremendously.
Click to expand...
Click to collapse
Thanks, I reread it last night and will do so again, will likely get back to this over the weekend
soupmagnet said:
Transfer the ROM you want to your sdcard and use TWRP to install it. Be sure to "factory reset" (wipe) before you install the ROM or there will be conflicts. It is usually a good idea to wipe cache and dalvik after the ROM installation. There's no need to root a custom ROM.
Click to expand...
Click to collapse
Thank you for the reply. I assume to transfer the ROM I want I'd use something like Window Explorer to drag/drop or should I use the command language?
Wiping the cache and dalvik - is that also done through TWRP?
one last thing; it is my understanding that once you install a custom ROM, you have "root" access.. will this access allow me to install the App Store/Android Market and install apps that normally require root, such as Titanium backup?
iRock48 said:
Thank you for the reply. I assume to transfer the ROM I want I'd use something like Window Explorer to drag/drop or should I use the command language?
Click to expand...
Click to collapse
In TWRP you can use "abd push" or there is "mount" function that it comes with that will allow you to mount your sdcard as an external drive, much like with the stock Amazon software.
Wiping the cache and dalvik - is that also done through TWRP?
Click to expand...
Click to collapse
Yes, after you install the ROM, you'll be given the option to.
one last thing; it is my understanding that once you install a custom ROM, you have "root" access.. will this access allow me to install the App Store/Android Market and install apps that normally require root, such as Titanium backup?
Click to expand...
Click to collapse
Yes, but the "Market" (Google Play) must be installed in TWRP as a "gapps" package. Just Google gapps for the version of android you're installing (CM10-JB, CM9-ICS, or CM7-GB).
ye i have the same issue "mv: can't rename '/system/bin/check_rooted': No such file or directory". I'm sitting at TWRP recovery screen, so I'm guessing just download rom of choice use the mount function to transfer the rom, full wipe and install. this should solve my getting no further in rooting process problem?
radici said:
ye i have the same issue "mv: can't rename '/system/bin/check_rooted': No such file or directory". I'm sitting at TWRP recovery screen, so I'm guessing just download rom of choice use the mount function to transfer the rom, full wipe and install. this should solve my getting no further in rooting process problem?
Click to expand...
Click to collapse
If your only error is "mv: can't rename '/system/bin/check_rooted': then chances are, you're already rooted. It just means there was no check_rooted file to rename, so you're good.
Not that it matters anyway because installing a custom ROM gives you "root" anyway.

Can't Get Into Recovery Mode

Following the steps provided by Team Win on http://teamw.in/project/twrp2/213, I flashed the pre lokid recovery img that they provided, however I can't access it, I get "Secure booting Error! Cause: boot certification verify"
My firmware is V50020d(seems to be a troublemaker)
Command used
Steps Taken:
1. Enter adb shell
2. Get root using su
3. dd if=/sdcard/openrecovery-twrp-2.8.0.1-awifi.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
How I try to enter recovery mode:
Power + Down, Release Power, Press and Hold Up + Power, Release All Three, Press Power again and again
Here are some suggestions:
First, go here
1. If you don't have root, see the instructions in the above thread to run ioroot.
2. To flash TWRP, follow the instructions in Step 3 of the first post.
3. After that, you can update to one of the later versions of TWRP here. TWRP 2.7.1.0 seems stable, not sure about the latest one
3. After you do that, you will probably want to flash your boot environment back to 4.2.2 base to avoid problems with AOSP roms that you might want to install later. If you're only going to use stock-based roms, you probably won't want to do this. Look here for instructions for that here.
woody1 said:
Here are some suggestions:
First, go here
1. If you don't have root, see the instructions in the above thread to run ioroot.
2. To flash TWRP, follow the instructions in Step 3 of the first post.
3. After that, you can update to one of the later versions of TWRP here. TWRP 2.7.1.0 seems stable, not sure about the latest one
3. After you do that, you will probably want to flash your boot environment back to 4.2.2 base to avoid problems with AOSP roms that you might want to install later. If you're only going to use stock-based roms, you probably won't want to do this. Look here for instructions for that here.
Click to expand...
Click to collapse
The linked provided only works for 20a and 20b, do you have a mehtod that works for 20d?
Oh, you will need to edit the .bat file to change the reference to 20b to 20d. That should do it.
woody1 said:
Oh, you will need to edit the .bat file to change the reference to 20b to 20d. That should do it.
Click to expand...
Click to collapse
So now the message is "Device Unlock, so Boot Success" however still no recovery mode.
Am I better off going back to stock and trying again?
kidanime3d said:
So now the message is "Device Unlock, so Boot Success" however still no recovery mode.
Am I better off going back to stock and trying again?
Click to expand...
Click to collapse
I just did this recently, starting with a stock recovery of 20d and ending up with root and TWRP, so I know this should work. First, do you have root? When you ran the bat file to install TWRP, did it appear to run successfully?
kidanime3d said:
So now the message is "Device Unlock, so Boot Success" however still no recovery mode.
Am I better off going back to stock and trying again?
Click to expand...
Click to collapse
Getting in to the recovery also seems to have a problem if the device has a cable plugged in. I find that If I do an adb reboot recovery and then I unplug the device it will enter recovery. I believe this issue is fixed in later recoveries but the one that you should now have on your device will not properly boot recovery with a cable connected.
woody1 said:
I just did this recently, starting with a stock recovery of 20d and ending up with root and TWRP, so I know this should work. First, do you have root? When you ran the bat file to install TWRP, did it appear to run successfully?
Click to expand...
Click to collapse
Flash stock via the LG Support Tool, then did everything again and now running CM11 M10
Beer
muiriddin said:
Getting in to the recovery also seems to have a problem if the device has a cable plugged in. I find that If I do an adb reboot recovery and then I unplug the device it will enter recovery. I believe this issue is fixed in later recoveries but the one that you should now have on your device will not properly boot recovery with a cable connected.
Click to expand...
Click to collapse
You were right adb caused an issue for some reason.
Beer

Update Didnt work Hangs on Logo

FireTV had original software and was rooted.
I used a web site on How to update a Rooted Amazon FireTV
http://www.aftvnews.com/how-to-upda...tv-to-the-latest-version-without-losing-root/
Unlocked bootloader
Installed ClockworkMod
Installed Busybox
Downloaded Pre Rooted Stock Software
Install went ok when it rebooted I have the FireTV Logo and it hangs
I can get to Recovery Mode using keyboard
I have Wiped Data/factory reset and I have Wiped Cache partition
Not sure what to do next
Not sure if i should try the install from zip again
Have you installed bootmenu as well?
No I didn't. If it was in the how to then I missed it
Which firmware file did you install?
If you see on all the newer firmwares on http://www.aftvnews.com/roms:
Boot Menu MUST be installed BEFORE installing this ROM or you will brick your Fire TV. Boot Menu and ClockworkMod are NOT the same thing.
You MUST first have installed Pre-Rooted ROM version 51.1.4.0 at some point before installing this version. You don’t have to downgrade to 51.1.4.0 if you are running a newer pre-rooted ROM. You just can’t skip from 51.1.3.0 or older straight to this version.
Click to expand...
Click to collapse
Yup your right. I installed a newer version that needed the bootloader so now im stuck. I tried the recovery with Fastboot Mode and the A to A usb cable but my computer didnt recognize the firetv. I can boot to CWM but im not sure what that gets me
Ok since I was able to boot into CMW I used adb push (an older version that didnt need the boot menu) to /sdcard/0/
and used that to install so Im back and working
Thanks
Cool congrats, follow that bootmenu guide before you upgrade again.
All i really wanted was the option in Developer options to turn on enable unknown install of apps. I have that now so unless anyone can suggest a reason to update to a newer version i think ill stay where im at.
need help
I have the same problem but i was trying to root it, is there a way you can send me instuctions on how you fixed the isues
trickyrick said:
Ok since I was able to boot into CMW I used adb push (an older version that didnt need the boot menu) to /sdcard/0/
and used that to install so Im back and working
Thanks
Click to expand...
Click to collapse
Do you have clockworkmode installed
trickyrick said:
All i really wanted was the option in Developer options to turn on enable unknown install of apps. I have that now so unless anyone can suggest a reason to update to a newer version i think ill stay where im at.
Click to expand...
Click to collapse
Same reason for upgrading from Windows 7 > Windows 8 > Windows 10. Improvements in the FireTV OS, bug fixes etc... , but to each their own.

Categories

Resources