Develop Bugs

4k Element Amazon Fire TV can't update

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.

Xtrons TQ709IPL/TE706PL Recovery Method (without physical hardware buttons)

So I've recently experienced some problems booting with my Xtrons TQ709IPL, so I thought I would share the method I used to fix it. This will probably work with other Xtrons devices (especially TE706PL since it just seems to be a TQ709IPL that comes with Android 10-- which oddly my TQ709IPL did as well when it was supposed to come with 9.0) and possibly other non-physical/touch button head units with similiar setups. This method is based on a post by @marchnz found here: [url]https://forum.xda-developers.com/android-auto/mtcd-software-development/mtcd-e-android-10-upgrade-using-t4123933[/URL] but fine-tuned to Xtrons unit.
To Preface this, I was unable to find the correct method to boot directly into recovery mode from RST. If anyone knows how on this unit, it'd be appreciated if they could share.
Beyond that, this also works if your device doesn't boot at all but the hardware buttons still react to RST being held in-- this will probably be due to a bad boot.img flash.
Required items:
Rockchip Head Unit with USB Port that can be recognized
Computer with Windows or Linux
USB-A to USB-A (or USB-C if your computer has the port)
Small pin, screwdriver-- something to push in the rst button
Rockchip Drivers and Android Tools: [url]https://github.com/rockchip-linux/tools[/URL]
ROM for your device in .img format: [url]https://yadi.sk/d/umCvHqCDzHccr[/URL]
Steps:
Install Rockchip Drivers and launch RKDevTool.
Plug Computer/Laptop into the Head Unit's Yellow USB-A port (this might be different on other models-- just try each out after doing the next step if it doesn't recognize your device)
Use a pin/small screw driver/etc to push in the RST button.
Hold button down until panel lights flash then stop pressing for about a second before pressing in again and holding (this should be done before the splash screen shows).
- If you did this successfully, your computer will now recognize your device in Maskrom mode. RKDevTool should show that a device is found.
Move over to the "Upgrade Firmware" tab and click firmware.
Select the .img file for your device.
Then click the "Upgrade" tab when the firmware has loaded.
- MAKE SURE YOU DO IT FROM HERE INSTEAD OF TRYING TO FLASH INDIVIDUAL IMGS IN THE "DOWNLOAD IMAGE" TAB! This caused my unit to not boot after I flashed the boot.img of my current firmware to it. Luckily, I was still able to get into Maskrom mode. So if you really want to try, make sure to use caution using that method!
It should now start flashing the firmware.
When it finishes, it should be recovered.
- Though, it failed and booted to recovery on mine once.
Done.
Hopefully, this will be of some use to some of you.

iamrance.asa said:
So I've recently experienced some problems booting with my Xtrons TQ709IPL, so I thought I would share the method I used to fix it. This will probably work with other Xtrons devices (especially TE706PL since it just seems to be a TQ709IPL that comes with Android 10-- which oddly my TQ709IPL did as well when it was supposed to come with 9.0) and possibly other non-physical/touch button head units with similiar setups. This method is based on a post by @marchnz found here: [url]https://forum.xda-developers.com/android-auto/mtcd-software-development/mtcd-e-android-10-upgrade-using-t4123933[/URL] but fine-tuned to Xtrons unit.
To Preface this, I was unable to find the correct method to boot directly into recovery mode from RST. If anyone knows how on this unit, it'd be appreciated if they could share.
Beyond that, this also works if your device doesn't boot at all but the hardware buttons still react to RST being held in-- this will probably be due to a bad boot.img flash.
Required items:
Rockchip Head Unit with USB Port that can be recognized
Computer with Windows or Linux
USB-A to USB-A (or USB-C if your computer has the port)
Small pin, screwdriver-- something to push in the rst button
Rockchip Drivers and Android Tools: [url]https://github.com/rockchip-linux/tools[/URL]
ROM for your device in .img format: [url]https://yadi.sk/d/umCvHqCDzHccr[/URL]
Steps:
Install Rockchip Drivers and launch RKDevTool.
Plug Computer/Laptop into the Head Unit's Yellow USB-A port (this might be different on other models-- just try each out after doing the next step if it doesn't recognize your device)
Use a pin/small screw driver/etc to push in the RST button.
Hold button down until panel lights flash then stop pressing for about a second before pressing in again and holding (this should be done before the splash screen shows).
- If you did this successfully, your computer will now recognize your device in Maskrom mode. RKDevTool should show that a device is found.
Move over to the "Upgrade Firmware" tab and click firmware.
Select the .img file for your device.
Then click the "Upgrade" tab when the firmware has loaded.
- MAKE SURE YOU DO IT FROM HERE INSTEAD OF TRYING TO FLASH INDIVIDUAL IMGS IN THE "DOWNLOAD IMAGE" TAB! This caused my unit to not boot after I flashed the boot.img of my current firmware to it. Luckily, I was still able to get into Maskrom mode. So if you really want to try, make sure to use caution using that method!
It should now start flashing the firmware.
When it finishes, it should be recovered.
- Though, it failed and booted to recovery on mine once.
Done.
Hopefully, this will be of some use to some of you.
Click to expand...
Click to collapse
Please help, I'm about 2 seconds from getting a new HU...
I also have the Xtrons TQ709IPL. I installed the drivers, but no matter what I do, when I finally get the HU into the correct mode, the USB insertion noise happens but then windows tells me that the device failed to install correctly. I also am unable to manually install the driver. This was on Windows 10, but I also tried it on Windows 8.1 and Windows7 all with the same results.
I must be doing something different than you, but I followed your instructions?

