Update Your Raspberry Pi Image For B+ & Model 2 Compatibility (Raspbian Base)

I’ve recently been going through all of the Raspberry Pi Images I’ve created and shared here on Everyday-Tech.com and updating them to work properly on newer Models of the Raspberry Pi. Surprisingly the update process is much easier than I would have anticipated going into this whole project. Since I have so many projects to update and test – I thought it might be helpful for others to document what process was required to update the image and any issues I ran into along the way.


I’ve found that many of the images available currently still haven’t updated a B+ / v2 compatible SD card image quite yet. But if you have a Model A or B handy, You don’t have to wait for the publisher to update the image. In most cases it’s as simple as doing the following:

1.) Boot image up using a compatible Model Raspberry Pi (At the time of this writing: Model A or B)

2.) Once Booted – Login and Run the following command:

3.) When finished – Shutdown.

4.) Test to make sure it boots up in your new Raspberry Pi!


That is it… Really.


The Details…


While I did encounter an issue updating my MineCraftPi image, All the others updated perfectly fine with only this 1 command! In order to lend some credibility to this argument, Here is what a senior forum moderator Plugwash said regarding the update process.

 If the image was installed using a plain Raspbian image from the raspberry pi foundation then the following should be sufficient.


Should I run RPI-UPDATE?

I assume that most people who are reading this are familiar with the update & upgrade commands – However I wanted to briefly cover the rpi-update and dist-upgrade commands as well, Since I wasn’t entirely sure If i needed to concern myself with these commands or not.

The short answer is No. Well, at least for most of us anyways…

Raspberry Pi Enginner Dom probably explains the role of rpi-update better than anyone.

rpi-update gets you the latest experimental firmware. It is usually fine, but occasionally may have regressions. You should run rpi-update regularly if you want to help with testing, and are happy to encounter bugs and submit bug reports. You might want want to run rpi-udpate if you are having a specific issue that a forum post, or commit messages on guithub suggests has been recently fixed. The changes from rpi-updates will appear with an apt-get update eventually, if there are no reports of regressions from the rpi-update testers. Most users should just use this.

So unless you care to be on the bleeding edge, or need the latest version of firmware to troubleshoot a specific issue – Most people will want to steer clear of running rpi-update from here on out. All of the firmware updates will eventually be rolled up in the next update / upgrade list. That being said, If the image you are working with hasn’t been updated in a long time (IE – before the changes to rpi-update) You may still need to run this.


Should I run DIST-UPGRADE?

The Raspberry Forum Moderator Plugwash describes dist-upgrade:

The main difference between upgrade and dist-upgrade is that dist-upgrade will add or remove packages to update others while upgrade won’t. Dist-upgrade can be a useful tool but you MUST check what it is planning to do before saying yes because sometimes it’s idea of what should be removed to make way for upgrades will disagree with yours ;).

Dist-upgrade VS. apt-get upgrade is essentially quick install VS. custom install. For most users and their environments, sudo apt-get upgrade (aka – quick install) is going to be the quickest, cleanest and simplest way to install or update your software. Dist-upgrade should only be used if you are confident in your ability to address the many prompts that it kicks off while it’s running!



This command is purely optional. It will update the appearance of the Raspberry Pi desktop environment – of which none of my images utilize.


Image Update Progress

Admittedly this section is more for my own sanity than anything else, but perhaps others may find it useful to see what was involved with updating all of my own images. Below is a list of all the Raspberry Pi images I have created and their current update status for newer models.

[learn_more caption=”PressPi”]

Status: Complete

Commands Used In Update:

[/learn_more][learn_more caption=”MineCraftPi”]

Status: Not Possible (using v2.2)

I’ve tried every command listed above to update the image, but I keep getting a number of errors when I boot it up on the Model B2. Since the image needs a bit of an overhaul anyways ( for v1.8 of MineCraft) – I’ll probably just re-build this one from scratch.

Update: 3/27/2015

MineCraftPi v3.0 is done! Should be made available tonight. (testing still in progress)

[/learn_more][learn_more caption=”NagiosPi”]

Status: Complete

Commands Used In Update:

[/learn_more][learn_more caption=”AdagiosPi”]

Status: Complete

Commands Used In Update:

[/learn_more][learn_more caption=”OSTicketPi”]

Status: Complete

Commands Used In Update: