Hello my friends,
I cook roms for Htc HD2 and HTC Elf/Elfin.
I cook only with com2 builds because i don't like the com3/com5 style.
For the moment, the lateste com2 build is old, and there is no update.
I would like to test mixing a Com3 or Com5 XIP with my latest Com2 SYS.
In fact, i hope that using a Com3 or Com5 xip will be able to make a faster rom.
What do you think about it ?
Thanks a lot,
regards,
Nixeus
I dont think you will get a bootable ROM with COM3 XIP and COM2 SYS.
But you will get a bootable ROM with COM5 SYS and COM3 XIP and viceversa.
Nixeus said:
Hello my friends,
I cook roms for Htc HD2 and HTC Elf/Elfin.
I cook only with com2 builds because i don't like the com3/com5 style.
For the moment, the lateste com2 build is old, and there is no update.
I would like to test mixing a Com3 or Com5 XIP with my latest Com2 SYS.
In fact, i hope that using a Com3 or Com5 xip will be able to make a faster rom.
What do you think about it ?
Thanks a lot,
regards,
Nixeus
Click to expand...
Click to collapse
FrankenROM taken to this extreme is an interesting concept. It may or may not boot, but I wonder if you will have issues, not only with OS/SYS/XIP incompatabilities, but also with OEMDrivers, too. You'll probably be ok as long as you have a native 6.5 nk.exe, but it seems like a bunch of trouble to go through for, at best, what might be a marginal increase in speed.
You'd probably be better off going back to a 6.1 build, strip out all of the oem stuff and then layering on something like mobile shell or a lightweight ui alternative to sense.
Best regards,
-boggsie
I dont think a COM3/COM5 XIP will be faster than your COM2 XIP... just my opinion.
Thanks for your answers ! Hope a new com2 !
Mixing COM2 with any bottom start builds is a strange and bad idea.... Mixing COM2 XIPs with COM3-5 SYS - also causes non bootable rom...
But if you wanna have fun - it's up to you
Nixeus said:
Hello my friends,
I cook roms for Htc HD2 and HTC Elf/Elfin.
I cook only with com2 builds because i don't like the com3/com5 style.
For the moment, the lateste com2 build is old, and there is no update.
I would like to test mixing a Com3 or Com5 XIP with my latest Com2 SYS.
In fact, i hope that using a Com3 or Com5 xip will be able to make a faster rom.
What do you think about it ?
Thanks a lot,
regards,
Nixeus
Click to expand...
Click to collapse
Most succesful thing you may make is to 6.1ize 21916 and remove whole honeycomb(and replacing it by i.e quick menu + startbutton) + remove 6.5 themes(or let me name it more correct: WHOLE 6.5's THEMING system:
(main part of idea:
Code:
[HKEY_LOCAL_MACHINE\System\GWE]
"EnableLayeredWindows"=dword:00000000
)
) + obvious sys optimizations, of course.
Such system is VERY fast. You are losing new style menus too, but overall performance gain, and in some cases battery lifetime is quite HUGE.
And i am not talking about some ridiculous benchmarks, i am talking about real data operating performance(i am squeezing out every possible performance gain in these machines for years for personal purposes, y'know..that build mixes 6.1 look'n feel with big flash/gfx/media improvements over 6.1, itself is still slower than 6.1, but is is really levelled out with other advantages, imho).
Your idea of mixing com2 with comx is as impossible as mixing winCE with 6.x(what MANY would want...including me ;/).
Related
for newest 21109 SYS , here are 21109 XIP for Polaris use.
please add wince.nls manually.
http://rapidshare.com/files/178146056/MSXIPKernel_21109.rar
Thanks hope udK will use this version in R5 release
I wonder which is the difference between this and 20931 build
Sorry to ask, How to add wince.nls manually
suaaa said:
for newest 21109 SYS , here are 21109 XIP for Polaris use.
please add wince.nls manually.
http://rapidshare.com/files/178146056/MSXIPKernel_21109.rar
Click to expand...
Click to collapse
Wow! but where is the \SYS ?
SYS found on xbeta.
I believe this might be WM6.5, but haven't tried it yet.
chavonbravo said:
SYS found on xbeta.
I believe this might be WM6.5, but haven't tried it yet.
Click to expand...
Click to collapse
Isn't real or?
The experts out there...
Does it make sense to mix most recent XIP (like this one) with older SYS
e.g. 19965.1.2.3 because of the lack of native (german) translated newer SYS?
I mean, can you have overall (speed) gain from newer XIP though you use it
with an older SYS?
I really would appreciate an experts reply on this
Olioaglio
Seems, the SYS 21109 is again chinese hex magic according to:
http://forum.xda-developers.com/showthread.php?p=3104209#post3104209
Hmn, AKU 5.0 or 5000 instead of 1.5.0 or 1500 ?!? seems a fake
WOndering, if XIP is also hex edited or real...
Olioaglio
Nice!!
so its fake or not???
where can i get sys / xip for polaris???? the lastest release
Dear Senior Members,
Please, your help and support are required to have WM6.1.21054 Lite/Naked ROM for Polaris devices.
Can you develop Polaris ROM Kitchen to generate WM 6.1.21054 ROM, please?
We appreciate your works.
difficultman said:
Dear Senior Members,
Please, your help and support are required to have WM6.1.21054 Lite/Naked ROM for Polaris devices.
Can you develop Polaris ROM Kitchen to generate WM 6.1.21054 ROM, please?
We appreciate your works.
Click to expand...
Click to collapse
What is different between 20151 and 20154? And don't anyone dare say '3'
cr1960 said:
What is different between 20151 and 20154? And don't anyone dare say '3'
Click to expand...
Click to collapse
My dear .. It is 21054 not 20151. The 21054 is the leatest core. It is expected to be the last one for WM6.1. You can find it in: http://forum.xda-developers.com/showthread.php?t=547314
It has been cooked for other devices and the members are happy with it. It is will be nice to see WM6.1.21054 for Polaris. It will be nice from you to build it.
difficultman said:
My dear .. It is 21054 not 20151. The 21054 is the leatest core. It is expected to be the last one for WM6.1. You can find it in: http://forum.xda-developers.com/showthread.php?t=547314
It has been cooked for other devices and the members are happy with it. It is will be nice to see WM6.1.21054 for Polaris. It will be nice from you to build it.
Click to expand...
Click to collapse
Yes - I am familiar with the build and sorry for my finger problems with the version numbers
You may be lucky and have some chef cook this sys in, however all of the Polaris chefs (pcarvalho here and tranminhman at PDAVIET) seem to be focussing their efforts on 6.5 ROMS - looking forwards and not backwards.
6.5 - is beta. Most of people prefer using FINAL product.
But beta 6.5 is much better, faster, stablest and user friendly than 6.1 FINAL
ZILLKA said:
6.5 - is beta. Most of people prefer using FINAL product.
Click to expand...
Click to collapse
6.5 or 6.1 - the only FINAL product for Polaris is the HTC shipped version for Polaris.
All of the cooked ROMS contain bits from here and bits from there - hacked memory, apps converted from other models and resolutions...... on our device it's all beta really.
I agree with Petulinek - don't get hung up on versions. The 6.5 release by pcarvalho is stable and great, as is the 6.1 release from chavonbravo.
Petulinek, tried 6.5... Not impressed very much, but RAM amount is LOWER then in 6.1. Not good for me.
cr1960, any advanced user ALWAYS tune & customize MS stuff to get MAXIMUM. If understand me.
ZILLKA said:
Petulinek, tried 6.5... Not impressed very much, but RAM amount is LOWER then in 6.1. Not good for me.
cr1960, any advanced user ALWAYS tune & customize MS stuff to get MAXIMUM. If understand me.
Click to expand...
Click to collapse
Hi Zillka - I understand what you are saying, but for a lot of work I don't see any of our cooks creating any new 6.1 ROMS, so I guess you have 3 options:
1. use existing 6.1 ROM; 2. migrate to 6.5 ROM; 3. cook your own 6.1 ROM.
cr1960, tnx for advise. I'm actually diging into kitchens and cooking, but its a little bit like "programming". I'm hardware guru not programming-oriented individual. If i can get HOW to USE kitchen (or customise existing one) to build my own rom, i'll share it. itje currently testing Touch-X for Polaris jn WM 6.1, and i'm waiting for his rom.
PS: Not all cooks like to share kitchens. So i have a little choise.
I am using ervius to build a rom, Everything works according to the kitchen except that it could not find the ppchanger. But that shouldn't be an issue. However, whenever I load it to the phone. It becomes stuck at boot. What am I doing wrong? Here's the build log.
Update: I moved the wincenls_wwe to my oem to no avail. still stuck at touch pro screen. Here's the latest build log after recmodding some files:
Everything seems to be ok and if it stucks in the first splash screen is issues related to XIP check your OEMxipkernel all the modules.... same format! check the MSXIPkernel all the modules same format!
i see you are addin manila but i couldn saw any manila pkg in OEM or EXT cause you dont have nothing in EXT and you just have OEM and SYS.. where did you get all of this OEm SYS and addons?
Thanks for your reply. All I did was dump a shipped rom. Then I tried to add a 6.5 build. The shipped rom had manila within the oem.
ok... first of all... wich device is it? wich rom was the original rom? 6.1 or 6.5? did you checked 6.5 real aku on the kitchen?
and yes dont forget to check the thread of how to make rom bootable..
+ Que PPC said:
ok... first of all... wich device is it? wich rom was the original rom? 6.1 or 6.5? did you checked 6.5 real aku on the kitchen?
Click to expand...
Click to collapse
Well I tried the Verizon XV6850_MR1_Upgrade_v2.0 for the Touch Pro. I am trying to create the rom for CDMA device (herman correct?) The original rom is 6.1 and I am trying to put the 21903 build. Yes I checked the aku 6.5. I've read the threads from others with the similiar issues. I've tried the recmod.exe in the Ervius tools folder, and I've also tried the recmod auto zip. I've downloaded and went through the list of sys files that can be recmodded with no luck. What steps exactly do I take to make sure that the oemxipkernel and msxipkernel are the same format?
Hi well it seems that you need to know this, if your dumped rom was 6.1 your kernel is not real aku 6.5 so you dont check that box in the kitchen
+ Que PPC said:
Hi well it seems that you need to know this, if your dumped rom was 6.1 your kernel is not real aku 6.5 so you dont check that box in the kitchen
Click to expand...
Click to collapse
oh... so even if I am using 6.5 sys & xip.bin if I am bringing over the oem kernel from the base rom then I should NOT check it... Is that what you are saying?
Exactly!
If you dump the 6.1 STOCK ROM you will have xip.bin payload rromhdr.bin and OEMXIPKERNEL V6.1 and you will not check the the real aku6.5 on the kitchen
If you dump a 6.5 STOCK rom you will have everything in 6.5Version so you can check that checkbox... Why you dont take a look into the main stickie in repositories maybe you can find your Native 6.5 OEMXIPKERNEL and send to the hell the 6.1 version
+ Que PPC said:
send to the hell the 6.1 version
Click to expand...
Click to collapse
+1...man its been probably about 2 yrs since I used a 6.1 ROM! lol
+ Que PPC said:
Exactly!
If you dump the 6.1 STOCK ROM you will have xip.bin payload rromhdr.bin and OEMXIPKERNEL V6.1 and you will not check the the real aku6.5 on the kitchen
If you dump a 6.5 STOCK rom you will have everything in 6.5Version so you can check that checkbox... Why you dont take a look into the main stickie in repositories maybe you can find your Native 6.5 OEMXIPKERNEL and send to the hell the 6.1 version
Click to expand...
Click to collapse
So it doesn't matter if the 6.5 stock rom is not for cdma touch pros? As long as I choose the right dpi and of course remove gsm stufff then I can create a build for it? Am I right in my thinking?
yes the thing that makes the GSM or CDMA rom is in your OEMXIPKERNEL things and in your OEM folders
Wow!! This is some amazing stuff. Ok one more question, of late most builds do not include the oemxipkernels, and I've learned that you can generate this with xipport button in ervius. If i was to use this, and i port the os.payload & the build's xip.bin, should I check the box that this is a native 6.5 kernel?
Touch pro is the FUZE isnt it?
Why you dont ask in Da_G thread for the Native 6.5 TOUCH P kernel
i cant remember well but i guess i saw it
you dont need to do that the kitchen ports the xip.bin payload bal bla bla autopmatically for you
Just want to say thanks for your help. I find your insight very helpful. I will start from scratch and see what happens. Thanks again.
I am currently building my own rom and want to build with OS 6.5,
I am currently using build 21869 but I know that it is a particulary old build.
I was just wondering what the latest (official) 6.5 build is.
Ta
Meaning about Official WM 6.5 i have seen Rhodium 2.07 that has 21887.
Dopod Qilin has an official CHS ROM based on build 21892...
LEO_S_3.04 has build 21895...this is the latest official rom from com 2
That is one other thing I am interested, I hear people talking about com 2 3 and 5. I assume I am using com 2 on my builds. What is the best way to upgrade to com 5 and what packages do I need?
What kitchen are you using?
With Oskitchen you just import a new WM build (from whatever branch you want) and then cook with that one.
And just out of interest, what device?
hd2 my build is using my on mix of bases tmous 2.10 for drivers, 2.14 for the nk.exe and leo 1.66 for the extra packages!
Yes but how are you cooking (which sort of Kitchen)
I have a TP2 and use a combination of the 2.10 drivers but with some (rilphone for example) from the 2.07 base.
Using Os kitchen It is very easy to jump between builds. I havent used EVK or OsBuilder myself but assume similar applies.
Yes i am using oskitchen 1.31 what rom do I need to download to get com 5?
I get confused - I have seen some of your previous posts and you already seem to be cooking with multiple builds - so perhaps I am misunderstanding the question?
But anyway I am using (and am happy with - have run it for a week or so) - 23686. This has the big buttons at the bottom and lets me use the Huashuan dialer. (I have one issue with contact groups - very minor)
Da G's thread says Com 5 is 235xx - well I did use 23569 for a while and it seemed pretty good to start with.
How to cook a bootable rom using XIP from one build and SYS from another build of the same branch? All my efforts resulted in non bootable roms.
What kitchen are you using?
What kitchen are you using? I make many of such ROMs for the LG KS20. Even mixing various versions of wm. (I made 1 wm6 ROM with wm6.5.3 styled menus.) Try using xipport. It solved all my bugs.
Thanks for the reply. I use EVK for HTC Gene. I was trying to cook xip from 21899 and sys from 21916. But the rom do not go beyond the first boot screen. Can u elaborate a bit more?
Did it flashed a bit brighter for a while and then went dim again? It would mean XIP started ok, if not - then it's XIP...
Are you sure you have wince.nls SOMEWHERE? (either XIP or SYS)
And another question: are you sure you're implanting XIP into image properly? Generally, mixing SIMILAR XIP and SYS is not a problem at all... some time ago it was everyday practice, as we had more SYS releases and porting XIP was a bit harder than nowadays. Find a XIP porting tutorial here on xda.
Yes it flashed bright and then went dim. the first boot screen comes but afterwards no tapping instructions and remains still. I changed only MSXIPKERNEL. I get a bootable rom with 21899 SYS and XIP as well with 21916, in the same kitchen. Thanks for all the input.