Ok, my USB cable was too long, I was using an extender to get to my laptop on my workbench from my car. If anyone else has this problem, make sure your USB cable is short. I am in now!
Next question, I have the TQ709IPL just like you. So which ROM do I need from the link you provided?

Fire TV 2nd Gen stuck in some kind of kiosk mode?

I purchased a used Fire TV 2nd gen online but when I boot it up, it goes into some kind of kiosk slideshow for 1st gen Amazon Echo devices that I can't exit.
It boots normally at first with the Fire TV logo an all but there's no config screen or anything. It boots to a white AMAZON ECHO screen with pics of the original Echo device then goes into a slide show showing all the various features of Amazon echo. The remote doesn't sync and the device will only show up on the Fire TV remote app for a few seconds before disappearing after boot. I can plug in a physical keyboard and if I press the ESC key, the screen will go black for a second before re-starting the slide show from the beginning. So far I've not been able to find any other keyboard functions that react, only the ESC key so far.
If I had to guess, I'd say it probably has a much older version of the OS on it as the slide show is for the older generations of Echo.
I'm assuming this used to be some kind of demo device, maybe from Best Buy or something but does anyone know how to get out of this slide show so it can be used as a normal device or is this thing just useless? Suggestions?

Hannover2k said:
I purchased a used Fire TV 2nd gen form ebay but when I boot it up, it goes into some kind of kiosk slideshow for Amazon Echo that I can't exit.
It boots normally at first with the Fire TV logo an all but there's no config screen or anything. It boots to a white AMAZON ECHO screen with pics of the original Echo device then goes into a slide show showing all the various features of Amazon echo. The remote doesn't sync and the device will only show up on the Fire TV remote app for a few seconds before disappearing after boot. I can plug in a physical keyboard and if I press the ESC key, the screen will go black for a second before re-starting the slide show from the beginning. So far I've not been able to find any other keyboard functions that react, only the ESC key so far.
If I had to guess, I'd say it probably has a much older version of the OS on it as the slide show is for the older generations of Echo.
I'm assuming this used to be some kind of demo device, maybe from Best Buy or something but does anyone know how to get out of this slide show so it can be used as a normal device or is this thing just useless? Suggestions?
Click to expand...
Click to collapse
Just as an update, I found that if I plug in a USB keyboard, pressing ALT+ESC will pop up a menu telling me to press the home button if I wish to return to the home screen. No remote works with it yet so that doesn't help much. Pressing ALT+Space will bring up what appears to be the FireTV search keyboard but typing doesn't bring up anything, it just echos what I type and there's no 'ENTER' key to submit anything.
If I do this immediately after the slideshow comes up, it will prompt that there's no network connection and take me to the network settings menu. I tried plugging in a LAN cable but the device doesn't seem to pull up an IP address. I manually entered an IP but was unable to find it on the network. Even tried using the APPS2FIRE app to see if it could see it in the search but it doesn't. I connected it to wifi successfully but same issue, it doesn't seem to actually pull an IP address as I can't see it on my network when I scan for it. The network settings know when the LAN is plugged in and removed though.
Plugging in USB A-A doesn't seem to do anything. I tried running the Unbrick batch file from one of the other posts but it's intended to work on non-rooted devices with the jumper trick, I think, and while it does kick off the script, it stops at 0% and never does anything. I'm sure this is an older OS that can still be rooted but I just don't know how to get to anything in it since I can't get into ADB.
Any suggestions would be appreciated though!

