Hello, I am in trouble: I was stupid and tinkered with firmware, not only from another country, but also for the wrong model. I really need help finding an Update.img I can use specifically for my television model and region. I have searched and searched online and can't find any firmwares for the 40S330...
Any help is appreciated. Thank you.
I had a real similar problem with the 50s434. I grabbed v408 from the big thread, put it on a flash drive, and held the power button during boot to get it to flash it. The TV screen was still dark, but I could tell it was booting. At that point, I could plug the TV into my network, and even cast to it, but still no video. Next, I yanked the power cord, waited a few seconds, and then held the power button down for about 15 seconds with it still unplugged. The idea is that we're draining all the capacitors, so all the ram gets cleared. Finally, I plugged it in and the remote worked again, and everything came up.
oneru said:
I had a real similar problem with the 50s434. I grabbed v408 from the big thread, put it on a flash drive, and held the power button during boot to get it to flash it. The TV screen was still dark, but I could tell it was booting. At that point, I could plug the TV into my network, and even cast to it, but still no video. Next, I yanked the power cord, waited a few seconds, and then held the power button down for about 15 seconds with it still unplugged. The idea is that we're draining all the capacitors, so all the ram gets cleared. Finally, I plugged it in and the remote worked again, and everything came up.
Click to expand...
Click to collapse
Unfortunately this did not work for me. Do you have any other suggestions?
I was just sent some NA specific firmware for my TV. It might just do the trick: https://ttetech.app.box.com/s/4dlp47ryxbaj855ey8l1fm1jui7xzfhn
S434 V440
http://na-update.cedock.com/apps/resource2/V8R851T02/V8-R851T02-LF1V440/FOTA-OTA/V8-R851T02-LF1V440.017008.zip
oneru said:
I was just sent some NA specific firmware for my TV. It might just do the trick: https://ttetech.app.box.com/s/4dlp47ryxbaj855ey8l1fm1jui7xzfhn
Click to expand...
Click to collapse
I'm sorry, I don't check xda often, but TCL actually sent the same thing and my problem is solved! Thank you for your help anyway!
anyone have this file?
Trickman2 said:
anyone have this file?
Click to expand...
Click to collapse
Which file ?
V8-R851T02-LF1V4xx OTA files....for N.America models...
V440
V453
V458
Thanks trying to fix 40S330 Andriod Tv.
Trickman2 said:
Thanks trying to fix 40S330 Andriod Tv.
Click to expand...
Click to collapse
Which firmware your 40S330 is using ?
I don't think is that posted here.....
Is it...R851T10 ?
stasiof said:
Which firmware your 40S330 is using ?
I don't think is that posted here.....
Is it...R851T10 ?
Click to expand...
Click to collapse
Honestly not sure that didn't seem to fix it...lol...says wrong package.
Trickman2 said:
Honestly not sure that didn't seem to fix it...lol...says wrong package.
Click to expand...
Click to collapse
TV working or not ?
If working, read firmware version in setting...
Which firmware you try ?
Don't let me pull every your answer.....
Related
Hi Guys,
i bought a Fire TV today and i think i already ****ed up.
I unpacked it, plugged everything in and got no signal on my TV. I saw that the remote was working since the light on the AFTV responded to my inputs. Tried changing channels on my TV but nothing worked. Then i figured to restart the AFTV and see again. Did that 2 or 3 times and nothing.
Turns out the HDMI cable wasn't fully plugged in. Stupid i know, but happens i guess.
So now i got the signal and the AFTV said the update failed and it should restart in a few minutes. OMG i think i unplugged it while it updated? Oh god no.
It never did restart on its own. I waited at least 15 min. Then i unplugged it again like the screen said and now it is stuck in the boot animation logo. 45 min in and nothing happens.
So i think i bricked my brand new AFTV. Is there anything i can do or do i have to send it back. Cant reach amazon support and support page says nothing about this. I m so mad right now.
Plugged in a usb keyboard and got into recovery mode. Recovery mode says the device will reboot in a "few minutes". It doesn't. I'm stuck.
CaptainFlakes said:
Plugged in a usb keyboard and got into recovery mode. Recovery mode says the device will reboot in a "few minutes". It doesn't. I'm stuck.
Click to expand...
Click to collapse
I think if you hit escape or something you should be able to get to the recovery menu. You could try doing a factory reset.
No i can't do anything in the amazon recovery. It just says the AFTV will restart. But it doesn't.
Why don't you just phone Amazon? They are usually VERY helpful and will help you out
Arkadian1 said:
Why don't you just phone Amazon? They are usually VERY helpful and will help you out
Click to expand...
Click to collapse
Yeah they did. They send me replacement. Just hoped to avoid that. But there seems no way to properly reset the device.
Thx for the help guys.
CaptainFlakes said:
Yeah they did. They send me replacement. Just hoped to avoid that. But there seems no way to properly reset the device.
Thx for the help guys.
Click to expand...
Click to collapse
That's best I don't work for Amazon, but I can't deny that their customer service is second to none!
Useful to know, though... never unplug a Fire TV when it is updating
I did it once with an iPad... I managed to sort it out, but it wasn't the easiest thing in the world to accomplish.
hi guys, rooted my fire tv 2 just the other day and it has been accidentally factory reset, whilst rooted
when i power it on, i get the standard TWRP homescreen, but am not able to press the right directional key on the keyboard, so it boots up to sstandard homescreen, as it has been factory reset it wants me to pair the remote for the first time, no matter how long i press the home key for, or however many times, but it just will not detect
tried new batteries, still a no go
could somebody help me please?
regards
chantelle310 said:
hi guys, rooted my fire tv 2 just the other day and it has been accidentally factory reset, whilst rooted
when i power it on, i get the standard TWRP homescreen, but am not able to press the right directional key on the keyboard, so it boots up to sstandard homescreen, as it has been factory reset it wants me to pair the remote for the first time, no matter how long i press the home key for, or however many times, but it just will not detect
tried new batteries, still a no go
could somebody help me please?
regards
Click to expand...
Click to collapse
I noticed pairing the remote is a little crappy. I would need to hold it down for a long time, then eventually it would continue.
rbox said:
I noticed pairing the remote is a little crappy. I would need to hold it down for a long time, then eventually it would continue.
Click to expand...
Click to collapse
I will try it again in the early hours of tomorrow when I'm not as frustrated by it lol so the factory reset whilst it being rooted hasn't caused any damage then? I was worried it had of
chantelle310 said:
I will try it again in the early hours of tomorrow when I'm not as frustrated by it lol so the factory reset whilst it being rooted hasn't caused any damage then? I was worried it had of
Click to expand...
Click to collapse
No. You can reset all day long if you want. I just did one yesterday. And it was a little frustrating getting the remote to sync. I really wish I could figure out a way to make it able to bypass that, since I just use a keyboard.
rbox said:
No. You can reset all day long if you want. I just did one yesterday. And it was a little frustrating getting the remote to sync. I really wish I could figure out a way to make it able to bypass that, since I just use a keyboard.
Click to expand...
Click to collapse
Phew. That's let me relax a little then. First time rooting properly and enjoying myself up until now haha.
That would be a great bypass. The FTV2 remote is a little crappy compared to 1st gen remote. The buttons feel horrible.
jeez that was a pain. taken me over 12 hours to get this thing to pair back, and i think it finally just happened by chance
for anyone else having this issue, just persevere it will finally pair
rbox said:
No. You can reset all day long if you want. I just did one yesterday. And it was a little frustrating getting the remote to sync. I really wish I could figure out a way to make it able to bypass that, since I just use a keyboard.
Click to expand...
Click to collapse
hey rbox, still having the issue with the right arrow key not becoming responsive in the TWRP boot up menu, but works fine after the home menu has booted up
any suggestions please?
regards
chantelle310 said:
hey rbox, still having the issue with the right arrow key not becoming responsive in the TWRP boot up menu, but works fine after the home menu has booted up
any suggestions please?
regards
Click to expand...
Click to collapse
Are you on TWRP version 3.0.0-4?
rbox said:
Are you on TWRP version 3.0.0-4?
Click to expand...
Click to collapse
I am yes. Was working fine then just weren't lol not too sure what went on. I've tried s different USB kb too
chantelle310 said:
I am yes. Was working fine then just weren't lol not too sure what went on. I've tried s different USB kb too
Click to expand...
Click to collapse
Not sure... everyone else reported it's working. Maybe try a different keyboard?
rbox said:
Not sure... everyone else reported it's working. Maybe try a different keyboard?
Click to expand...
Click to collapse
Right ok just checked and it seems I'm not on the latest. How do I go about updating considering I have no way of using the keyboard to install from sd card
Sorry for the probable annoying noob questions. Just trying to learn
Never mind. I figured it out via your thread rbox. Apologies for the noob moves. Such a big forum I get lost with pages lol
Thanks for the help
Anyone found a way/hack to have the Firetv2 remote connect without having any internet connection just like the old gen remote?
Thanks
I'm stuck on this issue with the Fire Stick 2 (tank)! Help please!
cannot pair the remote at all
Hi,
yesterday while using the watch I got the message "shutting down". The battery was flat and after charging the watch got stuck on the four moving boot symbols. To cure this I have tried both software repair and update using the Experia companion. I have as well tried resetting to factory settings using the watch own recovery but all to no avail. Can anyone please help me how to proceed from here?
baronimus said:
Hi,
yesterday while using the watch I got the message "shutting down". The battery was flat and after charging the watch got stuck on the four moving boot symbols. To cure this I have tried both software repair and update using the Experia companion. I have as well tried resetting to factory settings using the watch own recovery but all to no avail. Can anyone please help me how to proceed from here?
Click to expand...
Click to collapse
In the recovery log it says in the beginning: couldn't find tzdata for local time, GMT!, posixrules!
baronimus said:
In the recovery log it says in the beginning: couldn't find tzdata for local time, GMT!, posixrules!
Click to expand...
Click to collapse
I now installed twrp and flashed SWR50_6.0.1_MWD49B This was successful but the watch is still stuck on the four symbols. I'm outta clues please help anyone
baronimus said:
I now installed twrp and flashed SWR50_6.0.1_MWD49B This was successful but the watch is still stuck on the four symbols. I'm outta clues please help anyone
Click to expand...
Click to collapse
I had the same issue and responded on your partition likeness. I can only get mine back to LP. I have tried the above ROM and several others to no avail. If you happen to get yours going again, please advise the steps you took...and I'll do the same.
Will do
baronimus said:
Will do
Click to expand...
Click to collapse
Did you ever get yours to fully boot to MM? I have since tried other methods and am still stuck on the 4 dots / symbols. LP still runs fine, but would like to get it to MM.
I did not unfortunately. Mine works fine on LL except for gestures. It does not update automaticly which is good, since MM gives four dots. Why it doesn't work beats me.
All the best
baronimus said:
I did not unfortunately. Mine works fine on LL except for gestures. It does not update automaticly which is good, since MM gives four dots. Why it doesn't work beats me.
All the best
Click to expand...
Click to collapse
Same here. Thanks for the response. I was wondering if you somehow got it to work. I have tried a couple other ROMs to no avail. I'm quite sure if the experts had the watch, they could figure it out, but when theirs do not act like mine (ours), it may be hard for them to reproduce a fix. Anyway, LP works fine and does quite well with the battery also...so, it is fine.
golfnut22 said:
Same here. Thanks for the response. I was wondering if you somehow got it to work. I have tried a couple other ROMs to no avail. I'm quite sure if the experts had the watch, they could figure it out, but when theirs do not act like mine (ours), it may be hard for them to reproduce a fix. Anyway, LP works fine and does quite well with the battery also...so, it is fine.
Click to expand...
Click to collapse
Hmmm right now I believe my watch is fatally damaged. It rapidly loses power (100% to 0% in a couple of minutes) when connecting to the smartphone. I think my (perhaps your) problems arise from a physically damaged watch. I think the battery is damaged and perhaps also the HDD probably due to moist having entered the watch. My problem started after a swim.
Best of luck with your watch, I think mine goes to scrap
baronimus said:
Hmmm right now I believe my watch is fatally damaged. It rapidly loses power (100% to 0% in a couple of minutes) when connecting to the smartphone. I think my (perhaps your) problems arise from a physically damaged watch. I think the battery is damaged and perhaps also the HDD probably due to moist having entered the watch. My problem started after a swim.
Best of luck with your watch, I think mine goes to scrap
Click to expand...
Click to collapse
Oh, sorry to hear that. Right now, I can get a solid 2 days of battery life with just having bt and reviewing notifications. I hope it does not go your route, but thanks for the heads up. Several times I had to wait until mine fully discharged before I could get it going again when I was playing around with flashing files. Anyway, I figured I was sort of lucky not bricking in since I had no clue what I was doing. So, I have just decided to let it be for now and concede to running it on LP.
Hi,
My Galaxy S9 (Exynos) just stopped charging today. It had no problem this morning, but when I tried recharging in the evening, it won't charge at all. Connecting it to PC won't work either. But OTG works just fine. I am wondering if it is a hardware or software problem.
I unfortunately do not own a wireless charger so its almost dead now. If I could confirm it's a hardware problem, I would just buy another charging board but I would like to confirm it first before buying. Is this a common problem in s9? Could there be any issue on the software level?
Any help is appreciated. Thank you.
seijidinzuala said:
Hi,
My Galaxy S9 (Exynos) just stopped charging today. It had no problem this morning, but when I tried recharging in the evening, it won't charge at all. Connecting it to PC won't work either. But OTG works just fine. I am wondering if it is a hardware or software problem.
I unfortunately do not own a wireless charger so its almost dead now. If I could confirm it's a hardware problem, I would just buy another charging board but I would like to confirm it first before buying. Is this a common problem in s9? Could there be any issue on the software level?
Any help is appreciated. Thank you.
Click to expand...
Click to collapse
the only things that come to mind that could cause this is the board being bad or the kernel being corrupt. If you can OTG, you should be able to Odin with it (key word there is should), if you can Odin with it, just flash the HOME_CSC firmware files and if it charges afterwards, then you know it was the kernel. If it still doesnt work, bad charging port/card
Thank you for your response, but as I have said, my PC cannot charge it or even detect it at all. OTG is the only thing that works. Maybe the phone is blocking any data transfer when power come along on the usb port? Am I making any sense?
seijidinzuala said:
Thank you for your response, but as I have said, my PC cannot charge it or even detect it at all. OTG is the only thing that works. Maybe the phone is blocking any data transfer when power come along on the usb port? Am I making any sense?
Click to expand...
Click to collapse
you are making sense, but if the OTG works, then data transfer should be working too. Can you boot to DL mode?
youdoofus said:
the only things that come to mind that could cause this is the board being bad or the kernel being corrupt. If you can OTG, you should be able to Odin with it (key word there is should), if you can Odin with it, just flash the HOME_CSC firmware files and if it charges afterwards, then you know it was the kernel. If it still doesnt work, bad charging port/card
Click to expand...
Click to collapse
youdoofus said:
you are making sense, but if the OTG works, then data transfer should be working too. Can you boot to DL mode?
Click to expand...
Click to collapse
Yes I can boot to dl mode and recovery too. When I connect it to PC, the PC don't even make any sound (you know that usb connect sound).
youdoofus said:
you are making sense, but if the OTG works, then data transfer should be working too. Can you boot to DL mode?
Click to expand...
Click to collapse
I tried going to dl mode again and noticed that I can only boot to the warning screen, and then the volume button stops functioning there. Volume buttons works normally in recovery and OS. And also, I borrowed my friend's wireless charger and it was able to charge just fine with it.
youdoofus said:
you are making sense, but if the OTG works, then data transfer should be working too. Can you boot to DL mode?
Click to expand...
Click to collapse
I apologise for quoting you again and again, but I just wanted to update you that my Bixby button was stuck which made the volume buttons not working in the warning screen. I tore down the phone, fixed the bixby button and now I can boot to dl mode. And good news, Odin can detect the phone in dl mode. I will flash as you suggested and report back. Thanks a ton
seijidinzuala said:
I apologise for quoting you again and again, but I just wanted to update you that my Bixby button was stuck which made the volume buttons not working in the warning screen. I tore down the phone, fixed the bixby button and now I can boot to dl mode. And good news, Odin can detect the phone in dl mode. I will flash as you suggested and report back. Thanks a ton
Click to expand...
Click to collapse
youre most welcome! im glad you found the culprit because i wouldnt have ever thought of that. Situations like these are good in that they show examples of how weird stuff can get from time to time lol
if the phone is recognized by Odin and youre able to get to DL mode now, you should be all set
youdoofus said:
youre most welcome! im glad you found the culprit because i wouldnt have ever thought of that. Situations like these are good in that they show examples of how weird stuff can get from time to time lol
if the phone is recognized by Odin and youre able to get to DL mode now, you should be all set
Click to expand...
Click to collapse
So, I downloaded the firmware, did a complete wipe with the csc file. Annnd bad news, it still won't charge I just gonna buy a new charging board.
I wonder why the usb works only in download mode though, still give me doubts that the charging board is the culprit. :laugh: anyway thanks for helping.
Hey, I faced a similar problem today, what was your solution to fix it?
I got the screen on my S9 replaced and now it won't charge... usually. I took it back to the shop and they got it to charge with a different cable. I tried a different cable at home and it worked for a while, but now it's not charging again. So annoying and confusing.
I am going to write how it went since there are people asking. Maybe will be helpful or not helpful for people who stumble across this thread in the future too.
So, I gave up trying to fix it and bought a new charging board, it worked for a day and then it stopped working again. I am pretty sure even the original charging board was just fine. I think the whole issue had something to do with Samsung's security or self-protection system.
I will not buy Samsung again. Thanks.
I understand that this tablet (Samsung SM-T800) is old but If someone out there can give me some input I'd greatly appreciate it.
So far I've replaced the:
USB Charger Port Connector Module Flex Cable
LCD Connector Flex Ribbon Cable
Battery
I let it drain completely and recharged it today after installing the new charging port. Powered it up and I'm still getting a bootloop. If I hold the power button down and keep it down it will go to the set up screen, Which I set up thinking it would boot normally afterwards but it still wont. I've tried numerous stock firmwares for this particular model all with no luck. What am I missing? Can someone shed some light on my issue or give me some ideas to try out. PLEASE...
Much Thanks in advance -
tat2me2 said:
I'm trying to basically revive a friend's tablet. The problem is I've tried so many different things that I'm getting frustrated. Any recommendations on which firmware to use to get it back to the way it was out of the box or close to it. It is a U.S. model. Thanks for any help you can provide.
Click to expand...
Click to collapse
You need the cellular south XAR firmware for an unlocked model. If its a carrier branded model then you will need that specific firmware from the carrier.
ashyx said:
You need the cellular south XAR firmware for an unlocked model. If its a carrier branded model then you will need that specific firmware from the carrier.
Click to expand...
Click to collapse
Just to clarify, I just installed T800XXU1ANF8_T800XAR1ANF6_XAR via Odin - The device will cycle through the "Samsung Galaxy Tab S powered by android" screen then it will cycle through the colored Samsung logo and then start over. I'm dumfounded...
Thanks for replying, I've tried several of the XAR firmware's that are available, but the problem I'm running into is a constant bootloop afterwards on any that I try, even after resetting and clearing cache.
tat2me2 said:
Just to clarify, I just installed T800XXU1ANF8_T800XAR1ANF6_XAR via Odin - The device will cycle through the "Samsung Galaxy Tab S powered by android" screen then it will cycle through the colored Samsung logo and then start over. I'm dumfounded...
Thanks for replying, I've tried several of the XAR firmware's that are available, but the problem I'm running into is a constant bootloop afterwards on any that I try, even after resetting and clearing cache.
Click to expand...
Click to collapse
That is a very old kitkat firmware.
You will also need to factory reset from recovery.
ashyx said:
That is a very old kitkat firmware.
You will also need to factory reset from recovery.
Click to expand...
Click to collapse
I guess I'll try to figure out what the most recent firmware available is and try that.
ashyx said:
That is a very old kitkat firmware.
You will also need to factory reset from recovery.
Click to expand...
Click to collapse
I just flashed T800XXS1CRI5_T800XAR1CRI5_XAR - as I expected, it just boot-looped over and over again but for the hell of it I held the power button down for awhile and everything started to load like it should however when I let off of it, it went into the bootloop again. A few weeks ago I replaced the power/volume/headphone ribbon thinking that was the problem but now I'm truly perplexed. Any suggestions?
tat2me2 said:
I just flashed T800XXS1CRI5_T800XAR1CRI5_XAR - as I expected, it just boot-looped over and over again but for the hell of it I held the power button down for awhile and everything started to load like it should however when I let off of it, it went into the bootloop again. A few weeks ago I replaced the power/volume/headphone ribbon thinking that was the problem but now I'm truly perplexed. Any suggestions?
Click to expand...
Click to collapse
That behaviour suggests a completely flat battery.
ashyx said:
That behaviour suggests a completely flat battery.
Click to expand...
Click to collapse
Just ordered a new battery, should arrive tomorrow. I appreciate the help.
ashyx said:
That behaviour suggests a completely flat battery.
Click to expand...
Click to collapse
New battery and flex cable did not change the bootloop issue.
tat2me2 said:
New battery and flex cable did not change the bootloop issue.
Click to expand...
Click to collapse
I understand that this tablet (Samsung SM-T800) is old but If someone out there can give me some input I'd greatly appreciate it.
So far I've replaced the:
USB Charger Port Connector Module Flex Cable
LCD Connector Flex Ribbon Cable
Battery
I let it drain completely and recharged it today after installing the new charging port. Powered it up and I'm still getting a bootloop. If I hold the power button down and keep it down it will go to the set up screen, Which I set up thinking it would boot normally afterwards but it still wont. I've tried numerous stock firmwares for this particular model all with no luck. What am I missing? Can someone shed some light on my issue or give me some ideas to try out. PLEASE...
Much Thanks in advance -
Did you find a solution meanwhile? Because I now have the same strange behavior - when starting the device on battery, it boot-loops, when on power it does something similar but does not boot at all but rather shortly shows the grey battery symbol (charging), then black, then battery ...
However, if pressing and holding the power button while on power, it tells me the battery percentage. When using Home+Pwr+VolUp (then I can leave Home and VolUp but *must* keep Pwr pressed) sometimes it boots into recovery but most of the time it boots normally and everything seems to be perfect. As soon as I leave the power button, it immediately goes off. The battery itself seems OK, charging speed appears reasonable and once it is running, too.
However, it's completely random, at times it also runs smoothly for hours.
As I had similar problems before with original Samsung firmware I flashed latest TWRP and LineageOS a 2-3w ago - does not improve anything. I opened the back cover but could not see anything suspicious.
Earlier I was even able to do an "adb logcat" while it was running until a crash - it just stops, no OS errors or anything of interest. Hence, cannot be a SW-problem, I'd think.