[Q]ROM cooking inquiry - TG01 General

Hi.
Forgive me I asked here but it seems to be nowhere explained, maybe I was not able to find.
I try to utilize leeston2379 suggestions about cooking in His tutorial.
Could anybody explain me why newly created ROM from original firmware ( in my case Malezya ROM ) after dumping and building without any changes , differs significantly from original in size.
It is about 20-30MB lesser than original.
I dumped this newly created ROM. It seems to have all packages like original ROM but for example .dsm files are significantly lesser.
Could anybody confirm that such created ROM ( even without any changes ) can be safely loaded to tg01 and what exactly has been changed and why ?
I count on serious and comprehensive explanation.
Regards
fxdjacentyfxd

---

fxdjacentyfxd said:
Hi.
Forgive me I asked here but it seems to be nowhere explained, maybe I was not able to find.
I try to utilize leeston2379 suggestions about cooking in His tutorial.
Could anybody explain me why newly created ROM from original firmware ( in my case Malezya ROM ) after dumping and building without any changes , differs significantly from original in size.
It is about 20-30MB lesser than original.
I dumped this newly created ROM. It seems to have all packages like original ROM but for example .dsm files are significantly lesser.
Could anybody confirm that such created ROM ( even without any changes ) can be safely loaded to tg01 and what exactly has been changed and why ?
I count on serious and comprehensive explanation.
Regards
fxdjacentyfxd
Click to expand...
Click to collapse
hi, sorry for my poor english, but i will help you
when you dump a ROM, that has orginal 200 MB and you building a new ROM without any changes, then must your cooked ROM to have also 200 MB. ech oem package folder has one .dsm file. pls tell me: wich kitchen and wich ROM.
regards, miro

---

mirolg said:
hi, sorry for my poor english, but i will help you
when you dump a ROM, that has orginal 200 MB and you building a new ROM without any changes, then must your cooked ROM to have also 200 MB. ech oem package folder has one .dsm file. pls tell me: wich kitchen and wich ROM.
regards, miro
Click to expand...
Click to collapse
Thanks miro.
1) Kitchen suggested in this thread http://forum.xda-developers.com/showthread.php?t=804529 and with direct link here :
http://forum.xda-developers.com/attachment.php?attachmentid=416649&d=1286711727
2) I did two steps from this kitchen as leeston2379 suggested :
a) "1. dump.bat"
b) "2. build no XIP port_no auto.bat"
The same result ( I mean new ROM lesser than original ) I got when in step b)
I run "2. build.bat" instead of "2. build no XIP port_no auto.bat"
3) Original ROM I took for experiments is Malezya ROM from link :
http://www.toshiba.co.jp/product/etsg/cmt/english/asian/tg01/exe/TG01WP-WM6.5-Malaysia.exe
Currently I use this rom and I wanna to see what cooking is and in first step to cook ... nothing so dump and build without any changes.
Regards
fxdjacentyfxd

---

one question by side O i have noticed, you thank after a helpful post, but not with the thank button. why? is not why i like you thank- point- i´m wondering only- and you not the only.

---

fxdjacentyfxd said:
Thanks miro.
1) Kitchen suggested in this thread http://forum.xda-developers.com/showthread.php?t=804529 and with direct link here :
http://forum.xda-developers.com/attachment.php?attachmentid=416649&d=1286711727
2) I did two steps from this kitchen as leeston2379 suggested :
a) "1. dump.bat"
b) "2. build no XIP port_no auto.bat"
The same result ( I mean new ROM lesser than original ) I got when in step b)
I run "2. build.bat" instead of "2. build no XIP port_no auto.bat"
3) Original ROM I took for experiments is Malezya ROM from link :
http://www.toshiba.co.jp/product/etsg/cmt/english/asian/tg01/exe/TG01WP-WM6.5-Malaysia.exe
Currently I use this rom and I wanna to see what cooking is and in first step to cook ... nothing so dump and build without any changes.
Regards
fxdjacentyfxd
Click to expand...
Click to collapse
ok, this kitche i use mostly too.
the result in MB is the same if "2. build no XIP port_no auto.bat" or " 2. build.bat"
different is: 2. build no XIP port_no auto.bat- no new xip building- less time
i don´t know what is wrong- but is wrong and i think this ROM will brick your tg01

---

mirolg said:
one question by side O i have noticed, you danken after a hilfreiche post, but not with the thank button. why?
Click to expand...
Click to collapse
hehe, it was so called "thanks in advance" . If You give me answers to my questions I will press "thanks" button
Regards
fxdjacentyfxd

---

