Skip to content
This repository has been archived by the owner on Jun 16, 2022. It is now read-only.

Ledger device: UNKNOWN_ERROR (0x6a82) #4473

Open
aphex3k opened this issue Nov 26, 2021 · 38 comments
Open

Ledger device: UNKNOWN_ERROR (0x6a82) #4473

aphex3k opened this issue Nov 26, 2021 · 38 comments

Comments

@aphex3k
Copy link

aphex3k commented Nov 26, 2021

Ledger Live Version and Operating System

  • tested on Ledger Live 2.35.2
    • Ledger Nano S ₿itcoin app 2.0.0
  • Platform and version: macOS Monterey 12.0.1

Expected behavior

I expect to connect to remote bitcoind full node to create lss.json for SatStack.

Actual behavior

Ledger device: UNKNOWN_ERROR (0x6a82)

Steps to reproduce the behavior

  • I tried different USB/Thunderbolt adapters/cables
  • Other functionality during regular Ledger Live use seems unaffected

Screen Shot 2021-11-26 at 2 10 17 PM
@Retropex
Copy link

Same problem for myself after several searches I cannot find the solution.

@premmen2
Copy link

Same for me on Windows 11 with the latest version of Ledger Live and the bitcoin app.

@Retropex
Copy link

it's good I have the solution just downgrade the version of ledger live for it to work, the latest version breaks ledger sat stack. use version 2.33.1

@aphex3k
Copy link
Author

aphex3k commented Nov 29, 2021

it's good I have the solution just downgrade the version of ledger live for it to work, the latest version breaks ledger sat stack. use version 2.33.1

Where do I find an old version for Ledger Live in general and for macOS specifically?

@Retropex
Copy link

it's good I have the solution just downgrade the version of ledger live for it to work, the latest version breaks ledger sat stack. use version 2.33.1

Where do I find an old version for Ledger Live in general and for macOS specifically?

all versions for all platforms are available here : https://github.com/LedgerHQ/ledger-live-desktop

@d-rez
Copy link

d-rez commented Dec 13, 2021 •
edited
Loading

Same issue here with a Nano X on Windows. Zzzz. I don't mind temporarily not using my node but can this be fixed, Ledger? Or at least acknowledged? I noticed something wasn't right when it stopped syncing data with the BTC network recently.

Ledger live v2.36.2
BTC App v2.0.1

BTW, I think the title of this Issue should be edited to something more informative, like "Bitcoin full node support broken - UNKNOWN_ERROR (0x6a82)"

