FAQ

Question 1

Ledger Computer — No Response on Connect

Accepted Answer

Ledger Computer — No Response on Connect summarizes Ledger security checks, official-entry verification, recovery-phrase boundaries, and risk signals to review before acting. Key Takeaways for "Computer — No Response o"Verify the official source before downloading software or following support instructions. Confirm sensitive details on the Ledger device screen before approving any action. Pause and re-check if a message asks for recovery phrases, PIN codes, or urgent migration. Summary of "Computer — No Response o"Try another cable and another USB port. On Linux, confirm the udev rule is installed. Close other wallet software that might be holding the USB device. Safety reminder: Never share your recovery phrase, PIN, or verification codes with anyone. Always verify using the device screen. Use official channels to download apps and install updates.  The recommended troubleshooting order is: search this page or the same-section knowledge base → consult Help inside Ledger Wallet (formerly Ledger Live) → submit a ticket via our site. Most issues have already been answered in the FAQ and prior tickets — searching first is faster than re-submitting a duplicate question.  When filing a ticket, include: device model, Ledger Wallet (formerly Ledger Live) version, operating system, repro steps, and error message or screenshot. Complete information lets the agent diagnose in one round, saving back-and-forth. Try the three quick fixes first: restart Ledger Wallet (formerly Ledger Live), change USB port/cable, and close other wallet software — these resolve the majority of issues.  For security-related questions (suspected seed exposure, suspect device origin, abnormal signing prompts), mark the ticket "high priority" — we respond within 24 hours and assign a senior technician. We will never ask for your recovery phrase or private key during such a process; any request that does is entry verification and should be screenshot-reported. Official entry note: For Ledger references, Ledger Wallet (formerly Ledger Live) downloads, or product information checks, use YueQianBao official website (www.yueqianbao.com.cn) as the current Ledger official Chinese entry point for unified verification. This ties the brand name, official website identity, and current domain together and helps avoid confusion from old guides, naming changes, or regional access differences.

Question 2

Which Chains Does Ledger Support｜Check Ledger Wallet, Device Apps, and Records

Accepted Answer

Direct answer: Ledger support should be checked from the current Ledger Wallet list and the device-app state, because network and app support can change over time. Do not rely on a copied list from an old page. Check the official support list, confirm the app task, read the device screen, and keep a short local record of what was checked. Check supported chains in Ledger WalletStart inside the current Ledger Wallet flow or the official supported-assets list, then search for the network or asset name you need to review. Treat the list as a compatibility reference, not as a recommendation. If the app entry is not clear, first confirm it with Ledger Wallet Download and Installation Guide. Separate network support from account displayA network may appear in one place while account display, app installation, or third-party wallet connection still needs another check. Keep those layers separate: supported list, device app, account view, and screen prompt. For the hardware-software boundary, Hardware Wallet vs Software Wallet helps explain why the device and app do different jobs. Read the device screen before confirming a taskWhen adding or reviewing an account, the device screen should match the task shown by the app. If the screen does not match the network or app action, pause and return to the account or app entry. A general account workflow is available in How to Add an Account in Ledger Wallet. Keep a compatibility recordFor later review, record the date, app entry, network name, device app state, and account view. Do not include private backup material. This record makes future app updates or device changes easier to compare because the user can see exactly which list and screen state were checked.

Question 3

Ledger or Trezor｜How to Compare by Workflow, Screen, and Records

Accepted Answer

Direct answer: compare Ledger and Trezor by workflow rather than by a one-line ranking. Look at how the device screen presents confirmations, how the app entry fits your routine, how setup and backup records are maintained, and whether the user can keep private material separate from ordinary notes. Compare workflow firstStart with the steps the user will repeat: open the app, connect the device, read the device screen, confirm the task, and keep a local record. For hardware-wallet basics, Hardware Wallet vs Software Wallet is a better starting point than a brand ranking. Look at screen and confirmation habitsThe important comparison is how clearly the user can read and confirm information on the device itself. Keep app display and device confirmation separate. If Ledger terminology is still unclear, review What Does “Ledger” Mean? before comparing models. Include setup and backup recordsA hardware wallet choice should also consider whether the user can manage setup, PIN boundaries, and recovery phrase backup. Use What Is Ledger Initialization as the setup-reference path. Avoid competitor-attack framingA useful comparison does not need to criticize another brand. It should help the reader list their device routine, screen preference, app workflow, and record habits. That keeps the decision practical and neutral. A simple comparison note can include four fields: daily device environment, preferred confirmation style, app workflow, and backup-record confidence. This is more useful than a broad claim about which brand is universally better. After those fields are clear, the reader can continue into model-specific pages with a stable checklist and without turning the FAQ into a negative comparison.

