I have 6 of these cameras, with a mix of a and b firmware. I have sync'd all of them from a usb cable and no issues so far.
I won't be able to find it now, but I seem to recall somebody saying that when he left his "bricked" camera overnight with the battery pulled, it started working the next morning. I'm assuming some sort of time for internal capacitors to discharge? Worth a shot.
I'd say two from the same user implies that the user is doing something different from other users. Not hardware but a bug in chdk ( install process ) or a misunderstanding of something by the user.
I think i recall cases where i had to remove the RTC clock battery of my other powershots because the canon settings somehow got corrupted and prevented a boot. It's been a while.. Unfortunately you have to take apart the Ixus 160 to do that. But its not too bad, only a couple of screws. The Battery is soldered in, but if you short out the two contacts briefly it resets everything. Worth a try. It wont brick the cameras any more than they already are. (Its possible i'm remembering wrong and this will do nothing)
Quote from: 62ndidiot on 06 / March / 2018, 16:01:37Have you actually checked the batteries are charged?I have batteries as well as AC adapters. There are three total cameras, two bricked. As a quick test, I booted the good camera and it came up and showed a full battery. If I install the known good battery into either of the two bricked cameras and attempt to power them on, nothing happens when pressing either the power or the play button.
Have you actually checked the batteries are charged?
Quote from: 62ndidiot on 06 / March / 2018, 00:17:56I'd say two from the same user implies that the user is doing something different from other users. Not hardware but a bug in chdk ( install process ) or a misunderstanding of something by the user.Right, I'd like to know where I might have gone wrong then. This is my first attempt at asking a digital camera to boot anything other than the manufacturers OS and I think I've followed the directions pretty closely. The only deviation so far is the fact that sticks has a now-acknowledged bug and won't write correctly to SD cards on Ubuntu 16.04, so I ended up using licks. When I examine the SD card contents, from what I can tell, they do appear to be correct. Maybe it's just bad luck. I'm now forced to decide on trying to obtain yet another elph 160, or if I bite the bullet and buy a couple dlsr's. The bookscanner software maker pi-scan recommends Nikon 1 J5 for the DSLR (as of this writing) interfaced via libgphoto rather than chdk. Two new Nikon 1 J5's will cost me around $1000, which is a definite ouch. Currently, I'm out $100 in used cameras.
Sorry @waterwingz but I'm not that smart. My next suggestion however is to gain access to the small battery that powers the clock and maintains other settings. I looked in my Elph 130 and it's not obvious. This battery may be dead or it may be maintaining corrupted settings.
But if it doesn't boot without an SD card or even with an unwritelocked non chdk card how will it help to try with the firmware update method?
There are three total cameras, two bricked.
Started by atkulp General Help and Assistance on using CHDK stable releases
Started by TheEditor Hello, I'm a NEWBIE - HELP!! (Newbies assistance, User Guides and thank you notes)
Started by geekmidou General Help and Assistance on using CHDK stable releases
Started by negnet « 1 2 » General Help and Assistance on using CHDK stable releases
Started by Sdack Hotwire! Hardware Mods, Accessories and Insights
