# Updating via rpi-update **URL:** \ **Category:** uConsole\ **Created:** [January 26, 2024, 10:57pm UTC](https://forum.clockworkpi.com/t/updating-via-rpi-update/12262 "2024-01-26T22:57:47Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![meep.bot](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/meep.bot/32/8915_2.png) [@meep.bot](https://forum.clockworkpi.com/u/meep.bot)\ **Post date:** [January 26, 2024, 10:57pm UTC](https://forum.clockworkpi.com/t/updating-via-rpi-update/12262/1 "2024-01-26T22:57:47Z")
Should I not do this? Will it brick my uconsole? ---
**Author:** ![Ryan\_Finlayson](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/ryan_finlayson/32/5989_2.png) [@Ryan\_Finlayson](https://forum.clockworkpi.com/u/Ryan_Finlayson)\ **Post date:** [January 27, 2024, 4:47am UTC](https://forum.clockworkpi.com/t/updating-via-rpi-update/12262/2 "2024-01-27T04:47:35Z")
1. why are you doing this 2. rpi-update has been deprecated for the past 3 years according to its github page [GitHub - Hexxeh/rpi-update: An easier way to update the firmware of your Raspberry Pi](https://github.com/Hexxeh/rpi-update) 3. it only states it should be used with the official RPi images for standard RPi’s I wouldn’t risk it unless you have a really good answer to number 1. ---
**Author:** ![DeRock25](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/derock25/32/7976_2.png) [@DeRock25](https://forum.clockworkpi.com/u/DeRock25)\ **Post date:** [January 27, 2024, 2:16pm UTC](https://forum.clockworkpi.com/t/updating-via-rpi-update/12262/3 "2024-01-27T14:16:52Z")
I’m still waiting for my uconsole… But my devterm… The image from CPI has no login page installed… Has a custom config.txt… has pins reassigned to non standard…has 4 extra daemons running… if I updated something that made those 4 extra not work… I’d be sol untill I begged someone to update source and make them for the new update… Also… Even using the raspi-config app… will disable some of those daemons… or activate a login screen that doesn’t exist… making you built in screen not work… and it hang in boot… Tinkering I did both of those yesterday… Because the raspi-config settings when you open it are all showing weird values… Long story long… it’s a hobbyist device… Updates will always come with risks… ---
**Author:** ![meep.bot](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/meep.bot/32/8915_2.png) [@meep.bot](https://forum.clockworkpi.com/u/meep.bot)\ **Post date:** [January 27, 2024, 4:44pm UTC](https://forum.clockworkpi.com/t/updating-via-rpi-update/12262/4 "2024-01-27T16:44:24Z")
tbh I have no real reason other than just trying to keep all my electronics up-to-date, but I know this is a highly customized piece of hardware which is why i asked instead of just going ahead and doing it. good to know about rpi-update being depreciated! I haven’t messed around with a raspi since back when we still used that, so it sounds like I have to read up on whats changed since then. thanks everyone!