EDIT: Extract from logs:

        "type": "cmd.ERROR",
        "data": {
            "name": "TransportStatusError",
            "message": "Ledger device: UNKNOWN_ERROR (0x6a82)",
            "stack": "Error
                    at new TransportStatusError (C:\Program Files\Ledger Live\resources\app.asar\node_modules\@ledgerhq\errors\lib\index.js:184:18)
                    at TransportNodeHidSingleton.<anonymous> (C:\Program Files\Ledger Live\resources\app.asar\node_modules\@ledgerhq\hw-transport\lib\Transport.js:127:39)
                    at step (C:\Program Files\Ledger Live\resources\app.asar\node_modules\@ledgerhq\hw-transport\lib\Transport.js:33:23)
                    at Object.next (C:\Program Files\Ledger Live\resources\app.asar\node_modules\@ledgerhq\hw-transport\lib\Transport.js:14:53)
                    at fulfilled (C:\Program Files\Ledger Live\resources\app.asar\node_modules\@ledgerhq\hw-transport\lib\Transport.js:5:58)",
            "statusCode": 27266,
            "statusText": "UNKNOWN_ERROR"

        "level": "info",
        "message": "✖ CMD scanDescriptors error",
        "pname": "renderer",
        "timestamp": "2021-12-13T14:10:16.461Z"

        "type": "hw",
        "message": "getAddress bitcoin on <redacted> FAILED TransportStatusError: Ledger device: UNKNOWN_ERROR (0x6a82)",
        "level": "debug",
        "pname": "internal",
        "timestamp": "2021-12-13T14:10:16.461Z"

@aphex3k
Copy link
Author

aphex3k commented Dec 13, 2021

It works if you reverts back to an older Ledger version, however, you lose Taproot support.

@plk
Copy link

plk commented Jan 12, 2022

Same issue here with OSX, 2.36.2. Would be very nice to have this fixed so we can have Taproot and full node support. Makes the documentation page on sovereignty and verification look a little embarrassing since this hasn't worked for a few versions now ...

@tyuxar
Copy link

tyuxar commented Jan 16, 2022

I ran into the same bug on macOS 10.15.7 + Ledger Live 2.36.3.

I also found a "workaround": turn off the "Experimental JS implementations" in Settings, then it worked for me. Obviously this is only theoretical, there's not taproot support without it.

@d-rez
Copy link

d-rez commented Jan 18, 2022

I also found a "workaround": turn off the "Experimental JS implementations" in Settings, then it worked for me. Obviously this is only theoretical, there's not taproot support without it.

That doesn't seem like a viable workaround given that I never had this option enabled in the first place :D

@tyuxar
Copy link

tyuxar commented Jan 21, 2022

I also found a "workaround": turn off the "Experimental JS implementations" in Settings, then it worked for me. Obviously this is only theoretical, there's not taproot support without it.

That doesn't seem like a viable workaround given that I never had this option enabled in the first place :D

Well, back then it worked, now it doesn't. :)

I've upgraded Ledger Live meanwhile to 2.37.1 (bitcoin app 2.0.1), but the bug is still there. No matter which implementation I choose. This makes basically taproot unusable on Ledger. Well, on a second thought, not only taproot, but everything, because I get this error when I scan for, or want to add new accounts.

@blazsar
Copy link

blazsar commented Jan 21, 2022 •
edited
Loading

I had the same problem but it worked for me to do the following:

  • Disable all experimental features first
  • Reset ledger live (be aware that I said Ledger Live, NOT Ledger device)
  • Cleared Ledger Live Cache
  • Uninstalled all Apps from my ledger device
  • Reinstalled the Bitcoin App on device and initialized it
  • Went to accounts on ledger Live and added Bitcoin (toggle the 'Show all address types' switch on) and it showed my taproot address for adding.

2022-01-22 - 11-56-13

@tyuxar
Copy link

tyuxar commented Jan 23, 2022

Resetting Ledger Live on macOS also worked for me. What I did:

  • removed LL application
  • removed all LL related files and directories in my $HOME: find ~ -iname '*ledger*' 2> /dev/null, go through the list and erase them
  • reinstalled LL
  • reimported the accounts

I didn't need to turn on the experimental JS implementations for a successful account import.

@plk
Copy link

plk commented Feb 5, 2022

I tried all of these resest/reinstalls but still get the same error.

@memowete
Copy link

I tried all of these resest/reinstalls but still get the same error.

I had the same issue. I am not a tech person, however, reading here and elsewhere I figured to clear the Ledger Live Cache first, (Ledger not Connected). Navigated to Settings, Experimental Features, Developer mode - On. Navigated to Manager and connected my Ledger X to verify. Then clicked on Accounts +Add Account. It scanned my devise/ Blockchain and revealed my missing addresses. Can open new accounts now also. Go back to Developer mode and switch off. Hope it helps

@premmen2
Copy link

To everyone who got the issue resolved: are you connecting Ledger Live to a full node? For me everything is working until I try to connect Ledger Live with my full node.

@memowete
Copy link

To everyone who got the issue resolved: are you connecting Ledger Live to a full node? For me everything is working until I try to connect Ledger Live with my full node.

No, did not connect to full node

This was referenced Feb 23, 2022
Open
Open
@SpeedForceGN
Copy link

To everyone who got the issue resolved: are you connecting Ledger Live to a full node? For me everything is working until I try to connect Ledger Live with my full node.

Are you on the latest software? This blochchain issue is the second straw for me. First one is that I can not add Algorand to Ledger Live. Maybe I should look into other choices...

1 similar comment
@SpeedForceGN
Copy link

To everyone who got the issue resolved: are you connecting Ledger Live to a full node? For me everything is working until I try to connect Ledger Live with my full node.

Are you on the latest software? This blochchain issue is the second straw for me. First one is that I can not add Algorand to Ledger Live. Maybe I should look into other choices...

@plk
Copy link

plk commented Feb 23, 2022

To everyone who got the issue resolved: are you connecting Ledger Live to a full node? For me everything is working until I try to connect Ledger Live with my full node.

Yes, the issue for me is only when I try to connect to my full node.

@SpeedForceGN
Copy link

So I downgrade to version of 2.33.1 ledger live. Once I had this version up and running, I then made sure that developer was turned off (This is the only experimental feature that I activated). I then started the connection to my BITCOIN NODE. I followed all the steps, downloaded and installed Sat Stack. I now completed the NODE connection and synced SAT STACK with my accounts. This took approximately 2 hrs. After I had things up and running, I left the SAT STACK running and then downloaded and installed 2.38.3. My connection is still there with my node and Sat Stack is still running. Then I had to add my accounts back to LEDGER LIVE. I hope this works for everyone.

I do need to figure out how to have SAT STACK to autostart on reboot in Windows 11. Also need to know the differences of the 4 bitcoin accounts.

@LuckyKey613
Copy link

I had the same error but turned off "Extended account search" in the Experimental Features section in Settings and it worked for me.

@jagamaster
Copy link

jagamaster commented Mar 12, 2022 •
edited
Loading

Started to get "Ledger device: UNKNOWN_ERROR (0x6a82)" after upgrading firmware on Ledger Nano S.
I trying to switch ON "Extended account search" experimental option to import my Bitcoin Native and Legacy account to Ledger live application but get "Ledger device: UNKNOWN_ERROR (0x6a82)" error at account searching step.
Significant downgrading of Legder Live application doesn't help.

After downgrade Ledger Live to 2.33.1 version error 0x6a82 disappeared, but Bitcoin Native and Legacy accounts still not appears. Only native segwit.
I have another Ledger Nano X with old firmware and it's working fine on the save system.
Using MacOS 10.14.6 Mojave.
Tried also under Win10.

@kraikov kraikov mentioned this issue Mar 25, 2022
Merged
@kraikov
Copy link

kraikov commented Mar 28, 2022

Is there a way to get rid of the error with the latest firmware? As a last resort, how to rollback the firmware version? I suppose that's not possible.

@diwakergupta
Copy link

Any update on this? I'm also running into this issue, both Ledger Live on Desktop and mobile, latest firmware. Simple BTC transfer.

@mattderron
Copy link

I agree on renaming to specify "connecting to full node", the responses are getting confusing now with references to other seemingly unrelated issues.

Also hoping for a resolution to this soon, ability to connect to a full node on the latest version is important, IMO.

@goolash761
Copy link

Having the same issues on mine: cannot send transactions, cannot connect to my own node to send transactions, either. Customer service has been a dead end, telling me to reset, reinstall, etc, but it does not work.

@banonisking
Copy link

Im facing the same problem too, I already update my bitcoin apps at ledger manager and update my ledger live desktop version the error came out [(0x6a82)) is there any other way I can get the funds back? can I move it to another wallet with the secret phase phrase? anyone

I also just downloaded the 2.33.1 version and solved the problem. I finally solved it. I tried infinite methods. Finally, I downloaded 2.33.1 and solved it. I hope it will be useful to everyone.

@banonisking
Copy link

I also just downloaded the 2.33.1 version and solved the problem. I finally solved it. I tried infinite methods. Finally, I downloaded 2.33.1 and solved it. I hope it will be useful to everyone.,
謝謝這裡的大家，我終於可以了

@banonisking
Copy link

To everyone who got the issue resolved: are you connecting Ledger Live to a full node? For me everything is working until I try to connect Ledger Live with my full node.

I also just downloaded the 2.33.1 version and solved the problem. I finally solved it. I tried infinite methods. Finally, I downloaded 2.33.1 and solved it. I hope it will be useful to everyone.

@banonisking
Copy link

Having the same issues on mine: cannot send transactions, cannot connect to my own node to send transactions, either. Customer service has been a dead end, telling me to reset, reinstall, etc, but it does not work.

I also just downloaded the 2.33.1 version and solved the problem. I finally solved it. I tried infinite methods. Finally, I downloaded 2.33.1 and solved it. I hope it will be useful to everyone.

@vprf06
Copy link

vprf06 commented Apr 21, 2022

I had the same problem but it worked for me to do the following:

  • Disable all experimental features first
  • Reset ledger live (be aware that I said Ledger Live, NOT Ledger device)
  • Cleared Ledger Live Cache
  • Uninstalled all Apps from my ledger device
  • Reinstalled the Bitcoin App on device and initialized it
  • Went to accounts on ledger Live and added Bitcoin (toggle the 'Show all address types' switch on) and it showed my taproot address for adding.

2022-01-22 - 11-56-13

Clearing program cache and turning off experimental worked for me!

@jagamaster
Copy link

What exactly Ledger device do you have?
What device firmware version do you have?
What ledger Live version did you installed? OS?

(I am Ledger X with 2.0.2 Secure element firmware, tested with Win10 and MacOS Mojave 10.14.6) with lastest and several versions.

@ItzSilvx
Copy link

Can we update to the new version once we are done adding the btc account?

@tomav
Copy link

tomav commented Jun 7, 2022

Hi, is there any update on this? Still have the same issue.
Ledger device: UNKNOWN_ERROR (0x6a82)
Ledger Live 2.42.0 on OSX 12.4

@goolash761
Copy link

goolash761 commented Jun 7, 2022 via email

@oeisenslave oeisenslave mentioned this issue Jul 2, 2022
Closed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests