Comment on FirmwareHackInstallation in 400plus

[400...@googlecode.com]

Comment by OHo...@gmail.com:

To edit the first sector of the CF-card in FreeBSD use editors/hexedit:

dd if=$dev of=/tmp/eosBlock1 count=1
hexedit /tmp/eosBlock1
dd if=/tmp/eosBlock1 of=$dev count=1

Note:
EOS_DEVELOP starts on 0x47, the numbers are: 45 4F 53 5F 44 45 56 45 4C
4F 50.
BOOTDISK starts on 0x5C, the numbers are: 42 4F 4F 54 44 49 53 4B
Press F2 to save, F10 to quit.

For more information:
http://code.google.com/p/400plus/wiki/FirmwareHackInstallation

[400...@googlecode.com]

Comment by OHo...@gmail.com:

To edit the first sector of the CF-card in FreeBSD use editors/hexedit:<br
/>

dd if=$dev of=/tmp/eosBlock1 count=1<br />
hexedit /tmp/eosBlock1<br />
dd if=/tmp/eosBlock1 of=$dev count=1<br />

Note:<br />

EOS_DEVELOP starts on 0x47, the numbers are: 45 4F 53 5F 44 45 56 45 4C 4F

50.<br />
BOOTDISK starts on 0x5C, the numbers are: 42 4F 4F 54 44 49 53 4B.<br />

[400...@googlecode.com]

Comment by OHo...@gmail.com:

To edit the first sector of the CF-card in FreeBSD use editors/hexedit:`<br
/>`

dd if=$dev of=/tmp/eosBlock1 count=1`<br />`
hexedit /tmp/eosBlock1`<br />`
dd if=/tmp/eosBlock1 of=$dev count=1`<br />`

Note:`<br />`
EOS_DEVELOP starts on 0x47, the numbers are: 45 4F 53 5F 44 45 56 45 4C 4F
50.`<br />`
BOOTDISK starts on 0x5C, the numbers are: 42 4F 4F 54 44 49 53 4B.`<br />`

Press F2 to save, F10 to quit.`<br />`

[400...@googlecode.com]

Comment by OHo...@gmail.com:

To edit the first sector of the CF-card in FreeBSD use editors/hexedit:

{{{

dd if=$dev of=/tmp/eosBlock1 count=1
hexedit /tmp/eosBlock1
dd if=/tmp/eosBlock1 of=$dev count=1
}}}

Note:

EOS_DEVELOP starts on 0x47, the numbers are: 45 4F 53 5F 44 45 56 45 4C 4F
50.

BOOTDISK starts on 0x5C, the numbers are: 42 4F 4F 54 44 49 53 4B.

Press F2 to save, F10 to quit.

For more information:
http://code.google.com/p/400plus/wiki/FirmwareHackInstallation

[400...@googlecode.com]

Comment by fired...@gmail.com:

why not using the linux method and write directly to the CF card ? instead
of dumping it, editing and putting it back ?

[400...@googlecode.com]

Comment by OHo...@gmail.com:

FreeBSD won't let you seek into the middle of a block ("Invalid argument")

[400...@googlecode.com]

Comment by fired...@gmail.com:

i've edited the howto, please confirm if it works on FBSD.

[400...@googlecode.com]

Comment by stian...@gmail.com:

Hi, I cant get the hack to work. I've installed the latest firmvare 1.1.1.
But from there I don't know where things go wrong.
Then I try to instal the testfir.fir, screen goes blank, I wait for a while
(up to 20 min), then turn it of and remove battery.
Formate the card.
When using the MacBoot, I've to press the make dslr-bootable right? then
press Prepare card.
Then i´ve copied the autoexec.bin, just the bin file, over to the root of
the CF card.
But nothing happends.

I'm running Mac OS 1.7.1 Lion.

Do i have to write the code from "direct method"?

Thanks

[400...@googlecode.com]

Comment by stian...@gmail.com:

I've downloaded the 400plus-20110905-r802.zip.

[400...@googlecode.com]

Comment by scri...@gmail.com:

Macboot don't works with lion.

Try this script instead (is from Magic Lantern but should work, if not just
reformat the card):
https://groups.google.com/d/msg/ml-devel/zLDokl74ATU/ks4X8YU68fIJ

[400...@googlecode.com]

Comment by jesusar...@gmail.com:

Hi there, how can I remove the 400plus and reset all the original firmware
to my 400d? It's just installing the original canon firmware? I don't see
this procedure explained here or in the User'sGuide section, and I think
it's important if you just want to try the thing ;)
Thanks

[400...@googlecode.com]

Comment by jesusar...@gmail.com:

Aha, I think now I got the point: the hack is loaded from the card, it
doesn't modify the firmware inside of the camera. Just formatting the card
will delete the hack.

[400...@googlecode.com]

Comment by OHo...@gmail.com:

If it works for all linuxes I would recommend reinstating the old method,
it looked a lot cleaner. Note that FreeBSD is NOT linux.

The method you present now does not work on FreeBSD, everything after the
echo'd text is removed, i.e. count is not respected.

[400...@googlecode.com]

Comment by quar...@gmail.com:

Formatting the card with EOSCard works under Windows 7 also, all you need
is to right click EOSCard.exe, click Compatibility tab and check "Run this
program as administrator" and "Run this program in compatibility mode for
Windows XP(Service Pack 3)".

[400...@googlecode.com]

Comment by fired...@gmail.com:

OHo...@gmail.com, yeah i'm aware FBSD is not linux ... but still uses GNU
tools, unfortunately not the versions I would like to... perhaps in the
ports there is some "future-full" dd version ? anyway, your first comment
should help the FBSD guys... and after all the FBSD and Linux ppl, should
have some basic idea...

[400...@googlecode.com]

Comment by fired...@gmail.com:

OHo...@gmail.com, yeah i'm aware FBSD is not linux ... but still uses GNU
tools, unfortunately not the versions I would like to... perhaps in the

ports there is some "future-full" dd version ? or the problem was the block
mechanism of the FBSD kernel (IIRC i was reading some forums about that
earlier) ?

anyway, your first comment should help the FBSD guys... and after all the

FBSD ppl (and most of the Linux ppl), should have some basic idea of these
stuff ?

[400...@googlecode.com]

Comment by cshaff...@gmail.com:

Forgive my ignorance, but when I'm using MacBoot (on OS 10.6.8) to prepare
the card, do I select 'Make CHDK-bootable' , "Make DSLR-bootable, or "Make
scriptable"? I've yet get this working on my camera...

Also, I've been preparing the camera, then preparing the card, as per the
order of instructions as listed, but should I be doing that the other way
around? Any help is much appreciated. Thanks!

[400...@googlecode.com]

Comment by fired...@gmail.com:

Hi, I'm not familiar with MacBoot, but i guess it should be "Make
DSLR-bootable"
Prepare the camera first, you will need the CF card to flash the
testfir.fir firmware first.
Then prepare the card for the hack.
I guess if you do it the other way, it wont matter though.

[400...@googlecode.com]

Comment by grebrofi...@web.de:

Hi, since I have the 400plus firmware on my 400D it behaves very strange:

The USB (PTP) connection to the computer doesn't work anymore.

The Camera is detected by the OS as a USB device (Mac OS 10.5, Mac OS 10.6
system profiler, Linux Ubuntu lsusb) but the camera itself does not react
to the connection at all. After noticing this misbehaviour I decided
to 'update' the firmware again with the original canon v1.1.1. - without
success:
There is still this beeping sound at camera startup as well as the 'Factory
Menu' item in the 1st menu page – and no USB functionality!

Has anyone else this problem? What to do? I need help here. Thank you!

[400...@googlecode.com]

Comment by eduardo....@gmail.com:

@grebrofilipp:

Go to the "Developers menu", select "Exit Factory Mode", and no not come
back to this menu ever again.

[400...@googlecode.com]

Comment by grebrofi...@web.de:

@ eduardo.p:

Thank you very much!
Everything's working again.

Sorry, I must have overlooked this when playing around. I thought I bricked
it some way. Again thanks.

[400...@googlecode.com]

Comment by wni...@gmail.com:

After spending almost 2 days on finding and applying all sorts of info on
this, I must say that I never got it to work using Lion 10.7.2. When
booting back into a Snow Leopard system and using MacBoot as well as the
latest autoexec.bin, it worked instantly! Thought, I'd mention it to save
others from wasting so much time on a no-go.

[400...@googlecode.com]

Comment by joels...@gmail.com:

I would recommend adding a couple items:

- when adding testfir.fir: You will see very little confirmation that this
step worked, just wait 2-3 minutes, turn off the camera, and remove the
battery .
- For MacBoot: Select the "Make DSLR Bootable" radio button and the click
the "Prepare Card" button.

This hack looks great - I like the choice to have the hack run from the
card.

[400...@googlecode.com]

Comment by michaelo...@gmail.com:

OK..... I tried to get the installation 3 times and can't get it to work.
This is what I'm doing:

1) My camera has 1.1.1 installed.
2) I deleted everything from my cf card.
3) I downloaded test.fir file and copied it to my cf card.
4) Installed cf card and turned camera on. Ran firmware update from
camera menu. (red cf light flashed a few times, waited 2 minutes, turned
off camera, removed battery, replaced battery, turned on camera.
5) turned off camera, removed cf card, deleted all files, formatted and
copyed autoexec.bat file.
6) reinstalled cf card, camera dose not seem to have new firmware. still
seeing 1800 as max ISO.

Am I missing something or doing something wrong? Please help.

[400...@googlecode.com]

Comment by fired...@gmail.com:

read "Preparing each card" from this wiki page.

[400...@googlecode.com]

Comment by ngan1...@gmail.com:

Bro, i reckon you should follow here (Step 6) and get your card formatted
with cardtricks 1.45 before copying the autoexec.bin in your card, this
will allow your CF card to boot upon starting your 400D.

http://chdk.setepontos.com/index.php?topic=3290.0

Follow this step closely :-
6. download cardtricks 1.45 :
http://chdk.setepontos.com/index.php/topic,4214.0.html (first download
link). Run it to self extract the archive. Run the binary extracted, choose
CF drive, tick "cf boot sector" and then click "make bootable.

[400...@googlecode.com]

Comment by aech...@gmail.com:

If you're having problems with MacBoot on Lion, but - like me - you know
almost nothing about using the Terminal, benefit from my half-hour of
guess-and-checking:

Put the CF card in the card reader, then open Disk Utility and unmount the
EOS_DIGITAL (or whatever) image. Open terminal and type in "diskutil list"
(without quotes). Find the first partition of your CF card and note the
identifier, which will be something like "disk4s1". Then type in the code
in step 6 above, substituting "sdX1" for your CF card's identifier,
e.g. "dev=/dev/disk4s1" without quotes.

[400...@googlecode.com]

Comment by edwardwi...@gmail.com:

Just to confirm quar...@gmail.com's comment from Oct 12, 2011 - Using the
Windows 7 compatibility mode to run as Windows XP worked for me too

[400...@googlecode.com]

Comment by jeo...@gmail.com:

I have installed the 20111111 version on my CF-card and the blue LED
indicates that everything is all right when I turn the camera on. But when
I press the DISP. button (can't find any DP on my camera) the screen turns
black and wouldn't return until I press it again. So I can't see any
400plus menu. I have used Win7 to prepare my card.
What is wrong!

[Kamaris Gavriil]

Hello,
DP stands for "Direct Print" so the DP button is the one with the Blue Light. Press the button and use the jog dial or the zoom in out buttons to navigate :-)
It is tricky because DISP. button is right next to it and DP looks like DISP.
Note that i also use win7 and everything seems OK..not even admin rights for executing the pelican format tool.

regards
Gavriil

[400...@googlecode.com]

Comment by fired...@gmail.com:

This comment is not related to this wiki article. Please use the issue
system when you have problems.
The DP (Direct Print) button is the one with the Blue LED.

[400...@googlecode.com]

Comment by jeo...@gmail.com:

Sorry fired...@gmail.com. I though it was related. Anyhow, your answer
solved my problem. The issue was me. Thank you!

[400...@googlecode.com]

Comment by jeo...@gmail.com:

Sorry fired...@gmail.com. I thought it was related. Anyhow, your answer

[400...@googlecode.com]

Comment by michaele...@gmail.com:

I am confused, there are two file in the d/l page as follows:

400plus-20111111-3.src.zip

400plus-20111111-3.bin.zip

Do we need both of these or just one, as they each contain different
objects. and if both what directory structure do we need to set up on the
CF card?

[400...@googlecode.com]

Comment by michaele...@gmail.com:

I have done this about a dozen times now and it does not work!

1. Downloaded testfir.fir
2. Downloaded autoexec.bin

3. Updated Canon XTi Firmware with version 1.1.1
4. formated 4gig CF Card both in Camera and with EOSCard Utility
5. Transfered testfir.fir to CF Card, installed in Camera, Ran update
Firmwear, Screen went blank, waited more than two minutes, turned off
camera, unloaded and reloaded battery.
5. Transfered Autoexec.bin to CF Card, installed into camera and turned
camera on, no blue light flash, and nothing different about camera
operation.

I did this several time with no difference.

I do not believe that testfir.fir is working, or it is corrupt. Help Please.

[400...@googlecode.com]

Comment by eduardo....@gmail.com:

1 - As I already commented on the UserGuide page, the difference between
sources and binaries is explained in the Downloads page; please, read it.

2 - As has already been explained here, you need to prepare each card;
please read the "Preparing each card" section in this page.

[400...@googlecode.com]

Comment by michaele...@gmail.com:

Okay Eduardo

I downloaded testfir.fir again, and checked the hash code SHA1, with
Checksum Utility Version 1.1.
The hash code's do not match, so either the hash code posted at the
download site is wrong or the file is corrupt.
Which is probably why when I go to update the firmware with this file the
following happens:

update firmware 1.1.1, press okay, the screen flashes to "Loading" and then
goes blank. I never get the chance to see the screen that says Update
with "testfir.fir"

When I undate the Firmware with the Canon Firmware update the following
happens:

Update Firmware 1.1.1 press okay

Camera Loads the Update and screen says:

Update with "Firmware 1.1.1" Press yes again, and Camera update's the
Firmware.

As this does not happen with the "testfir.fir" update that I downloaded
from the link at 400Plus, and the checksums do not match I think that
something is wrong with your file?

You can email me directly at:

michae...@gmail.com

Thank You

[400...@googlecode.com]

Comment by michaele...@gmail.com:

Okay, I ran the checksum program on the testfir zip folder and they
matched, my bad.

still not working?

[400...@googlecode.com]

Comment by eduardo....@gmail.com:

@Michael: Could you please read the "Preparing each card" section and
follow all the steps outlined there? You have just prepared your camera,
now you need to prepare your card, or it will not work.

[400...@googlecode.com]

Comment by michaele...@gmail.com:

AS A MATTER OF FACT = READ BELOW

1st step, Format CF Card with EOS Utility Version 1.1

2nd step, Transfer testfir.fir to CF Card.

3rd step, Insert CF Card into camera, and turn camera on. It will update
automatically, I did leave the camera on for about three minutes before
turning off camera, and then removing battery.

4th step, Remove CF Card from camera and insert it into card reader, and
then into computer. Delete testfir.fir from CF Card,

5th step, Transfer AUTOEXEC.BIN to CF Card, then insert CF Card into
camera, turn on camera, blue light will flash, and it works then.

Now I am figuring out what all it will do. Learning curve. So far it is a
really neat program. I just have to figure out how to use it. i am mostly
interested in the EAB and Interval programs, though if it will really give
me ISO's like 25 and or 50 that would be really neat. I used to use a fuji
print film with an ISO of 25 and the colour saturation was fantistic.

Thanks Edwardo

[400...@googlecode.com]

Comment by corce...@gmail.com:

it was easy with Windows7. You must run Pelican as admin.

[400...@googlecode.com]

Comment by mikdun...@gmail.com:

Also easy with Windows 7.
Regarding "Windows: use EOScard by pelican, you need to check EOS_DEVELOP
and BOOTDISK like shown here.
[NOTE: Some Win7 users reported that no method was working for them;
install VirtualBox with Linux LiveCD running on it, and use the Linux
method, after attaching the card reader to the VM]"

I initially had a write failiure. Just had to set my Comodo Firewall
Defense+ and Sandbox security levels to disabled temporarily.

[400...@googlecode.com]

Comment by brko...@gmail.com:

Anybody, please is it possible to port this hacked firmware to canon EOS
450D? It would be so great....

[400...@googlecode.com]

Comment by chriss...@gmail.com:

What's wrong? I did everything like its written in the guide - but the blue
light lights the whole time and the operation of the camera is the same,
except a cant shoot pictures and i cant open the menu.... HELP!!!!

[400...@googlecode.com]

Comment by bruce.ci...@gmail.com:

I read through so many steps, procedures, and issues until I pulled my hair
out over this...and I don't know why! For anyone coming across this
installation, via Windows 7, who is still a little confused, read on:

It is easiest to "prepare card" first.

Step 1 - Format your CF

Step 2 - Download EOScard by Pelican by clicking the link under step one
of "Preparing each card" (save to Desktop for easy access)

Step 3 - Attach CF card to card reader...then to the PC

Step 4 - Right Click the the EOSCard icon that is now on the desktop. "Run
as Administrator"

Step 5 - As said under "Preparing each card", check the boxes next
to "EOS_DEVELOP" and "BOOTDISK". Click "Save".


The CF card is now ready to boot: Prepare camera:

Step 1 - After running the card through EOScard, copy testfir.fir onto the
CF.

Step 2 - Install the CF card into camera. (When you power the camera up,
it will automatically update and your screen will be blank - leave it for
at least 2 mins)

Step 3 - Power off camera and remove battery and replace
NOTE: After installing the firmware, my body would not power up. I simply
removed the battery pack a second time. That solved the problem.

Step 4 - Open the CF card via card reader and delete the testfir.fir file

Step 5 - Copy the autoexec.bin file to the root of the card

Step 6 - With card in the body, power up!

[400...@googlecode.com]

Comment by BigO...@gmail.com:

Success! However, the version of EOSCard I downloaded did not create a
bootable CF, even when I checked "Make Bootable." The SOLUTION--I used
CardTricks144.exe [which was what was recommended for the 350D hack I
accomplished on my XT] and simply hit the "make bootable" button.
Thanks for a very useful set of additional features.

OS--Win XP SP3

[400...@googlecode.com]

Comment by chance.g...@gmail.com:

I have a quick question. I am currently using the CHDK software, and I
wanted know if switching to this would cause any problems, since I think I
had to do a firmware hack for CHDK as well?

[400...@googlecode.com]

Comment by eduardo....@gmail.com:

400plus is for the 400D only, it will not work in any other camera, and
CHDK does not work on the 400D; so, if you are currently using CHDK, you
own a camera not supported by 400plus.

[400...@googlecode.com]

Comment by fh...@gmx.net:

I've had a problem with 400plus resetting itself everytime the camera was
turned off and on again. All settings, preferences, parameters were lost
each time on reboot. This was with an old Toshiba 512 MB CF card formatted
with FAT as reported by EOSCard. After using an 8 GB Intenso card with
FAT32, it is working now. Can anybody reproduce this problem? I don't need
a fix anymore, but it might help someone else.

[400...@googlecode.com]

Comment by eduardo....@gmail.com:

All can think is that you had saved a "preset", and 400plus was reloading
it each time the camera was turned on; I have never heard of anyone having
that issue before...

[400...@googlecode.com]

Comment by fh...@gmx.net:

I did try to save a preset, but it would reset on reboot. It was as if
400plus couldn't write to the card for some reason. Maybe the card was
faulty.

[400...@googlecode.com]

Comment by goo...@sysdef.de:

Preparing the Camera

3. Empty your CF, download the archive 400plus-testfir-1.bin.zip, unpack it
and copy the file testfir.fir into the root of your CF with the card reader.

[400...@googlecode.com]

Comment by martinsc...@gmail.com:

I've got the same problem with 400plus cannot save anything with my pq1 4GB
CF-Card (like this one here, but 4GB
http://www.geeks.com/details.asp?invtid=PQI-CF-2048-100). With another CF
card it works perfect…

[400...@googlecode.com]

Comment by 12...@budehaven.cornwall.sch.uk:

Help. I have updated my 400D successfully to 1.1.1. I then try to prepare
the 400D for the CF card. I rin the updater and the screen goes blank. I
wait for 3 minuets then I turn the power off (but the green light stays on)
then replace the battery. Then I put the bin file on to the CF card, put it
in the camera and nothing new happens. The blue light does not flash, and
the firmware still says 1.1.1.
It could be my card reader. I a getting a new one soon, so I will try that.
I am doing something else wrong?

[400...@googlecode.com]

Comment by backe...@gmail.com:

I have the same problem like in coment 20 oct 2012. I waited for more than
20 mintutes but after turning off camera the green light stayed on. Is it
normal? After 10 mintutes replaced the battery and followed the
instructions without success. Should I try it again from the beginning? Is
it possible?

[400...@googlecode.com]

Comment by bwieseon...@gmail.com:

I had a confusing issue with the "Preparing each card" section for 2
reasons.

Issue 1: User reading error:
"This step depends on your OS and CF Card, but first insert CF into the
camera and format it.
[NOTE: You can format it on the PC too]"

Which I slightly misread to mean this step was only about formatting the
card and the instructions for each OS below were simply "how to format for
each OS on your PC" per '[NOTE: You can format it on the PC too]'. Would
suggest adding after '...format it.' "Then follow the steps below for your
OS to prepare the CF card for 400Dplus."

Issue 2: Possible Windows PC error on running EOScard.exe to prepare CF card

* On Windows XP Pro ver 2002 SP3, right-click on EOScard.exe select "Run
as..", Run - Current user (or select user) "user" (an administrative
account) and UN-checked "Protect my computer and data from unauthorized
program activity" - OK.
* EOScard 1.32 opened and identified "I: EOS_DIGITAL [FAT32] 4GB" Sandisk
CF card.
* Checked EOS_DEVELOP and BOOTDISK (CHDK and ML boxes turned _grey_ and
depressed) checkboxes, Content section says "DCIM folder: ok" and all
others marked "-", clicked Save button.
* Get pop-up error window "EOScard 1.32" with image of red circle with
white X inside and "ZIP format." Clicked OK button.
* !!?? Looks like this step failed? - could not find this "ZIP format"
error documented.

* On Windows 7 Pro SP1, right-click on EOScard.exe select "Run as
administrator", OK on UAC (user account control) popup.
* EOScard 1.32 opened and identified "G: EOS_DIGITAL [FAT32] 4GB" Sandisk
CF card,Content section says "DCIM folder: ok" and all others marked "-",
Drive: 1, Ready. FAT32 VBR loaded.
* Checked EOS_DEVELOP and BOOTDISK (turns CHDK and ML boxes _colorful_ with
blue backround and depressed shadows) checkboxes, clicked Save button.
* Magic Lantern section reports "Unified stable release v2.3 --no
install.fir--, "ML succesfully installed". Drive: 1, Ready. Write
successful.
* CF card now has folders "DCIM" and "ML" with magiclantern content,
autoexec.bin, INSTALL.pdf and UserGuide.pdf (should note these files can be
deleted)

* Copied "400plus-20120415-14\bin\AUTOEXEC.BIN" file (not nightly build
400plus-20121123-r1514\AUTOEXEC.BIN) to CF card along with "languages.ini"
- replacing existing "AUTOEXEC.BIN" OF SIZE 1.59MB (from ML) with 60.4KB
version (400Dplus).
* Ejected CF card from computer and inserted into camera
* Power on camera and "Direct Print (DP) blue light" blinks on, steady on,
then off. In shooting mode pressing "DP" button brings up 400Dplus menu

[400...@googlecode.com]

Comment by bwieseon...@gmail.com:

I had a confusing issue with the "Preparing each card" section for 2
reasons.

# Issue 1 : User reading error: "This step depends on your OS and CF Card,

but first insert CF into the camera and format it. [NOTE: You can format it
on the PC too]"

* Which I slightly misread to mean this step was only about formatting the

card and the instructions for each OS below were simply "how to format for
each OS on your PC" per '[NOTE: You can format it on the PC too]'. Would
suggest adding after '...format it.' "Then follow the steps below for your
OS to prepare the CF card for 400Dplus."

# Issue 2 : Possible Windows PC error on running EOScard.exe to prepare CF

card

* On Windows XP Pro ver 2002 SP3, right-click on EOScard.exe select "Run
as..", Run - Current user (or select user) "user" (an administrative
account) and UN-checked "Protect my computer and data from unauthorized
program activity" - OK.

