Dell Latitude 5290 2-in-1 Touchscreen Bricked by Firmware Change (WCOM484E)

@tim753milner​ Could you let me know if there is a fix available? Because this is not only happening to me, but plenty of other latitude 5290 2 in 1's also. Thanks

I'm also affected by this, issue occurred after windows update (typically I'm on linux but needed to do something in windows - and it pushed updates). After windows update Touch screen no longer responds in win/linux - it was bricked literally just now by an update.

@pchelka​ Hey man, i saw your comment on reddit. I couldn't reply to you, my comments on reddit just get hidden idk why. Please let me know if you find ANY kind of solution. This is really stressful. Please check your Device manager if it shows WCOM484E or WCOM484D. Just know that this likely isn't a Permanent Brick, because this is just a firmware bug cause by windows updates. If Dell notices our post, they might be able to do something. So no need to worry :)

@pchelka​ Could you please ask that guy on reddit to dump the touchscreen firmware from the working unit?

I will, hopefully he will respond - from what i see last state was he could not get all the info needed.

@pchelka​ Hi, any updates?

@yotur​ 
He did not respond unfortunately

One note though - magically my touch screen started working again, (i have not launched windows sitting on ubuntu). How - i have no idea and no real way of finding out

Now i dont think there is a way i could extract that firmware for you? (without cutting up this pc).

P.s i can see in ubuntu > settings >wacom its named isdv4 484d

Just maybe... ubuntu updated my firmware to the correct version after windows bricked it?

@pchelka​ While the touch screen is working, please go to Device manager, under "human interface devices". look for HID compliant touch screen. open it and go to the details tab. and in there, select Hardware ids. Please send me a screenshot of what you see there, Thanks. And also, the touch screen coming back randomly is normal. After a sleep or shutdown, it breaks again

@yotur​ 

Ok so i can see bellow:

HID\VEN_WCOM&DEV_484D&Col01
HID\WCOM484D&Col01
HID\*WCOM484D&Col01
HID\VID_056A&UP:000D_U:0004
HID_DEVICE_UP:000D_U:0004
HID_DEVICE

After reboots it works just fine, so i was either hit by a different issue altogether. But then it does not explain why it was dead for me between different OS'es reboots for more than couple of days

Or something changed again and i have not launched windows since that update, nor did i try anything to fix it (i just used Ubuntu as normal via attached keyboard it did have some updates but i do not recall anything like firmware).

Windows still wants to update something but this time ill pass.

@pchelka​ DON'T, i repeat DON'T install ANY windows update. Just pause all windows updates. Thanks for letting me know, this is EXACTLY what you want to see. I'll let you know how you can extract the firmware (If you're fine with that). It will happen in linux btw.

Just let me know once you're ready and i'll tell you how you can extract the firmware. Thanks once again

@yotur​ 

Sure just send me the link to an instruction and ill run this, I'm fairly tech competent but i haven't had a need to grab firmware form chips so far 

note just not today as its pass midnight

Sure have your rest, as you said that it's past midnight, just do this whenever you want to

@pchelka​ Here: (I generated this from copilot, but this is accurate) 

📋 How to Extract the WCOM484D Firmware from Your Working System (Linux)

Since your system already runs Linux and your touchscreen is working properly (WCOM484D), you can try backing up the firmware using these steps:

🧪 Step-by-Step Firmware Extraction via fwupd

1. Open a Terminal
2. Check USB connection and controller ID

lsusb

→ Look for ID 056a:484d (Wacom AES controller)

1. Check if the device supports fwupd

sudo fwupdmgr get-devices

→ If your touchscreen appears in the list, continue below.

• Back up your firmware

  sudo fwupdmgr backup

  → This will save a firmware image to your system.

  1. Locate the firmware file
  • Usually saved to: /var/lib/fwupd
  • It may have extensions like .bin, .cab, or similar
  1. Share the firmware
  • Zip the file if needed and send it to Akif so he can attempt manual restoration on his system

Just let me know if you have any questions, i will ask copilot and send it to you.

Once again, thanks that you're taking your time to help me possibly fix this

@yotur​ 

its not really listed as USB device nor under fwupd, 
ill look for alternatives

@pchelka​ Ok, let me know if you find something else, or i'll ask copilot

( You can sleep if you want, i'm not forcing you to do this right now 😅😅)

@pchelka​ Hi, Any updates?