Hannover2k said:
I'm sure this is an older OS that can still be rooted but I just don't know how to get to anything in it since I can't get into ADB.
Any suggestions would be appreciated though!
Click to expand...
Click to collapse
If you can't get device to show up on adb devices via terminal/command prompt or access settings menu I don't think there's much you can do.
1.Try doing a scan with Fing Network Tools and see if IP shows.
2. Try downloading and installing FireTV remote App on your phone and connecting if it finds stick.
Without adb being activated on the stick, and settings menu unavailable to enable adb there is not much else for it m8, these ebay sticks are dodgy to say the least I've been stung a few times. Even bought one and opened it to find the heat shield casing missing and clk broke lol

Bertonumber1 said:
If you can't get device to show up on adb devices via terminal/command prompt or access settings menu I don't think there's much you can do.
1.Try doing a scan with Fing Network Tools and see if IP shows.
2. Try downloading and installing FireTV remote App on your phone and connecting if it finds stick.
Without adb being activated on the stick, and settings menu unavailable to enable adb there is not much else for it m8, these ebay sticks are dodgy to say the least I've been stung a few times. Even bought one and opened it to find the heat shield casing missing and clk broke lol
Click to expand...
Click to collapse
I'll give those a shot. I tried the jumper technique from the Unbrick Fire TV 2 post and was able to get partway through that process and to the prompt where it tells me to remove the jumper and press enter but it gets an error after copying the files, just before it should boot to twrp. something about the source path being empty. I can post a pic if that's helpful. I think may have forgotten to run the disable modemmanager command so I'll give that another try later. I didn't realize you had to run that every time you reboot linux. I know just enough to be dangerous with it.

Hannover2k said:
I'll give those a shot. I tried the jumper technique from the Unbrick Fire TV 2 post and was able to get partway through that process and to the prompt where it tells me to remove the jumper and press enter but it gets an error after copying the files, just before it should boot to twrp. something about the source path being empty. I can post a pic if that's helpful. I think may have forgotten to run the disable modemmanager command so I'll give that another try later. I didn't realize you had to run that every time you reboot linux. I know just enough to be dangerous with it.
Click to expand...
Click to collapse
Yeah great have a look here too
https://docs.google.com/document/u/0/d/1zYtqmf4RfLOkrPyPjf1C0CjAZf_0E1JohIlTyVY5kGs/mobilebasic
Files here
https://drive.google.com/drive/u/0/mobile/folders/1GbMTBHuFhwT_uyZaJs0ApsG_RQ5Wg_7F
Should work :good:

Bertonumber1 said:
Yeah great have a look here too
https://docs.google.com/document/u/0/d/1zYtqmf4RfLOkrPyPjf1C0CjAZf_0E1JohIlTyVY5kGs/mobilebasic
Files here
https://drive.google.com/drive/u/0/mobile/folders/1GbMTBHuFhwT_uyZaJs0ApsG_RQ5Wg_7F
Should work :good:
Click to expand...
Click to collapse
Unfortunately I can't use those methods. While I can get into the network settings, I can't get into any other settings. I never I never left it connected to wifi so I've been using a LAN cable to test. Booting without the LAN causes it to get an error and takes me to the network settings but I can't get to anything else from there.
Been messing with the jumper method from https://forum.xda-developers.com/fire-tv/development/unbrick-fire-tv-stick-2-anti-rollback-t3986303 but not having any luck yet as per the attached pic. Also tried the unbrick method which gets stuck at 000000200: 0% every time. Just for the heck of it, I shorted DAT0 and ran it and it popped up an error saying it can't locate a 'system' partition. The unit still boots up with the fire tv logo and goes into that demo mode so I'm sure there's a partition present. This is really a challenge! Running out of things to try though.

Hannover2k said:
Unfortunately I can't use those methods. While I can get into the network settings, I can't get into any other settings. I never I never left it connected to wifi so I've been using a LAN cable to test. Booting without the LAN causes it to get an error and takes me to the network settings but I can't get to anything else from there.
Been messing with the jumper method from https://forum.xda-developers.com/fire-tv/development/unbrick-fire-tv-stick-2-anti-rollback-t3986303 but not having any luck yet as per the attached pic. Also tried the unbrick method which gets stuck at 000000200: 0% every time. Just for the heck of it, I shorted DAT0 and ran it and it popped up an error saying it can't locate a 'system' partition. The unit still boots up with the fire tv logo and goes into that demo mode so I'm sure there's a partition present. This is really a challenge! Running out of things to try though.
Click to expand...
Click to collapse
You may have a stick that cannot be rooted/modified via amonet, one with dl mode disabled. These devices around December 2019 started to appear on the market and there's no way round them.

