I have an idea to apply the c2z patch to the firmware, before install it to my phone and then the problem is that the phone didn't actualy get updated, NSU just changes my language files and not installing the firmware..

Please someone try to see if it works for him.
For the people that don't know what they are doing: Don't Try This!!!

You need:
1. Nokia Software Updater
2. Nokia phone capable of updating software through NSU :)

Steps:
1. Connect your phone to the pc via PC Suite mode.
2. Start NSU and when it checks for an update, click reinstall.
3. After it starts downloading the firmware, disconnect your phone.
4. (WinXP) Go to C:\Documents and Settings\Username\Local Settings\Temporary Internet Files and look for your firmware:
http://img229.imageshack.us/img229/6988/shot2sh2.th.jpg (http://img229.imageshack.us/img229/6988/shot2sh2.jpg)
5. Copy it to other folder and hex edit it. (with winhex is piece of cake!)
You need to change the Hex Values shown in the your generated c2z patch to the corresponding one:

Copy to a new text file(optimal) the first code after the adress and the values to change:
http://img228.imageshack.us/img228/202/shot6qb2.th.jpg (http://img228.imageshack.us/img228/202/shot6qb2.jpg)
http://img228.imageshack.us/img228/4404/shot5xa1.th.jpg (http://img228.imageshack.us/img228/4404/shot5xa1.jpg)

The same for the other hex code.
http://img135.imageshack.us/img135/294/shot7jp8.th.jpg (http://img135.imageshack.us/img135/294/shot7jp8.jpg)

And now we open with winhex the firmware and replace the values:
http://img230.imageshack.us/img230/7008/shot8dl8.th.jpg (http://img230.imageshack.us/img230/7008/shot8dl8.jpg)

Search for the first code and change it to the code from the c2z patch:
http://img234.imageshack.us/img234/5928/shot9ux1.th.jpg (http://img234.imageshack.us/img234/5928/shot9ux1.jpg)

First done.
http://img229.imageshack.us/img229/4543/shot11ba1.th.jpg (http://img229.imageshack.us/img229/4543/shot11ba1.jpg)

The same for the second and third if you have one.
http://img228.imageshack.us/img228/8033/shot12tt1.th.jpg (http://img228.imageshack.us/img228/8033/shot12tt1.jpg)
http://img229.imageshack.us/img229/4928/shot13fa2.th.jpg (http://img229.imageshack.us/img229/4928/shot13fa2.jpg)


Now save it and copy the firmware file back to the dir where you took it from and reinstall (or update) you firmware through NSU. ;)

thanks for your tip but this may be harmful because permanant changes are made so we just want to investigate on fca concept ie in which no permanant change is made just the change is done in the ram. And every thing can be reversed back by just restarting the phone.
Secondly this patch is an alpha version and it slows down the speed of the phone because the phone have to search two drives instead of one.

thanks for your tip but this may be harmful because permanent changes are made so we just want to investigate on fca concept ie in which no permanent change is made just the change is done in the ram. And every thing can be reversed back by just restarting the phone.
Secondly this patch is an alpha version and it slows down the speed of the phone because the phone have to search two drives instead of one.

The point to be permanent is that you will be able to change the startup.mbm (I'm speaking for the Pre-FP1 phones) and many other files that are loaded in the phone startup. Also the c2z patch may be alpha and slowing down the phone(not in my case) but it will not brake it and when a new version comes out we will be able to apply it permanent again in about 30 minutes. ;)

then it would be more good to change the start.mbm file instead of risking the phone security and keeping it under permanant danger and stress.

then it would be more good to change the start.mbm file instead of risking the phone security and keeping it under permanant danger and stress.

You mean change it in the firmware it self and then install it.. this is bad idea ;) I don't want to be able to change my startup animation just in a firmware update.. or if you are talking to change it in the phone, its not possible! (The reason everybody knows is patching is temporary..)
I'm using my phone now with c2z patch applied all the time, also installing software, uninstalling etc. no problems found.. is it just me? If not what is the danger and stress that you are talking about?

ok man thumbs up just enjoy.
Anyways i was just talking about changing the animation in the firmware update.

