TCL U43P6036 (P6046) shuts down at boot before Android logo - Philips, Sony, TCL Android TV

Hi everyone,
My parents have a TCL U43P6036 (but hardware says P6046) that keeps shutting down at boot just after the dots animation/before the Android logo.
I don't have a clear backstory of the problems before this but I know the screen started to become darker on a side, there was also a moment when there was no image but the sound was working, and finally this problem of shutting down at boot.
It happens 100% of the time.
I tried a hard reboot but I'm not even sure the buttons under the screen are working for that purpose as there's not clear volume down button (the buttons are like "<", power/menu, ">"). And my attempts at a hard reboot all failed (Android says "error" and just reboots, then the TCL logo shows up and "error" again, etc.)
There's no reset button too, so I can't even try that.
Now I think the next step is trying to flash it but I'm not even sure of the version of Android. The manual says "Android N (7.0), O (8.0) Q3 ‘18 updt" but I don't know what it really says (is the OS Nougat 7 or Oreo 8?). I know some auto updates have been done.
Anyway, I'm stuck and not sure about the real problem here...

Update: tried to flash it but nothing happened at all. The TV starts like usual, then shuts down after the dots animation/before the Android logo... I don't even know if it detected the USB drive...

Related

[Q] Kaiser wont permenantly install froyo 2.2

Hey there , to start off , Im pretty new to putting android and stuff on here haha. Well I finally got it to boot up android using Haret.exe , but then today I decided I wanted it fully on my system without windows...well heres the problem
I flashed the kaiser by holding the camera button and hiting the reset button...which worked fine. Well after I did that , I hit the reset button , and the AT&T symbol came up , then after a few seconds the Penguin Boot screen comes up and starts doing the weird script thing , then I hit the Dpad to install. When It come to the screen , I make sure that Both NAND things are bubbled off , then I go at it and hit install , and clear all data etc , then it goes to formatting. And after everything is complete I go to quit , then it does some more black screen script stuff and then it started booting the green weird logo ( not the android , the one for Froyo 2.2 ) and then after a few minuites it finally boots up. I then wait 10-15mins for it to finish everything once installed , and then I turn it off by battery pull ( and normal shutoff , ive tried both). then when I turned it back on , It STILL goes to the at&t logo , and repeats EVERYTHING above..please help ,I have tried everything here , and nothing seems to work.....ahhh im so confused haha.
Regards , Dread
What is the problem? Does it boot into android after that? It sounds like you are just describing what happens when android boots normally.
If it's the AT&T logo you don't like, search on this forum for splash screens, there are lots of replacements to choose from.
It boots into android after that , but when I turn it off , I have to go through the whole install screen agian and then it has all the same settings , its just very annoying
Are you pressing the D-pad and installing every time you boot? You only need to install it once....
The second time you turn it on, just don't press anything while it's booting, and it will go straight into android, with all your settings saved.
so why does it go to the weird boot text penguin screen? shouldnt android start up as soon as the phone boots? or is it supposed to be penguin screen , then android load screen?
it's not weird, all phone (and linux system) boot in this way.
Oh alright , Is there any way to make it into a bootlogo?
DreadCode said:
Oh alright , Is there any way to make it into a bootlogo?
Click to expand...
Click to collapse
Not at the moment, but right now the text screen is there to show that the phone is actively booting into Android. Once it gets to a certain point, the Android boot logo will start, and the text screen goes away.
I know it looks messy, but look at it this way. You're able to see just what the phone is doing during boot, and see that the phone is still booting and not freezing up and crashing.
He can make a splash screen, just not one to cover the kernel bootloader. I have one that got left over on ths phone after a modded wm6.5 rom. I keep it because it shows CPU, memory and ROM/radio verson in the 2nd splash.
Sent from my Not So Super Froyo using XDA App
I can put a boot image while the kernel initializes but the text will still overlap it due to framebuffer issues.
another way is set the output to a virtual terminal so is not visible.

[Q] Screen Issues Lead To Bricked Device

I was trying out using a keyboard with a cheap USB OTG cable, and all was good. Then all of the sudden the screen went buggy, where ever other line of pixels was shifted to the left or the right, almost like some sort of corrupted video file. It started to reboot itself, and it got to the black screen with the Google logo and then the screen fuzzed in the same way as before. It then starts to reboot and does the same thing over and over again. I find that I can get to the recovery screen with the scroll arrows. From there, if I tell it to reboot into recovery it goes back into the same Google logo bootloop. I then went back to the original recovery screen and I decide to try out adb to see if it works. Sure enough it does, and I unwisely start flashing a stock 4.2 bootloader image. However, while it is flashing the screen does the same fuzz thing and and stays fuzzed. Then it doesn't respond to anything. I take out the battery, and try to restart and with will not turn on at all, no vibration, no light from the screen, nothing. I tried a unbricking methods from there, and nothing can make it come back alive. Any ideas?
Additional info:
GSM tajkju
Bootloader unlocked
Running stock unrooted 4.2 that I flashed manually
Stock recovery

Phone stuck on black screen even soft reset does not work

Hi,
I tried bunch of stupid **** today on my phone to try to update it and now its stuck on black screen. I tried to open recovery mode too but nothing shows up. Just a while ago it was boot looping with android logo and "Your device is unlocked message" but even that stopped now. Is there anything I could do or is this thing dead for good?
P.S. the device does not show up on ./adb devices as well

Bootloop after Flashing with Odin

Hello,
i wanted to root my A50. I watched a Tutorial (
) and i am stuck at 5:02 in the Booting screen (just the Samsung logo). Everytime after a while of showing the booting screen it restarts and shows: "The Phone is not running samsungs official software. You may have problems with features or security. and you wont be able to download Software updates". Then after a while it shows the booting screen again. This repeats all the time. I already googled and found nothing that can help me.
I hope anyone can help me
press the power button multiple times until it vibrates

Question C21Y Bricked / Can't flash

Hi, I'm having a problem with my phone (C21Y RMX-3263) being stuck in bootlop after accidentally updating magisk via direct install option (has been rooted once already with patched boot img and spd tools). I figured I should just flash the old firmware but neither SPD research and upgrade tools work properly, for about 10-30 seconds all is going well, but then it just gets stuck on downloading, on different parts like super, or boot randomly alternating between attempts. I've left it on for about 4 hours and tried multiple times with no progress at all. There is nothing visible on the screen but holding the vol down button and plugging the cable in seems to initiate fastboot. I've tried using different versions of the tools and different firmwares for my model but nothing seems to work. The bootloop itself is very weird - the phone buzzes and the splash logo appears, afterwards starting to glitch out extremely eerily, the colors start to become weird, white lines dance on the display and after that it turns blank and flashes gray for a few seconds before turning off, looping and doing it all again. Pretty sure this isn't a hardware issue as the phone was working fine before. Assistance would be much appreciated
its dead
loardsudo said:
its dead
Click to expand...
Click to collapse
Thank you for your incredibly detailed and elaborately constructive reply

Categories

Resources