Bricked IXUS 110 IS - page 2 - General Help and Assistance on using CHDK stable releases - CHDK Forum  

Bricked IXUS 110 IS

  • 22 Replies
  • 7145 Views
Re: Bricked IXUS 110 IS
« Reply #10 on: 17 / August / 2013, 13:33:12 »
Advertisements
In rec mode, camera is on for about a second (even lenses don't extend completely), there is CANON logo no the LCD, then LCD goes black and E32 is displayed for about 5 seconds. Then camera shuts down.


*

Offline srsa_4c

  • ******
  • 4426
Re: Bricked IXUS 110 IS
« Reply #11 on: 17 / August / 2013, 13:37:58 »
Actually, the old udumper might be able to dump the firmware.
Download Cardtricks 1.44 from this link, and prepare a card with the "NewDryOS" option. It requires a bootable card, it will dump the firmware without any visual activity (details in udumper.txt).
If it's unsuccessful, try the "DryOS" method.

In rec mode, camera is on for about a second (even lenses don't extend completely), there is CANON logo no the LCD, then LCD goes black and E32 is displayed for about 5 seconds. Then camera shuts down.
So, if it has to be CHDK, there's 5 seconds to make a dump.

*

Offline reyalp

  • ******
  • 13446
Re: Bricked IXUS 110 IS
« Reply #12 on: 17 / August / 2013, 16:11:09 »
I did a quick comparison of the stubs_entry.S files for 100b and 101f

The lowest change function address I found is
GetVRAMHPixelsSize 0xff8b58dc-> 0xff8b59cc

The highest unchanged is
IsStrobeChargeCompleted 0xff8a71a0

variable addresses are changed too:
canon_shoot_menu_active 0x000070bd -> 0x000070c1

Since the code size changed, the canon firmware initialized data segment (copied to 0x1900) would be all wrong when loading the wrong firmware:
FFB7DF64 -> FFB7E0D4

This would wreak all kinds of havoc, but it ought to croak pretty early.
Don't forget what the H stands for.

*

Offline lapser

  • *****
  • 1093
Re: Bricked IXUS 110 IS
« Reply #13 on: 17 / August / 2013, 22:03:29 »
I did a quick comparison of the stubs_entry.S files for 100b and 101f
I triggered my problem by booting the G1X_100g  SD card on my SX260_101a.  Can you predict what would happen from subs.entry.S?

The power button or play button had no visible effect with the G1X SD card in the SX260. I took the card out and still got no response. Taking the battery out and reinserting (without a SD card) then worked (printed SD card error message). Then the SX260 SD card worked.

I think this may have been what happened with my old SX260_100b. I remember the power button becoming unreliable for awhile, and then it stopped working complete (bricked camera) no matter what I did.
EOS-M3_120f / SX50_100b / SX260_101a / G1X_100g / D20_100b
https://www.youtube.com/user/DrLapser/videos


*

Offline reyalp

  • ******
  • 13446
Re: Bricked IXUS 110 IS
« Reply #14 on: 17 / August / 2013, 22:49:55 »
I triggered my problem by booting the G1X_100g  SD card on my SX260_101a.  Can you predict what would happen from subs.entry.S?
G1x and sx260 have different diskboot encodings, (7 and 8 respectively) so if the wrong diskboot is present, the canon firmware will load it, decode it with the wrong key, and attempt to execute the resulting garbage.

Since this all happens in the canon firmware, there is absolutely no way CHDK could prevent it.

Figuring out specifically what would happen would require duplicating the decode process and disassembling the resulting junk, but I'd expect it to hit an exception very quickly. If the exception handlers are also borked, it could end up in an infinite loop of exceptions. I would not expect this to be very dangerous, because it should fail very quickly. Poldy's scenario is potentially more dangerous, because it can run for a while and send wrong values to real functions.
Quote
The power button or play button had no visible effect with the G1X SD card in the SX260. I took the card out and still got no response. Taking the battery out and reinserting (without a SD card) then worked
This is what usually happens when you try to run a diskboot with the wrong encoding. The camera gets stuck in a state that requires the battery to be removed to reset. Collectively, CHDK developers have done this a LOT without any obvious permanent damage.
Quote
I remember the power button becoming unreliable for awhile, and then it stopped working complete (bricked camera) no matter what I did.
That sounds like a regular old hardware failure to me. It's hard to see how executing garbage code could cause a progressive failure like that.
Don't forget what the H stands for.

Re: Bricked IXUS 110 IS
« Reply #15 on: 17 / August / 2013, 23:35:18 »
Poldy's scenario is potentially more dangerous, because it can run for a while and send wrong values to real functions.
There have been many people who posted in the forum that, not knowing their correct firmware version,  or CHDK not being available for their exact version,  they simply tried all the firmware versions available for their camera.  Presumably many more people tried the same thing but did not post on the forum. 

Did this brick some cameras? Hard to say but you would think there would have been more complaints?
Ported :   A1200    SD940   G10    Powershot N    G16

*

Offline reyalp

  • ******
  • 13446
Re: Bricked IXUS 110 IS
« Reply #16 on: 18 / August / 2013, 00:56:29 »
There have been many people who posted in the forum that, not knowing their correct firmware version,  or CHDK not being available for their exact version,  they simply tried all the firmware versions available for their camera.  Presumably many more people tried the same thing but did not post on the forum. 

Did this brick some cameras? Hard to say but you would think there would have been more complaints?
I expect most people who tried an bricked their camera would complain somewhere, probably here or on the wiki.

I think the odds of this ending up just right to damage the camera are pretty low, but higher than if you try to execute an incorrectly decoded diskboot or a firmware that doesn't have remotely similar addresses. I don't have any opinion whether it happened in this case, but it's not completely implausible.

It might be worth digging through the ixus110 porting thread, and seeing if anyone else there reported trying the same combination. If someone did without bricking their camera, that would favor this being a coincidental failure.
Don't forget what the H stands for.

*

Offline lapser

  • *****
  • 1093
Re: Bricked IXUS 110 IS
« Reply #17 on: 18 / August / 2013, 02:12:55 »
That sounds like a regular old hardware failure to me. It's hard to see how executing garbage code could cause a progressive failure like that.
Yes, that's what I concluded at the time. I did open the battery door on that poor camera a few hundred times to get the card in and out for CHDK development. Now I use PTP.
There have been many people who posted in the forum that, not knowing their correct firmware version,  or CHDK not being available for their exact version,  they simply tried all the firmware versions available for their camera.
I plead guilty to doing that with the G1X, since there isn't a key sequence that shows the firmware version, and I was too lazy to figure out Card tricks. Did anyone figure out how to show the G1X firmware version page?

And I've crashed the camera many times and had to remove the battery while doing CHDK development, with no ill effects, but CHDK had started normally beforehand. When the power button doesn't work, though, it's not obvious what's going on.
EOS-M3_120f / SX50_100b / SX260_101a / G1X_100g / D20_100b
https://www.youtube.com/user/DrLapser/videos


*

Offline reyalp

  • ******
  • 13446
Re: Bricked IXUS 110 IS
« Reply #18 on: 29 / August / 2013, 22:14:24 »
Hi Poldy,

I'm not sure if you've given up on this or done something with the camera, but here's CHDK build for ixus110_sd960 that will attempt to save a romlog (camera error log) and a copy of ROM at startup. These could potentially help us figure out what happened to your camera.

I'm not sure if they will complete before the camera shuts down again, but it's worth a try. If it works at all, the romlog should at least get saved. The files saved on the card should be ROMLOG.LOG and ROMDUMP.BIN

The card will have to be made bootable and locked. You must have gone through the same process when you originally loaded the wrong firmware, so the card may still be set up correctly.

If you use this, you should hold the power button down so the CHDK will attempt to start in record mode.

edit:
In the original porting thread, I see that someone used a 101d build on a 101f camera without permanent damage: http://chdk.setepontos.com/index.php?topic=9133.msg95630#msg95630
I don't see any evidence of anyone trying 100b build on a later camera.
« Last Edit: 29 / August / 2013, 22:30:23 by reyalp »
Don't forget what the H stands for.

Re: Bricked IXUS 110 IS
« Reply #19 on: 07 / January / 2015, 08:24:43 »
I have gave up until yesterday, when I found camera tossed in some old box. That reminded me of this thread ind I found reyalp post.

I did what you said. At startup, there was for a second CHDK picture displayed. Romdump.bin was created, log file was empty.

http://www.filedropper.com/romdump

Thank you in advance.

 

Related Topics