Bertonumber1 said:
You may have a stick that cannot be rooted/modified via amonet, one with dl mode disabled. These devices around December 2019 started to appear on the market and there's no way round them.
Click to expand...
Click to collapse
The device is a Fire TV 2nd gen Sloane so I would expect it to work like others I've rooted, but that kiosk os might do just what you said and disabled DL mode. I'll still play with it a bit but not sure what else can be done. Maybe some new method will come along in the future so I'll just hold on to it.
Thanks for all the input though. Greatly appreciated.

Hannover2k said:
The device is a Fire TV 2nd gen Sloane so I would expect it to work like others I've rooted, but that kiosk os might do just what you said and disabled DL mode. I'll still play with it a bit but not sure what else can be done. Maybe some new method will come along in the future so I'll just hold on to it.
Thanks for all the input though. Greatly appreciated.
Click to expand...
Click to collapse
Sorry mate my bad I thought it was a stick you had I was helping some other guy in firestick tank forum and got mixed up.
Try the short method again only when you get the error :
Leave dc power on (plugged into box)
Remove USB a to USB a cable
Close terminal
Open new terminal up in amonet once again
Run the boot-rom step again BUT hit enter TWICE
Then plug USB cable back in
Pull the dc power and plug it in again
The script should go through
I followed this from another member and it always works for me, has worked on numerous Sloanes. Give it a go, worth a shot mate

Bertonumber1 said:
Sorry mate my bad I thought it was a stick you had I was helping some other guy in firestick tank forum and got mixed up.
Try the short method again only when you get the error :
Leave dc power on (plugged into box)
Remove USB a to USB a cable
Close terminal
Open new terminal up in amonet once again
Run the boot-rom step again BUT hit enter TWICE
Then plug USB cable back in
Pull the dc power and plug it in again
The script should go through
I followed this from another member and it always works for me, has worked on numerous Sloanes. Give it a go, worth a shot mate
Click to expand...
Click to collapse
Thanks for the info, it's worth a try. Just to clarify, when you say to press enter twice, do you mean to press it twice at the prompt where it tells you to remove the short and press enter?

Hannover2k said:
Thanks for the info, it's worth a try. Just to clarify, when you say to press enter twice, do you mean to press it twice at the prompt where it tells you to remove the short and press enter?
Click to expand...
Click to collapse
Hey @Hannover2k, yeah the Sloane is stubborn to root, just keep at it, once you see ***remove short and hit enter** and get an error try leaving it switched on but remove USB, then run the script again and hit enter again after you hit it once, disconnect/reconnect the dc power and plug USB in without the short (if displaying remove short) . Should go through
Another thing...
This what happened to me the other day. If your preloader is gone (it's displaying remove short when there is no short). Disconnect power, disconnect USB, run the the script and connect power and wait 50-70 seconds then plug USB back in.
As I said these Sloanes are tough but you should get it, using the short "jumper" method m8

Bertonumber1 said:
Hey @Hannover2k, yeah the Sloane is stubborn to root, just keep at it, once you see ***remove short and hit enter** and get an error try leaving it switched on but remove USB, then run the script again and hit enter again after you hit it once, diconnect/reconnect the dc power. Should go through
Another thing...
This what happened to me the other day. If your preloader is gone (it's displaying remove short when there is no short). Disconnect power, disconnect USB, run the the script and connect power and wait 50-70 seconds then plug USB back in.
As I said these Sloanes are tough but you should get it, using the short "jumper" method m8
Click to expand...
Click to collapse
Sorry is I'm missing something here. I've been trying to do your method and while I've been getting different error messages and results, I'm still not quite sure I'm doing it right.
After I get the first error after removing the short, you mention above to remove the USB then run the script again, etc. At what point do I plug the USB cable back in? Do I plug the USB back in after removing the power? When I do remove the power, do i need to reconnect the Jumper before plugging it back in?
Sorry if I'm lame, I've just done this jumper thing 100 times and can get many different results but not the one we're looking for! lol
UPDATE: Holy cow, I got it to work the very next time after posting the message! Here's what I did:
1) Ran the script, connected jumper and powered on the device.
2) Got error message.
3) Unplugged USB then re-ran script, pressing enter again after running the command.
4) Plugged USB back in.
I did not reconnect the jumper. When the USB cable was re-connected it did display a message to remove the jumper and press enter, however I did not have to do that. All kinds of stuff started flying all over the screen, then it got to;
Clearing Preloader Header
Flashing Tee
Flashing Bootloader
Flashing Unbrick Image
Flashing Boot
Booting to TWRP
I'm literally grinning ear to ear right now! Thanks for all your help with this! Even if it doesn't work at this point, I'm very happy to have gotten this far!
I can get these kiosk devices for $20 each. Box only, no power or remote. Does anyone think it would be worth it to buy a few of them and try to sell them off with refreshed imaged on them? There's a lot available so just wondering.

