ROM Kitchen Utensils

[ahmdhasn]

Hi Tj
I go through all the post and did as mention
I pick up CsAKU3.5b and traied the steps in the attached file by llbasha but I faced the prob as u mention in the 1st. page
"initflashfiles.dat is used for putting(copying) files in the right path and/or creating subdirectories during hard reset
* Normally all files added to ROM are placed \Windows folder. You need to modify initflashfiles.dat to define were to put the files, copy and rename the files, and create subdirectories. The initflashfiles.dat will be parsed during a hard reset. So, if your device happen to boot up after a ROM flashing with nothin in the start menu other than Today and/or coldinit; chances are there is a defect in initflashfiles.dat and/or the default.hv You can still access the contents of PPC at this state using ActiveSync though"

I do not know is it mistake I did or step missing in the attached proceedure by llbasha (that collect the information and files from here)
I asked him but he prefers to have the answer from you!!

Regards

[tjlabais]

Okay... So you want to know where you made a mistake... Can you still access the contents of your PPC using ActiveSync? If so,
1. copy default.hv from original llbasha ROM into your PPC.
2. hard reset your phone BUT: clear registry hive - yes / format storage - no
3. if you get a working startup, then there's something wrong with your default.hv
4. IF NOT, do the same for initflashfiles.dat.

The key here is to locate where you commit a mistake... So, we have to troubleshoot...
cheers,
TJ

Hi Tj
I go through all the post and did as mention
I pick up CsAKU3.5b and traied the steps in the attached file by llbasha but I faced the prob as u mention in the 1st. page
"initflashfiles.dat is used for putting(copying) files in the right path and/or creating subdirectories during hard reset
* Normally all files added to ROM are placed \Windows folder. You need to modify initflashfiles.dat to define were to put the files, copy and rename the files, and create subdirectories. The initflashfiles.dat will be parsed during a hard reset. So, if your device happen to boot up after a ROM flashing with nothin in the start menu other than Today and/or coldinit; chances are there is a defect in initflashfiles.dat and/or the default.hv You can still access the contents of PPC at this state using ActiveSync though"

I do not know is it mistake I did or step missing in the attached proceedure by llbasha (that collect the information and files from here)
I asked him but he prefers to have the answer from you!!

Regards

[ahmdhasn]

Thanks Tj
I assume that the sequence of the bat files are reviewd by u and ok
The programs icluded are as u mentioned
and the way in this file related to initflashfiles.dat & registry are ok

So the solution as u said

[llbasha]

@ahmdhasn / The_hesham

TJ, please allow me to answer.

1st... I did not refuse to answer any of your question. I only asked you to post in the right place. I specifically asked you to post your questions regarding the the tools/utensils here. I realize that not many people adhear to this simple fourm role but that does not make it right. I do this for fun as spare time activity and as a way to help others by sharing knowledge and/or experence. pay back to the forum I benefit from. So please do not be senstive... I would help you IF and when I can... OK.

2nd... As I mentioned in my rom posts, the tools attached with the rom are the same as those mentioned here by TJ. As for the sequance and/or steps they are correct. If you have used it and got a bad rom then check your work as mentioned by TJ, for example the hv files, iniflashfiles, the registery, the number of file, etc... However, as I said before this method is NOT like the kitchen. You must understand what every tool does otherwise you would have no way to trouble shoot your problems, should it happen.

Regards
llbasha

[ahmdhasn]

Dear llbasha
No sensitivity at all
But I go through the utensil method here and I couldn't understand it very well, once I saw ur bat. Files and the way u explain it. I was very happy and I had some question to a person used and tried this method.
However, the reason that I think this method is fantastic is that it gives u the opportunity to modify a good ROm (remove or add) as u want.
I already make my cook by Helmi_c kitchen as explained by Bepe.
I succeeded to cook, every thing was Ok, except:
1- FTP-explorer when I press the program it should create Bluetooth folder and start looking for another devices to copy and Or cut file..etc. But it trays to open the internet and gives me error. I tried to solve it by several way no successes.
2- I did not know about UPX so the ROM was full

So I found C_shekhar ROM has all what I need but I want to remove some prog and add other

Exactly as I can do by the Utensil.

My question to u was
1-Is this way of copy intiflash.dat ---> initflashfiles.dat.txt will not damage the file as said her and xda.?
2- The sequence of modifying the registry is this the one make the prob.?

However I will cook again and If I have prob I will post it here