mirolg said:
ok, this kitche i use mostly too.
the result in MB is the same if "2. build no XIP port_no auto.bat" or " 2. build.bat"
different is: 2. build no XIP port_no auto.bat- no new xip building- less time
i don´t know what is wrong- but is wrong and i think this ROM will brick your tg01
Click to expand...
Click to collapse
It's too bad So I will try the same not with original rom but for example with clean Mangasora rom and will see results.
Anyway is there any other available kitchen/way to use original rom for cooking not special prepared rom like Mangasora rom ?
Regards
fxdjacentyfxd

---

fxdjacentyfxd said:
hehe, it was so called "thanks in advance" . If You give me answers to my questions I will press "thanks" button
Regards
fxdjacentyfxd
Click to expand...
Click to collapse
no, no problem- but is not the first time. i think you are very critical
but

---

fxdjacentyfxd said:
It's too bad So I will try the same not with original rom but for example with clean Mangasora rom and will see results.
Anyway is there any other available kitchen/way to use original rom for cooking not special prepared rom like Mangasora rom ?
Regards
fxdjacentyfxd
Click to expand...
Click to collapse
the easyst kitchen is that you use. ffboy kitchen is not so easy to understand.
BUT i tell you: no matter ROM or custom ROM- that what you dump out must, when no changes, the same Value in MB and kB!
if you like- one link http://forum.xda-developers.com/showthread.php?t=564130

---

mirolg said:
BUT i tell you: no matter ROM or custom ROM- that what you dump out must, when no changes, the same Value in MB and kB!
Click to expand...
Click to collapse
Explain me one thing yet. I noticed that even retrieving payload from .tsw and merging it again with the same .tsw to get "new" .tsw gives ROM that is not binary equal to original. Yes, it has the same size but comparing both roms in any editor one can see a lot of similar looking places that has been changed. Could You xplain it to me ?
I tested original ROMs again. English Orange ROM and Malezya. Both after cooking nothing gives .tsw files that differs in size to their originals. Maybe You could ask Your colegues cookers about it ? Is this situation exception for original roms and if not what has to be done additionally after dumping , so that new .tsw files have the same size as their originals. I would really prefer to work on original roms
Regards
fxdjacentyfxd

---

.. your thread is open for all cooks, to answer you: D
all my knowledge i have from this "best" forum site and his members!
If someone begins to cook, he must be prepared and know that it can so often give problems and that the tg01 brick or not start. ShortPin and tg01 downloader-procedure i must make multiple times (i love and have also afraid for my tg01)
BUT this a way to learn everything and to find a solution.
wish you all succes
miro

---

mirolg said:
.. your thread is open for all cooks, to answer you: D
all my knowledge i have from this "best" forum site and his members!
If someone begins to cook, he must be prepared and know that it can so often give problems and that the tg01 brick or not start. ShortPin and tg01 downloader-procedure i must make multiple times (i love and have also afraid for my tg01)
BUT this a way to learn everything and to find a solution.
wish you all succes
miro
Click to expand...
Click to collapse
Maybe someone answer who knows. Anyway thanks for help.
What I found interesting. Such newly created rom form original rom has as You know lesser length. Dumping it again and building new rom without changes, gives at last what we want - new rom size has the same size as original ( not virgin one but this cooked without changes ).
Maybe it is nothing terrible that first rom created from original rom is lesser and as a matter of fact we should take for cooking not original rom but this created from it without changes ? . Maybe original rom has any redudant information ( I mentioned You , .dsm file were shortened after cooking and in my oppinion they are now similar to thouse I can typically see in Novembre or Mangasora roms ).
On the other hand, I have never found anywhere yet, original rom should be treated with any special atention during dumping and cooking.
I know I can use short pin method but matter must be worthy to sacrifice tg01. Currently problem seems to be known for some cookers ( some ot them had to use original rom as a base of cooking ) so I will wait.
Regards
fxdjacentyfxd

---

fxdjacentyfxd said:
I know I can use short pin method but matter must be worthy to sacrifice tg01.
Click to expand...
Click to collapse
I am dumping the Malaysia ROM now, I will rebuild and flash to my test device regardless of size difference and let you know the result. Give me a few hours though as i am very busy and doing this in 5 minute gaps when I a have chance.
I have dumped the ROM twice and found that "Missing Manifests" are reported.
First time there were 3 missing, 2nd time 5 missing. The manifests are .dsm files so I am assuming that if the .dsm is missing from a package it is no longer a package and won't be included in the ROM by BuildOS causing the size difference. The first dump also failed to separate the OEM and SYS packages but succeeded the second time
I have rebuilt and flashed the ROM and it appears to work, i do not have time to test it fully but it does boot and run with SPB Mobile Shell, HOWEVER as the two dumps had different .dsm files missing it may be something more important missing the next time causing a real brick.
This is purely speculation but I believe this particular ROM does not like to be dumped and you will have to use a different base ROM. I am happy for you to use mine but I would recommend one of Miros clean ROMs as a base.
Hope this is helpful
Attached is a photo of the output from the .bat file showing the missing .dsm files (this is from the second dump).