Hannover2k said:
Sorry is I'm missing something here. I've been trying to do your method and while I've been getting different error messages and results, I'm still not quite sure I'm doing it right.
After I get the first error after removing the short, you mention above to remove the USB then run the script again, etc. At what point do I plug the USB cable back in? Do I plug the USB back in after removing the power? When I do remove the power, do i need to reconnect the Jumper before plugging it back in?
Sorry if I'm lame, I've just done this jumper thing 100 times and can get many different results but not the one we're looking for! lol
UPDATE: Holy cow, I got it to work the very next time after posting the message! Here's what I did:
1) Ran the script, connected jumper and powered on the device.
2) Got error message.
3) Unplugged USB then re-ran script, pressing enter again after running the command.
4) Plugged USB back in.
I did not reconnect the jumper. When the USB cable was re-connected it did display a message to remove the jumper and press enter, however I did not have to do that. All kinds of stuff started flying all over the screen, then it got to;
Clearing Preloader Header
Flashing Tee
Flashing Bootloader
Flashing Unbrick Image
Flashing Boot
Booting to TWRP
I'm literally grinning ear to ear right now! Thanks for all your help with this! Even if it doesn't work at this point, I'm very happy to have gotten this far!
I can get these kiosk devices for $20 each. Box only, no power or remote. Does anyone think it would be worth it to buy a few of them and try to sell them off with refreshed imaged on them? There's a lot available so just wondering.
Click to expand...
Click to collapse
@Hannover2k Yeah that's you got it sorted then, I tried to explain that method but didn't do a very good job of it lol, make sure you push pre-rooted rom and supersu 2.82 zip to /sdcard, and flash.
Please Remember and note that you cannot flash unsigned zips such as magisk to the Sloane as you're bootloader remains incarcerated , if you're device has cleared preloader and you've entered into twrp it should work
Ps. if you can get a Sloane for that price pm me and we'll sort something, doesn't matter about power cables, remotes etc

Bertonumber1 said:
@Hannover2k Yeah that's you got it sorted then, I tried to explain that method but didn't do a very good job of it lol, make sure you push pre-rooted rom and supersu 2.82 zip to /sdcard, and flash.
Please Remember and note that you cannot flash unsigned zips such as magisk to the Sloane as you're bootloader remains incarcerated , if you're device has cleared preloader and you've entered into twrp it should work
Ps. if you can get a Sloane for that price pm me and we'll sort something, doesn't matter about power cables, remotes etc
Click to expand...
Click to collapse
After flashing the pre-rooted image the first time, everything seemed to work except whenever I restarted via the settings menu, it would show the TWRP pre boot screen but allowing it to continue to boot normally would result in a boot loop. Performing a power cycle would cause the device to skip over the TWRP menu and boot right into the device.
Tried clearing the SD partition and dalvik to free up space as it was only showing about 1.2gb free after the flash. Got the free space back but still the same boot issue after flash, though it did work after a power cycle as opposed to restarting, which I rarely do anyways.
Remembering the Kiosk was for the original echo devices, I got to thinking about it having an older OS again and maybe not liking being flashed directly to the latest version so I re-flashed it to v5.2.6.7_r1. It would boot loop after the TWRP pre login screen but after the first loop it would boot properly. Went ahead and flashed it back to 5.2.7.3_r1 and everything seems to be working perfectly now. Restarts properly and all functionality seems to be present.
I really appreciate your assistance with this. I had them send me another one so I can try this method once more and if it works again, I'll definitely let you know and we'll work something out.
-Han

