Hello,
Is there someone in the forum, who knows that a file or module is responsible for the platform versions of Build WM Standard
THX for Help
There is no one any ideas
That someone may have a concept of module aygshell.dll. Namely that the reason to block me all the keys on the porting ROM 21xxx or 20xxx
Related
I ever customized several wizard roms, but regarding porting ROM, I'm a newbie.
Let's think about two scenarios:
1. If I got an AKU 3.x ROM of other phone, i.e., a ROM of Artemis
2. If I got a WM6 ROM of other phone which version is newer than any current known ROMs, i.e., a Hermes WM6 ROM
If I want to port the ROM to run on a wizard, what are the most important files, modules, drivers or something like XIP section we need to port? are there any different steps when porting within those two scenarios? Will somebody make a brief introduction or write a tutorial here?
Bepe, mUn, Faria and other talent guys, I know you're expert on this, please show me your hands and help on this, thank you.
I am too learning this ... seems pretty tricky if not near impossible without proper XIP section. Meaning that if you want to port WM6 to a device that didn't had a WM6 it's impossible ... or very close to that.
Take this as an example http://forum.xda-developers.com/showpost.php?p=1243434&postcount=172
Not the actual files, those are device specific (xip.bin for example) but a little guide.
anichillus said:
I am too learning this ... seems pretty tricky if not near impossible without proper XIP section. Meaning that if you want to port WM6 to a device that didn't had a WM6 it's impossible ... or very close to that.
Take this as an example http://forum.xda-developers.com/showpost.php?p=1243434&postcount=172
Not the actual files, those are device specific (xip.bin for example) but a little guide.
Click to expand...
Click to collapse
thanks, that's great
hi all!
i am looking for documentation about mixing rom parts from different device...
let me explain:
i noticed that some cooked roms uses drivers from polaris, kernel and system from kaiser.
but i don't know exactly wich part of kaiser rom i need to use....
can anyone help me to learn this?
Hi,
Does anyone know (primarily ROM Chefs etc...) if the Kaiser TLR (see link bellow) work without adverse affects if i compile a ROM using the latest official ROM from HTC? Ive done whats required to make the "TLR'ed" ROM with the latest build and it built the new nbh file without any problems, i just dont know if it will work properly if you know what i mean.
But if anyone knows a way to rebuild these TLR files could you point me in the right direction.
The link mentioned above
http://forum.xda-developers.com/showthread.php?t=338820
Thanks in advance.
Hello Seniors,
I have a Tytn II with normal Rom version 3.29.707.0 WWE
Radio Version is 1.65.16.25
I am very new to this ROM cooking & flashing thing but it looks amazing & interesting to see how you make your devices look mesmerizing with all those features that you work upon. I read few instructions about how to install these cooked roms with RUU files..But due to lack of knowledge & experience, it doesn't seem to be working for me. I am looking forward to a Manila 3d or 2d rom's .cab file which comparatively is easier to install. Can someone please help me with a file or a link from where i can get a working Manila or any other Touch 3D rom's .cab file that i can use for my Kaiser..Your help will be highly appreciated.
I found one working .cab file for Manila 2d but it doesn't work in landscape mode.
vicky_crispy said:
Hello Seniors,
I have a Tytn II with normal Rom version 3.29.707.0 WWE
Radio Version is 1.65.16.25
I am very new to this ROM cooking & flashing thing but it looks amazing & interesting to see how you make your devices look mesmerizing with all those features that you work upon. I read few instructions about how to install these cooked roms with RUU files..But due to lack of knowledge & experience, it doesn't seem to be working for me. I am looking forward to a Manila 3d or 2d rom's .cab file which comparatively is easier to install. Can someone please help me with a file or a link from where i can get a working Manila or any other Touch 3D rom's .cab file that i can use for my Kaiser..Your help will be highly appreciated.
I found one working .cab file for Manila 2d but it doesn't work in landscape mode.
Click to expand...
Click to collapse
Firstly this should be posted in the software section as it has nothing to do with rom development. Had you posted in software you would have seen this.
http://forum.xda-developers.com/showthread.php?t=489749
And welcome to XDA, read much, search for answers before posting and above all have fun with your phone.
Manila 2D was ported from devices that do not have slide out keyboards, that is why it does not work in landscape. For more on M2D see my titorial here.
http://www.htcwiki.com/page/Manila+2D+and+M2D+Themes
what exactly are development branches? I read that "development branches" are device specific. are they just build numbers where support for a specific device was introduced? I noticed that both "build numbers" (starting with wm 6 I think) and "development branches" have 5 chars. do development branches refer to just the os part of a rom or the entire rom? if so does each manufacturer add specific files (I'm thinking this explains the 'SYS' dir when dumping a ROM) like drivers and such?
is there a thread listing WM 6.1 build numbers - all I can find is WM 6.5.3 build numbers (can anyone at least offer a hint regarding what build no. does WM 6.1 end and 6.5 start?)
does the XIP part of a rom have anything to do with the development branches? is it different for each development branch?
I noticed the XIP is extracted from the FAT region of the OS and after *fast* reading some topics on Win CE on msdn I take it it contains core os files for the WM os (kernel and core dll's etc) - is this right?
I also noticed a lot of fuss about the XIP in the cooking/kitchen forums; seems one may end up with an unbootable device if an improper XIP is added to a custom rom - can anyone explain?
I'd also appreciate if someone could explain what the following parts of the OS section of a dumped rom are responsible for:
fatheader.bin
fatimg.bin
imgfs.bin
minios.bin
thanks.