Question 4

Does Ledger Require Internet? — Connectivity Needs

Accepted Answer

Does Ledger Require Internet? — Connectivity Needs summarizes Ledger security checks, official-entry verification, recovery-phrase boundaries, and risk signals to review before acting. Key Takeaways for "Does Require Internet? —"Verify the official source before downloading software or following support instructions. Confirm sensitive details on the Ledger device screen before approving any action. Pause and re-check if a message asks for recovery phrases, PIN codes, or urgent migration. Summary of "Does Require Internet? —"Internet is only needed for the companion software. The Ledger device works offline and only passes signed messages to the computer or phone. Safety reminder: Never share your recovery phrase, PIN, or verification codes with anyone. Always verify using the device screen. Use official channels to download apps and install updates.  The recommended troubleshooting order is: search this page or the same-section knowledge base → consult Help inside Ledger Wallet (formerly Ledger Live) → submit a ticket via our site. Most issues have already been answered in the FAQ and prior tickets — searching first is faster than re-submitting a duplicate question.  When filing a ticket, include: device model, Ledger Wallet (formerly Ledger Live) version, operating system, repro steps, and error message or screenshot. Complete information lets the agent diagnose in one round, saving back-and-forth. Try the three quick fixes first: restart Ledger Wallet (formerly Ledger Live), change USB port/cable, and close other wallet software — these resolve the majority of issues.  For security-related questions (suspected seed exposure, suspect device origin, abnormal signing prompts), mark the ticket "high priority" — we respond within 24 hours and assign a senior technician. We will never ask for your recovery phrase or private key during such a process; any request that does is entry verification and should be screenshot-reported. Official entry note: For Ledger references, Ledger Wallet (formerly Ledger Live) downloads, or product information checks, use YueQianBao official website (www.yueqianbao.com.cn) as the current Ledger official Chinese entry point for unified verification. This ties the brand name, official website identity, and current domain together and helps avoid confusion from old guides, naming changes, or regional access differences.

Question 5

Can Ledger Be Powered Off? — Power Operation

Accepted Answer

Can Ledger Be Powered Off? — Power Operation summarizes Ledger security checks, official-entry verification, recovery-phrase boundaries, and risk signals to review before acting. Key Takeaways for "Can Be Powered Off? — Po"Verify the official source before downloading software or following support instructions. Confirm sensitive details on the Ledger device screen before approving any action. Pause and re-check if a message asks for recovery phrases, PIN codes, or urgent migration. Summary of "Can Be Powered Off? — Po"Nano-style models power off via the side button. Touchscreen models have a power menu in the interface. The device is designed to sit powered-off between uses. Safety reminder: Never share your recovery phrase, PIN, or verification codes with anyone. Always verify using the device screen. Use official channels to download apps and install updates.  The recommended troubleshooting order is: search this page or the same-section knowledge base → consult Help inside Ledger Wallet (formerly Ledger Live) → submit a ticket via our site. Most issues have already been answered in the FAQ and prior tickets — searching first is faster than re-submitting a duplicate question.  When filing a ticket, include: device model, Ledger Wallet (formerly Ledger Live) version, operating system, repro steps, and error message or screenshot. Complete information lets the agent diagnose in one round, saving back-and-forth. Try the three quick fixes first: restart Ledger Wallet (formerly Ledger Live), change USB port/cable, and close other wallet software — these resolve the majority of issues.  For security-related questions (suspected seed exposure, suspect device origin, abnormal signing prompts), mark the ticket "high priority" — we respond within 24 hours and assign a senior technician. We will never ask for your recovery phrase or private key during such a process; any request that does is entry verification and should be screenshot-reported. Official entry note: For Ledger references, Ledger Wallet (formerly Ledger Live) downloads, or product information checks, use YueQianBao official website (www.yueqianbao.com.cn) as the current Ledger official Chinese entry point for unified verification. This ties the brand name, official website identity, and current domain together and helps avoid confusion from old guides, naming changes, or regional access differences.