Hannover2k said:
After flashing the pre-rooted image the first time, everything seemed to work except whenever I restarted via the settings menu, it would show the TWRP pre boot screen but allowing it to continue to boot normally would result in a boot loop. Performing a power cycle would cause the device to skip over the TWRP menu and boot right into the device.
Tried clearing the SD partition and dalvik to free up space as it was only showing about 1.2gb free after the flash. Got the free space back but still the same boot issue after flash, though it did work after a power cycle as opposed to restarting, which I rarely do anyways.
Remembering the Kiosk was for the original echo devices, I got to thinking about it having an older OS again and maybe not liking being flashed directly to the latest version so I re-flashed it to v5.2.6.7_r1. It would boot loop after the TWRP pre login screen but after the first loop it would boot properly. Went ahead and flashed it back to 5.2.7.3_r1 and everything seems to be working perfectly now. Restarts properly and all functionality seems to be present.
I really appreciate your assistance with this. I had them send me another one so I can try this method once more and if it works again, I'll definitely let you know and we'll work something out.
-Han
Click to expand...
Click to collapse
The recovery partition maybe corrupted.
You may try updating twrp to the latest 3.0.05 from Sloane Twrp recovery page.
There you can download the file from here :
https://www.mediafire.com/file/brae6r8lu1np5jm/firetv2_recovery_v6.zip/file
,push it to Sloane /sdcard and run command
from pc
adb shell
Then run:
sh /sdcard/firetv2_recovery_v6.zip
Reboot
That should fix it.
As soon as you update TWRP
Reboot and flash the pre-rooted firmware and supersu 2.82.zip
Then wipe cache, dalvik
Let it boot up and then factory reset (data, dalvik, cache)
Reboot and it should be okay

Bertonumber1 said:
The recovery partition maybe corrupted.
You may try updating twrp to the latest 3.0.05 from Sloane Twrp recovery page.
There you can download the file from here :
https://www.mediafire.com/file/brae6r8lu1np5jm/firetv2_recovery_v6.zip/file
,push it to Sloane /sdcard and run command
from pc
adb shell
Then run:
sh /sdcard/firetv2_recovery_v6.zip
Reboot
That should fix it.
As soon as you update TWRP
Reboot and flash the pre-rooted firmware and supersu 2.82.zip
Then wipe cache, dalvik
Let it boot up and then factory reset (data, dalvik, cache)
Reboot and it should be okay
Click to expand...
Click to collapse
Thanks for the info. The image I installed already had that version of TWRP installed on it but like I said in my last comment, flashing to an older rom then re-flashing back to the latest one seems to have resolved the issue.
No more Kiosk mode, though I wish I could have gotten a look at those files just to see what was going on there.
Anyways, all good now and I have another one of those kiosk units I'm going to try the process again on and if it works, I have access to a lot of these devices so I may refresh them and sell them cheap.
Thanks again for everyones input! Still surprised I got it working normal again.

Bertonumber1 said:
@Hannover2k Yeah that's you got it sorted then, I tried to explain that method but didn't do a very good job of it lol, make sure you push pre-rooted rom and supersu 2.82 zip to /sdcard, and flash.
Please Remember and note that you cannot flash unsigned zips such as magisk to the Sloane as you're bootloader remains incarcerated , if you're device has cleared preloader and you've entered into twrp it should work
Ps. if you can get a Sloane for that price pm me and we'll sort something, doesn't matter about power cables, remotes etc
Click to expand...
Click to collapse
Good news!
I was given a 2nd unit with the same 'issue' and was able to get it to start taking the image within a couple mins. The guy who has them can't do anything with them and has lowered his price per unit so are these worth anything to anyone?
Again, it's the box only, no power cords or remote but I don't expect that to be an issue for someone looking to replace one.
I hope I'm not breaking any rules by asking that but I'm open to any thoughts on this.
-Han

Hannover2k said:
Good news!
I was given a 2nd unit with the same 'issue' and was able to get it to start taking the image within a couple mins. The guy who has them can't do anything with them and has lowered his price per unit so are these worth anything to anyone?
Again, it's the box only, no power cords or remote but I don't expect that to be an issue for someone looking to replace one.
I hope I'm not breaking any rules by asking that but I'm open to any thoughts on this.
-Han
Click to expand...
Click to collapse
@Bertonumber1

Sus_i said:
@Bertonumber1
Click to expand...
Click to collapse
Yeah I've already replied via pm to @Hannover2k I've already bought one with power brick and remote for Roger @Sus_i hannover2k only has the Sloane itself AFAIK I got the full shebang for £27 so it's all good perhaps @Hannover2k can provide a spare and that's us got a couple to got to work on in the name of furthering development

Bertonumber1 said:
Yeah I've already replied via pm to @Hannover2k I've already bought one with power brick and remote for Roger @Sus_i hannover2k only has the Sloane itself AFAIK I got the full shebang for £27 so it's all good perhaps @Hannover2k can provide a spare and that's us got a couple to got to work on in the name of furthering development
Click to expand...
Click to collapse
Hannover2k said:
Sorry is I'm missing something here. I've been trying to do your method and while I've been getting different error messages and results, I'm still not quite sure I'm doing it right.
After I get the first error after removing the short, you mention above to remove the USB then run the script again, etc. At what point do I plug the USB cable back in? Do I plug the USB back in after removing the power? When I do remove the power, do i need to reconnect the Jumper before plugging it back in?
Sorry if I'm lame, I've just done this jumper thing 100 times and can get many different results but not the one we're looking for! lol
UPDATE: Holy cow, I got it to work the very next time after posting the message! Here's what I did:
1) Ran the script, connected jumper and powered on the device.
2) Got error message.
3) Unplugged USB then re-ran script, pressing enter again after running the command.
4) Plugged USB back in.
I did not reconnect the jumper. When the USB cable was re-connected it did display a message to remove the jumper and press enter, however I did not have to do that. All kinds of stuff started flying all over the screen, then it got to;
Clearing Preloader Header
Flashing Tee
Flashing Bootloader
Flashing Unbrick Image
Flashing Boot
Booting to TWRP
I'm literally grinning ear to ear right now! Thanks for all your help with this! Even if it doesn't work at this point, I'm very happy to have gotten this far!
I can get these kiosk devices for $20 each. Box only, no power or remote. Does anyone think it would be worth it to buy a few of them and try to sell them off with refreshed imaged on them? There's a lot available so just wondering.
Click to expand...
Click to collapse
Just wanted to add my Order of Operations to this post. I also bought one of these "Kiosk" boxes without remote or power supply for $13 off of eBay. Great deal, I thought, if I can get it to root. It appears that the order in which you perform the steps is unique to your setup. After trying all the above suggestions with no success (similar errors as listed above), here's what worked for me:
1. Plug in male-to-male USB cable between FTV2 and Linux box
2. Short DAT0 pin on FTV2 board
3. Connect FTV2 AC power
4. Run script
5. Remove short, press enter once when prompted
After TWRP installed (and I figured out how to use it), I was successful in having a usable FTV2 with all of the perks this process brings. Thanks to all who contributed to make this possible, and an extra big thanks to @Hannover2k for being the first to try this on these specifically-challenged boxes. It was a huge help!

S343 boot loop? After firmware install

I knew I shouldnt of done it. Its just my luck.
Tonight I installed the R112.....V8-R851T02-LF1R112 CFW posted a few days back.
Previous to this I had V8-R851T02-LF1V453.018444 (stock)
Install went fine. Booted up, I went through set up. I enabled developer options and enabled adb. My phone could not find the tv to sideload anything so I restarted the TV. Powered down, then back on. But flickering every few seconds along with the white light on the bottom.
The bottom doesn't work for anything. I found if I unplug it and plug it back in then immediately hold down the button the light will start flashing like its installing a firmware. I tried to reinstall the one I previously mentioned. It blinked for a bit but then back to the same flickering on and off.
No help expected, anything GREATLY appreciated.
I tried to include as much info as I could.
Thanks

First, R112 is not for your TV.
If you can enter TV setting , reflash firmware by "Local update" with V458 OTA file ,posted here:
TCL Android TV model 55p8m / Android Recovery TCL/BeyondTV/BeyondTV
My TCL Android TV model 55p8m has stuck and can't press any key in remote. The screen gives options to - Try Again - Factory data reset, but do not know how to select one of this option and continue without a keyboard or remote connected to the...
forum.xda-developers.com
or try reflash by TV power button.
No IMG file released for S343.

Hello Stasiof, Thanks for replying.
I fell asleep last night waiting for the file to transfer to USB.
This morning before work, I unzipped all files onto the root of a FAT32 USB stick, put it in, started the TV holding down the button. It flashed like it was updating, but very briefly. I would say about 15 seconds. And nothing afterward. A blank screen still. Was I not supposed to unzip?