* EOScard 1.32 opened and identified "I: EOS_DIGITAL FAT32? 4GB" Sandisk
CF card.
* Checked EOS_DEVELOP and BOOTDISK (CHDK and ML boxes turned grey and

depressed) checkboxes, Content section says "DCIM folder: ok" and all
others marked "-", clicked Save button.
* Get pop-up error window "EOScard 1.32" with image of red circle with
white X inside and "ZIP format." Clicked OK button.
* !!?? Looks like this step failed? - could not find this "ZIP format"
error documented.

* On Windows 7 Pro SP1, right-click on EOScard.exe select "Run as
administrator", OK on UAC (user account control) popup.

* EOScard 1.32 opened and identified "G: EOS_DIGITAL FAT32? 4GB" Sandisk

CF card,Content section says "DCIM folder: ok" and all others marked "-",
Drive: 1, Ready. FAT32 VBR loaded.

* Checked EOS_DEVELOP and BOOTDISK (turns CHDK and ML boxes colorful with

blue backround and depressed shadows) checkboxes, clicked Save button.
* Magic Lantern section reports "Unified stable release v2.3 --no
install.fir--, "ML succesfully installed". Drive: 1, Ready. Write
successful.
* CF card now has folders "DCIM" and "ML" with magiclantern content,
autoexec.bin, INSTALL.pdf and UserGuide.pdf (should note these files can be
deleted)

* Copied "400plus-20120415-14\bin\AUTOEXEC.BIN" file (not nightly build
400plus-20121123-r1514\AUTOEXEC.BIN) to CF card along with "languages.ini"
- replacing existing "AUTOEXEC.BIN" OF SIZE 1.59MB (from ML) with 60.4KB
version (400Dplus).

* Ejected CF card from computer and inserted into camera.

[400...@googlecode.com]

Comment by bwieseon...@gmail.com:

I had a confusing issue with the "Preparing each card" section for 2

reasons/issues.

Issue 1: User reading error: "This step depends on your OS and CF Card, but
first insert CF into the camera and format it. [NOTE: You can format it on
the PC too]"

* Which I slightly misread to mean this step was only about formatting the
card and the instructions for each OS below were simply "how to format for
each OS on your PC" per '[NOTE: You can format it on the PC too]'. Would
suggest adding after '...format it.' "Then follow the steps below for your
OS to prepare the CF card for 400Dplus."

Issue 2: Possible Windows PC error on running EOScard.exe to prepare CF card

* (Failed!) On Windows XP Pro ver 2002 SP3, right-click on EOScard.exe

select "Run as..", Run - Current user (or select user) "user" (an
administrative account) and UN-checked "Protect my computer and data from
unauthorized program activity" - OK.
* EOScard 1.32 opened and identified "I: EOS_DIGITAL FAT32? 4GB" Sandisk
CF card.
* Checked EOS_DEVELOP and BOOTDISK (CHDK and ML boxes turned grey and
depressed) checkboxes, Content section says "DCIM folder: ok" and all
others marked "-", clicked Save button.
* Get pop-up error window "EOScard 1.32" with image of red circle with
white X inside and "ZIP format." Clicked OK button.
* !!?? Looks like this step failed? - could not find this "ZIP format"
error documented.

* (Worked!) On Windows 7 Pro SP1, right-click on EOScard.exe select "Run

[400...@googlecode.com]

Comment by bwieseon...@gmail.com:

I had a confusing issue with the "Preparing each card" section for 2

reasons.

Reason 1: User reading error: "This step depends on your OS and CF Card,

but first insert CF into the camera and format it. [NOTE: You can format it
on the PC too]"

* Which I slightly misread to mean this step was only about formatting the
card and the instructions for each OS below were simply "how to format for
each OS on your PC" per '[NOTE: You can format it on the PC too]'. Would
suggest adding after '...format it.' "Then follow the steps below for your
OS to prepare the CF card for 400Dplus."

Reason 2: Possible Windows PC error on running EOScard.exe to prepare CF

[400...@googlecode.com]

Comment by lim...@gmail.com:

typo: The paragraph "Removing 400plus" mistakenly says "4000plus" in one
occurrence.

For more information:
https://code.google.com/p/400plus/wiki/FirmwareHackInstallation

[400...@googlecode.com]

Comment by eduardo....@gmail.com:

> typo: The paragraph "Removing 400plus" mistakenly says "4000plus" in one
> occurrence.

Fixed... thanks!

[400...@googlecode.com]

Comment by FlyerKr...@gmail.com:

I had to do some extra legwork to get the "Preparing each card" working on
Ubuntu. Might be a 'duh' writeup for you advanced Linux users. Should help
anyone else find their CF card and fix the 'permission denied' error when
dd runs. The hack works great now!

Preparing each card in Ubuntu:
sudo fdisk -l #List to see where your CF card is. Easy way to find it is to
match the size
dev=/dev/sdX1 # replace X with your CF device (first partition) as before
ie sdc1
echo EOS_DEVELOP | sudo dd of="$dev" bs=1 seek=71 count=11 #dd needs to run
as super user
echo BOOTDISK | sudo dd of="$dev" bs=1 seek=92 count=8

[400...@googlecode.com]

[400...@googlecode.com]

[400...@googlecode.com]

Comment by cpile...@gmail.com:

Not working

Tried it on mac and PC cannot get it to work. I updated to 1.1.1, formated
my memory card, put testfir.fir on there (screen went black like it said it
would, let it sit 7 or 8 minutes, shut it off, removed batteries,
reformated the card w/eos card on pc and macboot on mac) put the 400plus
files on there. When I boot it up the direct print button turns blue but I
have NO change in features. Sometimes it freezes up and wont do anything
till I reformat the card on the computer...the direct print button turns
blue every f-ing time though.............

[400...@googlecode.com]

Comment by Stfbcon...@gmail.com:

how do you use the direct way of preparing the card as macboot will not
work for me for some reason?

[400...@googlecode.com]

Comment by 13o...@gmail.com:

My Print Button lights all the time, I can't do anything, the screen stays
black. The only thing I can do is let the flash pop out. I have to remove
the battery to turn the camera off. When I am using a fresh (formatted)
card, it works (thanksfully) normally again, but off course without the
400plus features.
I followed every steps correctly and used Windows7 with EOScard and
cardtricks (also as administrator). It seem to try booting (because the
blue light is on) but the screen just stays black.
What can I do.