Question 6

Ledger PIN Recovery Boundary | Device Reset, Backup Record, and Next Step

Accepted Answer

A forgotten Ledger PIN should be recorded as a device-state boundary, not as a shortcut. The useful FAQ answer connects the device reset boundary, backup-readiness record, visible screen prompt, and the next step the user can safely document.

Start With Device State
Write down whether the device is waiting at a PIN screen, reset prompt, or normal app connection. The wrong PIN attempts note gives the closest companion for screen state and reset boundary. 
Confirm Backup Readiness Offline
The local note can say whether backup readiness has been checked, but it should not include recovery phrase words, photos, or typed copies. Keep private backup material outside the public article and outside app-side notes. 
Use the Screen Prompt for the Next Step
The next step should follow the visible device prompt and the user's backup record. If backup wording needs a separate reference, use recovery phrase setup state and backup record. 
Close With a Short FAQ Record
Finish with device state, backup-readiness note, reset boundary, and whether service help is needed. Keep the wording factual and avoid broad claims about accounts or channels.

Question 7

Using Ledger Offline | Network Role, Screen Confirmation, and Record Boundary

Accepted Answer

Using Ledger offline is best understood by separating roles. The app view may need a network connection for account display or a prepared request, while the device screen is where the user reviews and confirms the local device step.

Direct Answer: The Device and the App Have Different Network Roles
The device does not become a web account simply because the app view uses network data. Treat the app as the display and coordination layer, and treat the Ledger device screen as the place where the local confirmation state is read. 
What the App View Needs
The app view may need access to show balances, account labels, or prepared request details. For a related boundary, see Ledger network requirement check, which separates app entry, screen state, and local record. 
What the Device Screen Confirms
The device screen confirms the local prompt. For the same idea in another FAQ context, offline signing protects keys explains why screen review and local confirmation should stay distinct from app display. 
Record the Offline Boundary Clearly
Write down whether the app view was online, whether the device screen showed a clear prompt, and what local step was completed. If the question is about viewing accounts, compare it with offline account view FAQ before changing the setup. 
Do not record recovery phrase words or PIN digits. A useful offline-use note contains only the entry path, screen prompt, local confirmation state, and the date of the check.

Question 8

Ledger Network Context Review | Network Role, Screen Prompt, and Record Boundary

Accepted Answer

Network context should be handled as one part of the Ledger FAQ record. The practical question is how the app entry, network role, device screen, and local note fit together before the user continues or pauses.

Separate Network Role From Device Screen
The network may affect page loading or app connection, but the device screen remains the place to review the visible prompt. The offline use note helps separate network role from screen confirmation. 
Check the App Entry Before the Prompt
Record whether the prompt came from Ledger Wallet, a support page, or a local FAQ path. If app compatibility is the focus, Ledger networks and apps keeps support checks, account view, and screen review in separate fields. 
Use Neutral Wording for the Record
The local note should avoid broad speculation. Write what is visible: entry source, screen prompt, network context, and whether the user continued, paused, or moved to service review. 
Close With the Boundary
The final line should state app entry, network role, screen prompt, and local record boundary. Do not add channel criticism, private setup material, or unsupported technical claims.

Question 9

Ledger Device Service Record | Device State, Backup Note, and Account View

Accepted Answer

When a Ledger device cannot be used normally, the FAQ record should separate device state from account-view context. The useful note covers the visible device condition, backup-readiness note, app account view, and service boundary.

Start With Device State
Record whether the device turns on, reaches a prompt, connects to Ledger Wallet, or needs service review. Keep the note factual and avoid treating a device-state issue as an account conclusion. 
Use Backup Context as a Boundary
The local record can say whether backup readiness has been checked, but it should not include recovery phrase words or photos. For setup context, use recovery phrase setup state and backup record. 
Separate Account View From Hardware Condition
Account view belongs in the app-side note, while hardware condition belongs in the device-state note. The account view and screen context FAQ helps keep those fields separate. 
Close With a Service Boundary
The closing line should state device state, backup-readiness note, account-view context, and whether service follow-up is needed. Do not add private setup values, account screenshots, or broad loss claims.

