Hi. dzo's bootloader requires flashing kernel/initrd/cmdline each time to change settings in android, while recovery is not an issue with RUU and hardspl there may a better way. We also maybe able to support leaving Windows Mobile in NAND and booting from sd for those that want multiboot capability even with the small flash size of the vogue. There a few approaches here, one involves adding multiboot support to HardSPL directly, another to extend tinboot to support a second embedded (cooked) xip with a key press switching modes. The first thing I want to try however is clearing the screen and drawing a basic framebuffer message or menu. We might also switch to a more capable bootloader when support for the NAND and SD can be added. This is in vogue thread but most of the concepts should apply to all HTC MSM devices with Windows Mobile. If you need to reach me try tmzt in #htc-linux on freenode.
do you have anything put together to test out? i'm not very interested in dual booting but i am interested in any bootloader improvements.
I don't have a vogue so I can only build images for others to test, hence this thread.
I am interested in Multiboot images. I would prefer to have Galaxo 1.6.3 as my standard OS and an Android 2.1 OS (like GAOSP or mustymod) as a second on my Samsung Galaxy. It is possible to have a Bootscreen at startup?
A HowTo for programming / customization would be awesome.
hatecore said:
I am interested in Multiboot images. I would prefer to have Galaxo 1.6.3 as my standard OS and an Android 2.1 OS (like GAOSP or mustymod) as a second on my Samsung Galaxy. It is possible to have a Bootscreen at startup?
A HowTo for programming / customization would be awesome.
Click to expand...
Click to collapse
You could try Andboot, which will load before Windows starts up and will let you choose between both OS. Good luck!
That´s my problem, Galaxy (i7500) don´t have Windows. Its an Android Handy. I don´t have any ideas for programming a Bootloader for Android...
hatecore said:
That´s my problem, Galaxy (i7500) don´t have Windows. Its an Android Handy. I don´t have any ideas for programming a Bootloader for Android...
Click to expand...
Click to collapse
So, basically you are asking if you can have a dual boot system on a native Android device? I don't believe that is possible yet.
Ok, I will search for some methods from Users in german language and then I will try it.
Thanks for your answers.
hatecore said:
Ok, I will search for some methods from Users in german language and then I will try it.
Thanks for your answers.
Click to expand...
Click to collapse
Check out some of the other Android projects as they might give you some better insight.
Related
hi guys
first off...sorry for posting the usual question...its been done to death
i have been out of the xda-dev site for a while and have lost track of things.
i always hoped himalaya linux would get done.... but from what i can see its still lacking the key components (eg phone support under gpe).
i am a uni student on placement at a company that actually writes mobile phone radio stacks...so i am learning embedded c and about the interesting side of the hardware/software interface.... now i want to actually do something about this lack of a fully usable phone.
my questions go as follows..
1> what is the current stage of himalaya linux ... i have a feeling the wiki's are probably out of date
2> is anyone actually still working on it
3> i know only a little about haret i get the idea it is also able to watch hardware (and isnt just a bootloader)...where can i find docs about using it to do this.
4> was jtag ever found on the himalaya
5> of the code in the tree what files are specific to the himalaya
i have much to learn on writing drivers etc for linux...and alot to learn about embedded c, reverse engineering etc....ok so i have a hell of a lot to learn....but i'm willing to try! (i also have 3 himalayas (1 has a bust screen) so plenty of tinkering can be done)
any other tidbits of information would also be appreciated
i think my basic goal would be the phone working.
after that get the other little bits and pieces
get the backpack cf working
get sdio and wireless working.
but these are the kind of goals that will take a long time so we'll see
i'd also love to work on the UI one day.. GPE and OPIE just dont toot my horn enough yet.
thanks
Tim
tim_programmer said:
1> what is the current stage of himalaya linux ... i have a feeling the wiki's are probably out of date
Click to expand...
Click to collapse
It is out of date, but some parts are in a good shape.
2> is anyone actually still working on it
Click to expand...
Click to collapse
Yes, because it has many common hardware and features with blueangel.
The kernel source is not being fixed, because it is decided to make blueangel
work first, and then reuse and adapt the cleaned code for himalaya.
3> i know only a little about haret i get the idea it is also able to watch hardware (and isnt just a bootloader)...where can i find docs about using it to do this.
Click to expand...
Click to collapse
There are no "real" docs, only the source code. Many pxa27x functions are
implemented in haret, that either work or need minor changes for pxa26x.
4> was jtag ever found on the himalaya
Click to expand...
Click to collapse
Yes, it's in wiki since 3 years or so
5> of the code in the tree what files are specific to the himalaya
Click to expand...
Click to collapse
Blueangel is the authoritative source.
i think my basic goal would be the phone working.
Click to expand...
Click to collapse
AFAIK, the phone works. But not with the latest 2.6.18-hh0 kernel.
This one has a lot of audio problems anyway, so it's not a major concern right now.
get the backpack cf working
Click to expand...
Click to collapse
It's a bit challenging. The backpack is implemented in so-called ASIC5,
and there are no docs for it.
get sdio and wireless working.
Click to expand...
Click to collapse
You mean SDIO wifi card ?
The SDIO host can be done relatively easy, but good luck with the wifi part
I know 2 of them, one with the TI acx100 (should be doable, because
there is linux acx100 driver), another needs the firmware upload in Motorola
SREC format, maybe even prism2.
And there is no free software SDIO for linux, you need to do some heavy RE.
Hello guys,
I have got Himalaya and I would like to help with implementation of some driver/software that is needed.
So I have got a few questions (some of them are similar to tim_programmer's, but I don't know if there are not outdated):
1. Where is the current branch with Himalaya specific code?
I have found:
- K2-6-12-hh2-xda0-ba0 (http://xanadux.cvs.sourceforge.net/xanadux/linux-2.6-xda/) and
- K2-6-21-hh20 (http://handhelds.org/cgi-bin/cvsweb.cgi/linux/kernel26/)
Is himalaya specific code that is in K2-6-12-hh2-xda0-ba0 already included in K2-6-21-hh20?
Or what differences are between these branches?
2. Is somewhere available (SD card/NFS) image with kernel+initrd+GPE that is already running on Himalaya?
I have found:
- http://wiki.xda-developers.com/index.php?pagename=HimalayaLinuxBooting
It boots, but freezes during boot (after some changes in initrd it was possible to connect to the MDA with SSH via USB bus)
- http://wiki.xda-developers.com/index.php?pagename=HimalayaStandaloneGPEWithoutSD
Link to GPE is dead.
- http://handhelds.org/moin/moin.cgi/Himalaya
There are screenshots of GPE so it should be working image somewhere.
3. Is it posssible to boot some BlueAngel "distribution" on Himalaya? (Possibly with a little changes?)
I have found:
- http://handhelds.org/moin/moin.cgi/BlueAngelHowtoInstallLinux
Could it be used on Himalaya?
4. What is the current state of Himalaya support in Linux? What is already done and what not (or partially)?
I have found:
- http://wiki.xda-developers.com/index.php?pagename=HimalayaToDo
But there is not mentioned of what branch state it is.
5. Is any other bootloader than HaRET with that is possible to boot to Linux directly from SD card without Windows booting?
I have found:
- bootldr (http://xanadux.cvs.sourceforge.net/xanadux/linux-2.6-xda/bootldr/)
What is it?
A lot of information about Himalaya development is outdated and I don't know where to start :-( So any help is welcome
Thanks
Drasar
drasar said:
A lot of information about Himalaya development is outdated and I don't know where to start :-( So any help is welcome
Click to expand...
Click to collapse
join #htc-linux at freenode.
Thanks for the link..just joined
btw when i start Haret on my Hima..the Thermometer goes up and the eyes go red..and then few lines comes up and thats it..i have tried every thing but cant get Linux to work
waiting for the New Linux Mobile
ather90 said:
btw when i start Haret on my Hima..the Thermometer goes up and the eyes go red..and then few lines comes up and thats it..i have tried every thing but cant get Linux to work
Click to expand...
Click to collapse
What kernel have you tried? What was the last message on display? Some old HaRET versions (e.g. 0.3.6) have a problem with big kernel and boot fails on mounting root fs. So try the newest HaRET 0.5.1 that goes fine.
Thankxxx alot..u are rite i have 0.3.6
here is what i have :
haret-0.5.1.exe
initrd-2.6.12.gz
modules-2.6.12.tgz
zImage-2.6.12
are these all latest
ather90 said:
haret-0.5.1.exe
initrd-2.6.12.gz
modules-2.6.12.tgz
zImage-2.6.12
Click to expand...
Click to collapse
For kernel 2.6.12, follow How To Compile 4 Himalaya instructions. It works, I have tried it yesterday ;-)
Thanks alot..thankfully i have Ubuntu so compling is no big
i will contact u for more assistance
Hello.
I've been trying to boot android the opal by trying the vogue kernal (since it has the same specs as the opal) on the opal until i came across this. a fellow xda-dev member had some good news on android booting on the opal.
heres the original quote from him in the "LINUX BOOTS at OPAL! Thanks to linwizard project!" thread.
MusikMonk said:
I have some good news, Android can boot on the Opal. This is just a proof of concept as it's missing tons of drivers and is completely useless.
Touchscreen and all keys except for the volume control (and obviously the reset button) are not working. So you basically can't do anything when you run it.
What I tried is the same as what's written in this thread about running Android on Gene. They're using the build made for the Herald/Wing (just as I was proposing in my last post) with customized initramfs and kernel.
You'll find all the necessary details in that thread. However, there's a newer build than the one mentioned there it's wing-linux-0.4pre2.cab. And the suitable kernel for that build is supposed to be the pre2 posted in this post but it didn't work on my Opal so I tried the older Gene kernel and it worked. The main difference between the two is bluetooth support, and that's obviously is of no use for us.
This doesn't effect the Windows rom, nor does it requires any special partitioning. Still it's best to have everything backed up before launching it, just in case.
This is the official site for the wing/herald build:
http://wing-linux.sf.net/
This thread on their forums about the Gene port will probably be of use to us:
http://sourceforge.net/apps/phpbb/wing-linux/viewtopic.php?f=4&t=4
I'm reading about the next steps but as I said before, I don't have any previous experience or knowledge about this type of things. If someone can give me hand, I would be more than grateful. At any rate, once I have better understanding of the concept I'll contact the people behind the Wing and the Gene ports.
P.S: If you do try to run this, keep in mind that this will take lots of time, specially for the first launch. And when you get an error saying something like "android sh: can't access tty" just ignore it and keep waiting. After a while you'll have a flashing "android" on the screen, and after some more waiting you'll reach the main screen.
Click to expand...
Click to collapse
i've not tried it yet, but the touchscreen drivers and buttons are not working. if anyone could help build a android kernel for the opal, it would be extremly great!
This thread will be used for future android builds for the opal.
It is possible "Android" in this mobile ????
I would like install to
no, i don't think you can install, but you can boot it from haret. i'm not sure too how to boot it though, trying to find a way.
okay i tried reached till ANDROID boot screen struck waiting for fone to respond.. responded now struck on power off screen..
nothing happens powering offffff strucks.. any way it worked half way.. now i have hope one day will run android on opal
If the Opal is based on the Omap850 chipset, anyone care to try the Wing-linux project on their phones? It's Android ported (or in the process of being ported) to the Wing/Herald. The keys won't be mapped to your phones but I wonder if it will actually boot all the way to the Android desktop. (Btw, the first boot takes a long time to finish.)
would love to try android!!
ivanmmj said:
If the Opal is based on the Omap850 chipset, anyone care to try the Wing-linux project on their phones? It's Android ported (or in the process of being ported) to the Wing/Herald. The keys won't be mapped to your phones but I wonder if it will actually boot all the way to the Android desktop. (Btw, the first boot takes a long time to finish.)
Click to expand...
Click to collapse
Actually, we're already working with wing-linux:
MusikMonk said:
What I tried is the same as what's written in this thread about running Android on Gene. They're using the build made for the Herald/Wing (just as I was proposing in my last post) with customized initramfs and kernel.
Click to expand...
Click to collapse
At any rate, the main thread is here:
http://forum.xda-developers.com/showthread.php?t=462188
I would appreciate any help because, at the moment, I seem to be the only Opal owner working on the port. And I lack the experience.
I was working on modifying the kernel so that the touchscreen would work but I ran into some problems and I've been too busy during the last week to do anything concerning this project.
i'll be happy if anyone could post links to videos showing android running on our HTC touch viva
I got Android CupCake installed and working on my HTC Opal a few weeks back using the WingLinux.
Keys are not mapped and Android is not fully functional but never the less, its android 1.6 on your viva...u can chk da pic off my facebook album, i dnt wanna upload'em again:
http://www.facebook.com/album.php?aid=2068361&id=1493937383
what is special in android which make it different from windows? How it connect to windows pc and linux?
http://www.enlightenment.org/p.php?p=about&l=en
After reading this i thought it is possible to bring this to our omap 850 devices so i just want see ur views
you can use e17 booting angstrom + illume thanks to wing linux project
but there aren't angstrom image ready to load you must compile...
As gp.triple pointed out, it should be possible to do. As Wing Linux uses Angstrom+Android so Angstrom+E17 shouldn't be a problem.
And pitillo on #wing-linux mentioned a couple of days ago that he was trying to build it for elf (aka Touch, another Omap850 device). If he succeded in making one, it should run as is on our devices.
Personally, I prefer having a Kernel that supports all Opal features before worrying about builds and packages. And sadely, I'm not having lots of success there
Anyway, check the link in my sig if you want to know more about Wing Linux.
MusikMonk said:
Personally, I prefer having a Kernel that supports all Opal features before worrying about builds and packages.
Click to expand...
Click to collapse
're right I also think that before we have a working kernel and then you can choose what you prefer
Linux is freedom
i tried android wing linux already , its cool thnx musik monk
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.
Hi all.
I'm creating a Windows Mobile Rom.
1)---I want to create a rom modifying my smartphone's rom and NOT creating a rom from a clean one (it will be almost impossibile).
2)---Which kitchen can i use?
3)---Where can I download the latest Windows Mobile 6.1 and 6.5 Builds? (Da-G's download don't work anymore on Mediafire)
Thanks
Try OS Builder as this is the most advanced and all in one solution. But be aware that if you start from an already cooked ROM you may face many kinds of problems because many cooks have applied methods to prevent dumping their ROMs.
Good luck!
tobbbie said:
Try OS Builder as this is the most advanced and all in one solution. But be aware that if you start from an already cooked ROM you may face many kinds of problems because many cooks have applied methods to prevent dumping their ROMs.
Good luck!
Click to expand...
Click to collapse
Thanks for you reply!
But, to pass from Winmo 6.0 to Winmo 6.1 or 6.5, do I need 6.1 or 6.5 builds (xip,sys)?
Where can I download these build?
Mich-C said:
Thanks for you reply!
But, to pass from Winmo 6.0 to Winmo 6.1 or 6.5, do I need 6.1 or 6.5 builds (xip,sys)?
Where can I download these build?
Click to expand...
Click to collapse
Oh well - you are much on your own with this old stuff now. Usually you cannot do much to the XIP (Kernel) parts as they are largely HW dependent. SYS is part of the ROM anyway and so part of regular cooking. Lookup the forums for your device and download what you can get. If it is an exotic device your chances are ~zero to get anything useful. If you have no experience in cooking it is a very long way to succeed (talking in weeks and months of learning!) - and there no others fighting the same problems any more. Look up the introduction link from my signature to get an idea of how things are connected.
What is your starting point (HW, ROM) and where do want to go?
TOBBIE, in practice I want to use Os Kitchen (http://forum.xda-developers.com/showthread.php?t=628948) because it's very simple to use.(I can alredy use it).
I downloaded but when I open it, I have the first screen (that showed in the thread). Is written: "....please, select an official rom update file..." It refers to an update Windows Mobile Build for cook the Rom.
So I searched Windows Mobile 6.1 and 6.5 Builds. I found 2 very good Builds from Da_G :
-6.1 http://forum.xda-developers.com/showthread.php?t=547314
-6.5 http://forum.xda-developers.com/showthread.php?t=544445
But ALL Links don't work and I ABSOLUTELY need this Build, without it, I can't cook...
Sorry, I have no experience with OS Kitchen. I have only used OS Builder finally and a very old device specific batch-kitchen before this.
Thanks, Can i give you "THANKS"?
But with wich build did you used to cook?
Mich-C said:
Thanks, Can i give you "THANKS"?
But with wich build did you used to cook?
Click to expand...
Click to collapse
Well first you need to split smartphone (no touchscreen) from touchscreen devices.
I have cooked only for smartphone -> see my signature kitchen and stuff is all there.
Then find a stock ROM for the right type (smartphone or touchscreen) with largely similar properties (screen resolution, maybe also CPU/Chipset).
Can't you tell which device you want to cook for?
I want to cook for my Toshiba Portege G910 with WinMob 6 Professional.
It's touchscreen, it has Qwerty Keyboard, it has Wvga Resolution 800x480. There is not even a rom for this device.
But I want to cook in Italian language, (I'm italian )
This will be tough I guess. Mind that a new ROM will not change the kernel, so any of the new memory schemes introduced with W6.1 and WM6.5 will not apply even if you put a new OS on top of it. So basically you will not gain speed with a new ROM. Adding a language is a tricky thing but is possible, see my signature, even without cooking an all new ROM. So is there no Italian on the device at all?
Oh, I'm sad for this: no extra speed
When I bought, my phone had italian language.
The Toshiba Portege G900 is very very similar to my G910. Also the G900 has WinMob 6.0 Pro.
An Italian guy made a Winmo 6.1 rom for the G900 (in italian language), and now the G900 is very very fast. http://www.youtube.com/watch?v=N4h23pR6JbI
I want to this with my G910, IT'S possible. Salvyc83 do this
(But now he can't help me)
Search for speed tweaks on WM6 if you are happy with the device otherwise. The effort to cook a well running 6.1 is enormous and it is not guaranteed if you get it faster on the UI then.
There are various registry settings to play with which can make the UI faster responding (cache for icons or fonts).
Good luck!
I need too to learn cooking roms. I will follow this thread.