[400...@googlecode.com]

Comment by 13o...@gmail.com:

My Print Button lights all the time, I can't do anything, the screen stays
black. The only thing I can do is let the flash pop out. I have to remove
the battery to turn the camera off. When I am using a fresh (formatted)
card, it works (thanksfully) normally again, but off course without the
400plus features. I followed every steps correctly and used Windows7 with
EOScard and cardtricks (also as administrator). It seem to try booting
(because the blue light is on) but the screen just stays black.

I tried it first with a 32GB SD Card in a CF Card Adapter and afterwards
with an original 2GB CF Card. Same results.

What can I do?

[400...@googlecode.com]

Comment by fired...@gmail.com:

Please open an issue, so we can comment on it.

[400...@googlecode.com]

Comment by Metallit...@gmail.com:

I can't seem to be able to check EOS_DEVELOP and BOOTDISK on EOScard 1.32
without getting CHDK and ML to light up. I remember being able to do it
before, but not this at this time.

The firmware just won't load up on the camera (it does with my older CF). I
assume it is a problem with the version of EOScard. Any ideas?

[400...@googlecode.com]

Comment by fired...@gmail.com:

Perhaps you should talk to Pelican (http://pel.hu/eoscard/), since he is
making this tool. He probably changed it to be easier for ML.
Anyway, it's not a problem to prepare the card with ML, then delete all the
files (do not format the card), then put 400Plus files on the card.

[400...@googlecode.com]

Comment by Metallit...@gmail.com:

Thank you, I just realized that there was a file with the same name for
this firmware and ML, so that's what was causing me trouble. I did as you
said, and it works now, thank you very much.

[400...@googlecode.com]

Comment by janardan...@gmail.com:

Can it be used with a Canon EOS 450D and with SD Card? Since 450D does not
have a CF card.

[400...@googlecode.com]

Comment by fired...@gmail.com:

This is not a place for such questions, see issue #180 and search for 450D
in CHDK forums: http://chdk.setepontos.com/

[400...@googlecode.com]

Comment by urondog...@hotmail.com:

what i got and what i did with it.

Camera-400d ver.1.1.1, fully charged battery, card reader and a 8G SanDisk
Ultra.

1.i've prepared the camera as firmware (1.1.1)

2.download '400plus-testfir-1.bin.zip' and unzip and copy the whole
foler 'testfir.fir' to the root of my CF card

3.insert CF to camera and went into camera menu-firmwarre ver. 1.1.1-
upate, then screen went black, wait for about 6-7mins, turn off camera-
remove battery and back in again.

4.format the card with camera, used EOScard- inside EOScard, check
EOS_DEVELOP and BOOTDISK(CHDK and ML in colour), save.

5.download '400plus-20130305-r1758' and copy 'AUTOEXEC.BIN' to the root of
CF.

6.after all this nothing happen.
please can someone tell me what i did wrong?
many thanks

[400...@googlecode.com]

Comment by fired...@gmail.com:

I guess your card is not prepared, something went wrong in preparing the
card. As it seems the testfir did it's job, so no need to repeat that step.
Please try to prepare your card again with EOScard and if it's not working,
please open an issue for the your problem.

[400...@googlecode.com]

Comment by colinban...@gmail.com:

<<I can't seem to be able to check EOS_DEVELOP and BOOTDISK on EOScard 1.32
without getting CHDK and ML to light up. I remember being able to do it
before, but not this at this time. <<

I can confirm that in the current version of EOSCard, it is impossible to
check EOS_DEVELOP and BOOKDISK and not have ML selected. Therefore the
instructions should change accordingly. The ML files will be written to the
card, and they should be deleted.

[400...@googlecode.com]

Comment by slerw...@gmail.com:

And now the way that works running Windows 7 x64.
First download the dd tool (link see in description above) unzip dd (e.g.
‘c:\tmp\dd’) and a hex editor (e.g. HxD)
1. Format CF card in camera
2. Open cmd window, navigate to dd tool path (e.g. ‘c:\tmp\dd’)
3. Insert CF card in reader and check the drive name (e.g. ‘f:’)
4. Enter into cmd window:
dd if=\\.\f: of=\\.\c:\tmp\eosBlock_read count=1
(‘f:’ and ‘c:\tmp\’ based on before used examples, change it to your
values)
5. Start hex editor and open ‘eosBlock_read’ file (e.g. ‘c:\tmp’)
6. Modify the values for FAT16:
EOS_DEVELOP starts on 43 (0x2B), the numbers are: 45 4F 53 5F 44 45 56 45
4C 4F 50
BOOTDISK starts on 64 (0x40), the numbers are: 42 4F 4F 54 44 49 53 4B
7. Or modify the values for FAT32:
EOS_DEVELOP starts on 71 (0x47), the numbers are: 45 4F 53 5F 44 45 56 45
4C 4F 50
BOOTDISK starts on 92 (0x5C), the numbers are: 42 4F 4F 54 44 49 53 4B
8. Save the file (e.g. ‘c:\tmp\eosBlock_write’)
9. Enter into cmd window:
dd if=\\.\c:\tmp\eosBlock_write of=\\.\f: count=1
(‘f:’ and ‘c:\tmp eosBlock_write’ based on before used examples, change it
to your values)
10. Copy the ‘AUTOEXEC.BIN’ and ‘languages.ini’ files to the CF card and go
for it

[400...@googlecode.com]

Comment by slerw...@gmail.com:

I also tried several ways (VM with Ubuntu, Win XP) all without any
successes.

And now the way that works running Windows 7 x64.

First download the *dd* tool (link see in description above) unzip dd (e.g.
c:\tmp\dd) and a hex editor (e.g. HxD)
#*Format CF card* in camera
#Open *cmd* window, navigate to *dd* tool path (e.g. c:\tmp\dd)
#Insert CF card in reader and check the *drive name* (e.g. f:)
#Enter into *cmd* window:

{{{ dd if=\\.\f: of=\\.\c:\tmp\eosBlock_read count=1 }}}

(f: and c:\tmp\ based on before used examples, change it to your values)
#Start *hex editor* and open *eosBlock_read* file (e.g. c:\tmp)
#Modify the values for *FAT16*:

EOS_DEVELOP starts on 43 (0x2B), the numbers are: 45 4F 53 5F 44 45 56 45
4C 4F 50
BOOTDISK starts on 64 (0x40), the numbers are: 42 4F 4F 54 44 49 53 4B

#Or modify the values for *FAT32*:

EOS_DEVELOP starts on 71 (0x47), the numbers are: 45 4F 53 5F 44 45 56 45
4C 4F 50
BOOTDISK starts on 92 (0x5C), the numbers are: 42 4F 4F 54 44 49 53 4B

#*Save* the file (e.g. c:\tmp\eosBlock_write)
#Enter into *cmd* window:

{{{ dd if=\\.\c:\tmp\eosBlock_write of=\\.\f: count=1 }}}
(‘f:’ and ‘c:\tmp eosBlock_write’ based on before used examples, change
it to your values)

#*Copy* the ‘AUTOEXEC.BIN’ and ‘languages.ini’ files *to the CF card* and

[400...@googlecode.com]

Comment by slerw...@gmail.com:

I also tried several ways (VM with Ubuntu, Win XP) all without any
successes.

And now the way that works running Windows 7 x64.
First download the *dd* tool (link see in description above) unzip dd (e.g.
c:\tmp\dd) and a hex editor (e.g. HxD)
# *Format CF card* in camera

# Open *cmd* window, navigate to *dd* tool path (e.g. c:\tmp\dd)
# Insert CF card in reader and check the *drive name* (e.g. f:)
# Enter into *cmd* window:

{{{ dd if=\\.\f: of=\\.\c:\tmp\eosBlock_read count=1 }}}
(f: and c:\tmp\ based on before used examples, change it to your values)

# Start *hex editor* and open *eosBlock_read* file (e.g. c:\tmp)
# Modify the values for *FAT16*:

EOS_DEVELOP starts on 43 (0x2B), the numbers are: 45 4F 53 5F 44 45 56 45
4C 4F 50
BOOTDISK starts on 64 (0x40), the numbers are: 42 4F 4F 54 44 49 53 4B

# Or modify the values for *FAT32*:

EOS_DEVELOP starts on 71 (0x47), the numbers are: 45 4F 53 5F 44 45 56 45
4C 4F 50
BOOTDISK starts on 92 (0x5C), the numbers are: 42 4F 4F 54 44 49 53 4B

# *Save* the file (e.g. c:\tmp\eosBlock_write)
# Enter into *cmd* window:

{{{ dd if=\\.\c:\tmp\eosBlock_write of=\\.\f: count=1 }}}

(f: and c:\tmp eosBlock_write based on before used examples, change it to
your values)
# *Copy* the ‘AUTOEXEC.BIN’ and ‘languages.ini’ files *to the CF card* and

[400...@googlecode.com]

Comment by slerw...@gmail.com:

I also tried several ways (VM with Ubuntu, Win XP) all without any
successes.

* And now the way that works running Windows 7 x64.
* First download the *dd* tool (link see in description above) unzip dd

(e.g. c:\tmp\dd) and a hex editor (e.g. HxD)

* *Format CF card* in camera
* Open *cmd* window, navigate to *dd* tool path (e.g. c:\tmp\dd)
* Insert CF card in reader and check the *drive name* (e.g. f:)
* Enter into *cmd* window:

{{{ dd if=\\.\f: of=\\.\c:\tmp\eosBlock_read count=1 }}}
(f: and c:\tmp\ based on before used examples, change it to your values)

* Start *hex editor* and open *eosBlock_read* file (e.g. c:\tmp)
* Modify the values for *FAT16*:
# EOS_DEVELOP starts on 43 (0x2B), the numbers are: 45 4F 53 5F 44 45 56
45 4C 4F 50
# BOOTDISK starts on 64 (0x40), the numbers are: 42 4F 4F 54 44 49 53 4B
* Or modify the values for *FAT32*:
# EOS_DEVELOP starts on 71 (0x47), the numbers are: 45 4F 53 5F 44 45 56
45 4C 4F 50
# BOOTDISK starts on 92 (0x5C), the numbers are: 42 4F 4F 54 44 49 53 4B
* *Save* the file (e.g. c:\tmp\eosBlock_write)
* Enter into *cmd* window:

{{{ dd if=\\.\c:\tmp\eosBlock_write of=\\.\f: count=1 }}}
(f: and c:\tmp eosBlock_write based on before used examples, change it to
your values)

* *Copy* the ‘AUTOEXEC.BIN’ and ‘languages.ini’ files *to the CF card* and

[400...@googlecode.com]

Comment by slerw...@gmail.com:

I also tried several ways (VM with Ubuntu, Win XP) all without any
successes.

* And now the way that works running Windows 7 x64.
* First download the *dd* tool (link see in description above) unzip dd
(e.g. c:\tmp\dd) and a hex editor (e.g. HxD)

* Format CF card in camera
* Open cmd window, navigate to dd tool path (e.g. c:\tmp\dd)
* Insert CF card in reader and check the drive name (e.g. f:)
* Enter into cmd window:

{{{ dd if=\\.\f: of=\\.\c:\tmp\eosBlock_read count=1 }}}
(f: and c:\tmp\ based on before used examples, change it to your values)

* Start hex editor and open eosBlock_read file (e.g. c:\tmp)
* Modify the values for FAT16:

EOS_DEVELOP starts on 43 (0x2B), the numbers are: 45 4F 53 5F 44 45 56 45
4C 4F 50

BOOTDISK starts on 64 (0x40), the numbers are: 42 4F 4F 54 44 49 53 4B

* Or modify the values for FAT32:

EOS_DEVELOP starts on 71 (0x47), the numbers are: 45 4F 53 5F 44 45 56 45
4C 4F 50

BOOTDISK starts on 92 (0x5C), the numbers are: 42 4F 4F 54 44 49 53 4B
* *Save* the file (e.g. c:\tmp\eosBlock_write)
* Enter into *cmd* window:
{{{ dd if=\\.\c:\tmp\eosBlock_write of=\\.\f: count=1 }}}
(f: and c:\tmp eosBlock_write based on before used examples, change it to
your values)

* Copy the ‘AUTOEXEC.BIN’ and ‘languages.ini’ files to the CF card and go

[400...@googlecode.com]

[400...@googlecode.com]

Comment by slerw...@gmail.com:

I also tried several ways (VM with Ubuntu, Win XP) all without any
successes.

* And now the way that works running Windows 7 x64.

* First download the dd tool (link see in description above) unzip dd

(e.g. c:\tmp\dd) and a hex editor (e.g. HxD)
* Format CF card in camera
* Open cmd window, navigate to dd tool path (e.g. c:\tmp\dd)
* Insert CF card in reader and check the drive name (e.g. f:)
* Enter into cmd window:
{{{ dd if=\\.\f: of=\\.\c:\tmp\eosBlock_read count=1 }}}
(f: and c:\tmp\ based on before used examples, change it to your values)
* Start hex editor and open eosBlock_read file (e.g. c:\tmp)
* Modify the values for FAT16:
EOS_DEVELOP starts on 43 (0x2B), the numbers are: 45 4F 53 5F 44 45 56 45
4C 4F 50
BOOTDISK starts on 64 (0x40), the numbers are: 42 4F 4F 54 44 49 53 4B
* Or modify the values for FAT32:
EOS_DEVELOP starts on 71 (0x47), the numbers are: 45 4F 53 5F 44 45 56 45
4C 4F 50
BOOTDISK starts on 92 (0x5C), the numbers are: 42 4F 4F 54 44 49 53 4B

* Save the file (e.g. c:\tmp\eosBlock_write)

* Enter into cmd window:

[400...@googlecode.com]

Comment by slerw...@gmail.com:

I also tried several ways (VM with Ubuntu, Win XP) all without any
successes.

* And now the way that works running Windows 7 x64.
* First download the dd tool (link see in description above) unzip dd
(e.g. c:\tmp\dd) and a hex editor (e.g. HxD)
* Format CF card in camera
* Open cmd window, navigate to dd tool path (e.g. c:\tmp\dd)
* Insert CF card in reader and check the drive name (e.g. f:)
* Enter into cmd window:
{{{ dd if=\\.\f: of=\\.\c:\tmp\eosBlock_read count=1 }}}
(f: and c:\tmp\ based on before used examples, change it to your values)
* Start hex editor and open eosBlock_read file (e.g. c:\tmp)
* Modify the values for FAT16:

# EOS_DEVELOP starts on 43 (0x2B), the numbers are: 45 4F 53 5F 44 45 56
45 4C 4F 50
# BOOTDISK starts on 64 (0x40), the numbers are: 42 4F 4F 54 44 49 53 4B

* Or modify the values for FAT32:

# EOS_DEVELOP starts on 71 (0x47), the numbers are: 45 4F 53 5F 44 45 56
45 4C 4F 50
# BOOTDISK starts on 92 (0x5C), the numbers are: 42 4F 4F 54 44 49 53 4B

[400...@googlecode.com]

[400...@googlecode.com]

Comment by webw...@gmail.com:

on Debian EOScard works with Wine

username@localhost: ~# wine /path_to_exe_file/EOScard.exe

[400...@googlecode.com]

Comment by imihaj...@gmail.com:

The first step of the installation procedure cannot be undone (at least for
now). Fuck.
The main disadvantage of 400plus is the slower camera start-up time. I need
my fast start-up back :(

[400...@googlecode.com]

Comment by fired...@gmail.com:

Yes, you trade the small delay in start-up for a basket of features.
You do not need to undo the first step of the installation procedure,
unless your camera still has a warranty and you want to send it to an
official service. The first step does nothing more then changing one flag
in the bootloader. It does not delay your start-up time. If you truly want
to undo the first step, we can prepare an special firmware for that.
If you need your fast start-up back, then just remove 400Plus from your CF
card.

[400...@googlecode.com]

Comment by fired...@gmail.com:

https://code.google.com/p/400plus/wiki/UserGuide#Standard_Initialization
See this too.

[400...@googlecode.com]

Comment by maurosil...@gmail.com:

I don't know if this operation is correct and useful, but i've tried few
times to make the CF Bootable whit EOScard and i never get the hack work.
I've tried to make bootable my CF with CardTricks and it work perfectly!!
Sorry for my English, i'm Italian ;)

[400...@googlecode.com]

Comment by andy9...@gmx.de:

It doesn't work here. I'm using Linux and I did all steps exactly as
described above. fdisk -l recognizes the CF card as bookable (boot flag is
set), my SUSE system can mount the card and I have access to it. I copied
both files, AUTOEXEC.BIN and languages.ini, into the root directory of my
CF card, but nothing happens. My EOS reacts like always.

[400...@googlecode.com]

Comment by fired...@gmail.com:

The so called "boot flag" is not the real boot flag of the partition...
it's a flag in the camera itself... other than that, you need the volume
label set to it's correct value. Please read the guide again and do the
steps.
(keep in mind that you need to enable the camera boot flag with a specific
firmware at first time)

[400...@googlecode.com]

Comment by fired...@gmail.com:

See 400plus-testfir-1.bin.zip, for enabling the camera boot flag. Without
this, you will never have the hack running.

[400...@googlecode.com]

Comment by andy9...@gmx.de:

Of course I used 400plus-testfir-1.bin.zip to update the firmware (which is
v. 1.1.1). Is there a way to check whether this initial procedure went okay?

[400...@googlecode.com]

Comment by fired...@gmail.com:

repeat the steps, you've missed something i guess ...
the guide is well written so most (all) users got it...
dunno what you're missing, but it should work.

[400...@googlecode.com]

Comment by andy9...@gmx.de:

Oh, it works now. Thanks a million. :) I must have done something wrong
first.

[400...@googlecode.com]

Comment by dogbisco...@gmail.com:

I am in the US and have the Rebel T1i version of the 400D. It turns out it
needs a different .fir file to install the 1.1.1 firmware. I found the
right file and updated the firmware but now I'm wondering if the hack will
work. Has anyone here tried it on a T1i?

[400...@googlecode.com]

Comment by eduardo....@gmail.com:

@dogbiscotti:

The Rebel T1i (or Kiss X3) name corresponds to the 500D; do not even try to
run 400plus on that camera. However, there is a version of Magic Lantern
for the 500D; have a look here: http://magiclantern.wikia.com/wiki/Unified

[400...@googlecode.com]

Comment by dogbisco...@gmail.com:

Thanks, Eduardo, will take a look.