@TioJefe i will get back to this. currently i am starting to use a grapheneOS phone w Orbot running to connect my trezor app downloaded from its github page and it works great.
I’d still like it to work well but now I’ve run into a failure to be able to backup my system. I’m going to handle that first because if I can’t backup my qubes then it’s not worth a whole lot to keep configuring it. Just posted about it if you may have any knowledge on that subject.
Thank you for the reply. I will try this out after the backup gets working.
The Trezor Bridge has been deprecated and is no longer compatible with the latest version of Trezor Suite. It was functioning previously, but now it doesn’t work, unless you are using an ancient version.
Assigning the USB device to the Trezor VM is sufficient to detect the device:
trezorctl list
webusb:001:1 - Current [Trezor Safe 3, XXXXXXXXXXXXXXXXXXX]
However not enough to get Trezor suite working, the wallet keeps loading indefinitely and nothing happens, I tried to check the relevant threads in the forum but I don’t see anything that I haven’t tried, this only affects Suite, I’m able to use Trezor safe 3 with XMR wallet just fine.
I am having the exact same issue, and cannot find any documentation that works. Did you ever get this to work? If so, could you please post the exact steps you took to get it working? Thank You!
Good evening, and sorry for the delayed response. I have been using Qubes for nine months, and initially (with version 4.2.4) I was able to install Trezor on every attempt, and it worked each time. I followed the main tutorial from the forum as well as @smrtak’s guide, and both were completely successful. I also used @tiojefe’s tweaks, and everything went smoothly.
However, in mid‑December I reformatted my notebook, and when I tried to reinstall Trezor I got stuck in an infinite loop while the wallet was loading. Right now I’m trying to install Trezor on version 4.3, but I have had zero success after countless attempts.
Honestly, I don’t know what I’m doing wrong, and I’m not an advanced user who can pinpoint my own mistake, so I’m studying the documentation bit by bit in the little spare time I have each day, hoping to find a solution or discover where I’m going wrong.
I am using Qubes 4.3.0, with whonix-workstation-18 and a Trezor Model T. Considering the new features that whonix-workstation-18 implements ( sysmaint user, Boot mode settings, Default boot mode for derived AppVMs settings, etc.), could you please rewrite or update your guide? I tried every suggestion in this posts thread using whonix-workstation-18, all to no avail.
When the Trezor-suite is run, it DOES recognize the Trezor Model T. Then it tells me I need a firmware update and asks me if I want to update the Trezor. After clicking yes, it starts the firmware update, and then 1 second in, it gives me an error saying “Unknown error”. If I try to update again, it keeps doing the same thing.
Can you try updating this guide for the latest Qubes/Whonix, or provide some advice as to how I can get this working with a Model T?
Please let me know if you figure this out. I am using Qubes 4.3, and whonix-workstation-18. My trezor is the Trezor Model T. I can get the Trezor-Suite app to recognize my Trezor, but then it asks for a firmware upgrade. When it starts upgrading, the connection breaks and is gives me a generic error, and disconnects my Trezor Model T. If you figure this out, please let me know.
For what it’s worth, turning the qube with Trezor Suite into an HVM and attaching the PCI device for the USB port my Trezor is connected to works for me. Only the standard way through sys-usb doesn’t.
Switching to HVM made trezor suite work again. Previously updating would just spin and spin even though the hardware was recognized. This is on 4.2.4, haven’t tried on 4.3 yet.
I’m spamming this on all the Trezor threads I can find. I could never get a good solution, so I worked with AI to diagnose and create a working solution. It’s a python script, it depends on python3-trezor and python3-libusb1. The flow is 1) plug trezor in, unlock, and attach to qube, 2) run script, 3) use trezor suite, or launch a chrome-based browser with “–disable-features=LocalNetworkAccessChecks“ and then the trezor website and metamask should work. The script has nice long comment docs explaining everything in it. I don’t know how long this will be viable for, but at least for the moment, it’s a relatively easy solution for getting the trezor to work.