# Failure to Upgrade v2.48.0-\>v2.51.1+rev2 on a fin

**URL:** <https://forums.balena.io/t/failure-to-upgrade-v2-48-0-v2-51-1-rev2-on-a-fin/200242>\
**Category:** Product support\
**Created:** [October 17, 2020, 12:42am UTC](https://forums.balena.io/t/failure-to-upgrade-v2-48-0-v2-51-1-rev2-on-a-fin/200242 "2020-10-17T00:42:35Z")\
**Posts on this page:** 1\
**Showing post:** 19

<div class="post-metadata">

**Author:** ![crbn60](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/crbn60/32/3671_2.png) [@crbn60](https://forums.balena.io/u/crbn60)\
**Post date:** [October 20, 2020, 6:43pm UTC](https://forums.balena.io/t/failure-to-upgrade-v2-48-0-v2-51-1-rev2-on-a-fin/200242/19 "2020-10-20T18:43:29Z")

</div>

I was just looking around and found this post:

> [@Application default device type](https://forums.balena.io/t/application-default-device-type/147515/17):
>
> That makes things clear. The issue is that the device is pre-registered with balena device register and you can see that after that point the device shows up in the dashboard with a device type matching the default device type of the application. As a result, when you later use balena config generate you change the device type of the already registered device. Perhaps it might be better to have the CLI error when ---device and --device-type are used together, so that it’s clear which option i…

That would indicate, to me, that reflashing the device isn’t going to change the `deviceType`. Does that mean I will need to re-register the device completely?

Thanks,

A.

---

_[View the full topic](https://forums.balena.io/t/failure-to-upgrade-v2-48-0-v2-51-1-rev2-on-a-fin/200242)._