By the way, u could be a good teacher (Utensil and Ram disk) explanations was very good

[llbasha]

Dear Ahmdhasn,
I you just want to remove/add few files, in many cases you do not need to edit the registery and/or iniflashfiles.dat at all and no harm would happen, and in this case I would strongly suggest using the Add/Remove method as suggested by TJ here. Open the file cook.bat, read it, understand it, and edit it to include your files.

The process of copying the iniflashfiles.dat from the dump to the rom editor director does NOT make any changes to the file. It only copy it and rename it so you can work on it while keep the other safe un touched.

The hard part in using this tools is that you do not often get an erro messages and you would never know you have done the right thing until you burn your rom. Hence, you have to work systematically and very carefully to avoid later disappoinment.

I shall be on the road until the end of the month. In fact I have a flight to catch in few hours. So I hope by the time I come back I see your first rom uploaded here...........
Good luck and best regards
llbasha

[tjlabais]

@ahmdhasn:

Now I understand your predicament... If you would notice, I placed an introduction of the utensils about things we need to know when editing a ROM... these are bits and pieces of critical information when doing so, and not a really a step by step guide because each and everyone of us has their own personal preferences in the customization of the ROM. My dismay at first was that, I get a thousand page views from it and not even a single question on what to do UNTIL llbasha came around. And yes, llbasha commented that the wealth of resources available can be very intimidating at first. BUT, one will get the hang of it when you start getting your feet wet. As the saying goes... 'no guts no glory'

So, for your question, this information might be useful for you: All the files we add to the ROM stays in the ROM. If we modify some files like the registry (.hv) and initflashfiles.dat, we can experiment at first by copying the modified files to your PPC. Then perform a semi-hard reset - which means clear registry hive - yes / then format storage - no. If what you want to work on will not work, this means theirs something wrong, we simply just hard reset with format storage - yes | and everything will go back to the original ROM files. This applies even to adding your personal apps. We test it using this method, before we finally burn the ROM, when everything seems to work ok. Oh, by the way, sometimes, we can't copy the files twice... meaning if you have a second modification, you need to format storage again before copying.

Also, another thing we should keep in mind, the files that we got for the ROM is not really intended for the hima, SO, sometimes, files fail to work, and has to be replaced. In fact, bits and pieces of software has been picked up from different ROM versions and ROM devices just to keep it going... As a clue, if something doesn't come out right, we get a similar file from a different ROM that is known to be working...

That's how we solved a couple of non working files (i.e. non functioning excel in virgy rom, the button lock page in most AKU3.5 ROMs, etc...) Whether we like it or not, there are some things that will not really function in the WM5 environment... (i.e. backpack accessories) Things like these require programming skills and adequate knowledge in the device to do some modifications of the original file to work in our himas OR worst write a new WM5 device driver... This is where people like buzz, mamaich, etc. come in, BUT, because everyone here does it in their spare time, we'll have to be patient...

Good Luck! and thanks for your feedback...
TJ

[ahmdhasn]

Thanks llbasha & Tj
When I have time, I will start again & take all this valuable notes into consideration
Another ques.
How to use upx ?
Is all software could be Upexed?
How can I know that this dll & exe will work after beeing upxed?

Sorry 4 2 much ques.

llbasha

I hope to u a save trip.

[tjlabais]

Th UPX syntax is found in the first page... Just like my previous post, we need to experiment and copy files to our himas. Take note that you do not need to format storage if the files you're working on is not a system file... UPX is an ongoing project and is still in progress... there are dlls that can't be UPXed - you will know because the software will say so. Sometimes, you can't used maximum compression because the file you UPXed will perform abnormally, BUT will perform okay at 70% compression. It really needs time to experiment and test.

Good Luck!
TJ

Thanks llbasha & Tj
When I have time, I will start again & take all this valuable notes into consideration
Another ques.
How to use upx ?
Is all software could be Upexed?
How can I know that this dll & exe will work after beeing upxed?

Sorry 4 2 much ques.

llbasha

I hope to u a save trip.

[ahmdhasn]

Would u pls explain more
do I have to do this in pc
Start
Run
cmd
Go to the folder upx
and type

UPX --lzma -9 --strip-relocs=0 --compress-icons=0 filename.extwhere: EXT may be EXE or DLL / -9 maximum compression / -1 least compression

Decompressing the files back to original state

UPX -d --strip-relocs=0 filename.ext


I