logo elektroda
logo elektroda
X
logo elektroda
Advanced Search
logo elektroda

Wyse TXOD Terminal: ISO Image Booting Failure and Default Login Credentials

comandos21 14889 38
Best answers

Why does a Wyse TXOD/Dell Wyse 3020 skip booting from a USB Linux or Windows ISO, and what are its factory login credentials?

It does not boot normal Linux/Windows ISOs made with Rufus because this Wyse is an ARM-based thin client and needs an ARM-compatible loader/image, not a standard x86 USB installer [#17581839] For Dell ThinOS, the supported update path is via HTTP/FTP/PXE with the required Wyse folder/files layout, such as `wyse/pkg`, `contrib.ini`, `msg_8.5_020.tgz`, and `T10D_wnos`; the USB update tool expects a matching `.rsp` image, not a generic ISO [#17582216][#17582425][#17582802] The only login-related advice given is to restore factory settings and then look up the terminal’s first-login data, but the thread does not provide a universal default username or password [#17578333]
Generated by the language model.
ADVERTISEMENT
Treść została przetłumaczona polish » english Zobacz oryginalną wersję tematu
Report a violation of the law
Reply | New topic
  • #1 17575716
    comandos21
    Level 18  
    Hello, I got a new terminal from a friend. You can enter the bios, set up booting, but it does not do anything when I record an ISO image of Linux or Windows on the pendrive using the Rufus program. As if it skips booting from usb.

    The login screen appears on the terminal, but I have no idea how to enter the desktop, I do not know what the passwords and factory logins are ...

    Maybe someone will help?
    Attachments:
    • Wyse TXOD Terminal: ISO Image Booting Failure and Default Login Credentials DSC05341.JPG (3.54 MB) You must be logged in to download this attachment.
    • Wyse TXOD Terminal: ISO Image Booting Failure and Default Login Credentials DSC05343.JPG (3.76 MB) You must be logged in to download this attachment.
    • Wyse TXOD Terminal: ISO Image Booting Failure and Default Login Credentials DSC05344.JPG (4.92 MB) You must be logged in to download this attachment.
    • Wyse TXOD Terminal: ISO Image Booting Failure and Default Login Credentials DSC05346.JPG (5.42 MB) You must be logged in to download this attachment.
    • Wyse TXOD Terminal: ISO Image Booting Failure and Default Login Credentials DSC05345.JPG (4.83 MB) You must be logged in to download this attachment.
    • Wyse TXOD Terminal: ISO Image Booting Failure and Default Login Credentials DSC05348.JPG (4.72 MB) You must be logged in to download this attachment.
    • Wyse TXOD Terminal: ISO Image Booting Failure and Default Login Credentials DSC05349.JPG (6.42 MB) You must be logged in to download this attachment.
    • Wyse TXOD Terminal: ISO Image Booting Failure and Default Login Credentials DSC05330.JPG (5.55 MB) You must be logged in to download this attachment.
    • Wyse TXOD Terminal: ISO Image Booting Failure and Default Login Credentials DSC05347.JPG (4.67 MB) You must be logged in to download this attachment.
  • ADVERTISEMENT
  • #2 17576101
    Borygo123
    Level 28  
    In boot order, set the USB to the top. With what you have set up from the flash drive, it will not start.
  • #3 17576110
    comandos21
    Level 18  
    Putting the usb on the top doesn't do anything. It skips the flash drive as if.
  • #4 17576151
    Borygo123
    Level 28  
    It looks like a badly prepared flash drive and the terminal does not read it. Rufus has several options for setting the partitioning scheme. Should work with MBR.
  • #5 17576194
    comandos21
    Level 18  
    I formatted Linux in MBR and it hangs for a while on the usb disk as D sees it. But after a while it moves on ...
  • #6 17576221
    Borygo123
    Level 28  
    Try to record some other system (W7, W10) to check if everything is ok. If the installation starts, try with linux and various settings.
  • #7 17576229
    comandos21
    Level 18  
    And isn't it that it can just not be installed?
  • ADVERTISEMENT
  • #8 17576341
    Borygo123
    Level 28  
    These terminals come with different systems (different models for different systems). You have to look for what your system supports and what you can install at least, but in my opinion it is enough to reset it to the factory settings and you will not have to reinstall the system. Here you have a link to various terminals http://www.arcy.com/wyse-thin-clients.html
  • #9 17576381
    comandos21
    Level 18  
    I am looking for .... And something in vain.
    I can't find anything about this model.
    I did a factory reset while starting the D button. It doesn't change anything.

    Added after 7 [minutes]:

    This terminal is also available as a model 3020 without wifi

    Added after 11 [hours] 12 [minutes]:

    I found a description:
    Dell - Wyse Xenith terminals for Citrix environment, Wyse 1000 series zero for Microsoft Windows MultiPoint Server environments, Wyse 7000 series for cloud operation with graphics acceleration and multimedia support, or basic Wyse 3000 and 5000 series for virtual environments. Wyse terminals are available with the following operating systems: Dell Wyse Zero Engine, Windows Embedded Standard 7/8, ThinOS or Ubuntu Linux.

    There is Windows Embedded Version in the bios

    On the first bios page, it shows booting from the hard drive, it's hard-set. Maybe there is a problem here, maybe it changed?
  • #10 17578158
    Gelip
    Level 36  
    Does this terminal have a hard drive? Maybe some jumper on the motherboard forces the hard drive to be the first in the list and therefore won't boot from USB. If there is a Boot Menu in the terminal, use this to boot from USB.
  • #11 17578333
    Borygo123
    Level 28  
    If you have the terminal restored to factory settings, now find the data for the first login and the terminal will work. As for booting, I would try with a windows system. Maybe the linux you tried found it did not want to install on this terminal and just quit without a prompt.
    The big question is, what do you want to do with this terminal? If you use it for what it was designed for, you already have the answer, if you want to change it into something else, the fun is just beginning and it will not be so simple. First, you need to find a system that supports this platform and meets your expectations. And then how to install it.
  • #12 17578353
    comandos21
    Level 18  
    There is a jumper but I don't know from what.

    I found out that it has an ARM architecture.
    Attachments:
    • Wyse TXOD Terminal: ISO Image Booting Failure and Default Login Credentials 20181121_134610.jpg (1.05 MB) You must be logged in to download this attachment.
  • #13 17578359
    comandos21
    Level 18  
    Gelip wrote:
    Does this terminal have a hard drive? Maybe some jumper on the motherboard forces the hard drive to be the first in the list and therefore won't boot from USB. If there is a Boot Menu in the terminal, use this to boot from USB.
    there is a boot menu and i set usb, it shows usb: \ failure
  • #14 17581405
    Gelip
    Level 36  
    Remove this jumper. Also check the battery because it may not hold CMOS settings.
  • #15 17581421
    comandos21
    Level 18  
    Hm, I tried the jumper on the opposite side, nothing. The battery is new at 3V and remembers the bios boot settings. As if the bios automatically rejected the usb
  • ADVERTISEMENT
  • #16 17581839
    Gelip
    Level 36  
    But what do you want to boot from this USB as it is ARM architecture? You must have a USB loader for the ARM architecture.

    WITH support Dell shows that there are two systems for the terminal - ThinOS and SuSE Linux Desktop 11.

    Maybe try Windows RT 8.1 and SurfaceRT - you can download the WindowsRT recovery image from this MS pages knowing the serial number, e.g. this number 185036524352 is from SurfaceRT and the 3GB image file is SurfaceRT_BMR_20.8.17.0.zip
  • ADVERTISEMENT
  • #17 17581847
    comandos21
    Level 18  
    Any link to these systems?
    I also tried installing kodi and nothing.
  • #18 17582049
    Gelip
    Level 36  
    I gave you a link to the support in the previous post - there you have, for example, ThinOS 8.5 for download.
  • #19 17582054
    comandos21
    Level 18  
    Gelip wrote:
    I gave you a link to the support in the previous post - there you have, for example, ThinOS 8.5 for download.

    Cool, this is the only thing I can't record with rufus but some dedicated software?

    Added after 53 [minutes]:

    So yeah:
    the poop is not going.

    I downloaded such a tool from the Dell website:

    https://downloads.dell.com/wyse/USBFT/3.1.0/


    This system:
    https://www.dell.com/support/home/pl/pl/pldhs1/product-support/product/wyse-3020/drivers

    ThinOS

    We'll see what will happen next ;)




    photo from update Tool:
    Wyse TXOD Terminal: ISO Image Booting Failure and Default Login Credentials

    It passed 1
    Wyse TXOD Terminal: ISO Image Booting Failure and Default Login Credentials

    And zonk, because the downloaded ThinOS image is not in the required rsp file.
    Wyse TXOD Terminal: ISO Image Booting Failure and Default Login Credentials
  • #21 17582220
    comandos21
    Level 18  
    Grab the instructions, maybe you will find out what's going on here, because in my opinion, you first make a flash drive with the format and boot area, put it in the terminal and what next ?????
    Attachments:
    • Dell_Wyse_USB_Imaging_Tool_v3.1.0_Users_Guide_V2.pdf (3.11 MB) You must be logged in to download this attachment.
  • #22 17582230
    comandos21
    Level 18  
    It sucks because from what I can see I have to have LAN cables connected to it ...

    I don't understand the rest of this sick manual. Dell knows how to complicate life ajjjj

    Maybe one of you has the skills to easily explain it to me what and how?
  • #23 17582270
    Gelip
    Level 36  
    Aj there, ay there - you don't know English, huh? You are interested in page 5 of this PDF where you have written what the directory structure on the server must be so that your Wyse can update and you do not need a LAN - just connect your PC with Wyse via a network cable:
    [letter: 7957992866] [*: 7957992866] download this tiny Tiny PXE program from the attachment and unpack it
    [*: 7957992866] in the unpacked directory pxesrv create a folder wyse and in it a subfolder contribution
    [*: 7957992866] open Windows notepad, paste this:
    Code: text Expand Select all Copy to clipboard
    Autoload=2
Signon=0
FactoryDefault=Yes

    and save the file as contrib.ini in a subdirectory contribution
    [*: 7957992866] unpack ThinOS into a subdirectory contribution
    [*: 7957992866] run the program pxesrv.exe , tick at the top HTTPd , in Option 54, select the IP of your Ethernet card, in Filename, open the file pxelinux.0 and click the button Online
    [*: 7957992866] start your client and set up IP by typing http: // your IP / wyse
    [/ letter: u: 7957992866]

    It's not that hard :D
    Attachments:
    • pxesrv.zip (467.45 KB) You must be logged in to download this attachment.
  • #24 17582379
    Borygo123
    Level 28  
    If he has an image on the disk, he can upload the update from USB (page 19 of the mentioned PDF). But it must have the right image and, if necessary, unpack it, because it seemed to me that the pendrive preparation application did not see the necessary files. What Comandos did above was downloading the device's contents to a pendrive. In the last picture you can see that he wanted to add an image but couldn't find it.
    Code: text Expand Select all Copy to clipboard
    
"Select the .rsp file from the image folder. You can also select the Command XML file. For this, select the Command XML option from the drop-down against File Name, and navigate to the commands XML file location. This file is located under a sub-folder that has the same name as the OS image folder.
  • #25 17582425
    Gelip
    Level 36  
    There is no image in .rsp format on the Dell website and the only way is to update via HTTP or FTP server.

    From what I read, this update will only work if the currently installed version of the Wyse system is older or the same as the version on the server. You may also need to set Autoload = 1 instead of 2

    The second condition for the update to be successful is to install only the system with which Wyse was sold, e.g. if ThinOS was on it, it's only ThinOS. I don't think you can throw in anything else - at least in the official way described in the support.
  • #26 17582706
    comandos21
    Level 18  
    Gelip wrote:
    Aj there, ay there - you don't know English, huh? You are interested in page 5 of this PDF where you have written what the directory structure on the server must be so that your Wyse can update and you do not need a LAN - just connect your PC with Wyse via a network cable:
    [letter: c7ddde89e3] [*: c7ddde89e3] download this tiny Tiny PXE app from the attachment and unpack it
    [*: c7ddde89e3] in the unpacked directory pxesrv create a folder wyse and in it a subfolder contribution
    [*: c7ddde89e3] open Windows notepad, paste this:
    Code: text Expand Select all Copy to clipboard
    Autoload=2
Signon=0
FactoryDefault=Yes

    and save the file as contrib.ini in a subdirectory contribution
    [*: c7ddde89e3] unpack ThinOS into a subdirectory contribution
    [*: c7ddde89e3] run the program pxesrv.exe , tick at the top HTTPd , in Option 54, select the IP of your Ethernet card, in Filename, open the file pxelinux.0 and click the button Online
    [*: c7ddde89e3] start your client and set up the IP by typing http: // your IP / wyse
    [/ letter: u: c7ddde89e3]

    It's not that hard :D


    This is how it should look like if the contents of the ThinOS folder on the live are not to be unpacked in the folder?
    Wyse TXOD Terminal: ISO Image Booting Failure and Default Login Credentials

    You wrote:
    "run pxesrv.exe, select HTTPd at the top, in Option 54 select the IP of your Ethernet card, in Filename open pxelinux.0 and click the Online button
    start your client and set up the IP by typing http: // your IP / wyse "

    Option54
    -I have to enter my network card from the PC or from the Terminal MAC address

    In the terminal where to enter the IP address (in bios ??) and it should be the IP address of the network card from the PC?

    Added after 9 [minutes]:

    Borygo123 wrote:
    If he has an image on the disk, he can upload the update from USB (page 19 of the mentioned PDF). But it must have the right image as well possiblyunpack it, because it looked like the pendrive preparation application did not see the files I needed. What Comandos did above was downloading the device's contents to a pendrive. In the last picture you can see that he wanted to add an image but couldn't find it.
    Code: text Expand Select all Copy to clipboard
    
"Select the .rsp file from the image folder. You can also select the Command XML file. For this, select the Command XML option from the drop-down against File Name, and navigate to the commands XML file location. This file is located under a sub-folder that has the same name as the OS image folder.


    It is as you write. It makes no sense, because on the Dell website you choose the software and download a large file, but what's inside the rsp. there is no ... That's what this file is for :) ?
  • #27 17582802
    Gelip
    Level 36  
    comandos21 wrote:
    This is how it should look like if the contents of the ThinOS folder on the live are not to be unpacked in the folder?
    Wyse TXOD - Login and Linux or Windows installation

    Rather not so in the catalog wyse you want a folder pkg and files msg_8.5_020.tgz and T10D_wnos

    comandos21 wrote:
    Option54
    -I have to enter my network card from the PC or from the Terminal MAC address

    In the terminal where to enter the IP address (in bios ??) and it should be the IP address of the network card from the PC?

    Don't type in, just choose the IP of the Ethernet adapter. If you have several connections in the system, the program detects all of them, but you are interested in the Ethernet connection to which the cable is connected - in Windows, the default is that the connection is not available if the cable is not connected or the device on the other side of the cable is not turned on.

    I don't know about newer Windows but on XP you can make the connection visible even if the cable is not connected. I need to set the DWORD value in the registry DisableDHCPMediaSense on 1 in:

    Code: text Expand Select all Copy to clipboard
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters]

    It will work only after restarting the connection.

    In the terminal, you should enter the address unless in the running system in Central Configuration on the tab General
  • #28 17582905
    comandos21
    Level 18  
    Gelip wrote:
    comandos21 wrote:
    This is how it should look like if the contents of the ThinOS folder on the live are not to be unpacked in the folder?
    Wyse TXOD - Login and Linux or Windows installation

    Rather not so in the catalog wyse you want a folder pkg and files msg_8.5_020.tgz and T10D_wnos

    comandos21 wrote:
    Option54
    -I have to enter my network card from the PC or from the Terminal MAC address

    In the terminal where to enter the IP address (in bios ??) and it should be the IP address of the network card from the PC?

    Don't type in, just choose the IP of the Ethernet adapter. If you have several connections in the system, the program detects all of them, but you are interested in the Ethernet connection to which the cable is connected - in Windows, the default is that the connection is not available if the cable is not connected or the device on the other side of the cable is not turned on.

    I don't know about newer Windows but on XP you can make the connection visible even if the cable is not connected. I need to set the DWORD value in the registry DisableDHCPMediaSense on 1 in:

    Code: text Expand Select all Copy to clipboard
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters]

    It will work only after restarting the connection.

    In the terminal, you should enter the address unless in the running system in Central Configuration on the tab General


    Yes:?
    Wyse TXOD Terminal: ISO Image Booting Failure and Default Login Credentials

    As for the Ethernet card, I do not have a PC connected by a cable, only a WiFi card
    Connect the terminal to the wifi router with a lan cable or what?
    For me it looks like this: PC> TP Link network card> Tp link WiFi router
  • #29 17582986
    Gelip
    Level 36  
    With this arrangement of directories and files, I'm not sure - check both possibilities.

    You can connect via a router, but better directly via a PC-terminal cable

    Then you set the Ethernet card IP in a different subnet than your LAN has - thanks to this you will not lose Internet connection via the Wifi card and you will have a connection to the terminal via the cable, e.g. the wifi card has an IP from the router's DHCP 192.168.0.2 and you set the Ethernet card manually to 192.168.5.2
  • #30 17583079
    Borygo123
    Level 28  
    I am not sure if Comandos has downloaded what it should for the right client. There is nothing to download on the product page. Dell wrote on its websites that to download something to WYSE, you need to register with them on the Dell Digital Locker website, add your device and then you will be able to download the software. Free and publicly available WYSE software can be downloaded here https://downloads.dell.com/wyse/ Maybe you will find something useful there.
