Attempted firmware update stuck on bootloader, PERMANENTLY?

[Thomas29]

I was attempting to update Firmware from 1.6.0 to 1.6.1 I got to the step where the bootloader is displayed on the device.
Now it is stuck, literally permanently stuck and I don't know how to fix it?

Support.ledger.com troubleshooting FAQ the directions said to open ledger live and go to Manager tab to continue update I can't do that because it asks that I
unlock the device.  Cant unlock device because it is stuck, showing bootloader on screen.  What do I do now?  

I've restarted the computer and plugged the ledger back in. Still stuck on bootloader... I can't get it work at all?

Is my Ledger Nano S broken? Do I need to purchase a new one?

[Rath_]

Support.ledger.com troubleshooting FAQ the directions said to open ledger live and go to Manager tab to continue update I can't do that because it asks that I
unlock the device.

Have you tried going into the settings of Ledger Live (top-right corner) and selecting "Repair your Ledger device" under "Help" tab?

[HCP]

Is my Ledger Nano S broken? Do I need to purchase a new one?

Most likely "No" to both your questions. It should be possible to recover the device, although there is a chance you'll need to do a full restore. Do you have your 24 word seed mnemonic available?

Support.ledger.com troubleshooting FAQ the directions said to open ledger live and go to Manager tab to continue update I can't do that because it asks that I
unlock the device.  Cant unlock device because it is stuck, showing bootloader on screen.  What do I do now? 

Additionally... if you leave it on the "Manager" screen, it should eventually prompt you to attempt to "Repair" after a minute or so:



Click the "Repair" button and follow the onscreen instructions.

[Thomas29]

I was about to click repair but Ledger Live closed on me and now it's not showing up again. I'm not sure how to find it and I tried a google search but still can't find it? 

[Rath_]

I was about to click repair but Ledger Live closed on me and now it's not showing up again. I'm not sure how to find it and I tried a google search but still can't find it?  

Ledger Live shouldn't close and uninstall on its own. Can you try to launch it from its install directory ("C:\Program Files\Ledger Live")?

[dkbit98]

I knew it it was ledger even before opening this topic  

It is important that you have your backup and seed phrase saved, then you can try full uninstall Ledger Live or try to clear cash in LL settings.
Perform clean installation and try again connecting your wallet.

[Thomas29]

I was attempting to update Firmware from 1.6.0 to 1.6.1 I got to the step where the bootloader is displayed on the device.

Very strange, everything went smoothly for me and was not time consuming.

Support.ledger.com troubleshooting FAQ the directions said to open ledger live and go to Manager tab to continue update

In fact they say open it as administrator  Did you try to follow their troubleshooting as it is?

Follow these steps if your device is stuck on Bootloader:

Open Ledger Live.
On Windows: Right-click Ledger Live and run as an Administrator.
Connect your Ledger Nano S.
Go to the Manager tab of Ledger Live desktop and click on Continue.
If the loader is at 100% and the device stays stuck on Bootloader:
Windows/Linux: Restart Ledger Live by pressing CTRL + R. Then start the repair tool once more.
MacOS: Restart Ledger Live by pressing ⌘ + R. Then start the repair tool once more.

Hope above restoring steps don't depend on firmware and will work for you.

Thank you managed to restart it on another computer as the CTRL+R wasn't working even when I restarted my computer. @BitCyrptex I said Ledger closed on me not uninstalled. I downloaded the Firmware Update the day they released it. From what I read the servers can get overloaded and this can happen... not saying that's what the problem was in this case idk.

[joniboini]

I said Ledger closed on me not uninstalled. I downloaded the Firmware Update the day they released it. From what I read the servers can get overloaded and this can happen... not saying that's what the problem was in this case idk.

There might be additionals details on Event Viewer if you're still curious as to why it happens. As for the overload, I thought the app would download the firmware first before they run the update, so there should be no issue if the server went bust in the middle. Looks like I was wrong.