Norns: update fail recovery

several people have updated directly to 2.0.1 from 1.x, which was designed to fail, but failed to fail correctly. (new thread idea: “failing correctly”) :slight_smile:

here’s how you recover. it involves terminals.

  1. on your laptop, download norns190405.tgz and copy it to a FAT-formatted USB thumbdrive. make sure your browser doesn’t uncompress it. make sure the filename is norns190405.tgz

  2. insert the thumbdrive. power up norns.

  3. connect via serial (which is also described at

  • connect usb cable from norns power to laptop
  • run
  • type (but do not press enter)
screen /dev/tty.usb
  • press TAB. this will autofill the rest of the path, which will look something like tty.usbASDF23
  • complete the line with 115200 so it looks like
screen /dev/tty.usbASDF23 115200
  • press enter. you should get a blank screen. press enter again. you’ll get a login prompt. user: we password: sleep
  1. time to run the update. copy-paste these commands line by line and push enter. none of them should fail. if they fail, something didn’t work right.
cd update
cp /media/usb0/norns190405.tgz .
tar xzvf norns190405.tgz
tar xzvf 190405.tgz
cd 190405

the update will run now. when done, shut down norns.

sudo shutdown now

you can close the terminal.

reboot norns and you’ll be at 2.0.0. you can then use SYSTEM > UPDATE to get the newest version.


That worked!! Thanks. I used putty and did a serial connection on a windows machine instead of screen. The key was those command lines. Back to doing interesting things with NORNS :smile:

I made it to, cd update
and got, no such file or directory
ls -la shows
total 84
drwxr-xr-x 8 we we 4096 May 7 11:04 .
drwxr-xr-x 3 root root 4096 May 15 2018 …
-rw------- 1 we we 706 May 7 11:04 .bash_history
-rw-r–r-- 1 we we 220 Apr 18 2018 .bash_logout
-rw-r–r-- 1 we we 3523 Apr 18 2018 .bashrc
-rw-r–r-- 1 we we 6797 May 7 11:04 changelog.txt
drwxr-xr-x 3 we we 4096 May 15 2018 .config
drwxr-xr-x 8 we we 4096 Sep 6 2018 dust
drwxr-xr-x 3 we we 4096 May 15 2018 .local
drwxr-xr-x 3 we we 4096 Oct 29 2018 maiden
drwxr-xr-x 14 we we 4096 Apr 23 02:52 norns
drwxr-xr-x 5 we we 4096 Oct 29 2018 norns-image
-rw-r–r-- 1 we we 675 Apr 18 2018 .profile
-rw-r–r-- 1 we we 16 May 7 09:44 psk.wifi
-rw-r–r-- 1 we we 56 Mar 11 17:03 scan.wifi
-rw-r–r-- 1 we we 9 May 7 09:44 ssid.wifi
-rw-r–r-- 1 we we 7 May 7 09:44 status.wifi
-rw-r–r-- 1 we we 7 May 7 11:04 version.txt
-rw------- 1 we we 1001 Sep 6 2018 .viminfo
-rw-r–r-- 1 we we 51 May 7 09:44 wpa_supplicant.conf

if I cd norns there is an update.sh_template script

on the norns display, under ‘system 190422’ - the update option is there

I was wondering if I should just mkdir update in the root and keep going, but I don’t want to mess things up more than already have. I’d prefer to fail correctly this time!

Any advice?

yes do

mkdir update

and all will be well!

1 Like

thank you, that worked perfectly.
Very excited for the update!

1 Like

I had to do this…I accidentally deleted the Code folder in maiden. Eek. Looks like it worked for me.

Thank You!
deleting failed script files in maiden I too came across this issue.
but followed these steps despite seeing the line “failed updates” in the terminal log ( first time I ever used that) and what do you know… everything worked!
back to gladly loosing sleep with norns

does anyone knows a way to get around using tab for autocompletion in putty (windows) for this?
i can’t get it to work on my machine

i think on windows you just identify the COM port that was enumerated?

i couldn’t get it to work on windows so trying on mac now and after enabling autocompletion i still have no result. when pressing TAB nothing happens

now i’m not seeing the usb drive on norns when connecting with putty. i tried all ports without success.
i tried to update with what look now like a broken file. without wifi or usb drive i’m not sure how i could try to update again with a clean file. any help would be welcome

do you mean that /media/usb0 is not found?

is your USB disk FAT formatted?

finally updated with success! looks like the ports were there i was looking in the wrong place with the wrong commands. sorry for bothering you. thanks for your help :slight_smile: