Related
I have a first generation kindle fire, and was attempting to root the device using the kindle fire utility. So far, I had installed FFF and TWRP, but the tutorial I was following was outdated and by the time I realized this I had installed both utilities multiple times. It was on about the third attempt that the device froze.
The device is currently stuck on the boot screen with the "fire" in blue. In the top right corner, it says "v1.4a". At the bottom of the screen, it says "Press power button for boot menu". Unfortunately, the power button doesn't do anything; It doesn't shut the kindle down, doesn't enter the boot menu, nothing. When I have the kindle plugged into my windows 7 (64 bit) pc, a notification pops up saying "USB device not recognised". Sure enough, in the device manager window it shows up as "unknown device".
I've been searching for hours trying to find the solution but nothing matches the same problem. Any help would be greatly appreciated.
Crowbar Offensive said:
I have a first generation kindle fire, and was attempting to root the device using the kindle fire utility. So far, I had installed FFF and TWRP, but the tutorial I was following was outdated and by the time I realized this I had installed both utilities multiple times. It was on about the third attempt that the device froze.
The device is currently stuck on the boot screen with the "fire" in blue. In the top right corner, it says "v1.4a". At the bottom of the screen, it says "Press power button for boot menu". Unfortunately, the power button doesn't do anything; It doesn't shut the kindle down, doesn't enter the boot menu, nothing. When I have the kindle plugged into my windows 7 (64 bit) pc, a notification pops up saying "USB device not recognised". Sure enough, in the device manager window it shows up as "unknown device".
I've been searching for hours trying to find the solution but nothing matches the same problem. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Very informative...kudos to you.
Make sure the device is completely powered down (hold power button until it shuts off) and power it up again. When you see the Kindle Fire logo, press and hold the power button, or tap it repeatedly, and hopefully the boot menu will appear at the bottom.
Let's see if that works and we'll go from there.
Bob
soupmagnet said:
Very informative...kudos to you.
Make sure the device is completely powered down (hold power button until it shuts off) and power it up again. When you see the Kindle Fire logo, press and hold the power button, or tap it repeatedly, and hopefully the boot menu will appear at the bottom.
Let's see if that works and we'll go from there.
Click to expand...
Click to collapse
----------------------------------------------------------------------------------------------------------
I have exactly the same problem, with the same screen details. I tried your suggestion several times, with no response.
An old borrowed Windows 7 box got me nowhere - TWRP kept complaining that it couldn't connect, although I'd loaded adb. I quit when it started loading endless Explorer windows full of crapware and became unresponsive. I'm totally lost with Windows, anyway, so I just hit the wall switch to end to pain.
I'm running debian sid and I'm much happier with linux, after using it exclusively for well over ten years, although I'm an experienced user rather than an expert.
I've pried the back off my Kindle, but I'm afraid to touch the inside, except as a last resort. I downloaded SoupKit, but can't decompress it.
What's the best thing to try next?
Paleoflatus said:
----------------------------------------------------------------------------------------------------------
I have exactly the same problem, with the same screen details. I tried your suggestion several times, with no response.
An old borrowed Windows 7 box got me nowhere - TWRP kept complaining that it couldn't connect, although I'd loaded adb. I quit when it started loading endless Explorer windows full of crapware and became unresponsive. I'm totally lost with Windows, anyway, so I just hit the wall switch to end to pain.
I'm running debian sid and I'm much happier with linux, after using it exclusively for well over ten years, although I'm an experienced user rather than an expert.
I've pried the back off my Kindle, but I'm afraid to touch the inside, except as a last resort. I downloaded SoupKit, but can't decompress it.
What's the best thing to try next?
Click to expand...
Click to collapse
Are you unable to bring up the boot menu upon startup?
Bob
soupmagnet said:
Are you unable to bring up the boot menu upon startup?
Click to expand...
Click to collapse
First, thanks for the help you're generously offering.
No. The start button quickly raises the centred "kindle(white) fire(blue)", with "v1.4a" at the top right and "Press power button for boot menu" at the bottom. Neither my Debian sid box (file manager, or lsusb), nor a borrowed win7 box (file manager) recognises it. Repeated presses, or a few seconds of the power button at boot have no effect, but a very long press shuts it down.
I managed to detach the back without damage, but I'm reluctant to do the shorting trick at boot, if there's a better way. If all is lost, it's no further problem, as it was never much use, anyway, due to Amazon's geoblocking here in Australia. If I can't get cyanogenmod or equivalent on it, I'll just chuck it.
I'd prefer to fix it with my Linux box, if possible, as I've used nothing but Linux and Android for well over ten years.
I have the firetv rooted with xposed running and the xbmc launcher running. I tried to upgrade to beta xbmc 14 nightly but it did not work. So I then tried to uninstall xbmc fully with adb. Now my firetv will boot to the firetv animation screen and then go to black screen with the error: Acitivy org.xbmc.xbmc splash screen not found. I have tried to reinstall xbmc 13.1 for adb but it will not go thru. I've tried killing xbmclauncher (se.blunden.xbmclauncher.apk) with no luck. Tried to uninstall Xposed with no luck. I can connect to my firetv thru adb and can create a su adb shell, but can't get anything to work through adb. Please help this fool!
apazrjon said:
I have the firetv rooted with xposed running and the xbmc launcher running. I tried to upgrade to beta xbmc 14 nightly but it did not work. So I then tried to uninstall xbmc fully with adb. Now my firetv will boot to the firetv animation screen and then go to black screen with the error: Acitivy org.xbmc.xbmc splash screen not found. I have tried to reinstall xbmc 13.1 for adb but it will not go thru. I've tried killing xbmclauncher (se.blunden.xbmclauncher.apk) with no luck. Tried to uninstall Xposed with no luck. I can connect to my firetv thru adb and can create a su adb shell, but can't get anything to work through adb. Please help this fool!
Click to expand...
Click to collapse
i recommend a factory reset
If you have got to the point of desperation and no other help is forthcoming. I ran through this guide when I had an issue and it restored my AFTV.
It won't let me post the link. So have a look on firetvnews .com and you should see a way to restore the AFTV. Or read below, I just copied it:
If you’ve managed to brick your Fire TV or for whatever reason are unable to get to the settings menu to perform a factory reset, here is how to enter recovery mode without fully booting into the Fire TV’s operating system.
To do this you will need a USB keyboard with a “Print Screen” or “SysRq” key. Mac keyboards generally do not have this key so will not work. Before you get started, plug the USB keyboard into the Fire TV and unplug the Fire TV’s power. Now plug the power in and while the Fire TV is booting, you need to press the following 3 keys simultaneously: Alt + Print Screen + i
Pressing those 3 keys sends a “kill all tasks” command to the Fire TV. If you kill all tasks during boot up enough times, the Fire TV will enter Recovery Mode. So after pressing Alt + Print Screen + i, the Fire TV will flicker and restart the boot up process. While it’s trying to boot up a second time, press Alt + Print Screen + i again. Repeat this process several times until the Fire TV displays the message “The System Update was not successful.” When you see this message, you are now in Recovery Mode.
If you are having trouble getting into Recovery Mode, a good time to press Alt + Print Screen + i is as soon as you see the colorful boot animation. Pressing Alt + Print Screen + i should cause the screen to go black and the boot animation to restart. Press Alt + Print Screen + i every time the boot animation restarts. After 4 or 5 restarts, you should see a white Amazon logo followed by the “Update was not successful” screen. You can also try holding Alt + Print Screen + i through out the entire initial boot up process.
Once on the “Update was not successful” screen, press the Home key on your keyboard. This should bring up a menu in the upper left corner. Use the arrow keys to highlight the factory reset option and hit enter.
Yeah I've seen that factory reset method. I am almost at that point! I have a wireless k400, but it doesn't seem to work. I just need to get my hands on a wired keyboard. I was hoping there may be some better adb commands to accomplish removing xposed and xbmc launcher, but I guess probably not. Time to get a wired keyboard! Thanks for the quick responses! Cheers!
apazrjon said:
Yeah I've seen that factory reset method. I am almost at that point! I have a wireless k400, but it doesn't seem to work. I just need to get my hands on a wired keyboard. I was hoping there may be some better adb commands to accomplish removing xposed and xbmc launcher, but I guess probably not. Time to get a wired keyboard! Thanks for the quick responses! Cheers!
Click to expand...
Click to collapse
I would use command "adb shell pm list packages -f" that way you can see what apps are installed on the Fire TV and exact package name.....
Next uninstall with "adb uninstall com.amazon.app.name" (no directory or .apk specification needed)
I was playing with some Xposed mods yesterday and locked the fire TV up as well, uninstalling mod fixed it. (Xposed Additions Module)
apazrjon said:
I was hoping there may be some better adb commands to accomplish removing xposed and xbmc launcher, but I guess probably not. Time to get a wired keyboard! Thanks for the quick responses! Cheers!
Click to expand...
Click to collapse
Only thing I can think of is to try an adb install of xbmc with the -r flag set, then an uninstall of Xposed before uninstalling XBMC. The -r should force a reinstall and get you back to a useable interface but otherwise, yep, sounds like a reset'll be required.
roustabout said:
Only thing I can think of is to try an adb install of xbmc with the -r flag set, then an uninstall of Xposed before uninstalling XBMC. The -r should force a reinstall and get you back to a useable interface but otherwise, yep, sounds like a reset'll be required.
Click to expand...
Click to collapse
If adb is working, adb reboot recovery should get you into recovery so you can do the factory reset.
reboot recovery does get me into the update download page but no buttons on my remote or my wireless k400 seem to get me to recovery for factory reset. Any thoughts?
apazrjon said:
reboot recovery does get me into the update download page but no buttons on my remote or my wireless k400 seem to get me to recovery for factory reset. Any thoughts?
Click to expand...
Click to collapse
Did you already uninstall all Xposed modules and the Xposed framework ?
trying that next. It seems that adb will only work right after I reboot for some reason. Going to try again right now.
Just went ahead and got a $10 usb keyboard from walmart. Still couldn't get the home button to work for getting my into recovery. Then i decided to press shift + home and it worked. I don't know if it was the key combo or just good timing with the home button. Who knows. Back to factory now! Time to rebuild. Everything was set up perfect! Just couldn't leave well enough alone, lol! Thanks for all the help. My adb would only work for one time at a time and wouldn't uninstal anything. Cheers!
deleted content ..
sorry ., didn't notice I would have been duplicating what others already posted ....
rbox said:
If adb is working, adb reboot recovery should get you into recovery so you can do the factory reset.
Click to expand...
Click to collapse
Sorry, meant "only command flag in ADB you might try before going for a full restore"
I thought the OPs core problem was that xposed was telling his system to use a nonexistent app as the launcher, and he wasn't able to get the app back in even for long enough to uninstall Xposed, reboot, and then uninstall XBMC.
Smithy71 said:
Once on the “Update was not successful” screen, press the Home key on your keyboard. This should bring up a menu in the upper left corner. Use the arrow keys to highlight the factory reset option and hit enter.
Click to expand...
Click to collapse
I've got a gray screen and can't get rid of it. I'm rooted and have elmerohueso's Launcher installed. All has been working perfect until the other night when I got a "low memory" pop up with a request to uninstall some apps. After that, the screen grayed and that was that. I've gotten to the“Update was not successful” screen but cannot get the menu to show up. I'm using a usb keyboard and have tried home, shift + home, and every other combo I can think of but the menu will not show up.
Anyone have another suggestion?
When you are on the update unsuccessful screen, press alt + sys rq + i to reboot back to the update screen again and then press home to bring up recovery menu. That's what I did on my keyboard
Smithy71 said:
If you have got to the point of desperation and no other help is forthcoming. I ran through this guide when I had an issue and it restored my AFTV.
It won't let me post the link. So have a look on firetvnews .com and you should see a way to restore the AFTV. Or read below, I just copied it:
If you’ve managed to brick your Fire TV or for whatever reason are unable to get to the settings menu to perform a factory reset, here is how to enter recovery mode without fully booting into the Fire TV’s operating system.
To do this you will need a USB keyboard with a “Print Screen” or “SysRq” key. Mac keyboards generally do not have this key so will not work. Before you get started, plug the USB keyboard into the Fire TV and unplug the Fire TV’s power. Now plug the power in and while the Fire TV is booting, you need to press the following 3 keys simultaneously: Alt + Print Screen + i
Pressing those 3 keys sends a “kill all tasks” command to the Fire TV. If you kill all tasks during boot up enough times, the Fire TV will enter Recovery Mode. So after pressing Alt + Print Screen + i, the Fire TV will flicker and restart the boot up process. While it’s trying to boot up a second time, press Alt + Print Screen + i again. Repeat this process several times until the Fire TV displays the message “The System Update was not successful.” When you see this message, you are now in Recovery Mode.
If you are having trouble getting into Recovery Mode, a good time to press Alt + Print Screen + i is as soon as you see the colorful boot animation. Pressing Alt + Print Screen + i should cause the screen to go black and the boot animation to restart. Press Alt + Print Screen + i every time the boot animation restarts. After 4 or 5 restarts, you should see a white Amazon logo followed by the “Update was not successful” screen. You can also try holding Alt + Print Screen + i through out the entire initial boot up process.
Once on the “Update was not successful” screen, press the Home key on your keyboard. This should bring up a menu in the upper left corner. Use the arrow keys to highlight the factory reset option and hit enter.
Click to expand...
Click to collapse
how to connect usb keyboard same time usb power? fire tv have no usb port
roy0175 said:
how to connect usb keyboard same time usb power? fire tv have no usb port
Click to expand...
Click to collapse
OTG Y Cable! It's an OTG cable that can also deliver power to the FireTV while you are using it with a mouse, keyboard, etc...
Hello,
Only today I received my fire tv and rooted with ADBfire tool and disabled updates with pm disable com.amazon.dcp command ( this is the only method I used). Then installed busybox and wanted to mount USB drive with ADBfire tool but there was some errors so I uninstalled busybox and done factory reset. After this my box boots to Amazon fire TV colour logo and says "press start on the remote" when I press start for 2-3 times the led on the box starts to flash orange colour . I found that you can enter recovery mode with USB keyboard connected. I done everything but my box just keeps restarting and no recovery option. Is it possible that my recovery partition is corrupted? Is there something I can do to unbrick my box?
Just a follow up:
I'm still can't boot to recovery mode. What I tried:
Holding Print/I/ALT and after I see amazon colour logo press all buttons again. Then screen flickers and starts boot again. Then again after I see colour logo press all buttons. After 2-3 times box restarts and on TV shows message "No Signal' for about 1-2 sec and box starts boot again. Then I see black screen with Amazon logo but no recovery option nothing =. I was playing for about 1h and no recovery. Is it possible that my box can't enter recovery?
When entering recovery menu does ethernet must be connected? Does remote must be on? I'm trying everything but can't enter recovery mode. My box just restarts and that's it. Any info or help will appreciated
kodikas said:
When entering recovery menu does ethernet must be connected? Does remote must be on? I'm trying everything but can't enter recovery mode. My box just restarts and that's it. Any info or help will appreciated
Click to expand...
Click to collapse
Hi
Have tried a differnt keyboard? or the keyboard without the HUB? (if you are using one)
[email protected] said:
Hi
Have tried a differnt keyboard? or the keyboard without the HUB? (if you are using one)
Click to expand...
Click to collapse
I was trying with 4 different keyboards and connecting with or without hub. Then on 3 different TV + 3 different HDMI cables + removed batteries on remote + ethernet cable connected and disconnected + different combinations on keyboard NOTHING by my understanding this is because I done "disable com.amazon.dcp" and then factory reset. I'm planing to play more latter today and update if I will have any luck.
kodikas said:
I was trying with 4 different keyboards and connecting with or without hub. Then on 3 different TV + 3 different HDMI cables + removed batteries on remote + ethernet cable connected and disconnected + different combinations on keyboard NOTHING by my understanding this is because I done "disable com.amazon.dcp" and then factory reset. I'm planing to play more latter today and update if I will have any luck.
Click to expand...
Click to collapse
I can verify it has nothing to do with disabling the updates in that manner.. I have factory reseted at least 10 times and each time I disable the updates immediately with pm disable. It must be something else you've done.
mastafunk said:
I can verify it has nothing to do with disabling the updates in that manner.. I have factory reseted at least 10 times and each time I disable the updates immediately with pm disable. It must be something else you've done.
Click to expand...
Click to collapse
Rooted then installed busybox and that's it.
You are probably just using the wrong key presses or your timing is off. On my keyboard, its alt + sysrq + i. Do that a few times while booting up. If you do manage to get to the "update failed" screen, do the keypress again. The press home button on keyboard to bring up menu and choose factory reset. Or maybe when its booting and tells you to press home key on remote, use a keyboard instead and see if it gets any further.
{ParanoiA} said:
You are probably just using the wrong key presses or your timing is off. On my keyboard, its alt + sysrq + i. Do that a few times while booting up. If you do manage to get to the "update failed" screen, do the keypress again. The press home button on keyboard to bring up menu and choose factory reset. Or maybe when its booting and tells you to press home key on remote, use a keyboard instead and see if it gets any further.
Click to expand...
Click to collapse
When I see colour Amazon logo I'm pressing Alt+PrtSc/Sysrq+i then screen goes black and colour Amazon logon come up then again I'm pressing the same combination and then box just won't boot, then I wait for about 2 min and again box starts to boot first white Amazon logo then colour Amazon logo and I'm pressing combination again then box restarts 2 times and shuts down. I was trying left ALT right ALT 4 different keyboards but never saw failed screen. My friend have Amazon box and I booted to failed screen without problems with all keyboards. I think that I need to send box back to Amazon for replacement.
Could you fix the problem?
Hello,
I was reading some post of bricked FATVs, wondering if you fixed your proboem and if you did, how?
How can you brick a AFTV?
Thanks
kodikas said:
When I see colour Amazon logo I'm pressing Alt+PrtSc/Sysrq+i then screen goes black and colour Amazon logon come up then again I'm pressing the same combination and then box just won't boot, then I wait for about 2 min and again box starts to boot first white Amazon logo then colour Amazon logo and I'm pressing combination again then box restarts 2 times and shuts down. I was trying left ALT right ALT 4 different keyboards but never saw failed screen. My friend have Amazon box and I booted to failed screen without problems with all keyboards. I think that I need to send box back to Amazon for replacement.
Click to expand...
Click to collapse
If your able to boot to amazon logo did you try remote sequence to factory reset (back button and right arrow for 15 sec
Sent from my SM-N900V using XDA Premium 4 mobile app
Just saw your post. Just tried and factory reset starts but after reboot stuck on the same Press (PLAY) to start.
davekaz said:
If your able to boot to amazon logo did you try remote sequence to factory reset (back button and right arrow for 15 sec
Sent from my SM-N900V using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Did you mean the keys on the keyboard or remote? Amazon white logo or color one? I'm stucking the white screen. Even after I press alt prtsc i then wipe data
i have the tv on its launch firmware 5.2.5.0, and it is pretty buggy.
this tv has pretty much zero dev work going on, so it has a locked bootloader, no recovery, ect.
it has been rooted (kingroot) and had updates disabled.
i reenabled the updates (unblocked from router and fixed build number).
it downloads the update and tries to install it, but it is still on 5.2.5.0 when it reboots.
i tried factory resetting before and after i removed root. (which doesn't remove or restore anything aside from making me put my account back in)
anyone have any ideas?
maybe someone can tell me how to pull a logcat when trying to install the OTA?
well, alright then.
Did you ever get this resolved? I have the same issue...still stuck on 5.2.5.0
I have the same issue with my Element TV stuck at 5.2.5.0
Based on this link it should be at 5.2.6.2 http://www.aftvnews.com/amazon-fire-tv-fire-tv-stick-software-update-history/
I need to figure out how to manually update the TV...any ideas?
To manually install a software update on your Element 4K Ultra HD Smart TV - Amazon Fire TV Edition:
1. From a computer, click the following link:
w w w. amazon. c o m /television-update
A .zip file named “firetvedition_update.zip” will download automatically.
2. Open the .zip file and extract the enclosed files by right-clicking the file and selecting “Extract All,” then following the prompts. (On a Mac, double-click the .zip file to extract the files.)
3. Next, plug a USB storage device into your computer with at least 4MB of available memory. If you’re already using a USB storage device with your TV to view photos or play music or videos, then this same device should also work for the software update. (The USB device must be FAT32 formatted.)
4. The USB storage device will appear as a removable drive on your computer. Drag and drop or copy and paste the files directly onto the USB device, making sure not to put them in a subfolder. Once the files have been copied, you can eject the USB device to safely disconnect it from your computer.
5. Unplug any external devices from your TV, then unplug the TV’s power cord.
6. Plug the USB stick into either USB port on your TV, then plug in the power cord for the TV. The TV will turn on by itself and begin installing the update. It will reboot during this time. Be sure to keep the TV and USB stick firmly plugged in. If prompted, press the power button on the front of your TV to finish the reboot process.
After your TV has rebooted, your software update is complete. You may remove the USB stick and reconnect any external devices. Your TV should download any future software updates automatically.
Unfortunately, my tv still doesn't boot up from the flash drive.
I have tried 5 different flash drives of different sizes.
I am going to write that image file using rufus on a flash drive and see what happens.
Maybe this will bypass having to mount it?
Anyone have any ideas?
I followed the steps and was able to boot from USB, but it didn't help much. (see the pictures attached)
Then I tried again to boot up but this time didn't boot at all from USB...no clue why.
fbuzila said:
I followed the steps and was able to boot from USB, but it didn't help much. (see the pictures attached)
Then I tried again to boot up but this time didn't boot at all from USB...no clue why.
Click to expand...
Click to collapse
My usb only booted once but my controls were not working, so I restarted and I could never get it to boot off the usb again.
This tv will probably have to be rooted since I get permission denied on everything.
I was hoping maybe to copy the upgrade img somewhere on to the tv and maybe execute it from there.
Poopiepants74 said:
This tv will probably have to be rooted since I get permission denied on everything.
I was hoping maybe to copy the upgrade img somewhere on to the tv and maybe execute it from there.
Click to expand...
Click to collapse
I am going to try wiping the image as mentioned in the link below, then try updates again.
w w w .aftvnews.c o m/how-to-unbrick-by-entering-recovery-mode-and-factory-reset-the-amazon-fire-tv/
Damn good news!!!
I finally got the damn thing upgraded, and no thanks to Amazon or Element.
They were both useless and kept sending me back and forth between support for both companies.
This is how you were able to break the Ouya console startup process when booting and it works for Element Fire TV's as well.
So it's a bit of a hit or miss, but I am pretty confident it will work if your patient.
1. Download the following file and put it on a USB stick
http://www.aftvnews.com/amazon-fire-tv-fire-tv-stick-software-update-history/
Search for: Version 5.2.5.1 (Build 577224220) and download that file
Throw it on a flash drive formatted Fat32
2. Connect a usb keyboard to your Element Fire TV
3. Turn of your Element TV by pulling the power plug, wait 5 seconds and turn it back on with the remote.
4. As soon as you see the element logo start tapping on your "Left alt", "I "(key) and "Print Screen" at the same time. This will cause a break and restart the system. You will do this several times continuously every time you seem the Element logo. The TV should reboot about 3-4 times, so you should see the Element logo 3-4 different times while tapping the key combination. At some point you will see a screen that reads updating.
5. The first time you come across the updating screen wait 5 minutes and if the progress bar does nothing, it is frozen/stuck. Once again, "Left alt", "I"(key) and "Print Screen" at the same time and it will restart. Once again you will see the Element logo and repeat the key combo routine.
You will then see the 2nd upgrade screen and you should see the progress bar moving and it should complete this time around.
Notes:
Never restart if it is updating and you see the progress bar moving or your usb is flashing.
Please reply with any questions, successes or failures.
Good luck!
Poopiepants
Well, I somehow managed to update to 5.2.5.1. I used a combination of the methods that @Poopiepants74 described in post #5 and post #10. I used post #5 to get to the boot menu, and then I was running into the same error message that @fbuzila had in post #6.
So, I left the TV at the boot menu, removed the USB stick, downloaded and added the 5.2.5.1 update file to the USB stick, put the USB stick back in the TV and continued with the steps to "update from USB", which was successful.
Now my TV has been on 5.2.5.1 for 48 hours and has not attempted to update to a newer version. When I check manually through the settings, it says there is no update available.
I will give it a week or so to see if it 'checks in' and tries to update it its own.
still stuck on 6.2.6.0 here. can't find a newer package to download anywhere*sigh*
20 days later...still hasn't updated. I remain on 5.2.5.1 still.
Anyone know where to manually download the latest Fire OS 5.2.6.7 for Fire TV Edition 1 (Element) Edition? I am still stuck on 5.2.5.1. Since I was able to manually update to 5.2.5.1 I'd like to attempt to manually update to the latest 5.2.6.7
Please follow these troubleshooting steps to get the issue resolved.
@ Power off the device
@ Unplug the power cord from the wall outlet
@ Hold down the return button on the TV (on the bottom bezel, next to the power button) and plug in the TV
@ When on the 'Amazon system recovery' screen, release the return button on the TV
@ Using the volume down button on the bezel of the TV, move down to 'wipe data/factory reset' option
@ Press the power button on the bezel of the TV to select ‘wipe data/factory reset’
@ Using the volume down button on the bezel of the TV, navigate to the “Yes” option
@ Press the power button to select “Yes” with the power button
@ Select “reboot system now” with the power button
Please go through the steps and see if that fixes your TV issue.
The only available update to the Fire OS, I have been able to find online is this one:
https://www.amazon.com/television-update
release-margo-54.5.7.2
Build TIME : 2017-06-24 09:27:46
FireOS 5.2.5.1
The latest version Fire OS 5.2.7.0 is nowhere to be found on the internet.
Unfortunately, some apps like Bravo do not seem to work with 5.2.5.1.
I will be contacting Amazon and see if any updates are available.
So after contacting Amazon, they sent me a link to their source files.
https://www.amazon.com/gp/help/cust...e=UTF8&nodeId=201452680&qid=1564247290&sr=1-1
So if you have this issue you need the recovery pill file and not just an update.
The recovery file will contain the MstarUpgrade.bin file.
Here is 5.2.6.8 straight from Element.
A quicker way to get into the Recovery menu without a keyboard.
Disconnect the power cable from the wall for 20 seconds, while holding down the power button.
Plug the TV back in and it will turn on automatically.
Immediately hold down the input button which is right next to the power button (Pictured as a Box with an arrow), until you hit the recovery menu.
Select upgrade from USB and you should be set.
It's not recognizing my signature file, so hopefully I will here from them soon to resolve my issue.
Poopiepants74 said:
So if you have this issue you need the recovery pill file and not just an update.
The recovery file will contain the MstarUpgrade.bin file.
Here is 5.2.6.8 straight from Element.
A quicker way to get into the Recovery menu without a keyboard.
Disconnect the power cable from the wall for 20 seconds, while holding down the power button.
Plug the TV back in and it will turn on automatically.
Immediately hold down the input button which is right next to the power button (Pictured as a Box with an arrow), until you hit the recovery menu.
Select upgrade from USB and you should be set.
It's not recognizing my signature file, so hopefully I will here from them soon to resolve my issue.
Click to expand...
Click to collapse
Same. Doesn't recognize for me either...
Good news Element pushed an update which my TV was able to install.
5.2.7.1 is out and it worked for me.
The TV just prompted me out of the blue to install this update and it successfully completed.
Hi - I was installing some external memory, a 16gb Sandisk USB memory stick. The fire cube recognised it straight away & I proceeded to format it as ‘internal storage’. I got a msg to say that the format was complete. The TV screen then flashed & the next thing the fire cube re-booted & all I have is an Android Recovery screen. I’ve tried the mute + the volume down for 60 secs. None of the keys on the remote are doing anything nor are any of the buttons on the fire cube.
Can anybody help or is this bricked due to the software version?
All there is for recovery options on stock 2nd gen Cube's is safe mode and fastboot. Holding vol down on the Cube (not remote) during boot up during the second animated Amazon logo puts it in safe mode.
Fastboot is useless for anyone that's not Amazon because they blocked all the useful fastboot commands like flash and boot.
Did you try using the Cube buttons to select factory reset? If the cube buttons don't work, plug in a keyboard and use that.
Finnzz said:
All there is for recovery options on stock 2nd gen Cube's is safe mode and fastboot. Holding vol down on the Cube (not remote) during boot up during the second animated Amazon logo puts it in safe mode.
Fastboot is useless for anyone that's not Amazon because they blocked all the useful fastboot commands like flash and boot.
Did you try using the Cube buttons to select factory reset? If the cube buttons don't work, plug in a keyboard and use that.
Click to expand...
Click to collapse
Hi - Yes, I’ve tried the mute & volume down button on the cube & held down for 60+ seconds. Nothing happened. It does seem to know when a key is pressed because if I press the right hand button with a circle on it, the ‘try again’ turns green. I’ve tried a keyboard attached via a OTG cable & that didn’t do anything…
Clubcard said:
if I press the right hand button with a circle on it, the ‘try again’ turns green.
Click to expand...
Click to collapse
Does the device reboot after you release the button after 'try again' turns green? If so, that means that 'try again" was selected and executed. If not, did you try not only pressing that button, but also holding it (long press) after the selection turns green? The typical way the recovery menu works is that the first moments of the button being pressed highlights the selection (by turning the selection green), and then the continued (without interruption) holding of the button (and eventual release of the button) actually selects and executes the highlighted selection.
Navigation of the recovery menu is usually done using a short press of the same button. You'll need to navigate to the other menu selection 'factory data reset', and then use a long press (and eventual release) to select and execute that selection.
Clubcard said:
I’ve tried a keyboard attached via a OTG cable & that didn’t do anything…
Click to expand...
Click to collapse
Try the keyboard both with and without an OTG cable, and in each of those cases, externally powering the keyboard (using some sort of split usb cable) because power may not be supplied to the usb port while in the recovery menu.
Functioner said:
Does the device reboot after you release the button after 'try again' turns green? If so, that means that 'try again" was selected and executed. If not, did you try not only pressing that button, but also holding it (long press) after the selection turns green? The typical way the recovery menu works is that the first moments of the button being pressed highlights the selection (by turning the selection green), and then the continued (without interruption) holding of the button (and eventual release of the button) actually selects and executes the highlighted selection.
Navigation of the recovery menu is usually done using a short press of the same button. You'll need to navigate to the other menu selection 'factory data reset', and then use a long press (and eventual release) to select and execute that selection.
Try the keyboard both with and without an OTG cable, and in each of those cases, externally powering the keyboard (using some sort of split usb cable) because power may not be supplied to the usb port while in the recovery menu.
Click to expand...
Click to collapse
Hi - It’s unplugged as all the cube is doing is flashing blue all the time. When I apply power, I get the FireTv logo & then the Android recovery screen comes up. The cube doesn’t do anything. When the ‘try again‘ hightlights green, nothing I do will make it reboot. I’ve pressed every button on the remote & all the buttons on the cube.
The USB on the back is a micro USB & all I have is a USB keyboard which is why I had to connect it via the OTG I had. I’ve attached a photo. I do have a different OTG cable which has a micro USB input for a power supply. I’ve tried that & the keyboard has power but I still can’t select the factory reset..
I will corrupt the data partition on my spare gen2 cube device so that I can check what it takes to make navigation of the recovery menu work.
Functioner said:
I will corrupt the data partition on my spare gen2 cube device so that I can check what it takes to make navigation of the recovery menu work.
[/QUOTE
It’s very good of you to do that but it’s rather extreme. What if you brick yours?
Click to expand...
Click to collapse
My raven device has DFU functionality. Yours most certainly does not. It would be very unlikely that I wouldn't be able to recover it.
Functioner said:
My raven device has DFU functionality. Yours most certainly does not. It would be very unlikely that I wouldn't be able to recover it.
Click to expand...
Click to collapse
Hi - Have you managed to sort anything out yet?
tengo el mismo caso lograste resolverlo?
Clubcard said:
Hi - Have you managed to sort anything out yet?
Click to expand...
Click to collapse
I was able to reproduce the issue on my device. My device booted to the recovery menu as shown in the OP.
Unfortunately, you're quite correct. There is no way to navigate the menu or execute either of the options shown in the menu. You should ask amazon to replace your device.
Functioner said:
I was able to reproduce the issue on my device. My device booted to the recovery menu as shown in the OP.
Unfortunately, you're quite correct. There is no way to navigate the menu or execute either of the options shown in the menu. You should ask amazon to replace your device.
Click to expand...
Click to collapse
Unfortunately it’s 18 months old & all Amazon are prepared to offer is 15% discount..
Clubcard said:
Unfortunately it’s 18 months old & all Amazon are prepared to offer is 15% discount..
Click to expand...
Click to collapse
The fact that the device could boot to this unrecoverable mode at all is a programming mistake that is the fault of amazon or its agents. The probability of it happening seems to have increased with the newest firmware version, as a few others have posted to xda recently with claims of the same issue. If it becomes more widespread, amazon may be forced to address the matter with something other than a trivial discount. You may want to consider holding on to your device in the event that this happens.
I'm still investigating the matter. There is some evidence in the recovery code of infrared remote code support for the recovery menu, but I blasted a wide range of codes, and there is no evidence in the log that any of them are even being received. I have tested the keyboard possibilities thoroughly, but not exhaustively. I may turn up something later but my confidence level is not high.
Functioner said:
The fact that the device could boot to this unrecoverable mode at all is a programming mistake that is the fault of amazon or its agents. The probability of it happening seems to have increased with the newest firmware version, as a few others have posted to xda recently with claims of the same issue. If it becomes more widespread, amazon may be forced to address the matter with something other than a trivial discount. You may want to consider holding on to your device in the event that this happens.
I'm still investigating the matter. There is some evidence in the recovery code of infrared remote code support for the recovery menu, but I blasted a wide range of codes, and there is no evidence in the log that any of them are even being received. I have tested the keyboard possibilities thoroughly, but not exhaustively. I may turn up something later but my confidence level is not high.
Click to expand...
Click to collapse
OK, thanks. The standard control/alt/delete as used on a PC works in that it reboots the cube. I couldn’t get anything else to work..
Clubcard said:
OK, thanks. The standard control/alt/delete as used on a PC works in that it reboots the cube. I couldn’t get anything else to work..
Click to expand...
Click to collapse
What happens if you hold the volume up key on the Cube during boot, to boot to fastboot, connect your computer via USB, and type fastboot continue?
Pro-me3us said:
What happens if you hold the volume up key on the Cube during boot, to boot to fastboot, connect your computer via USB, and type fastboot continue?
Click to expand...
Click to collapse
Hi - Will check that out later when I finish work. Thanks..
Clubcard said:
Hi - Will check that out later when I finish work. Thanks..
Click to expand...
Click to collapse
Hi - When I re-read your Instructions I couldn’t figure out how to do what you advised. Anyway I made what must have been my 10th phone call to Amazon. It went from them offering me 15% discount, then 20% & then 30%. I said no to all & finally after a lot of polite badgering, they have allowed to me buy a new one & I have an email from Amazon stating that I will get a full refund when my cube is delivered tomorrow
Clubcard said:
they have allowed to me buy a new one
Click to expand...
Click to collapse
Are they giving you a 3rd gen Cube I didn't think Amazon had any more new 2nd gen Cubes?
@Functioner is right, there does't appear to be any navigation options in that menu. Amazon didn't fully implemented the standard Android recovery menu WITH navigation, which effectively bricks the device.
Amazon is at fault here, however getting them to admit to it is another thing.
Regarding my previous instructions. Holding down the volume up button on the Cube (not the remote) during boot will put the Cube in fastboot mode.
You then need to use your computer with ADB/fastboot installed on it, and issue the fastboot command fastboot continue to the Cube over USB.
I don't know if activation of that recovery menu will prevent the device from booting into fastboot, you'll have to see.
Since you are getting a new Cube, I'd advise you skip the mandatory registration firmware update.
Pro-me3us said:
Are they giving you a 3rd gen Cube I didn't think Amazon had any more new 2nd gen Cubes?
@Functioner is right, there does't appear to be any navigation options in that menu. Amazon didn't fully implemented the standard Android recovery menu WITH navigation, which effectively bricks the device.
Amazon is at fault here, however getting them to admit to it is another thing.
Regarding my previous instructions. Holding down the volume up button on the Cube (not the remote) during boot will put the Cube in fastboot mode.
You then need to use your computer with ADB/fastboot installed on it, and issue the fastboot command fastboot continue to the Cube over USB.
I don't know if activation of that recovery menu will prevent the device from booting into fastboot, you'll have to see.
Since you are getting a new Cube, I'd advise you skip the mandatory registration firmware update.
Click to expand...
Click to collapse
Hi - Yes, it’s a 3rd Gen I’m getting. I had the downloader app & had kodi & few other apps on my 2nd Gen. Will this 3rd Gen not allow me to have any of these 3rd party apps on?