Remote desktop and Putty not working after rpi-upgrade

[rickinpatel]

I had successfully enabled SSH and was working on to raspberry pi using remote desktop on windows. But after the firmware upgrade I dont know what happened and suddenly now its not working. Do I have only option of formatting and re installing os. I had installed python opencv and lot of modules which will be hectic to install again . Please suggest me some solution

[wh7qq]

Are you still using the default password "raspberry"? The upgrade has probably brought in the new security requirement that SSH is disabled by default until the password has been changed. If you connect the Pi to a monitor, keyboard and mouse, you can then change the password, either in linux, raspi-config or the Raspberry Pi Configuration tool in the desktop menu. Reboot and you should be able to SSH to the RPi again, using the new password.

[klricks]

Are you still using the default password "raspberry"? The upgrade has probably brought in the new security requirement that SSH is disabled by default until the password has been changed. If you connect the Pi to a monitor, keyboard and mouse, you can then change the password, either in linux, raspi-config or the Raspberry Pi Configuration tool in the desktop menu. Reboot and you should be able to SSH to the RPi again, using the new password.

This is not exactly true. Changing the password does not automatically enable ssh. If password is not changed you will get a 'nag' message on each boot, but if ssh is enabled then ssh will work with the default password: raspberry

ssh can be enabled by using the interfaces menu in either the GUI tool or by using sudo raspi-config
-OR- by putting an empty file named ssh in the boot folder.

[rickinpatel]

I think the image of the OS was corrupted due to some or the other reason.

I tried a lot of solution but none was working properly and at last i have to do the trick of replacing the BOOT section file with the fresh file from new image and yup it worked but what happened next was nasty the audio, wireless and bluetooth interface stopped working and it is worst I think while upgrade this files got corrupted lying in the other section and now i cant work with the wifi can anyone help me with that

[B.Goode]

now i cant work with the wifi can anyone help me with that

My suggestion:

Put your customised but apparently corrupted microSD card to one side for safe keeping.

On a new microSD card install a fresh clean copy of Raspbian, either by directly writing an image or by using the NOOBS Installer.

https://downloads.raspberrypi.org/raspb ... jessie.zip

Or

https://downloads.raspberrypi.org/NOOBS ... v2_1_0.zip

are the current versions at the time of writing.

Verify that the audio, WiFi and Bluetooth facilities that were 'broken' are now functional again.

Then reinstall opencv and other modules following your notes from the previous occasion when you did it successfully. Alternatively, by plugging a microSD USB dongle into your RPi it might be possible to mount the suspect microSD card and transfer across the modifications you apples to it.


The other possible approach is to use rpi-update (if that is what you used, although your post mentions something else) to revert the configuration of the allegedly corrupt OS back to the version that was working before you changed it.

[rickinpatel]

Thanks everyone for response I did add certain .bin files for hardware that were missing and now everythings working fine

[mfa298]

I had successfully enabled SSH and was working on to raspberry pi using remote desktop on windows. But after the firmware upgrade I dont know what happened and suddenly now its not working.

Unless trying out some bleeding edge feature or trying to fix some bug (probably with the aid of an engineer) there's generally no need for rpi-update now.

Normal apt-get update && apt-get upgrade will normally update you to the newest stable firmware / kernel as they're released.

[rickinpatel]

thanks everyone made it run by adding some files manually which were missing to run the hardware. There were .bin file related to wifi driver missing which had to be added