Device: Jade Plus
Current firmware: 1.0.39 (no radio)
Attempted firmware: 1.0.40-beta4 (no radio)
Update method: JadeLink pendrive firmware update
Issue:
I tried updating my Jade Plus to firmware version 1.0.40-beta4 using the JadeLink pendrive method.
The update process completes successfully and the device shows:
"Firmware upgrade successful"
After rebooting, the device starts normally, but the firmware version remains unchanged and still shows the previous version.
Additionally, none of the new 1.0.40-beta4 features appear on the device.
Behavior observed:
Firmware flashing process completes normally
Success message shown
Device reboots successfully
Old firmware remains active after reboot
even I tried reseting the device once and again tried to flash 1.0.40 - beta4 (no radio) but the issue remains the same.
Additional info:
Official firmware binary used from GitHub
Device currently contains no wallet/keys
Issue tested multiple times
Possible cause:
Could this be related to firmware rollback/A-B slot fallback or firmware validation failing after reboot?
Device: Jade Plus
Current firmware: 1.0.39 (no radio)
Attempted firmware: 1.0.40-beta4 (no radio)
Update method: JadeLink pendrive firmware update
Issue:
I tried updating my Jade Plus to firmware version 1.0.40-beta4 using the JadeLink pendrive method.
The update process completes successfully and the device shows:
"Firmware upgrade successful"
After rebooting, the device starts normally, but the firmware version remains unchanged and still shows the previous version.
Additionally, none of the new 1.0.40-beta4 features appear on the device.
Behavior observed:
Firmware flashing process completes normally
Success message shown
Device reboots successfully
Old firmware remains active after reboot
even I tried reseting the device once and again tried to flash 1.0.40 - beta4 (no radio) but the issue remains the same.
Additional info:
Official firmware binary used from GitHub
Device currently contains no wallet/keys
Issue tested multiple times
Possible cause:
Could this be related to firmware rollback/A-B slot fallback or firmware validation failing after reboot?