The point to be permanent is that you will be able to change the startup.mbm (I'm speaking for the Pre-FP1 phones) and many other files that are loaded in the phone startup. Also the c2z patch may be alpha and slowing down the phone(not in my case) but it will not brake it and when a new version comes out we will be able to apply it permanent again in about 30 minutes. ;)

How come my E65 (preFP1) loads from C:\ instead of Z:\ always? And yes, I know its preFP1...

How come my E65 (preFP1) loads from C:\ instead of Z:\ always? And yes, I know its preFP1...

Haha :P A million dollar question? :D: It seems nokia made it by default to load the files from C:\, and when I say Pre-FP1 is not loading the files from C:\ first, that doesn't mean it cannot! The c2z patch proves it. Just from nokia didn't made it work that way on some models, maybe because they didn't needed or didn't thought of it till now (E65 is practically new 2007 model). :P
Don't know. :))

Hi illegible,
Just answer one more question.
As we all know that c2z patch is not compatible with all the phones when we apply it to some phones they hang and we have to remove the battery to restart our phones and our phone become alright because the patch is gone. Now when some one will apply this permanently in his firmware his phone will hang and on restarting his phone will not even show the nokia logo and will hang there showing a white screen only. Because EFSrv.dll is that file which loads the z drive on phone. Now after hanging the phone will just become a piece of junk and will not reformat not even connect to any device so will not format so what will you do at that time will you throw in a dust bin.
Now with all the other phones with which its compatible . I some one will accidently place any corrupt file in c drive like menu structure file or phoneengine.dll or phoneclinet.dll or wsini.ini or dllpreload list or any such other system file etc.
His phone will not even restart so what will you do then will you throw it in dust bin.There,s no way to divert it back so first provide any solution.

From my point of view its very dangerous and will advise you not to try it.

Its a well known saying
Think before you leap.:oops2::oops2::oops2::confused:

Well! I don't know about others but I'm definitely not gonna try it. Editing the firmware file is always a risky affair and what about the CRC in this case? Remember the Symbaali hack resulted in many dead phones. I don't have the courage to do it & wouldn't recommend anyone...but good to know that you have found an alternative ;)

yeh i forget about it its the real damage maker.

For all other users,
Nokia uses a mechanism CRC (cycle redudancy cheak). This is a cheak sum to keep the data and detect any error or alternation in data. Nokia uses this mechanism to protect its firmwares from being damaged or altered.
The popularity of CRC,S is due to their error detecting capabilities
They can even detect an error of n bits (you can say that an alternation which is not even longer than 2 or three bits)

They are in the form of long codes which are constructed by using finit e fields the most common finite field used is GF(2). It only consists of 0and1. ie any long code containing zero,s and ones.

So if any change is done in the firmware and its detected by crc then your phone will become dead and useless.

i think now symbaali would has learnt how to create a new crc for any alterted portion of the firmware because he have made many changes which were not possible without changing the crc.

Hi illegible,
Just answer one more question.
As we all know that c2z patch is not compatible with all the phones when we apply it to some phones they hang and we have to remove the battery to restart our phones and our phone become alright because the patch is gone. Now when some one will apply this permanently in his firmware his phone will hang and on restarting his phone will not even show the nokia logo and will hang there showing a white screen only. Because EFSrv.dll is that file which loads the z drive on phone. Now after hanging the phone will just become a piece of junk and will not reformat not even connect to any device so will not format so what will you do at that time will you throw in a dust bin.
Now with all the other phones with which its compatible . I some one will accidently place any corrupt file in c drive like menu structure file or phoneengine.dll or phoneclinet.dll or wsini.ini or dllpreload list or any such other system file etc.
His phone will not even restart so what will you do then will you throw it in dust bin.There,s no way to divert it back so first provide any solution.

From my point of view its very dangerous and will advise you not to try it.

Its a well known saying
Think before you leap.:oops2::oops2::oops2::confused:

Hey, I just posted an idea, I didn't posted a solution (It didn't even worked for me!). Its not for people who can't even make a simple patch by themselfs, any other should know what his phone is capable of and what not. Also didn't thought, there would be so stupid people(sorry if offence someone), that would apply this patch permanent, when they know its not working on there phones...
I thought the guys here are a little smarter than this. :LoL:
For the people that don't know what they are doing: Don't Try This!!!

:))

Well! I don't know about others but I'm definitely not gonna try it. Editing the firmware file is always a risky affair and what about the CRC in this case? Remember the Symbaali hack resulted in many dead phones. I don't have the courage to do it & wouldn't recommend anyone...but good to know that you have found an alternative

Maybe this is the reason, why its not installing it to my phone. If NSU check the CRC and if it doesn't match with the one in his database maybe, it skips the installation. But the CRC check has to be the same, because here I don't add or remove any bytes, just changing them and is it possible to tell that with a CRC check..?

How about an alternative method - You put C2Z patch apply command on startup (it wouldn't change startup animation, but at least it will be permanent) with tool like Powerboot. The only real problem is what would be the execution command (perhaps something like "rompatcher patch_name") and that should be implemented in rompatcher itself (automatic applying of patches from command line or smth).