Reading mode: Light Dark

The firmware 1.10 killed my nx100

Go to last post
I did my most recent EX1 update on my normal 16GB card and it updated without incident. However, it appears not to have fixed all the stability issues. The camera froze yesterday when I switched the flash from "Auto" (which it had been set at during the update a few days ago) to fill flash. None of the buttons worked after that. Pulling the battery reset things, but this is still a slightly disconcerting occurrence.
brianj said:
Here's another possible clue, or it may be irrelevant, I use a standard 1gb SD card to do my EX1 upgrades, not a SDHC card as I normally use for image storage, and have never had a problem.

Brian
Click to expand...
 
phototransformations said:
I did my most recent EX1 update on my normal 16GB card and it updated without incident. However, it appears not to have fixed all the stability issues. The camera froze yesterday when I switched the flash from "Auto" (which it had been set at during the update a few days ago) to fill flash. None of the buttons worked after that. Pulling the battery reset things, but this is still a slightly disconcerting occurrence.
brianj said:
Here's another possible clue, or it may be irrelevant, I use a standard 1gb SD card to do my EX1 upgrades, not a SDHC card as I normally use for image storage, and have never had a problem.
Click to expand...
Click to expand...
Interesting, I can only add that once I have upgraded I go through and make all my required settings, and for flash I open the flash and set it to ON, then close it again. This makes the fill flash feature available simply by opening the flash when required.

Brian
 
Yes, that's what I usually do, too. I just forgot to reset the flash after the update.
 
It comes with 1.02 FW version (the first one had 1.01)
I'm afraid of trying upgrade to 1.10 one more time...
 
EugeneL83 said:
It comes with 1.02 FW version (the first one had 1.01)
I'm afraid of trying upgrade to 1.10 one more time...
Click to expand...
EugeneL83 said:
[Previous] - P.S. Battery was charged to 100%, SD was formatted. There were nx100.bin and lens.bin only.
Click to expand...
Eugene

Sorry if somebody may have already said this - I've not really read the entire thread... but .. aren't you only supposed to have ONE bin file on the card.. not both. You DO have to do the body and lens updates quite seperately... and I do think that having BOTH bin files on a card at same time COULD cause a problem. Has this been mentioned at all ??

--
eric-UK
Staffordshire
 
ericN2 said:
EugeneL83 said:
It comes with 1.02 FW version (the first one had 1.01)
I'm afraid of trying upgrade to 1.10 one more time...
Click to expand...
ericN2 said:
[Previous] - P.S. Battery was charged to 100%, SD was formatted. There were nx100.bin and lens.bin only.
Click to expand...
Eugene

Sorry if somebody may have already said this - I've not really read the entire thread... but .. aren't you only supposed to have ONE bin file on the card.. not both. You DO have to do the body and lens updates quite seperately... and I do think that having BOTH bin files on a card at same time COULD cause a problem. Has this been mentioned at all ??

--
eric-UK
Staffordshire
Click to expand...
It has nothing to do with it. When I tried to upgrade my fw I already saw this thread and was very careful. I formated a 4gb sandisk card in camera, charged the battery, and put only ONE file (camera.bin) on the card.

After all these precautions i was confident that nothing can go wrong (I did countless fw updates on dozens of cameras) but it seems that I was wrong about that. The camera got bricked and I am waiting the replacement and in the meantime I bought another nx100 :)

Very nice camera, I really like it, it is a shame that things like this happen so often.
--
Click Profile for Equipment
 
slyves said:
It has nothing to do with it. When I tried to upgrade my fw I already saw this thread and was very careful. I formated a 4gb sandisk card in camera, charged the battery, and put only ONE file (camera.bin) on the card.
Click to expand...
Only using one file (camera.bin), I have always put all the files contained in the downloaded zip into the root directory of the SD card.

Can anyone clarify what is required with this?

Brian
 
Has samsung told anyone who's camera died after update why it happened. And if it is the update have they put a fix in so it does not happen .

Updated mine when I first got it a month ago with no problem both camera and lens on same card at same time.

--
Keep on Shooting!!!!
Jeff
 
brianj said:
slyves said:
It has nothing to do with it. When I tried to upgrade my fw I already saw this thread and was very careful. I formated a 4gb sandisk card in camera, charged the battery, and put only ONE file (camera.bin) on the card.
Click to expand...
Only using one file (camera.bin), I have always put all the files contained in the downloaded zip into the root directory of the SD card.

Can anyone clarify what is required with this?

Brian
Click to expand...
Brian -

Maybe you've already seen this but I just don't see any better reference as to exactly what is to be done...
The list of various Firmware updates -

http://www.samsung.com/uk/support/detail/supportPrdDetail.do?menu=SP01&prd_ia_cd=2701&prd_mdl_cd=EV-NX10ZZBABFR&prd_mdl_name=NX10&srchword=NX10

.. and the PDF for the latest v1.30 for the NX10 ..
http://dl.dropbox.com/u/2591259/NX10-FirmwareUpgradeGuidev1.30.pdf

--
eric-UK
Staffordshire
 
jeffsvisions said:
Has samsung told anyone who's camera died after update why it happened. And if it is the update have they put a fix in so it does not happen .

