I used the NSU software to install my N95 firmware (21.xxx) and everything was fine.
I had some problems with my phone so I wanted to use the NSU to reinstall the firmware and reset the phone. When I opened NSU it told me there was an update available. I let it install the update and now the NSU software doesnt work.
It downloads the firmware, but when it attempts to flash the phone, I get a message that the nsl host process has crashed. I have tried numerous times, rebooted the computer, and tried ensuring that no other nokia software is running. None of these have any effect.
I didn't, but I did come up with a cunning solution!
I still had the previous installer for version 1.4.14 of the NSU software, so the only problem was that it kept doing this version check which made it want to download the new version of NSU.
So.. using Charles, an http proxy debugger, I captured the version check requests being sent by the software, and got Charles to rewrite them to downgrade the returned version number, fooling the NSU software into thinking it was still up to date Genius if I do say so myself.
The end result is that I can continue to use the old version until they fix whatever it is they broke!
Let me know if you'd like any more info on following this route, otherwise I hope you get sorted.
Hi, I'm having the same problem. I don't have the last version of NSU, but I have 1.3.95.
This connects using HTTPS, and Charles 3.2 seems to fail to decode this properly, causing NSU to return an error that it couldn't connect. This also seems to be the case with any HTTPS website - the proxy causes a certificate error.
The decode SSL checkbox is selected. If I disable the proxy, NSU works fine.
Any ideas? Do later versions of NSU not use https? Or does an older version of Charles work better?
Charles uses a man-in-the-middle approach with ssl traffic.
To get it to work, you need to add the certificate charles uses to your trusted root store.
Open your internet options (either through ie or control panel), go to the content tab, and click the certificates button. Click the Trusted Certification Authorities tab, and click import. Follow the prompts and the certiciate you need is in C:\Program Files\Charles\docs.
Once you add that, you should find the ssl stuff works ok!
I originally tried to rewrite the header interactively, but that didn't work (possibly a timeout in the request?). Using the "rewrite" tool to just replace the latest version number with the old one worked perfectly though.