Hi all,
so I am new to the world of Windows Mobile - use to be a Symbian fan and then got the HTC Touch Diamond recently due to my Nokia dieing of old age.
I want to learn how to cook ROMs so I can customize what I want as I want. I tried sending Da_G a PM as he seems to be quite knowledable about cooking - although he seems to be MIA (his last post was a long time ago) and I have not gotten a reply yet.
So now onto some questions which are probably stupid, but I do not know the answers to.
So I have an HTC Touch Diamond which originally comes with Windows Mobile 6.1, I am using osKitchen as it seems really popular and it looks easy enough to use. I followed the guide which is here but it does not give me the complete info I want.
So in order to cook a ROM you first need to have an original ROM (so in my case an original ROM for the HTC Touch Diamond off the HTC site?)... I got that(RUU_Diamond_HTC_WWE-AFK_2.03.421.2_Radio_Signed_Diamond_52.51.25.26_1.09.25.23_Ship.exe)
Then you open it up with osKitchen, it extracts it blah blah blah.
I then get a popup about a new ROM has been imported and it asks me if I want to automatically configure the project to use the ROM. I click yes.
Then it says the device profile currently selected uses a pre 6.5 kernel, module allocation space will be extremely limited. Do I want to auto enable module to file conversion for a list of files? Now I read somewhere that if you are using pre 6.5 kernel you want files, if you are using the 6.5 kernel you want modules? I am not sure what to click here as I want to upgrade to windows mobile 6.5 ...
So do I enable the conversion or not?
Then it pops up with the project settings, under SYS Packages I can see all of the phones services. OEM packages, I am not too sure what that is... One thing which is worrying is that there is a red circle with an X in it infront of OEM Drivers... If I hover over it, it says there are issues detected in the OEMdriers. They all seem to be errors detected in the registry and the registery key path entry is invalid due to 2 adjacent backslahes? So is this normal? What do I do?
Also there is a block "RecMod" under OEM Packages. What does that do and what is it used for?
EXT Packages, over here we have all of the applications which will be preinstalled when you flash the ROM? I know how to add .cab packages to it and it seems simple enough. Once again there is a RecMod with a tick box?
ROM Tweaking I have not really bothered with yet, would first like to learn the basics. Anything I should know about in ROM Tweaking?
Now back to SYS Packages. This is where you update/port/upgrade ? to newer windows mobile versions? Now I think if you are changing between window mobile major build versions or what ever you want to call it (like from 6.1 to 6.5) kernel changes perhaps? You call it porting? Anyways, so now I want to change to the latest build in WM6.5 .
I took a look at this thread: http://forum.xda-developers.com/showthread.php?t=650783
Now it seems like the first 3 digits indicate something, what exactly I am not too sure. Perhaps someone could explain?
There is HTC HTC which is made by HTC I think and possibly meant for HTC?
Then there is COM 2 and LG. Now since I have an HTC do I have to use the HTC one or not? Also it seems some have newer / higher WM builds? So why are there these many different builds and what difference does it make as to what they are? Also what are the COM 2, 3 and 5 ?
Anyways, I downloaded the HTC one. Now I want to port / upgrade to it. It is WM6.5 now as well. So I click Import, then goto Import a new WM build. Select the appropriate build dump, then click on start importing. It will import it and then what? Is there anything else I need to do?
I am assuming go back to Project Settings and under SYS build change it to the newer one which I have just imported? Although is this really all I need to do? Will I now have a proper functioning cooked ROM running WM6.5 with the new build?
Thanks
If you're cooking a 6.5 rom, and you have a 6.5 native kernel (there should be one out there, unless you're using a cdma diamond), then DO NOT RECMOD (convert to files). If you have to use a 6.1 kernel, then you have to recmod a lot of modules. Look around, there are threads with native kernels for many older devices. I'm not going to dig up a link, I'll let you find it. Just get the Diamond native kernel and use it.
If you have a cdma diamond, then I believe that people use the cdma raphael native kernel, but supposedly it's buggy.
OEM Drivers has an .rgu that usually has a few mistakes in it; that's probably the error you're getting. I wouldn't worry about it, but the kitchen may tell you which line the error appears in, and you can fix it.
As far as rom tweaking goes, all you need to know is that manila sucks, and Sense is blight on humanity. Good luck and have fun.
Real Beginners Stuff Please.
PsyCLown89 said:
Hi all,
so I am new to the world of Windows Mobile......
I want to learn how to cook ROMs so I can customize what I want as I want.....
So now onto some questions which are probably stupid, but I do not know the answers to......
...... I followed the guide which is here but it does not give me the complete info I want.....
..... What do I do?
..... What does that do and what is it used for?
..... would first like to learn the basics......
..... so now I want to change to the latest build in WM6.5 .
..... do I have to use the HTC one or not? Also it seems some have newer / higher WM builds? So why are there these many different builds and what difference does it make as to what they are? Also what are the COM 2, 3 and 5 ?
.....and then what? Is there anything else I need to do?
.....Thanks
Click to expand...
Click to collapse
Hi,
So many questions
I too am new to the world of Windows Mobile, and have learnt how to flash different ROMs sussessfully.
I have spent my time reading hundreds of threads about flashing, and having a go - the tutorials and threads have been great source of knowledge.
Now I want to start cooking a ROM and things are different..... I have read thousands of posts and tutorials and watched videos, but I haven't found a real Noobs method of: starting, choosing a kitchen, finding a ROM, importing the new bits, and making the changes. It all goes wrong right from the very start.
Choose a kitchen, and then what ? (exact steps, not just "find a ROM you like, then..", etc. etc.)
None of the threads I have read seem to be able to give the nitty gritty to start, they all skip over it.
I have a Kaiser, and am in a similar position to you, there isn't a native 6.5 kernel for the Kaiser, so how do I make a 6.5 build in a kitchen, when I don't have a 6.5 build to start off ?
Please can someone give a REAL NOOBS guide to starting off.
Thanks & Regards,
It all comes down to the basics. If you do not know what a kitchen actually does, then there probably is no point in cooking to start of with.
Kitchens available today make a lot of things heaps easier than they were several years ago.
Try starting with this thread.... it is not for your device, but you get to learn the basics and actually understand what happens in the background.
http://forum.xda-developers.com/showthread.php?t=335631
Cooking is not just clicking around with your mouse.
pkoper said:
.... If you do not know what a kitchen actually does, then there probably is no point in cooking to start of with.
..... Cooking is not just clicking around with your mouse.
Click to expand...
Click to collapse
This may be new to me, but it also was to EVERY cook there is, or has been at sometime. We all learn something new at some time, and all I was asking for is a little starter to get me going. I realaise it isn't a point and click exercise, otherwise I would have made a ROM by now, and not asked for help. I didn't write the software for the kitchen, so I don't know how it works.
http://forum.xda-developers.com/showthread.php?t=335631
Click to expand...
Click to collapse
Thanks for that, I hadn't seen that one, but unfortunately, it also doesn't give the procedure for starting with a WM6.1 ROM and adding/changing files to end up with a WM6.5 Native Kernel.
Please, give me a break.
Fish-Man said:
I have a Kaiser, and am in a similar position to you, there isn't a native 6.5 kernel for the Kaiser, so how do I make a 6.5 build in a kitchen, when I don't have a 6.5 build to start off ?
Click to expand...
Click to collapse
Using search you would have found the native kernel:
http://forum.xda-developers.com/showthread.php?t=619663
Fish-Man said:
Thanks for that, I hadn't seen that one, but unfortunately, it also doesn't give the procedure for starting with a WM6.1 ROM and adding/changing files to end up with a WM6.5 Native Kernel.
Click to expand...
Click to collapse
Thats exactly what I meant. Do you know what the kernel actualy is?
pkoper said:
Using search you would have found the native kernel:
http://forum.xda-developers.com/showthread.php?t=619663
Click to expand...
Click to collapse
Thanks, but I already have them. They are "files" not a "stock build" that the cooks tell you to start with. Again, do I need to start with a "stock build" of WM6.1, or can I use those WM6.5 "files" instead, if so, what am I missing from the "stock build" that I need to continue ?
Thats exactly what I meant. Do you know what the kernel actualy is?
Click to expand...
Click to collapse
Yes, It's a piece of code, usually written in assembly language (for speed of execution), that sits between the hardware devices and the system drivers and programs, to translate what the programs want, to what the hardware can understand, and deliver the results from the hardware, back to the programs.
It is the core of the Operating System, and is the first thing that is loaded into memory when the system boots, and stays there until you turn off the device (unlike other programs that are loaded, and unloaded as needed). It is loaded into a seperate and protected area of memory, where it executes processes, handles interrupts, memory management, process management, file management and I/O management.
The User, cannot interract directly with the kernel (or hardware), but has to go via a seperate program (usually containing a GUI), that can send it's requests to the kernel for processing. After the kernel has processed the programs requests, the kernel gives the information to the program, which then outputs it to the User.
Is that enough of an explanation ? Sorry I had to simplify it, but there are a lot of other noobs here that may have gained some knowledge from that, so rather than blow thier minds with acronyms and babble, I thought it best to explain it simply.
Now, are there any more questions you want me to answer, before telling me what I need to know, to understand the first few steps in cooking a ROM ?
Regards,
Fish-Man said:
Hi,
So many questions
I too am new to the world of Windows Mobile, and have learnt how to flash different ROMs sussessfully.
I have spent my time reading hundreds of threads about flashing, and having a go - the tutorials and threads have been great source of knowledge.
Now I want to start cooking a ROM and things are different..... I have read thousands of posts and tutorials and watched videos, but I haven't found a real Noobs method of: starting, choosing a kitchen, finding a ROM, importing the new bits, and making the changes. It all goes wrong right from the very start.
Choose a kitchen, and then what ? (exact steps, not just "find a ROM you like, then..", etc. etc.)
None of the threads I have read seem to be able to give the nitty gritty to start, they all skip over it.
I have a Kaiser, and am in a similar position to you, there isn't a native 6.5 kernel for the Kaiser, so how do I make a 6.5 build in a kitchen, when I don't have a 6.5 build to start off ?
Please can someone give a REAL NOOBS guide to starting off.
Thanks & Regards,
Click to expand...
Click to collapse
I don't think what you're looking for exist, persay. There are several kitchens out there to choose from. The only thing that helped me when starting out was frequenting the thread of the kitchen that I was using. It's in the kitchen's thread that you'll find all the nitty gritty answers you're looking for and other people that are in the same boat as you, and more experienced users of the same kitchen who would probably be more apt at answering questions about specific kitchen.
Fish-Man said:
Thanks, but I already have them. They are "files" not a "stock build" that the cooks tell you to start with. Again, do I need to start with a "stock build" of WM6.1, or can I use those WM6.5 "files" instead, if so, what am I missing from the "stock build" that I need to continue ?
Yes, It's a piece of code, usually written in assembly language (for speed of execution), that sits between the hardware devices and the system drivers and programs, to translate what the programs want, to what the hardware can understand, and deliver the results from the hardware, back to the programs.
It is the core of the Operating System, and is the first thing that is loaded into memory when the system boots, and stays there until you turn off the device (unlike other programs that are loaded, and unloaded as needed). It is loaded into a seperate and protected area of memory, where it executes processes, handles interrupts, memory management, process management, file management and I/O management.
The User, cannot interract directly with the kernel (or hardware), but has to go via a seperate program (usually containing a GUI), that can send it's requests to the kernel for processing. After the kernel has processed the programs requests, the kernel gives the information to the program, which then outputs it to the User.
Is that enough of an explanation ? Sorry I had to simplify it, but there are a lot of other noobs here that may have gained some knowledge from that, so rather than blow thier minds with acronyms and babble, I thought it best to explain it simply.
Now, are there any more questions you want me to answer, before telling me what I need to know, to understand the first few steps in cooking a ROM ?
Regards,
Click to expand...
Click to collapse
Nice quick knowledge drop on kernel. It sounds to me like you already have a better grasp on things then some!
Fish-Man said:
Thanks, but I already have them. They are "files" not a "stock build" that the cooks tell you to start with. Again, do I need to start with a "stock build" of WM6.1, or can I use those WM6.5 "files" instead, if so, what am I missing from the "stock build" that I need to continue ?
Click to expand...
Click to collapse
Thats because there is no stock 6.5 for the Kaiser. Not sure what "those WM6.5 files" are, but you do need the drivers for your device. Any leaked build will not contain those.
Dumping a stock rom will give you insight as to what is actually in the rom. When you then download one of the leaked builds you can you will recognize the files and hence see what needs replacing in order to upgrade.
Now, are there any more questions you want me to answer, before telling me what I need to know, to understand the first few steps in cooking a ROM ?
Regards,
Click to expand...
Click to collapse
What kitchen are you using? As there are obviously slight differences as to what is where.
I would just get a ready kitchen and study it.
http://forum.xda-developers.com/showthread.php?t=517957
for your reference maybe you should read this....
http://forum.xda-developers.com/showthread.php?t=901712
i had made the tutorial how to cook ROM, step by step. it has different device and different OS but worth to read.....
i don't have enough capability to Cook but i try to....
also in this http://forum.xda-developers.com/forumdisplay.php?f=385
some of members also made tutorial as well.......
i hope it can help.
Thinking of a new method of installing AoW, and I think I have found a way to install AoW without the Dev update on the latest release of W10M.
How many of you would want something like this done? It would require full interop/cap unlock with 1st/2nd/3rd party permissions unlocked as well using the Root Tool.
I am starting research on this now to see if it is worth while.
Let me know peeps!
If this would manage to skip the device hardware check and allow us to run project astoria on 512MB RAM devices then I am really interested and ready to test.
Thanks, I am still doing a lot of research to see if this is even possible, but I have the AoW files for P.A. I just need to figure out the registry entries, and where each file goes.
Might be awhile, but I will let you know when I have an alpha installer.
sandix said:
Thanks, I am still doing a lot of research to see if this is even possible, but I have the AoW files for P.A. I just need to figure out the registry entries, and where each file goes.
Might be awhile, but I will let you know when I have an alpha installer.
Click to expand...
Click to collapse
I already tried adding the files and registry entries myself, some of the registry entries can't be written, at least not by any registry editor released until now, also did the downgrade and update with an other device's entries trick to try to enable it so I now seem to have all the aow files in their place and the entries are also there (at least the entries I know about) yet it doesn't work so at least for users of devices with 512MB RAM this might not be possible (I think that somehow the android build/hyper-v implementation/something else check the hardware and don't allow it to boot on 512MB RAM).
I am still willing to test but I think that even if you manage to find and write all the registry entries you might need an other tester with a (hardware wise) better device to actually find out if it's working or not.
Ranomez said:
I already tried adding the files and registry entries myself, some of the registry entries can't be written, at least not by any registry editor released until now, also did the downgrade and update with an other device's entries trick to try to enable it so I now seem to have all the aow files in their place and the entries are also there (at least the entries I know about) yet it doesn't work so at least for users of devices with 512MB RAM this might not be possible (I think that somehow the android build/hyper-v implementation/something else check the hardware and don't allow it to boot on 512MB RAM).
I am still willing to test but I think that even if you manage to find and write all the registry entries you might need an other tester with a (hardware wise) better device to actually find out if it's working or not.
Click to expand...
Click to collapse
Well I have a Lumia 640 which is not supported yet, but will be in the future. 1GB RAM Quad-Core
i can test if you want i have a lumia 625....
UPDATE: I think I am getting close to a solution. if someone who has astoria on their device already could you rip all the files from "C:\Windows\System32\aow" from your phone, zip them up and send them to me in a private message? It would be of GREAT help to make sure I have the latest files.
Thank you.
Old post, but I'm interested.
I have the files, go pm.
I would venture to say anyone with a high spec windows 10 mobile device is extremely interested in this. I think heathcliff is researching this. if astoria could be ported to the latest build of windows 10 mobile..
barc0d3 said:
I would venture to say anyone with a high spec windows 10 mobile device is extremely interested in this. I think heathcliff is researching this. if astoria could be ported to the latest build of windows 10 mobile..
Click to expand...
Click to collapse
I made some tests but I was stuck on adding new values in registry.. But I had all the values to put and all the files and other modifications
valentinbreiz said:
I made some tests but I was stuck on adding new values in registry.. But I had all the values to put and all the files and other modifications
Click to expand...
Click to collapse
Realistically this would only work on Nokia, which requires a special DLL to be used in the project to set/create registry items.
sandix said:
UPDATE: I think I am getting close to a solution. if someone who has astoria on their device already could you rip all the files from "C:\Windows\System32\aow" from your phone, zip them up and send them to me in a private message? It would be of GREAT help to make sure I have the latest files.
Thank you.
Click to expand...
Click to collapse
You need a lot more than that, me and other people are working on this. I already pushed all the astoria files and dlls, and restored the service key and values to trigger the dlls. It needs more than that to work in newer builds, when i mean newer builds i refer to 10586.x or higher .
xxJMarian said:
You need a lot more than that, me and other people are working on this. I already pushed all the astoria files and dlls, and restored the service key and values to trigger the dlls. It needs more than that to work in newer builds, when i mean newer builds i refer to 10586.x or higher .
Click to expand...
Click to collapse
Hey thanks for the reply, I already know this, but thanks for the information! However, I have long since abandoned this project (see date of my OP and the post you quoted). Cheers!:good:
Be careful
sandix said:
Thinking of a new method of installing AoW, and I think I have found a way to install AoW without the Dev update on the latest release of W10M.
How many of you would want something like this done? It would require full interop/cap unlock with 1st/2nd/3rd party permissions unlocked as well using the Root Tool.
I am starting research on this now to see if it is worth while.
Let me know peeps!
Click to expand...
Click to collapse
Well... I have a Lumia 925 running latest Windows 10 Mobile build ever (Redstone 4) Build 15254
But be careful!
You may brick a lot of devices...
If you really want to work on this, i can give you all the files i've got on my research aswell as the registry keys that you can import with interop tools. Since i had to format my pc and such, didn't install anything related to windows phone, so i left the project in the trunk but, as i said, if you really want to work on this i can provide you with the files and keys.
Yep!
xxJMarian said:
If you really want to work on this, i can give you all the files i've got on my research aswell as the registry keys that you can import with interop tools. Since i had to format my pc and such, didn't install anything related to windows phone, so i left the project in the trunk but, as i said, if you really want to work on this i can provide you with the files and keys.
Click to expand...
Click to collapse
Well... I will take it!
Just upload it to a download server for example MEGA.CO.NZ
And and the download link to me via private messages.
If everything would succeed and I will finally make it to the finish, I will make a program that will install Astoria onto your phone via just pressing a button!
You can also check out my other software that I made and published to xda developers, I will be very happy if one of them will help you fixing problems with your phone (if you have problems of course) or installing Windows 10 Mobile onto your phone with just 3 clicks!
Good luck!
Sincerely
Gor Mirzoyan
(founder of XWintech Corporation)
(Birth year: 2005, yes I am actually 13 years old, it's not a joke)
I hope you manage to get this working!
Ever since its announcement I was hoping to see the day it gets out!
How's the progress? Nearly done?