I am sorry, but could you clarify what recommendations you guys told them?
Tested it on my own device with an address that is like 7y old. Using the old Ledger nano. There was only one transaction involved with that address and it was a t2t. No shielding involved at all. This is what I get after upgrading to latest Zcash app version (did not let me send with old app version - forced me to upgrade to latest).
→ Disconnect of the Hardware Wallet and could not broadcast the new t2t transaction
5 Likes
Hi! This is the issue that I could test with the build ledger gave me. They are confirming their changes and going through their release process.
What they told us is that given it takes an update on both ledger live and the Zcash transparent app it is not instant
3 Likes
Yes, of course. let me go back to the conversations and I’ll summarize it provided that I get consent from the people involved, since that is a private conversation and we are a privacy-centric ecosystem 
2 Likes
@jenkin We are debugging a similar issue on iOS at the moment. Feel free to email me directly at andrea@electriccoin.co, I will do my best to help you debug/resolve this.
4 Likes
Have you setup the Ledger dev environment with Ledger Live and SDK?
You mean for the test I did? no. Just installed the beta version Ledger gave me and used a configuration of Ledger Live Beta for it to get app updates from the beta provisioning channel to install the dev version of their Zcash transparent app.
I meant for the investigation that you guys (Zondax/ECC/ZF/you) did. It seems it would be difficult to debug without.
8 Likes
just updated my ledger live and zcash app – This finally worked for me 
4 Likes
I actually still get the same error after updating so not sure whats going on.
1 Like
Please note that this update only resolves the t-to-t issue that led Binance to suspend withdrawals. It does not fix the problem that occurs when deshielding into a Ledger device. We’re aworking with Ledger to determine when that issue will be addressed.
2 Likes
It works only on ledger live desktop v2.109, I’ve been able to move my Zec from my t address secured by a ledger nano x to Zashi and then shield them (and finally move them to Keystone ;)).
2 Likes
Yeah it turns out I had accidentally made a deshielding tx initially and so its another issue. Sorry for the confusion! (I swept the small test amount that it was with Ywallet)
сеть BNB для Zcash на BINANCE работает и на ввод и на вывод!
Hi! I know Russian very well, but I write in English, because this is an English-speaking forum, and we need to respect the culture of communication, because others can’t understand what you wrote. So, please write in English. But there is also a Russian-speaking thread.
2 Likes
Thank you for the clarification, I was under the illusion that it also solved the when issue deshielding to Ledger, but I realized that it didn’t as soon as I tried.
I stay optimist because you are working on it 
.
2 Likes
The “deshielding” issue you mention can be bypassed with importing the seed into the Ywallet Sweep. Otherwise, I know of no current efforts to actaully fix that issue.
Just updated my Ledger Live and my Nano X, but unfortunately it still doesn’t work for me. Tested via iPhone and Mac, but I still get this error message. Device not connected …
1 Like
I got this same error but it was for a previous, unresolved issue where funds were sent from a shielded address to the ledger transparent address. You can confirm this (if you didn’t know for sure) by checking the txid in a block explorer for any shielded inputs. Here is an example
There is currently no fix in Ledger for this but you can recover the funds with the Ywallet sweep function.