Develop Bugs

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 TV.
Please help
Android Recovery TCL/BeyondTV/BeyondTV
9/PPR1.180610.011/xin1_zeng05102015
User/release-keys
Use volume up/down and power
Can't load Android system. Your build may be corrupt. If you continue to get this message, you may need to perform a factory reset, and erase all user data stored on this device
- Try Again
- Factory data reset
Click to expand...
Click to collapse

smartcard2 said:
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 TV.
Please help
Click to expand...
Click to collapse
Your TV should have some buttons or multifunctional joystick somewhere behind. Look for that

how did you get in there?
i've been trying to but can't lol
i would try usb keyboard / or a usb male to male cable to see if fastboot / adb is working

fuqi said:
how did you get in there?
i've been trying to but can't lol
i would try usb keyboard / or a usb male to male cable to see if fastboot / adb is working
Click to expand...
Click to collapse
Tried all options, and still in the same stage.
I came to know my model is Australian based model

did you try to re-install the latest firmware?

I couldn't find the new firmware.
Do you have it?

https://drive.google.com/open?id=1K5MiRPwuZ1zCZXeu31UBSAKfGQT5AqZa

Which file and how to apply

smartcard2 said:
Which file and how to apply
Click to expand...
Click to collapse
use : V8-R851T02-LF1V252.011680_PKG_USB_GMC.zip (will be done in 3 min)
extract it till u get a "Update.img" put it on a Usb Stick. Hold power button on your TV for around 10 seconds (while it's off).

fuqi said:
use : V8-R851T02-LF1V252.011680_PKG_USB_GMC.zip (will be done in 3 min)
extract it till u get a "Update.img" put it on a Usb Stick. Hold power button on your TV for around 10 seconds (while it's off).
Click to expand...
Click to collapse
Thanks fuqi.
I did the following:
1) unziped the Update.img file to a USB drive, the USB does not have any other file lthan Update.img
2) Switched off the TV
3) Inserted the USB stick to one of the USB port in the TV
4) Switched On the TV while holding the power button
But nothing happened, still the same of screen came back stating "Android Recovery TCL/BeyondTV/BeyondTV.........................."

knowing this plattform very well it is almost Impossible to corrupt the realtek update. mechanism.
there is supposed to come a blue screen with a Progress bar.
either way, you could also try the other v252 zip.

fuqi said:
knowing this plattform very well it is almost Impossible to corrupt the realtek update. mechanism.
there is supposed to come a blue screen with a Progress bar.
either way, you could also try the other v252 zip.
Click to expand...
Click to collapse
Should I make the USB stick as a bootable first (before copying the IMG file)?

no, just a normal usb stick, probably fat32 needed. i did not try exfat/ntfs

thanks for sharing , i Suppose that firmware are compatible wit the TCL 65P8M ,

yes

I keep trying the steps, I used multiple USB sticks (USB 2.0 and 3.0), tried it on both USB ports and the device just does not recognise it and it goes back to the android revovery screen. The bottom light also keeps blinking while the TV is on and also as soon as I turn on the switch on the power, the TV turns on, the only way to turn the TV on and off, is through the switch.
PS: I'm the same person as smartcard2

did you try "V8-R851T02-LF1V252.011680.zip" as well? since update.img and .zip files uses different update mechanism.
don't want to confuse you. V8-R851T02-LF1V252.011680_PKG_USB_GMC.zip <- this is the .img you tried.

fuqi said:
did you try "V8-R851T02-LF1V252.011680.zip" as well? since update.img and .zip files uses different update mechanism.
don't want to confuse you. V8-R851T02-LF1V252.011680_PKG_USB_GMC.zip <- this is the .img you tried.
Click to expand...
Click to collapse
Thanks for the reply. Yes, I have been trying the V8-R851T02-LF1V252.011680_PKG_USB_GMC.zip
Now I downloaded the V8-R851T02-LF1V252.011680.zip file, but it has many files not one single IMG file. So I unzipped all these files to the USB and tried but still did not work

yea. just put the zip on the usb, no need to extract in this case.

fuqi said:
yea. just put the zip on the usb, no need to extract in this case.
Click to expand...
Click to collapse
Tried, still not working

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.

Bricked Fire TV (Gen 2 - V7.6.1.4)

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?

Fire TV Stick 4k half dead open for suggestions

2 days ago I came back to my Fire TV Stick 4k only to find black screen with "loading..." letters in corner, and at that moment pressing home button did nothing, seemed that remote isn't working at first or device froze.
3 Hours before that I has using device, and only thing I did i power toggled it 3 times in few seconds using power button on remote (don't ask why it irrelevant now)
After I power toggled the device, and after "Fire TV" logo it stated that it can't find my remote. So i changed fresh batteries, tried to resync remote to device and all other stuff, but nothing helped. So I decided to try my remote on another device, and concluded that remote is perfectly fine and connects to other device without problems, and that it's nothing wrong with it.
At the same time it baffled me that device didn't load home screen after boot, just notification that it cant find remote and black screen after that.
Later I discovered that remote is in fact working (built in firmware restore functions and menu that is accessed by long pressing home button for few seconds).
So I decided to do factory reset by pressing key combination.
Factory reset menu came up, and after I pressed "OK" nothing happened, device didn't reboot.
Pressed key combo again, and let the timer for factory reset count down to zero.
When it came to '1' it froze.
Pressing key combo again factory reset menu would come again and do countdown from start.
I can also invoke menu accessed by pressing home button for few seconds, but what ever I choose from there it freezes, but if I press home button again it opens same menu again and move left-right and even enter "profiles", so it's not frozen, it just seems that it can't open any menu entry for some reason.
At he same time I can access it via wifi ADB and run ADB shell commands, so it is connected to wifi that has internet access.
I tried running "adb reboot recovery", device reboots, comes up with Fire tv logo and "no command" on screen.
It sits there for a minute and after it reboots and goes into normal boot.
I also tried "am start -n com.amazon.tv.launcher/.ui.SettingsActivity" folowing "am broadcast -a com.amazon.tv.intent.action.MASTER_CLEAR" but no avail.
it states "Broadcast completed: result=0" and that is it.
How do I factory restore / flash firmware, whatever ?
I will take any suggestion before tossing it into bin, because I think memory got corrupted somehow and device is processing and executing fine.
Edit 1 :
Safe mode method using USB keyboard on OTG cable doesn't work. Tried ctrl+alt+menu+prtscr+i several times, it invokes nothing.
Edit 2 :
Tried rooting using shorting to ground exploit, but it doesn't work since serial number of device is too high thus bootloader locked.
Edit 3:
I can see all the installed packages over ADB and uninstall ony of them normally.

Hi mate, try my solution up for the bootlooping firestick

Travel_Mate said:
Hi mate, try my solution up for the bootlooping firestick
Click to expand...
Click to collapse
Thank you for suggestion. The main question is how do I format USB stick to Android "internal memory" if I don't have Xiaomi 4K stick, like you mentioned in your original post ?
I have another working Fire Stick 4k, and have formatted USB stick using that device, but since Fire Stick 4k uses Fire OS 6, and possibility to format USB stick to "internal memory" is a feature of Fire OS 7, I don't think it will work.
At the moment I just formatted this stick using Fire OS 6, connected using OTG to malfunctioned stick, I can see Fire TV accessing it few times on boot (LED flashes), but after boot I don't see any activity. I will let it sit for a few hours.