cancel
Showing results for 
Search instead for 
Did you mean: 

Original topic:

Tiuch screen not working after ui 6.1 update

(Topic created on: 06-09-2024 07:49 AM)
120 Views
delmonte56
Beginner Level 2
Options
Galaxy S
My samsung s21 ultra touch screen stopped working after ui 6.1 update kindly tell me a solution cannot downgrade to ui 6.0 tried everything there is some binary issue or something
0 Likes
6 Comments
Happysonu
Active Level 3
Galaxy S
Jsa hi hm uograde krty firewarm ko binary bhi upgrade ho jty so downgrade nhi kr sakty ap dobare s flash kro apna phone ko but is bar csc change kr ka
0 Likes
delmonte56
Beginner Level 2
Galaxy S
Bro xaa csc rkh k dkha tha aapka hu gya tu kindly guide krdu
Mera model sm998u1 hai
0 Likes
Happysonu
Active Level 3
Galaxy S
Try krn koi aur csc rkh k umeed ha ho jay ga
0 Likes
Happysonu
Active Level 3
Galaxy S
Bro mra apna esa masla nhi bna but yh software glitch ha isa software mn hi solve krna ho ga
0 Likes
ArhumAB
Active Level 3
Galaxy S
Visit customer service centre for guidance.
0 Likes
phucklogy
Beginner Level 3
Galaxy S
I recently updated my Samsung Galaxy S21+ 5G SM-G996U VZW (Verizon variant) to the latest firmware (G996USQSBGXF1) android 14 using ODIN, as I was currently out of the US and couldn't receive OTA updates.

The US Snapdragon variant of the Galaxy S21+ lacks the OEM unlock option in its developer settings, thereby restricting certain actions such as installing custom ROMs and Recovery. However, since I was only flashing a stock firmware update, this limitation didn't pose an obstacle.

I downloaded the correct firmware from SamFW and proceeded with the flashing process. I opted for the normal CSC instead of the HOME CSC, as it resets the data, but since I didn't have any important data, I proceeded with it. The flash completed successfully, and the phone booted up as expected. However, upon reaching the welcome screen, I encountered an issue where I couldn't interact with the screen via touch. I force-shutdown my device, cleared the cache, and even tried a factory reset again, but unfortunately, none of these methods worked.

Assuming it was a software bug (ironically), I tried to downgrade to firmware version G996USQSBGXE2. Unfortunately, this didn't resolve the touch screen issue either. It's important to note that attempting to downgrade to a lower binary version results in errors like "SW REV FAIL" and "SECURE CHECK FAIL" making G996USQSBGXE2 my only viable option.

Now the goal was to set up the phone and diagnose the issue. I used an OTG cable to connect a mouse, which enabled me to simulate touches and complete the setup. Additionally, I configured the Microsoft Link to Windows feature, allowing simultaneous interaction with both keyboard and mouse. This setup eliminated the need for constantly plugging and unplugging the OTG cable and switching between HID (mouse and keyboard), making it easier to navigate and control the phone despite the touch screen problem.

I also attempted wireless debugging of the display using ADB, in case I needed to reserve the USB port for other purposes later on. However, I wasn't able to gather much useful information from this process. Next, I tried to resolve the issue using Samsung Smart Switch on a PC, but unfortunately, this method also didn't work for me.

After trying everything, here are two potential solutions that I can suggest for this bug:

One potential solution is to perform a TSP FW Update using the dialer code *#2663#. Access the TSP FW update menu and select "TSP FW Update." If the phone's TSP FW version is listed as "NA," this could potentially be the root of the problem. I haven't been able to try this yet as I currently don't have access to my phone, and there's a chance it might fail, but I'm hopeful it could resolve the issue. If anyone tries this and has success or further insights, do let me know.

The second potential solution is to wait for a new firmware release. If the TSP FW Update doesn't resolve the issue, it might be necessary to wait for a newer firmware version. If OTA updates aren't available, flashing the new firmware via ODIN could be required.

You could try replicating all these steps to see if any of them could solve your problem, but it's important to do your homework and research thoroughly beforehand. If anyone has any additional suggestions, your help would be greatly appreciated.
0 Likes