xdeadxpoolx said:
Hello Stasiof, Thanks for replying.
I fell asleep last night waiting for the file to transfer to USB.
This morning before work, I unzipped all files onto the root of a FAT32 USB stick, put it in, started the TV holding down the button. It flashed like it was updating, but very briefly. I would say about 15 seconds. And nothing afterward. A blank screen still. Was I not supposed to unzip?
Click to expand...
Click to collapse
Do not unzip, copy to USB as downloaded.

Disable Developer Option TCL BeyondTV 2021

Hello, I accidentally activated the simulate secondary display (4K resolution) in dev option and now it has been freeze (after Android logo disappear, it stuck at black screen), i couldn't control anything. What should i do, or can i put it into recovery mode to hard reset? Thanks

michioxd said:
Hello, I accidentally activated the simulate secondary display (4K resolution) in dev option and now it has been freeze (after Android logo disappear, it stuck at black screen), i couldn't control anything. What should i do, or can i put it into recovery mode to hard reset? Thanks
Click to expand...
Click to collapse
IMG flash.....firmware.

stasiof said:
IMG flash.....firmware.
Click to expand...
Click to collapse
How to find the firmware?? I don't have the model here...

michioxd said:
How to find the firmware?? I don't have the model here...
Click to expand...
Click to collapse
Sticker at the back of TV,
or put into recovery mode to hard reset.

stasiof said:
Sticker at the back of TV,
or put into recovery mode to hard reset.
Click to expand...
Click to collapse
But how to put it into recovery mode? It's need a keyboard?

Download V660 IMG file ,unzip and "update.img" copy to USB flash drive.
Insert USB drive in TV.
Unplug TV from power.
Press and hold TV power button (P61x must have bellow front LED) and in the same time plug TV back to power.
V660 IMG (must unzip)...
https://blobmarketingsemp.blob.core.windows.net/website/drivers/V660.zip

stasiof said:
Unplug TV from power.
Press and hold TV power button (P61x must have bellow front LED) and in the same time plug TV back to power.
Click to expand...
Click to collapse
I will try, thanks so much

michioxd said:
I will try, thanks so much
Click to expand...
Click to collapse
I found restore file......your TV is P618 ,right?

stasiof said:
I found restore file......your TV is P618 ,right?
Click to expand...
Click to collapse
Yes?

michioxd said:
Yes?
Click to expand...
Click to collapse
Read above...V660 IMG file
1. Format a USB Flash drive using FAT32.
2. Download the zip file containing the software for your TV to your computer.
3. Unzip and copy the software "update.img" file to the root catalogue of the USB flash drive.
4. Unplug the power cord to your TV.
5. Insert the USB flash drive into the USB port on the back of the TV.
6. Press and hold the power button on the TV, not the remote.
7. While holding the button on the TV, plugin the power cord of the TV again.
8. When the software install message appears on the TV, release the power button.
9. Do not unplug the power cord during the software install. When the initial setup screen appears on the TV the software install is completed.

stasiof said:
Read above...V660
Click to expand...
Click to collapse
sorry but.. what's this?

michioxd said:
sorry but.. what's this?
Click to expand...
Click to collapse
Can you read post #6 above again....

stasiof said:
Download V660 IMG file ,unzip and "update.img" copy to USB flash drive.
Insert USB drive in TV.
Unplug TV from power.
Press and hold TV power button (P61x must have bellow front LED) and in the same time plug TV back to power.
V660 IMG (must unzip)...
https://blobmarketingsemp.blob.core.windows.net/website/drivers/V660.zip
Click to expand...
Click to collapse
i have a question, this firmware use for p61x or only p618?

michioxd said:
i have a question, this firmware use for p61x or only p618?
Click to expand...
Click to collapse
x can be 5...6 or 8
P615
P616
P618...all same for firmware.
Your platform (R851T02) thread is here:
TCL Android TV model 55p8m / Android Recovery TCL/BeyondTV/BeyondTV
My TCL Android TV model 55p8m has stuck and can't press any key in remote. The screen gives options to - Try Again - Factory data reset, but do not know how to select one of this option and continue without a keyboard or remote connected to the...
forum.xda-developers.com

stasiof said:
x can be 5...6 or 8
P615
P616
P618...all same for firmware.
Your platform (R851T02) thread is here:
TCL Android TV model 55p8m / Android Recovery TCL/BeyondTV/BeyondTV
My TCL Android TV model 55p8m has stuck and can't press any key in remote. The screen gives options to - Try Again - Factory data reset, but do not know how to select one of this option and continue without a keyboard or remote connected to the...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks so much, it's working!

michioxd said:
Thanks so much, it's working!
Click to expand...
Click to collapse