Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Mikrotik mANT 19s is bricked by upgrading from 3.23.12.0 to nightly #1149

Closed
aanon4 opened this issue Apr 3, 2024 · 5 comments
Closed

Mikrotik mANT 19s is bricked by upgrading from 3.23.12.0 to nightly #1149

aanon4 opened this issue Apr 3, 2024 · 5 comments
Labels
bug Something isn't working must fix

Comments

@aanon4
Copy link
Contributor

aanon4 commented Apr 3, 2024

Upgrading the Mikrotik mANT 19s (that nice AC sector device) bricks the device. It appears to flash the new image, but then gets stuck in a boot loop. Watching the device on my desk the reboot happens so fast I doubt it ever makes it into the new image.
@aanon4 aanon4 added bug Something isn't working must fix labels Apr 3, 2024
@aanon4
Copy link
Contributor Author

aanon4 commented Apr 3, 2024

Booting the nightly ram image works. Flashing the main image while running the night ram image also work. It looks like something in the upgrade process is broken.

@aanon4
Copy link
Contributor Author

aanon4 commented Apr 3, 2024

Can upgrade nightly to nightly okay.

@aanon4 aanon4 changed the title Mikrotik mANT 19s is bricked by upgrading to nightly Mikrotik mANT 19s is bricked by upgrading from 3.23.12.0 to nightly Apr 3, 2024
@aanon4
Copy link
Contributor Author

aanon4 commented Apr 3, 2024

Cannot downgrade from nightly to 3.23.12.0

@aanon4
Copy link
Contributor Author

aanon4 commented Apr 3, 2024

So it looks like they changed the alignment of the header information in the flash, so the old code can't flash new firmware, and new firmware can't flash old code. Will change the alignment back. It makes flashing a little more inefficient but nothing problematic for our use case.

@aanon4 aanon4 mentioned this issue Apr 3, 2024
Merged
@aanon4
Copy link
Contributor Author

aanon4 commented Apr 3, 2024

Fixed

@aanon4 aanon4 closed this as completed Apr 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working must fix
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@aanon4