Updated mine when I first got it a month ago with no problem both camera and lens on same card at same time.

--
Keep on Shooting!!!!
Jeff
Click to expand...
Which further confirms what I have to really believe... after knowing of more than one who have done the Firmware updates with no trouble at all.. it must surely be user error..for whatever odd reason, but it just cannot be either the FW itself nor the camera in general.. it woud just be more general to lots more users if it was either the FW or the camera.
People are NOT infallible..no explanation , but it does happen...

--
eric-UK
Staffordshire
 
There doesn't seem to be much room for user error in a firmware update procedure as long as you have a charged battery, good card, and don't fiddle with the buttons or turn the camera off. There are lots of errors that occur in hardware and software but only to a few people. Perhaps there was a defective batch of cameras incompatible wtih a particular version of the firmware. Perhaps some camera setting triggers this problem, or some random glitch in the existing firmware causes it, but only when the camera is in a particular state (such as the glitches that still cause the EX1 to freeze from time to time).

Without any word from Samsung, it's not possible to know why, but in the cases I've read about recently with Samsung cameras, the users seem to have done nothing wrong.
ericN2 said:
Which further confirms what I have to really believe... after knowing of more than one who have done the Firmware updates with no trouble at all.. it must surely be user error..for whatever odd reason, but it just cannot be either the FW itself nor the camera in general.. it woud just be more general to lots more users if it was either the FW or the camera.
People are NOT infallible..no explanation , but it does happen...

--
eric-UK
Staffordshire
Click to expand...
 
phototransformations said:
There doesn't seem to be much room for user error in a firmware update procedure as long as you have a charged battery, good card, and don't fiddle with the buttons or turn the camera off. There are lots of errors that occur in hardware and software but only to a few people. Perhaps there was a defective batch of cameras incompatible wtih a particular version of the firmware. Perhaps some camera setting triggers this problem, or some random glitch in the existing firmware causes it, but only when the camera is in a particular state (such as the glitches that still cause the EX1 to freeze from time to time).

Without any word from Samsung, it's not possible to know why, but in the cases I've read about recently with Samsung cameras, the users seem to have done nothing wrong.
ericN2 said:
Which further confirms what I have to really believe... after knowing of more than one who have done the Firmware updates with no trouble at all.. it must surely be user error..for whatever odd reason, but it just cannot be either the FW itself nor the camera in general.. it woud just be more general to lots more users if it was either the FW or the camera.
People are NOT infallible..no explanation , but it does happen...
Click to expand...
Click to expand...
Yes - and of course what you say here raises yet again the possibility of a different sort of "user error" although strictly speaking it may well not truly be that..but suppose SOME owners have had a bad d/load of the Firmware..it's theoretically not totally possible because Samsung DO mention the actual size and details of the FW concerned.. but to be honest, I'm not sure if I have always checked accurately any FW d/load..maybe just believed it to be OK..but if a d/load WAS incorrect for some reason..could be THAT has been the culprit.

I'm not really sure that it's entirely fair to quibble about Samsung never saying anything about this.. how can they, really, when it IS the case that the USER has to take full responsibility , and no way can Samsung account for every persons actions.

I think this simply has no answer..it's pure conjecture to try to explain anything.. it has happened, and I'm sorry for those who have suffered..

--
eric-UK
Staffordshire
 
On the cameras that are having a problem . Have you owned your camera for a while? Mine I remember seeing on the box or when I registered it that the build date was Feb 2011. could it be that the older models are having the problem. And the newer have been fixed. Or could it be the speed of the card or manufacture. My card was new a Nikura 16GB SDHC Ultra High Speed Premium Class 6 Memory Card .
Camera nx 100

--
Keep on Shooting!!!!
Jeff
 
Please tell me what I did wrong?

I used a sandisk 4gb card. The battery was full. I copied one single file (camera.bin) in the cards root directory. Results ... the camera got bricked.

Bought a second nx100 after two days (still waiting for the refund or exchange for the first one) and did EXACTLY the same steps, using the SAME card and copying the SAME file (left it on my desktop). Surprise ... it worked as it should.

So .. where is the user error ?!

--
Click Profile for Equipment
 
Not sure why you are hunting for an explanation that blames the user. Some of the users who have encountered this problem have been EX1 users, and the EX1 firmware updates are in ZIP files, which have internal checksums to ensure that the firmware is not corrupted as you are guessing might have been the case with some of the people who have had this problem. Besides, good practice on Samsung's part would be to have the camera check the firmware against a checksum or CRC value stored in the firmware update itself to be sure that it is intact before attempting to apply it to the camera.

It's annoying when software developers and hardware manufacturers blame the user for engineering or programming defects. But I'm surprised to find another user blaming the user.
 
It seems exceedingly unlikely that this is your error.
 
You must log in or register to reply here.

Keyboard shortcuts

f
Forum
m
My threads
Mobile site
About
Editorial content
Cameras & Lenses
Community
All content, design, and layout are Copyright © 1998–2025 Digital Photography Review All Rights Reserved.
Reproduction in whole or part in any form or medium without specific written permission is prohibited.
When you use DPReview links to buy products, the site may earn a commission.
©GPS Media - Guides, Products, Services.
Back
Top