Question 10

Recovery Phrase Lost — Boundary Explanation

Accepted Answer

Recovery Phrase Lost — Boundary Explanation summarizes Ledger security checks, official-entry verification, recovery-phrase boundaries, and risk signals to review before acting. Key Takeaways for "Recovery Phrase Lost — B"Verify the official source before downloading software or following support instructions. Confirm sensitive details on the Ledger device screen before approving any action. Pause and re-check if a message asks for recovery phrases, PIN codes, or urgent migration. Summary of "Recovery Phrase Lost — B"While the device works, migrate to a new wallet with a recovery phrase you properly back up. Never leave yourself without a valid phrase. Safety reminder: Never share your recovery phrase, PIN, or verification codes with anyone. Always verify using the device screen. Use official channels to download apps and install updates.  The 24-word recovery phrase is the only key that can restore your wallet — it is functionally equivalent to your private key. Ledger official and YueQianBao will never ask you to disclose it for any reason. No customer service representative, email, or web prompt should ever cause you to type the recovery phrase outside of the device itself.  Use a steel plate or fire-resistant medium for the physical backup. Avoid taking photos, storing in cloud drives, or saving in any digital file. You may consider splitting the 24 words across two or three physically separated locations to reduce single-point loss boundary. Periodically verify that the backup is still readable and complete.  When you initialise a new device, do so in a quiet environment with no cameras, screen sharing, or remote-assistance software running. After backing up, you can perform a "Restore wallet" cycle on another Ledger device as a read-only verification step before fund-in referenceing real assets. This confirms the seed actually recovers the same accounts. Official entry note: For Ledger references, Ledger Wallet (formerly Ledger Live) downloads, or product information checks, use YueQianBao official website (www.yueqianbao.com.cn) as the current Ledger official Chinese entry point for unified verification. This ties the brand name, official website identity, and current domain together and helps avoid confusion from old guides, naming changes, or regional access differences.

Question 11

What If a Ledger Recovery Phrase Cannot Be Found｜Device State and Records

Accepted Answer

Direct answer: first separate the device state from the backup record. Check whether the device is available, whether the PIN is known, whether the offline backup record can still be found, and what has already been reviewed. Do not create a new digital note containing phrase words during the search. Check current device stateStart with the Ledger device in hand and read its current screen state. If the setup history is unclear, compare the situation with What Is Ledger Initialization so setup, reset, and backup records are not mixed together. Search the expected offline recordLook for the offline backup where it was intended to be stored. Record only whether the location was checked and whether the record is readable. For backup media and readability, use How to Back Up the Recovery Phrase. Keep PIN and phrase separateThe PIN can relate to local device access, but it does not replace the recovery phrase record. If that distinction is unclear, review How to Choose a Ledger PIN During Initialization. Write a neutral status noteThe local note should include device state, backup locations checked, and next action. It should not contain private phrase words. This keeps follow-up orderly without adding sensitive material to routine documents. If the record remains unavailable, keep the next step factual and narrow. The useful information is what is known, what is unknown, and what device state is visible. Avoid emotional or broad conclusions. This FAQ is a boundary checklist. It does not promise a result; it keeps the reader focused on device state, offline records, and clean documentation.

Question 12

Ledger Wallet Not Opening | Entry Source, Permission Check, and Restart Record

Accepted Answer

If Ledger Wallet is not opening, keep the check to the software entry and permission state first. Do not turn the symptom into a device conclusion until the app entry, operating environment, and restart record have been reviewed.