---

... As already mentioned: Each folder (if any OEM packages) need a .dsm file. Without it, the package can not be cooked. Ie = if at the end (finished ROM) that those. dsm missing, is missing the complete pakage = Created ROM has less RAM.
if you has nothing doing- but a .dsm file is missing, then is something wrong
what? i don´t know

---

leeston2379 said:
I am dumping the Malaysia ROM now, I will rebuild and flash to my test device regardless of size difference and let you know the result. Give me a few hours though as i am very busy and doing this in 5 minute gaps when I a have chance.
Click to expand...
Click to collapse
You are great ! I am waiting for results.
leeston2379 said:
I have dumped the ROM twice and found that "Missing Manifests" are reported.
First time there were 3 missing, 2nd time 5 missing. The manifests are .dsm files so i am assuming that if the .dsm is missing from a package it is no longer a package and won't be included in the ROM by BuildOS causing the size difference.
This is purely speculation but I believe this particular ROM does not like to be dumped and you will have to use a different base rom.
I am rebuilding the ROM now and will flash it soon.
Click to expand...
Click to collapse
Maybe You are right but I hope You are not
So Your test will show the truth. I did not pay attention on this "Missing manifest" assuming that any errors stop dumping/building.
Regards
fxdjacentyfxd

---

Updated post #13

---

leeston2379 said:
I have dumped the ROM twice and found that "Missing Manifests" are reported.
First time there were 3 missing, 2nd time 5 missing. The manifests are .dsm files so I am assuming that if the .dsm is missing from a package it is no longer a package and won't be included in the ROM by BuildOS causing the size difference. The first dump also failed to separate the OEM and SYS packages but succeeded the second time
I have rebuilt and flashed the ROM and it appears to work, i do not have time to test it fully but it does boot and run with SPB Mobile Shell, HOWEVER as the two dumps had different .dsm files missing it may be something more important missing the next time causing a real brick.
This is purely speculation but I believe this particular ROM does not like to be dumped and you will have to use a different base ROM. I am happy for you to use mine but I would recommend one of Miros clean ROMs as a base.
Hope this is helpful
Attached is a photo of the output from the .bat file showing the missing .dsm files (this is from the second dump).
Click to expand...
Click to collapse
Thanks a lot for Your test. I have this manifest warning too doing dump process to text file. I have found somwhere in internet that some of this .dsm are concerned with XIP . Here if You wanna to see Nokser's thread not concerned with tg01 but mentioning some of the manifest files :
http://webcache.googleusercontent.c...fd3-bd127a05e4de.dsm&cd=1&hl=pl&ct=clnk&gl=pl
Anyway, could You explain me once again what build is running without brick ?
You simply did dump and build on malezya rom and took created .tsw or You dumped created rom again and built again and took this double built rom?
Regards
fxdjacentyfxd

---

fxdjacentyfxd said:
Anyway, could You explain me once again what build is running without brick ?
You simply did dump and build on malezya rom and took created .tsw or You dumped created rom again and built again and took this double built rom?
Regards
fxdjacentyfxd
Click to expand...
Click to collapse
I dumped the original ROM rebuilt it then flashed it. I did not double build.
Just dumped the rebuilt ROM and no errors occurred. It may be worth dumping the Malaysian ROM removing the packages you require then adding them to the Orange UK ROM as this dumps OK and both ROMs are in English.
The build of the Malaysian ROM is CE OS 5.2.21840 (Build 21840.5.0.60), just for reference.

---

leeston2379 said:
I dumped the original ROM rebuilt it then flashed it. I did not double build.
Click to expand...
Click to collapse
I am not familiar with the matter so far but I did simple test as in Nokser's thread about dumping XIP. I took xip.bin created after dumping malezya rom and dumped it via XipPort.exe. All "not available" manifest files are present so in my oppinion it should be possible to avoid this "terrible" warnings and maybe any new dump script is required for such original rom. This time it is my speculation
Regards
fxdjacentyfxd

---

leeston2379 said:
I dumped the original ROM rebuilt it then flashed it. I did not double build.
Just dumped the rebuilt ROM and no errors occurred. It may be worth dumping the Malaysian ROM removing the packages you require then adding them to the Orange UK ROM as this dumps OK and both ROMs are in English.
The build of the Malaysian ROM is CE OS 5.2.21840 (Build 21840.5.0.60), just for reference.
Click to expand...
Click to collapse
Hmmm, really ? I dumped English Orange ROM too. I do not remember whether mentioned warnings appeared but I am sure created rom was lesser than original rom like with Malezya rom.
Regards
fxdjacentyfxd