Hi to all,
I thing that there are very few chefs and we should share knowledge the others cookers should share them kitchens too.
Bugs
Bt headset bug (i was not able to fix it i am open to suggestions)
DeadLink V2
Kitchen WM6.1 21042
Regards
Rukako
Thanks for sharing Rukako, mm.. your Deadlink rom without manila is what I need.. as I dont use it.
I'll try and make one.. thaks again for posting it
Rukako please fix kitchen archive (Kitchen WM6.1 21042) crc error.
I need this kitchen for translate it for another language.
Build 21054
Thanks Rukako for your nice work. It will be nice and sweet from you if you could do:
- Modifying the Kitchen to include 21054 files.
- Developing simple guide lines to cook lite or naked version of your ROM.
Thanks again for your nice MW6.1 ROM Kitchen.
Can anyone point me latest WM6.1 Polaris kitchen with XIP SIP integrated?
I wish to try cook WWE rom for my O2 Orbit2, since i cant find sutable rom for myself.
161 views and no comments?
Please be patient before re-post and use the SEARCH button BEFORE posting or i must delete your thread.
I'm not impatient, and know how to use SEARCH. Serching this forum i found only OLD Build 19965.1.2.3 versions WM6.1. I new that PDAVIET using 21xxx kitchen, thats why i'v searching for the latest 6.1 Build 21xxx.
[23July]Kitchen Windows Mobile 6.1 :Kitchen WM6.1 21042 http://forum.xda-developers.com/showthread.php?t=539904&highlight=kitchen
[23July]Kitchen Windows Mobile 6.5 :Kitchen WM6.5 21900 http://forum.xda-developers.com/showthread.php?t=539905&highlight=kitchen
Search button only 2 seconde if this is what you search.
thanks to rukako for the post.
Maci said:
nedržkuj a koukej navalit ty linky smrade!
Click to expand...
Click to collapse
Behave yourself, your pubescent speech anyone cares
I have Universal and got a question.
Can I use WM5 stock ROM to cook WM6.1 or 6.5?
Are there any dfferences between cooking from stock/base WM5 and from base WM6.1 to newer versions?
Yes it is, cause the core is different...
but you can go to the HTC Universal forum and download a 6.5 or 6.1 kitchen by any chef and get the OEM and ROM folders you will need the native 6.5 kernel too read the tutorials here to set or port a new device into OSkitchen or EVK
Well I flashed my device to WWE| Energy Series 21903.
But I want to have Dutch language on my device.
I found this Rom
[ROM][Nld][May 01] [email protected] 1.7 Nld | 21903 | Manila 2.5.20121412.1 | Dutch
Link
It uses the same 21903 version As Enery use but this one is actually Dutch
my questions are
Where Can i find The mui Files
Can I export the mui files from [email protected] rom to my windows folder of the energy rom
Do I need to do any registery tweaks to get it working
Someone please help me out, energy rom is the only rom I like but I hate that it's in english, No offence but it's quit annoying
If help can be in Dutch it will be better for me to understand
Hope ya'll can help me out
Thanks in advance!!
someone any help?
I already did a search but it didn't cleared anything up...
take a look here http://forum.xda-developers.com/showthread.php?t=676225
giacominos said:
take a look here http://forum.xda-developers.com/showthread.php?t=676225
Click to expand...
Click to collapse
I already looked there I went from happy to depressed by this
jan-willem3 said:
Note: this is only for the 23566 build of windows mobile 6.5.X
Note: You can use this on al windows builds with the 23566 build of windows mobile 6.5.X.
Note: The hole package includes some no needed files but it is a few (500 Kb or something like that) so no worries . And if they needed for a program they are there
Click to expand...
Click to collapse
Since i got no 23566 Build but a 21903
So i Don't have WM 6.5.x
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.