crwdns2936637:0crwdne2936637:0 crwdns2853008:0crwdne2853008:0 crwdns2861143:0crwdne2861143:0

Released May 2015, identified by model number SM-T350. Features 8.0″ TFT capacitive touchscreen, 5 MP camera, Wi-Fi, GPS, Bluetooth.

crwdns2934591:0118crwdne2934591:0 crwdns2934593:0crwdne2934593:0

crwdns2933897:0crwdne2933897:0

SM T290. Screen replaced and after an update touch stopped working.

I replaced the screen of a Samsung Tab A 8.0 T290. Touch was working fine. Client said there was an update and updated it. The touch stopped working. I ordered a new screen thinking the one I installed was defective. Same issue, the touch was not working . Client claims he contacted Samsung and Samsung would have said the firmware recognized it was not an original screen and locked the touch.

anyone heard about this? Is this something new that Samsung does? I replaced it on another tablet same model and no issues whatsoever.

please advise.

thanks

crwdns2934089:0crwdne2934089:0 crwdns2934093:0crwdne2934093:0

crwdns2934109:0crwdne2934109:0

crwdns2853045:0crwdne2853045:0 crwdns2853046:0crwdne2853046:0
crwdns2889612:0crwdne2889612:0 2
crwdns2942205:01crwdne2942205:0

I have the exact same issue as written. After I had installed the new screen and was assembling the tablet I accidentally powered the unit on and in that short period the touch worked fine. I had shut the tablet back down to finish reassembly and on rebooting for the first official time I have had no touch control. I’m lost.

crwdns2934271:0crwdnd2934271:0crwdne2934271:0

crwdns2934285:0crwdne2934285:0

crwdns2933315:02crwdne2933315:0

crwdns2934221:0crwdne2934221:0
crwdns2931211:0crwdne2931211:0 crwdns2931215:0crwdne2931215:0 crwdns2934225:0crwdne2934225:0
crwdns2934057:0crwdne2934057:0

crwdns2933897:0crwdne2933897:0

I did a rollback of the Firmware and it fixed the issue

crwdns2934105:0crwdne2934105:0

crwdns2853045:0crwdne2853045:0 crwdns2853046:0crwdne2853046:0
crwdns2889612:0crwdne2889612:0 2

crwdns2942205:01crwdne2942205:0:

I'm having the same problem ... which version did you get back to?

crwdns2934271:0crwdnd2934271:0crwdne2934271:0

crwdns2934285:0crwdne2934285:0

crwdns2933897:0crwdne2933897:0

I have this same issue on one of my kids’ tablets that has a replaced screen. Rolling back the firmware to the previous version fixed it. Looking over the system logs from before and after the firmware update and seeing which devices are recognized, I suspect they left a driver out of the firmware either on purpose or by mistake. Somehow I doubt Samsung would do this on purpose as I wouldn’t expect replacing screens on one particular model of tablet to be a big source of revenue for them but you never know.

crwdns2934105:0crwdne2934105:0

crwdns2853045:0crwdne2853045:0 crwdns2853046:0crwdne2853046:0
crwdns2889612:0crwdne2889612:0 1

crwdns2944067:02crwdne2944067:0:

How you downgrade firmware??

crwdns2934271:0crwdnd2934271:0crwdne2934271:0

would it be possible to tell which version you used to get the firmware back? if you have any tutorial you used it would be great ... i need to do this downgrade too

crwdns2934271:0crwdnd2934271:0crwdne2934271:0

crwdns2934285:0crwdne2934285:0

crwdns2934229:0crwdne2934229:0

Carl Letourneau crwdns2934231:0crwdne2934231:0
crwdns2936625:0crwdne2936625:0:

crwdns2936751:024crwdne2936751:0 0

crwdns2936753:07crwdne2936753:0 1

crwdns2936753:030crwdne2936753:0 6

crwdns2942667:0crwdne2942667:0 1,605