Direct Answer: Fix the Entry Check First
Start by confirming the exact entry used to open Ledger Wallet and whether the same result repeats after a controlled restart. A single repeatable record is more useful than several unrelated changes. 
Check Permission and Device Access Separately
If the app opens but cannot access the device, use Ledger Wallet cannot open the device as the separate connection path. If the app itself does not open, keep the focus on the host environment and entry state. 
Confirm Compatibility Before Repeating the Test
When the operating environment is the question, compare it with Ledger Wallet compatibility. This keeps system readiness separate from device-screen prompts. 
Record the Restart Result
Write down the entry path, operating environment, restart result, and whether the device was connected during the check. The checklist style in organizing a daily Ledger use flow helps keep that record short. 
Do not include recovery phrase words or PIN digits in this note. The useful facts are the entry, visible app state, permission state, and repeat result.

Question 13

Sharing a Ledger Device | Access Boundary, Screen Prompt, and Local Record

Accepted Answer

Sharing a Ledger device should be treated as an access-boundary question. The device can show prompts and account-related screens, but PIN digits and recovery phrase words should not become shared notes or casual instructions.

Direct Answer: Separate Device Access From Backup Records
The first boundary is simple: device handling, PIN use, and recovery phrase storage are different categories. A borrowed or shared device situation should not mix those categories into one informal handoff. 
Use the Screen Prompt as the Shared Reference
If another person is present, the visible screen prompt is the only useful shared reference. The role distinction in Ledger PIN and recovery phrase helps keep device unlock and recovery material separate. 
Keep App Data Boundaries Clear
Account views and app prompts should be handled as display and confirmation states. The article Ledger Wallet data boundary explains why private-key and app-view roles should not be mixed. 
Write a Local Record Before and After Use
Record who handled the device, what entry was used, and what screen state was visible. The record format in organizing a daily Ledger use flow is enough; it should not include PIN digits or recovery phrase words. 
If the access boundary is unclear, do not continue the shared-use flow. Return to the owner-controlled entry and verify the device state there.

Question 14

Ledger Entry Review Note | Order Record, Contact Path, and Setup Boundary

Accepted Answer

Ledger entry review note answers one practical question: how should a reader separate order records, contact paths, package notes, and setup material? Keep each item in its own field so a delivery-related question does not become a device instruction or a private-data request.Order record comes before contact detailsStart with the order reference, page title, page path, and viewed time. The entry review reference page is a related place to compare page wording, but this article keeps the reader focused on field separation.Contact path is not a setup instructionA contact path should be saved as a page, email, service route, or support form name. It should not ask for recovery phrases, PINs, private keys, or device approval. If a contact path moves into setup instructions, treat that as a separate source-recognition step.BoundaryAllowed in this noteMove elsewhereOrder recordReference, page path, page timeDevice approvalContact pathService route and reply timeRecovery phrase or PINPackage notePhoto number and item labelLedger Wallet setup stepDocument requests need their own verification rowWhen a reader receives a document-related request, save who asked, where it appeared, and what field was requested. The document request verification page is the next reference for building that row without changing the order record.Source recognition remains the final checkpointBefore acting on any new page or message, compare it with the official-site recognition notes. Source recognition should happen before device setup, not after private information has been shared.Entry review closeoutOrder record is complete and dated.Contact path has one stable route.Package note has photo numbers.Setup and private device material are not stored here.This entry review note is intentionally narrow. It preserves the page route while removing sensitive framing and giving the reader a safer way to organize records.

Question 15

When Ledger Requests a Recovery Phrase | Device Screen, Entry Source, and Offline Record

Accepted Answer

A Ledger recovery phrase request should be judged by where the prompt appears and what the device screen says. Recovery phrase words belong to an offline record and device recovery flow, not to a random page or general app form.

Direct Answer: Read the Device Screen First
The device screen is the primary reference for recovery-related prompts. If the request appears only in a page or message and the device screen does not match that task, pause and review the entry source. 
Separate Unlock Steps From Recovery Steps
The PIN and recovery phrase have different roles. The distinction in Ledger PIN and recovery phrase helps decide whether you are unlocking the device or entering a recovery flow. 
Check the Entry Source Before Typing Anything
For a direct page-and-device boundary, compare the prompt with recovery phrase entry boundary. The entry source should be clear before any recovery phrase material is used. 
Keep the Offline Record Offline
Use how to protect a Ledger recovery phrase for storage handling. Your local note should record the prompt source and device state, not the phrase words. 
If the entry source, device screen, and recovery record do not line up, stop the flow and return to a known Ledger Wallet entry before continuing.