this is rom for new gene ie ht8xxxxx
nothing new just port xip sys for new gene
original rom
here is kitchen only work for new gene
part1 part2
extract all file in same folder
Thank you for the same. Just for the sake of curiosity, how much RAM is available free, on startup, in this ROM?
Hey Ankit, you did it yourself? have you found out the kitchen?
After reading the original thread, i guess there are many unsolved issues with this ROM. Calculator doesn't works, calender gives problem, powerpoint gives some certificate error, No java etc. And i think this also does not include Windows Live.
So i dont think its worth an upgrade. This ROM needs some serious tweaking before i can use it. I haven't installed this ROM but i got all this conclusion from the original thread. Is anybody's experience better with this ROM?
dheerajk27 said:
Thank you for the same. Just for the sake of curiosity, how much RAM is available free, on startup, in this ROM?
Click to expand...
Click to collapse
According to the author, you'll have about 29 MB. Haven't tested yet.
krazy_about_technology said:
Hey Ankit, you did it yourself? have you found out the kitchen?
After reading the original thread, i guess there are many unsolved issues with this ROM. Calculator doesn't works, calender gives problem, powerpoint gives some certificate error, No java etc. And i think this also does not include Windows Live.
So i dont think its worth an upgrade. This ROM needs some serious tweaking before i can use it. I haven't installed this ROM but i got all this conclusion from the original thread. Is anybody's experience better with this ROM?
Click to expand...
Click to collapse
yes i did it myself
i port xip sys first then use Ramersonw's Kitchen (some modification required )
i will upload kitchen tonight so u modify it
because my exam is there i not be able to Cook rom
can u post some screen shots plzzz..if u hav any
thnx
@ankit360: I would really appreciate it buddy if you share with me the details of the process of XIP porting you gone through. I want to learn the whole process as its quiet an important information to cook a ROM successfully. After knowing all this, i would be able to create ROMs and share them with our friends here.
Its really great man! you learned the process so quickly. Hats off to you!
Hey Ankit,
I tried this ROM. Its clean and ultra fast and very little problems. I am sure if they are ironed out, this could be an ultimate ROM for Gene. i have written about the problems in my previous post. In addition to those here is another one.
I tried installing windows live on this rom too but it didn't worked. Since this is a quiet clean ROM with no Windows Live in ROM, there is no possibility of any conflict. I think the problem is related to some certificates.
I examined my original WM 6 ROM and found that All the ROMs in this forum contains all the other certificates except these two from HTC on the top of the list, see the attached files.
I think this could be the cause of all the Windows Live problems as may be since these certificates are not present, windows live is unable to communicate with the server over an encrypted ssl connection.
What do you think?
I will try to extract these out of the ROM. You try yourself too and PM me if there is any success.
can u list out all bug so i will try to fix it
Just trying out your ROM, its lightning fast!
Thanks for the ROM
60 MB free after restoration of around 300 contacts! Wow, Gr8 Word
@ankit360: OK, here is the list of bugs:
1. Calculator is not working. Reports a missing file "\windows\spbcalc_p.gif".
2. Calender not working.
3. Java runtime is not included (if you correct this error and insert a java runtime, use the latest JBed version, it is the only runtime that can run opera mini fullscreen)
4. Powerpoint shortcut not working. It needs a change in registry. If you click the shortcut it will say some certificate thing but thats not true. The shortcut points to the shortname :MSPOWERPINT. These shortnames are created in registry and the path to powerpoint exe is not correctly given there. either correcting the path in registry or making the shortcut directly point to the powerpoint executable will correct this error.
5. Small bug but there is no option to set the device lock (password when the phone is restarted)
6. No Transcriber (Not really a bug but i need it)
7. Clock canot be set to 12 hour format. it always returns to 24 hour format.
8. Search feature that comes with default windows mobile has been removed.
9. Tabs in HTC home show up even when they are removed from settings>today>htc home setting. It happens sometimes only i think.
10. Windows Live not working at all even after installing the official cab. I tried about 10 cabs from this forum. Nothing worked. It confirms that the issue is not due to conflict with older version of live on ROM coz this ROM doesn't have windows live on it.
Thats all i can think of right now. Will post more if i find some.
man i don't have time to fix this issue bcoz my exam is there
i make kitchen for this rom work only for new gene
try to fix bug and release some nice rom
happy rom cooking
part1 part2
extract all file in same folder
Hey ankit,
I have succeeded in porting the XIP of the default kitchen given by Ramersonw by using my original Wm 6 XIP as base. I have created a ROM based on that kitchen which i will post tomorrow as i am currently uploading both of these.
The kitchen is working perfectly for new GENE and i am 90% sure that i'll be able to port most of the ROMs using this kitchen. Will post kitchen on the Ramersonw's thread also.
that's grate news plz post only xip or changes u made is default kitchens i will not able to download whole because i don;t have enough bandwidth
Hi Ankit,
I am uploading the zip file with changes only. Here is the link for it. And dont forget to read the Readme.txt i have included in it. I am also uploading the ROM i created. Wait for the new ROM thread. Here is the address for the zip file:
http://cid-988261b694475a67.skydriv...gesOnly|_for|_NewGene|_Kitchen|_Ramersonw.zip
thanks for sharing file i will test it
i want to know is ur xip porting procedure is work on different gene rom ?
my xip port procedure work on only this rom
My XIP will work on any ROM which has the same version of WM 6.1. Actually buddy, as you might already know, what happens is that XIP contains a portion of the main files of the WIndows Mobile operating system which are executed without loading into main ram. That is why this part is called XIP (eXecute In Place). So These files have to be the exact same version as the rest of the OS. My XIP is from CE OS 5.2.20931 (Build 20931.1.5.0) so all the ROMs that use this version of WM 6.1 can use this XIP as base.
And this is true for your ROM too. You can use the XIP with any ROM with same version and build no.
I hope i have made myself clear but feel free to ask more.
thanks for info man i really don't known this
Sorry for bumping this.
I have installed this ROM, And I really liked this. It has fastest responce times, and the most Available RAM, from all the ROM's for Gene(More than 25% using even after 2 Hrs of use.)
So Ankit or Sumit, if you have time, will you please modify this rom (I still need to learn cooking.)
Download Java - JBed
Attached the spbcalc_p.gif. Placing it in windows dir, works.
Thanks
Sumit
brother Sumit / Ankit: Please cook and release for Old Gene also.
Related
Hi just wondered if there where any new downloads to get for my NIKE. These are my settings at the moment.
Rom Version - 2.09.721.2 WWE (I know there is a 2.12.707.2 but can't locate it )
Radio Version - 1.71.09.01
Protocol Version - 25.75.40.02.eMoH
OS Version - CE 5.2.20765 (Build 20765.1.4.4) - tried 21014 and 21109 but these have bluetooth issues.
If anyone can post the link for any downloads that would be great.
Thanks
DT
Currently cooking with IOLITE 20765 SYS and ROM and IOLITE OEM 5.50
d_train said:
Hi just wondered if there where any new downloads to get for my NIKE. These are my settings at the moment.
Rom Version - 2.09.721.2 WWE (I know there is a 2.12.707.2 but can't locate it )
Radio Version - 1.71.09.01
Protocol Version - 25.75.40.02.eMoH
OS Version - CE 5.2.20765 (Build 20765.1.4.4) - tried 21014 and 21109 but these have bluetooth issues.
If anyone can post the link for any downloads that would be great.
Click to expand...
Click to collapse
In the past, we usually wait until some kind soul, namely jerpelea, has ported the ROMs over completely.
There is a new release, but it is not fully ported yet, and some work is required:
http://forum.xda-developers.com/showthread.php?t=491470
My test build looks promising, but it does swell the ROM significantly.
rling said:
In the past, we usually wait until some kind soul, namely jerpelea, has ported the ROMs over completely.
There is a new release, but it is not fully ported yet, and some work is required:
http://forum.xda-developers.com/showthread.php?t=491470
My test build looks promising, but it does swell the ROM significantly.
Click to expand...
Click to collapse
When you say some work - I assume you mean extracting the nb files and converting that to the SYS and OEM folders?
Sorry if it sounds like a dumb question, still very new to the ROM thing.
Am I also right in saying that the XIP (ROM) can only be a Niki one, but the SYS and OEM folders can be more generic (QVGA of course)? SYS is the actual WM6.1 OS and OEM is additional Apps or amy I way off on a tangent ?
thanks for all your help rling - you have been a of great assistance to a cooking noob
DT
Okay have grabbed the XIP and SYS 21032 from the link you gave me rling - thanks.
I have worked through the tutorial - http://forum.xda-developers.com/showthread.php?t=438676
The only thing that confuses me a little is the maps.txt files - I couldn't see any errors indicated by !!!!!!!!!!!!!!!!!!!!!!!! So am I safe to say that it should be a go for cooking? I have attached the final map.txt file.
I also noticed that the SYS dierectory doesn't have a .VM folder like the older ones I have used - did I miss a step somewhere?
Thanks
DT
d_train said:
When you say some work - I assume you mean extracting the nb files and converting that to the SYS and OEM folders?
Click to expand...
Click to collapse
That's the easy part.
Am I also right in saying that the XIP (ROM) can only be a Niki one, but the SYS
Click to expand...
Click to collapse
Generally yes. However, sometimes, if the XIP and SYS are mismatched, you could end up with some unexpected problems, eg bluetooth, camera, and other hardware failures.
Make sure you have the .rom and .vm folder correct in the SYS folder before cooking, or the ROM will hang at bootup.
rling
I can't find a .VM folder with the 21032 SYS I downloaded - have I missed something?
DT
If I remember, just use your original .VM and .ROM SYS folders if you want to port a SYS...
That was the bad thing with jerpelea : he did everything for us so we didn't have to use our brains anymore to cook .
For OEMs, you can use any QVGA package you find in the ROM you're trying to port, but keep the Nike OEMDriver folder if you want to be sure.
For the XIP porting, I never did it by myself since hexa adresses are not my cup of tea... Maybe someone will do this hard job for us...
Okay I used XipporterEX 1.2.R31 to automatically port the xip. Just a question, in the sys folder (under myTools in the Xipporter directory) there is now a .ROM and .VM and a dump folder. Is this the .VM folder I need and does the contents of the dump folder go into the ROM\XIP folder of the kitchen?
Hope all this makes sense
Thanks
DT
rling said:
Make sure you have the .rom and .vm folder correct in the SYS folder before cooking, or the ROM will hang at bootup.
Click to expand...
Click to collapse
Is this where the hex editing comes into play because I can't actually find how to create the .VM and .ROM folders and their files.
I guess my porting skills are poorly lacking
Can a porting GURU please port 21028 and 21032 to NIKI PLEASE PLEASE PLEASE
Or can a Guru take me under their wing and teach me the black art of porting
Might have to ask either BlackDragon or jerpelea nicely. These are the only two that I know of that have released XIP/SYS ports for the Nike in the Kitchen thread.
Since jerpelea and Blackdragon have gone fo new devices, we should learn XIP porting by ourselves if we want to make our Nikes better in the future...
I'm going to try to port 21032 XIP with XIPAddrTool I think, that's the only tool I know about it...
May the spirits of our cooking gurus protect me
Antubis said:
May the spirits of our cooking gurus protect me
Click to expand...
Click to collapse
Good luck my friend, hopefully you can do a better job than me.
May the cooking spirits be favourable to you
DT
Antubis said:
Since jerpelea and Blackdragon have gone fo new devices, we should learn XIP porting by ourselves if we want to make our Nikes better in the future...
I'm going to try to port 21032 XIP with XIPAddrTool I think, that's the only tool I know about it...
May the spirits of our cooking gurus protect me
Click to expand...
Click to collapse
Good luck.
Here's a link of more ROMs (Diamond) including 21189:
http://forum.xda-developers.com/showthread.php?t=467460
d_train said:
...hopefully you can do a better job than me...
DT
Click to expand...
Click to collapse
I don't think so
When I try XipportEx, the ported XIP doesn't boot (maybe that's because of the fact he puts 3 of the XIP modules into an OEM package ?)
When I want to use XipAddrTool, I've got a problem with Xipport : he dumps the xip.bin, but I get an exception when I want to make XIP packages... Maybe I did something wrong with my Vista, in the past I managed to obtain it easily...
[edit] : I just think I may launch it using admin privilege that afternoon... ^^'
Okay I got the ROM 21028 (and phone) to boot.
I used XIPporter to create the os.nb.payload file - what I could never work out (and can't find the answer to) is what in the world goes into the XIP folder. I found someone had placed a link to download the ROM and SYS for the Topaz (ver 21028) so I downloaded it and used the XIP folder from it and it worked. So you could say I sort of cheated - so if anyone can enlighten me as to what goes in the XIP folder for a ROM and where the heck I get the files from it would be greatly appreciated.
As far as the SYS goes - I also used it successfully - well it booted okay. But the customisations never ran and you can't change the today theme, even though they are there, selecting them changes nothing. Can someone guide me as to what I need to look for to get this working? I never got to test too much else at this stage - needed my phone working okay for work tomorrow, so had to flash back to a know working ROM - hope to update soon.
How do you take a screen capture image of your phone's screen so I can show some pictures of the tests??
Regards
DT
I have looked at the Calc from 21028 and I actually don't mind it, however it appears it is missing a font or something as the menus and title are boxes and not text...anyone offer any advice?
DT
d_train said:
I have looked at the Calc from 21028 and I actually don't mind it, however it appears it is missing a font or something as the menus and title are boxes and not text...anyone offer any advice?
DT
Click to expand...
Click to collapse
That would be missing the language pack. There is one ported for Hermes, but it is all in Chinese!
See how I go this week with time. Might just dip my toes into porting the ROM from scratch.
d_train said:
How do you take a screen capture image of your phone's screen so I can show some pictures of the tests??
Click to expand...
Click to collapse
There's a free program called SPB screenshot. Do a google. It's great. Can do single or multiple shots. Saves all the pics in My Documents folder for transfer to PC when you connect.
Have ported the 21032 XIP, and it appears to work in place of the 21014 in my ROM
SYS porting not working - locks up during boot at the red lettering page...
rling said:
Have ported the 21032 XIP, and it appears to work in place of the 21014 in my ROM
SYS porting not working - locks up during boot at the red lettering page...
Click to expand...
Click to collapse
fantastic - I got mine booting, but the customisations never ran - so the install was only half done - couldn't change the timezone (kept resetting) and minor glitches
Can you upload your ROM? Maybe I can test it with my SYS.
Where did you get the files from for the XIP directory? I can't find any info as to where these come from - or are they the same for all ROMs (like the .ROM and .VM within the SYS)
DT
Dear Friends and Friend Chefs ,
As you all know that i was working on creating XIP for our beloved Gene that is supports all the new features (mostly hidden from causal user, but even then very useful) that were introduced in WM 6.1 and carried forward with some enhancements in WM 6.5. The most important feature we were missing was the new improved virtual memory management model that 6.1 offers to solve the windows mobile version of the "DLL Hell" problem, Windows Developers may know about this
At the Core of this issue is the file initvmmap.exe which initializes the extended slot VM model when the device starts. This file was introduced in WM 6.1 but chefs never added it to the XIP because they were told that they should never insert anything new into the XIP. BTW, when people said that they were not wrong, but as always in this biological world, exceptions do exist . Since original Gene XIP was either WM 5 or 6, initvmmap.exe was always missing, causing the system to use older model.
Along with that, although its not much used, but the Storage Card encryption filter driver was updated in Wm 6.1. In WM 6 it was called encfilt.dll but in WM 6.1 upwards, its called mencflt.dll. I dont know the benefits of using it exactly, but the fact is it is newer and perhaps better in some way.
None of the previous ROMs were having these two features in them.
Today, i was successful in porting these features on Gene XIP and now we have an original manufacturer made identical WM 6.1 and 6.5 feature complete XIP for both old and new gene. These xips have made debut in WM 6.1 Pro Users ROM v2.7.
So i insist all chefs to download and use these XIPs as base while porting/making ROMs for Gene. This will make sure your ROM is providing the users with full experience of the Windows Mobile OS.
Thanks!
Background: It was not that hard inserting these files into the XIP.
Initvmmap.exe has a fixed E32 address of 0x00100000 and O32 address of 0x00130000. This is just like we have fixed addresses for device.exe and filesys.exe for both old and new gene. So after observing this in XIPs of about 10 devices, i just copied the file and it worked.
Mencflt.dll was looking like a problem at first but using the same addresses as encfilt.dll worked.
I also took some registry entries from WM 6.1 Emulator image's XIP (these were same in the 6.5 emulator image's boot.rgu, which i got from Ankit (a big thanks goes to him for making me aware of this fact.)). These entries direct the loader of OS to use the new memory model and use initvmmap.exe for that.
Download the XIPs
XIPs in Dumped Format
XIPs in XIP.bin Format
Please Note: You may notice that even though these XIPs are complete, these dont have hd.dll and oxa*.dll. I have left these files because these are only used for debugging purpose when a new build of Windows mobile is being made by Microsoft developers or at HTC. These are not useful for normal users in any way. Removing them only saves space in the XIP, hence free ram.
Also, although these XIPs are fully compatible with 6.1 memory model, 6.5 extended this model by adding a large amount to the available VM space and slots, which is only posssible using a compatible nk.exe in our xips. This ain't gonna happen most likely.
Thanks Krazy for the new XIP's
To use your new xip's in the cooking, do we have to just replace the xip folder with the one you have uploaded after extracting the rom and rebuild it.
If possible can you tell us know how to incorporate this new xip's in rom cooking.
That will be very great of you for new chef's like me.
Thank you!!!
Thank you Sumit. You really rock!
By the way, best of luck for your interview...
Thanks all of you guys!
Actually the XIP is currently ported for WM 6.1 21051. To use it for any other SYS, just take MSXIPKERNEL and MSXIPKERNELTK packages from the new XIP and replace the packages in this XIP and then relocate the addresses using original addresses in this XIP. It should be used as usual as you were using the original WM 6 xip as base for porting. You can also use XIPPorterEX.
Though going overhead a bit, but will try.
If successfull, I will be familiar with the XIP porting.
Thank you Krazy......
Ported 21815 XIP according to your XIP address, and amazing.... it work well on OG.
Thank you, NOW all CHEFS have to include INITVMMAP in their XIP.
it's nice to see we start thinking about XIP which r most untouch since long time
i want to ask some question did u also make changes in Nk.exe if not there is no use of all this because its required some slot to initvmmap.exe to work (correct me if i m wrong)
is its possible to patch nk.exe ? do you have any link or documentation where we learn how to patch nk.exe + add slot in it ?
@Ankit360
I think this is what you are looking for.
http://forum.xda-developers.com/showpost.php?p=3806368&postcount=1017
Though I could not understand a bit of it.
@Ankit: No nk.exe for WM 6 and WM 6.1 is same. Its different for WM 6.5. And ya its my mistake too, i shouldn't have called the XIP fully WM 6.5 compatible. Actually the story goes like this:
In WM 6, when an executable loads, its DLLs are loaded in Slot 0 along with the exe itself. And the memory architecture of WIndows Mobile is such that this creates problem when multiple programs are running at the same time. For more info, you can read the Windows Mobile Team Blog's Two part Tutorial : "Slaying the Virtual Memory Monster".
Now in WM 6.1, there was a new structure which uses the initvmmap.exe to initialize the VM in such a way that dlls that are not in XIP and are more than 32 KB is size are not loaded in Slot 0, instead they are loaded in Slot 60 and 61 (dont remember the number correctly though, these are the last slots. Which solves that problem to a greater extent. And this is the level upto which my XIPs are working.
In WM 6.5, this architecture was furthur enhanced by extending the number of slots available by a huge percentage, i guess its double or more. This gives applications more virtual memory than previously possible and allows loading of more DLLs in module format. But enabling this extended VM layout needs a new nk.exe that can support it. It also requires at least 128 MB of RAM if i am not wrong. Thats why we may never have it. There is no patching of nk.exe, an altogether new nk.exe is required. And this is the reason why we need to recmod the modules of IE and Flash in our WM 6.5 ROMs to get them working properly. WM 6.5 SYS has larger number of modules due to availability of more VM space.
I hope this had cleared up some things for you.
krazy_about_technology said:
@Ankit: No nk.exe for WM 6 and WM 6.1 is same. Its different for WM 6.5. And ya its my mistake too, i shouldn't have called the XIP fully WM 6.5 compatible. Actually the story goes like this:
In WM 6, when an executable loads, its DLLs are loaded in Slot 0 along with the exe itself. And the memory architecture of WIndows Mobile is such that this creates problem when multiple programs are running at the same time. For more info, you can read the Windows Mobile Team Blog's Two part Tutorial : "Slaying the Virtual Memory Monster".
Now in WM 6.1, there was a new structure which uses the initvmmap.exe to initialize the VM in such a way that dlls that are not in XIP and are more than 32 KB is size are not loaded in Slot 0, instead they are loaded in Slot 60 and 61 (dont remember the number correctly though, these are the last slots. Which solves that problem to a greater extent. And this is the level upto which my XIPs are working.
In WM 6.5, this architecture was furthur enhanced by extending the number of slots available by a huge percentage, i guess its double or more. This gives applications more virtual memory than previously possible and allows loading of more DLLs in module format. But enabling this extended VM layout needs a new nk.exe that can support it. It also requires at least 128 MB of RAM if i am not wrong. Thats why we may never have it. There is no patching of nk.exe, an altogether new nk.exe is required. And this is the reason why we need to recmod the modules of IE and Flash in our WM 6.5 ROMs to get them working properly. WM 6.5 SYS has larger number of modules due to availability of more VM space.
I hope this had cleared up some things for you.
Click to expand...
Click to collapse
thanks for reply i got it now, there is any way to see that initvmmap.exe is working or not ?
There is, but its not that straight forward as initvmmap does its work at the very begining of the OS loading process, even some files in XIP are not executed by then so its a bit tricky to record. But i will post a method for it, one of my friend at microsoft once told me about it.
ankit360 said:
thanks for reply i got it now, there is any way to see that initvmmap.exe is working or not ?
Click to expand...
Click to collapse
Go to HKLM/init. If you can see initvmmap, it should work.
As my friend Helloworld1 said that If we are using native 6.5 or 6.1 NK.exe, it will not even boot without this.
so anybody interested to make native 6.5 nk.exe for gene ?
ankit360 said:
so anybody interested to make native 6.5 nk.exe for gene ?
Click to expand...
Click to collapse
Still looking for more info about it.
Does it possible to ask in PPCGeeks forum?
I think everybody there more interest in New SYS, they give fast response for question related to NEW SYS, but slow for others.
i m stuck at certain point in both patching XIP + android on Gene project , there is two reason for this first is, i don't know what exact IC and Part use in gene
second is i don't know how to see Code in dll and exe file .
We have to use platform builder to make native NK.exe work well on our device, I don't know how to operate the tools.
BesFen said:
We have to use platform builder to make native NK.exe work well on our device, I don't know how to operate the tools.
Click to expand...
Click to collapse
give me link whatever u saw about platform builder, i will try
Ankit, if you are following the Conflipper's WM 6.5 kitchen thread at PPCGeeks, you may know that i have asked DA_G about nk.exe. He said that all the devices that are currently having the 6.5 native nk.exe had test roms built by microsoft itself at one time. So the kernel nk.exe for those devices was recompiled against teh 6.5 codebase. We cannot do it right now ourselves as we dont have the source code for kernel and WM 6.5. Futhermore, he said that the nk.exe combines both device specific hardware initialization code as well as WM 6.5 code in it which makes it almost impossible to do it. But he added that a clever hack using a disassembler might do the trick. He is also searching for such hacks so that all the devices can have native WM 6.5 kernels.
One more thing, devices with 64 MB RAM can have native 6.5 kernel, it has nothing to do with the RAM size. I apologize for conveying wrong information previously in this thread, but i wasn't aware of it.
I dont know about the ICs used in Gene but to view code in DLLs and EXEs you use a Disassembler. IDA Pro is a great tool for that purpose and all the senior guys here like da_g use it. But its paid so.... BTW, you wont get full C or C++ source code with it, it emits assembly code.
Platform Rebuilder i dont think can do this, are you 100% sure about it besfen?
krazy_about_technology said:
Platform Rebuilder i dont think can do this, are you 100% sure about it besfen?
Click to expand...
Click to collapse
Platform Builder 5, Not Platform rebuilder.
It is development tool kit for win mobile, You can download it from Microsoft site. But still need native BSP ( I don't know what is this)
Information I get that native BSP is device depended and can be hardly downloaded from legal way. They are licenced to oem.
I think it hard to make it for GENE.
OK, i got your words wrong. Ya Platform Builder kit is a way to do that but BSP (Board Support Package) is needed for compiling the OS kernel and driver code is also needed to be recompiled in some cases. This is specific to the device's motherboard configuration. You are right, its not legally possible to download and use it as its only liscensed to the manufacturers. Otherwise, guys like Da_G and Conflipper had done this way before Anyways, they are still looking for something so our chances are not all gone.
Thanks for all the great cooks....
My inspiration 4 releasing this kitchen is Mr.Krazy , But I think he is also going to release this updated rom soon with a new kitchen.
I just tried to do one myself.
I know there are many fine cooks here and all are happy with the new 6.5 I know they wont expect wm6.1, But as a cook i like to try the new roms. But i am not releasing the rom, just the kitchen.
I tried my level best to port the XIP for both new and old Gene, But i only tried on old gene.
For kitchen tools, I used and both worked fine (for old gene only, I dont have new gene)
(Ramersonw's Kitchen for Gene)
http://forum.xda-developers.com/showthread.php?t=464632
(BesFen's Kitchen)
http://forum.xda-developers.com/showthread.php?t=505156
For Sys and original rom Xip and language Packs, I recompiled the packs for gene.
Da_G's
http://forum.xda-developers.com/showthread.php?t=547314
For OEM i used
ankit360 Ingredients to Cook ROM
http://forum.xda-developers.com/showthread.php?t=544966
I dint modify any files in sys Its been 3 days i tested. Its fine.
(with PP 6 starting was 24 mb and after 2days its 19 mb)
I dont have to warn about rom cooking. As you cooks know all.
Download Here and post review, It took hours of learning.
wm6.1_Build 21054 SYS and XIP (ported for new and old gene)
Good..
Do you use an Old Kitchen or New Kitchen (Base on Platform rebuilder)???
BesFen said:
Good..
Do you use an Old Kitchen or New Kitchen (Base on Platform rebuilder)???
Click to expand...
Click to collapse
Hi i used your Build_WM6.1_ROM.cmd from DUMP & REBUILD ROM from this thread
[16 August 09|TUTORIAL|XIP+SYS] MSXIPKernel + MSXIPKernelLTK & SYS of Build 23025
http://forum.xda-developers.com/showthread.php?t=505156
I gave the links for the tools and i mentioned your thread also
Battery Backup
tvk24 said:
Hi i used your Build_WM6.1_ROM.cmd from DUMP & REBUILD ROM from this thread
[16 August 09|TUTORIAL|XIP+SYS] MSXIPKernel + MSXIPKernelLTK & SYS of Build 23025
http://forum.xda-developers.com/showthread.php?t=505156
I gave the links for the tools and i mentioned your thread also
Click to expand...
Click to collapse
Hey buddy,
How about the battery backup in this ROM? Since in Krazy's ROM, I was getting just one day of battery backup.
yours_vinodh said:
Hey buddy,
How about the battery backup in this ROM? Since in Krazy's ROM, I was getting just one day of battery backup.
Click to expand...
Click to collapse
To be honest it came 1 day. But i was testing with some packages and av files. And did normal use of calls and texts.
tvk24 said:
To be honest it came 1 day. But i was testing with some packages and av files. And did normal use of calls and texts.
Click to expand...
Click to collapse
try to make 0 module in slot 0 partitions, it can increase the battery back up, mine is 2,5 days with active exchange mail.
BesFen said:
try to make 0 module in slot 0 partitions, it can increase the battery back up, mine is 2,5 days with active exchange mail.
Click to expand...
Click to collapse
hey buddy can u explain in simple steps how to do this?
ams1576 said:
hey buddy can u explain in simple steps how to do this?
Click to expand...
Click to collapse
Convert some module to file.
tvk24 said:
Hi i used your Build_WM6.1_ROM.cmd from DUMP & REBUILD ROM from this thread
[16 August 09|TUTORIAL|XIP+SYS] MSXIPKernel + MSXIPKernelLTK & SYS of Build 23025
http://forum.xda-developers.com/showthread.php?t=505156
I gave the links for the tools and i mentioned your thread also
Click to expand...
Click to collapse
Why don't you use new kitchen base on platform rebuilder?? it can be use both for wm 6.5 and wm 6.1, it more simple, no need to port xip, you can follow my tut.
Good..
How Says everybody into 6.5? Eh? Atleast I am still in 6.1. With Sumit's VM Ultimate 3.1.1.
Its great someone is still interested in developing 6.1. I always find 6.1 in much better than 6.5 in Usage wise. All apps run smooth. Doing great, So keep it up pal, I was so upset Sumit's no longer relesing 6.1 developments. Now we have you.
Great Going!
Its not true that i wont release 6.1 now. There were no new builds since long and ever since this 21054 has came out i am on phone internet so i cannot post it. I have already made the ROM from it and it works nice and well.
As Besfen has pointed out and also from the word of one of my other friend in forum, the problem with new 6.1 builds is that there are larger sized and a bit more modules in the recent builds which cause the slot 0 to fill more. This causes decrease in available virtual memory and drainage of battery. I was not aware of this issue till i built the 21051 build, Pro Users ROM 6.1 Edition version 2.7. The new ROM that i have built is not having the power issue and i got 2.5 days of battery with quiet heavy use.
The trick is to recmod (covert to dll) the modules which are heavier in size, like say more than 150 or 200 kb. Plus we also have to keep in mind that we dont recmod resource only modules, the modules which dont have code inside them. Resource only modules are automatically relocated in SLOT 63 as according to Da_G and recmodding them will actually cause them to be allocated in slot 0 dynamically at the runtime (when we actually use them in out phone). These modules generally have names ending in "res" or sometimes, the word comes in between the name. To really verify this, you need to open the module in a program like PE Explorer and check that it should not have a .data or .text segments. Resource dlls only have .rcdata segments. For more information on these segments and all, you will need to understand the intricacies of "The PE File Format" which is available on MSDN, just search for it.
krazy_about_technology said:
Its not true that i wont release 6.1 now. There were no new builds since long and ever since this 21054 has came out i am on phone internet so i cannot post it. I have already made the ROM from it and it works nice and well.
As Besfen has pointed out and also from the word of one of my other friend in forum, the problem with new 6.1 builds is that there are larger sized and a bit more modules in the recent builds which cause the slot 0 to fill more. This causes decrease in available virtual memory and drainage of battery. I was not aware of this issue till i built the 21051 build, Pro Users ROM 6.1 Edition version 2.7. The new ROM that i have built is not having the power issue and i got 2.5 days of battery with quiet heavy use.
The trick is to recmod (covert to dll) the modules which are heavier in size, like say more than 150 or 200 kb. Plus we also have to keep in mind that we dont recmod resource only modules, the modules which dont have code inside them. Resource only modules are automatically relocated in SLOT 63 as according to Da_G and recmodding them will actually cause them to be allocated in slot 0 dynamically at the runtime (when we actually use them in out phone). These modules generally have names ending in "res" or sometimes, the word comes in between the name. To really verify this, you need to open the module in a program like PE Explorer and check that it should not have a .data or .text segments. Resource dlls only have .rcdata segments. For more information on these segments and all, you will need to understand the intricacies of "The PE File Format" which is available on MSDN, just search for it.
Click to expand...
Click to collapse
Nice tut.ThanksHere is more abou it
http://www.everythingdiamond.info/showthread.php?t=490
I have cooked a tranitional chinese using 23518 and manila 2.5 with OEM driver 2.00.4. It work and very stable. When I cooked with OEM driver 3.003b, it hold at startup screen. Can anyone help me to point what thing I missing?
I only replace the 3 folders "OEMDrivers, OEMDriversHigh and OEMMISC" that extracted from 3.003b official Rom. How about the xip I also need to amend in cooking kitchen? Because it contain some folder named OEMXIPkernal inside the File & module folder. Thanks!
I think you can try the 3.003 driver from Rafyvitto. It contains the 3 directories that you mention
http://www.4shared.com/file/223023852/7cc1ad29/Rafyvitto_Cleaned_3003b_oem_dr.html
btw...i am trying to cook a traditional chinese rom too...but i think i screw up somewhere in the xip..
加油
我等著你完成繁體中文版
I have finished the ROM and testing for few day. However it show the the beta expire message and the used 23518 source contain the timebomb. I don't know how to remove it !!!
Maybe you can try the 23549 to replace 23518.
Can you teach us how to cook a rom ?
use chinese.
sallust said:
I have finished the ROM and testing for few day. However it show the the beta expire message and the used 23518 source contain the timebomb. I don't know how to remove it !!!
Click to expand...
Click to collapse
To remove the time bomb from beta build you need to patch the s000 module in sys/shell/shell.32.exe/s000 using the tool i attached, and then recook, good luck
rafyvitto
Very thank ,rafyvitto
I have found this patch before and now I am testing with my ROM.
Is there anyone can tell me How to get drivers From The official ROM
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