rpi-update now wont boot

[vibez]

Hi,

I ran rpi-update on my pi and rebooted. Now I get to the rainbow coloured screen, then to the noobz recovery console. After that, just a black screen and a single red light showing on my pi. Any ideas how to fix this?

[emwtur]

Same happened to me
I've installed Raspbian from NOOBS !
after running "sudo rpi-update" I only get a black screen - after the NOOBS "press shift" screen
- it worked a couple of weeks ago !

[vibez]

ever find a fix?

[emwtur]

ever find a fix?

not really - pressed shift and reinstalled

[AndrewS]

I've just tested it myself and you're right, the latest firmware appears to break NOOBS.
So I've filed a bug report https://github.com/raspberrypi/firmware/issues/204 and hopefully it won't take too long for the devs to push out a fixed NOOBS-friendly firmware

[gsh]

OK,

There was a mod that went into the kernel and firmware two days ago which modifies the way rebooting works... It _should_ work properly but looks like it doesn't!

Will investigate

Gordon

[RaTTuS]

FYI
rpi-update should not be run as a matter of course for 99.9% of most users

I don't think that it should be mentioned generally as it puts people on the bleeding edge [unless with a lot of caveats]

99.9% of people should only need to do apt-get update && apt-get upgrade

[vibez]

Thanks guys. The boot partition on the noobs card is on the 2nd partition, therefore windows doesn't see it. I've mounted the card using a linux live cd and can see that in the boot partition there is a boot.bak folder full of .elfs. I'm going to overwrite the files in \boot with those found in \boot.bak and see if that fixes things...

Should that work?

[gsh]

No...

For the moment I'd suggest you recover Raspbian from clean...

But you'll have to copy off anything you want to keep, I'm testing a fix right now so this shouldn't be a problem tomorrow...

Gordon

[vibez]

Which partition should I copy off so that I keep everything?

[gsh]

I'd suggest just copying any data that you really don't want to lose...

Don't bother copying everything off... Then hit shift when it boots and hit Raspbian again...

After all that's one of the reasons for having NOOBS!!!

Thanks

Gordon

[vibez]

There isn't really much data as such, but there are a lot of tweaks/config files that I've applied. I doubt I can remember all the files I've amended. It would be a lot better if I could just fix this card so I could boot. Why would recovering the boot files not work? Is the firmware upgrade touching more files than that?

[vibez]

I see there is an offline mode mentioned in the bug report that someone says allowed their card to boot. Are there any instructions on how to run this?

[gsh]

PM me an email address and I'll send you a binary you can use...

Gordon

[vibez]

PM sent

[emwtur]

ever find a fix?

not really - pressed shift and reinstalled

Nice to see the quick response to this problem !
I NEEDED to do an rpi-update to get an usb layer that sane could work with to get my scanner working.
anyway - to verify that NOOBS was the cause of the problem .- I made another SD card with a "clean" raspian installation - and there I was able to perform a rpi-update.
TTFN

[AndrewS]

This problem has been fixed with the latest version of the firmware - https://github.com/Hexxeh/rpi-firmware/ ... 057edddf3d
If you're able to run rpi-update then use that, but if you're unable to use rpi-update to fix your 'broken' NOOBS, then simply copy the three files from the link above to the second partition of your NOOBS SD card (which will be something like /dev/sdf5 when using a USB card-reader on Linux).

Unsurprisingly, the offline mode of rpi-update is documented here https://github.com/Hexxeh/rpi-update but as mentioned it's an expert option.