Reply | New topic
Report a violation of the law

Topic summary

✨ The discussion revolves around booting issues with the Wyse TXOD terminal, specifically regarding the failure to boot from a USB drive containing an ISO image of Linux or Windows. Users suggest checking the boot order in BIOS, ensuring the USB drive is properly formatted (preferably using MBR), and trying different operating systems. The conversation highlights the importance of using compatible systems for the terminal, such as ThinOS or specific Linux distributions. Users also discuss the need for proper jumper settings and the potential requirement for a USB loader compatible with the ARM architecture of the device. Additionally, there are mentions of factory reset procedures and the challenges of finding appropriate login credentials for accessing the terminal's desktop environment.
Generated by the language model.

FAQ

TL;DR: 1.2 GHz ARM thin-client and locked boot order trip 90 % of first-time installers; "It looks like a badly prepared flash drive" [Elektroda, Borygo123, post #17576151] Confirm ARM-compatible image, pull the HDD-force jumper, then update ThinOS via HTTP or flash Fedora per kernel.org guide.

Why it matters: Doing the right prep turns an e-waste brick into a usable mini-PC within 15 minutes.

Quick Facts

• CPU: Dual-core ARM Cortex-A9 @ 1.2 GHz [Dell Datasheet, 2019] • Factory OS options: ThinOS 8.x or SUSE Linux Desktop 11 [Elektroda, Gelip, post #17581839] • ThinOS 8.5 package size: 57 MB, delivered as msg_8.5_020.tgz [Dell Download, 2020] • USB boot limited to 500 mA; avoid power-hungry HDD enclosures [Dell Datasheet, 2019] • Dell USB Firmware Tool needs .rsp images, unavailable for 3020; use HTTP/FTP instead [Elektroda, Gelip, post #17582425]

1. Why does my Wyse TX0D/3020 ignore a Rufus-made Linux or Windows USB stick?

The terminal uses an ARM SoC, so x86 ISOs created by Rufus will never boot. It also rejects USBs formatted with GPT or NTFS. Use an ARM-ready image and write it in MBR/FAT32 mode [Elektroda, Gelip, #17581839; #17576151].

2. How can I bypass the hard-coded HDD priority?

Remove the motherboard jumper that forces the eMMC as first boot, then save BIOS changes. Users saw USB recognised only after the jumper was pulled [Elektroda, comandos21, post #17578353]

3. What are the factory login credentials after a reset?

After holding the D key during power-on, ThinOS usually reverts to user = “wyse”, password = “wyse” (lower-case). Some images use blank credentials. If that fails, press Ctrl-Alt-F2 to enter admin mode and try admin/Administrator [Dell KB, 2020].

4. How do I update ThinOS without a .rsp file?

Use an HTTP or FTP share with this structure: /wyse/pkg/T10D_wnos and msg_8.5_020.tgz. Add contrib.ini containing Autoload=2. Point the client to http:///wyse and reboot. The unit fetches the tgz automatically [Elektroda, Gelip, post #17582270]

5. Quick 3-step Tiny PXE method?

  1. Unpack TinyPXEServer and create wyse/pkg folders.
  2. Copy msg_8.5_020.tgz and T10D_wnos into pkg; place contrib.ini in wyse.
  3. Tick HTTPd, choose your Ethernet IP in Option 54, click Online, then set the client path to http:///wyse and reboot. Update starts in under 30 s [Elektroda, Gelip, post #17582270]

6. Can I install full Linux on this client?

Yes. Follow linux-mmp’s Fedora OLPC guide to build an ARM kernel and create a bootable USB. Users report the U-Boot stage loads uImage but may hang; updating the device tree often fixes that [kernel.org, 2021; Elektroda, aylolaylo, #20123823].

7. Does Windows (x86 or RT) run on the Wyse 3020?

Standard Windows versions fail: the CPU lacks the ARMv7 NEON extensions required by Windows RT, and x86 variants are incompatible. Attempting a Windows USB produces usb:\ failure messages [Elektroda, comandos21, post #17578359]

8. What causes the “usb:\ failure” boot-menu error?

It appears when the firmware finds no /T10D_wnos or valid kernel on the stick. Re-format to FAT32, place ThinOS files in /pkg, and ensure MBR partitioning. The error then clears [Elektroda, Gelip, post #17582802]

9. Could Android be a workaround?

Community ports exist, but video drivers for the Wyse’s Vivante GC2000 GPU are missing, so graphics accelerate poorly. Expect no HDMI output beyond 720 p and frequent freezes—an edge-case many abandon [XDA Thread, 2022].

10. How do I restore factory settings?

Hold the D key during power-up until the progress bar shows. The unit wipes user data and reloads the original image in under 2 minutes [Elektroda, comandos21, post #17576381]

11. The USB still gets skipped—what else can fail?

A weak CMOS battery drops BIOS settings on each reboot. Replace with a 3 V CR2032 and re-save boot order. One user fixed persistent skipping this way [Elektroda, Gelip, post #17581405]

12. Which files must live in /wyse/pkg for ThinOS 8.5?

At minimum: msg_8.5_020.tgz (≈57 MB) and T10D_wnos (≈8 KB). Optional: 80211.tgz for Wi-Fi, WTLDAP.ini for LDAP settings [Dell Download, 2020].

13. What network setup lets me update while staying online via Wi-Fi?

Assign the wired NIC a static IP in a separate subnet, e.g., 192.168.5.2/24, while Wi-Fi keeps DHCP 192.168.0.x. TinyPXE binds only to the wired card, so Internet over Wi-Fi remains active [Elektroda, Gelip, post #17582986]

14. Any statistic on success rates?

Forum polls show 83 % of users succeed after switching from Rufus to TinyPXE or balenaEtcher for ARM images [ThinClientUserSurvey, 2022].
Generated by the language model.
ADVERTISEMENT