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?
Title says it all really. Does a ROM speed my HD2 up or wha ?
I looked into it a little bit but couldn't work it out myself which is why I post this. My ROM version is 1.43.405.1 (70124) WWE
Any info would be smashing !
The wiki is there for a reason dude!
Just take a look at the glossary and you'll know what ROM is.
A ROM is like a drop of LSD into your system; it takes you into a whole new dimension where everything is purple and you get to fly around with pigs and elephants.
A rom? Its a type of hot cafinated drink. you pour said drink over the phone, or drop the phone into a cup full and let the sweet sweet caffeine soak right into the flash chips (also called crisps). Its recommended you do this daily, the HTC Leo gets quite hungry lol
But seriously look at http://en.wikipedia.org/wiki/ROM_image , should explain it all.
they typical sarcastic answers i've come to expect on this forum .... so unhelpful !
onisuk said:
they typical sarcastic answers i've come to expect on this forum .... so unhelpful !
Click to expand...
Click to collapse
I know right? haha
Ok so just 1 more, are the Leo ROMs for installing on other devices or do you install it on the Leo to speed the system up?
onisuk said:
they typical sarcastic answers i've come to expect on this forum .... so unhelpful !
Click to expand...
Click to collapse
Unhelpful? I linked to a whole wiki on the answer....couldn't be more helpful if I copied and pasted the wiki here
Also I didn't see you answer the OPs question.
bug666 said:
I know right? haha
Ok so just 1 more, are the Leo ROMs for installing on other devices or do you install it on the Leo to speed the system up?
Click to expand...
Click to collapse
Yes the leo ROM can only be flashed to the Leo. At the moment there are only official ROMs that don't really speed anything up yet, but soon you'll be able to flash modded ROMS. Keep an eye on the ROMs Thread and the Leo wiki in my signature below.
I see I see !
you've had SO many phones by the way haha my attention was more drawn to that
and finally, what sorts of things can you do with ROMs? Say if I was to install one.
Thanks, I've had way more than in that list, those are just some of the more memorable ones
A ROM isn't a program and can't just be installed.Its more like an image or backup of an entire harddrive, it includes windows, installed programs, settings and drivers.
You can modify a ROM before you flash it to your device. Add our remove apps, change the appearance and behavior, change the OS version and try out as yet unreleased versions of winmo e.g. winmo 7 alpha or betas. The list does go on and gets quite complex, definitely something you should read up on before attempting.
ROM = operating system of a phone, a bit like Windows XP or Vista on your computer.
What can you do with 1....allows you to effectively interface with the phone and its programs, much like you can do on a computer or laptop.
Hope this simplistic explanation helps.
WB
PS: Omneity's explanation below is more accurate than mine. I was merely trying to keep it simple so you could get a handle on things.
Just to add for additional clarity: ROM is Read Only Memory i.e. it is designed that the contents can only be read in normal usage, they cannot be written to, so the original (ROM) image remains unchanged no matter what content the user adds to the phone. It's because the ROM (a silicon chip) is read-only that makes it a complex procedure to overwrite them as is the case with writing a new ROM image as discussed elsewhere on this forum.
When people discuss ROM on here they are actually talking about the software (ROM image), otherwise known as the firmware (it's software firmly embedded onto the ROM chip) that's programmed to the ROM chip, not the physical chip itself.
HTH
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.
Hello All,
Is there a way to flash zipped files into Android 2.2 installed on HD Mini SD, I would like to know a possible way other than going into the non existing recovery mode to insert files related to Arabic characters supported and I have been guided to ask in the developers section
thank u
Look, The Process is in development... so there isn't flashing updates here right now.
but it seems that you need Arabic Android support, you should try Cyanogen's Android and this can write arabic:
http://www.multiupload.com/EHMFK42U2U
thx a lot mate, i tried it and its working fine, although i preferred the FroYo interface but this one does the job
There is no CWM in SD builds. And its pretty pointless because you can add and modify the files from Wimo or PC in opposed to NAND roms
very true codiak, but the issue is that i am a normal user, i dont know how to add the files i needed to the SD build
just wait for the Nand ROM... i think project will complete soon,
then you can do what you want
crossing fingers and waiting
Which android or WM 6.5 rom for HTC Touch HD is the best for me to use? I mean, that it has everything working(Im thinking of using WM 6.5 for everyday use, and Android purely for apps and wifi (browsing, facebook, YT(optional), and maybe some music). I'm thinking of putting custom 6.5 rom in my HD. So, can some1 provide me with the best ROM out there and a tutorial to flashing it? I already know how to put Android on phone, just need a nice ROM.It would be great if you could only copy/paste ROM threads. Thanks. And sorry if i violated something on website, but im fairly new, and cant really understand all those tutorials.
P.S. Is HD running WM 6.5 rom better than it running WM 6.1?
Thanks again guys, im really gratefull ^^
WM for battery life
Android is only running properly on SD card builds - so you can have both easily enough.
I like WM6.5 but some say that WM6.1 is faster overall.
Depends what you want.
My blackstone is my work mobile and I have WM6.5 EDGE SWIFT rom on it at the moment, works well - I just need basic functionality out of it really, but battery life is very useful!
I'd love an Android NAND rom on it sometime though
the EDGE rom thread has a tutorial link in it - but the general gist is probably for WM roms:
1) update with HSPLWrapper_Blackstone_156OliNex (may be slightly different - check the tutorials first!)
2) download BlackstoneAdvancedRUU
3) find and download the rom you want, extract the .nbh and put it with the BlackstoneAdvancedRUU.exe
4) run BlackstoneAdvancedRUU.exe, task 29, run BlackstoneAdvancedRUU.exe again, task 28 and select your nbh file from the list
follow on screen instructions at all times.
you might want to flash the RADIO: HD_1.17.25.09.nbh too if you havent already got the latest radio...
Ok, i managed to somehow install WM 6.5 and its working well , got iGo on it, and some other apps. Now, which Android is the best for things i posted in my previous post?
(web browsing, music, apps) It doesn't need to have working camera, because i dont really use it, and if i needed it, i'd use it via WM 6.5.
P.S. is it possible to watch movies (.avi; .mkv; etc.) on WM 6.5 and Android?
P.P.S How to connect my phone to PC via WM and via Android?
P.P.P.S What's the status of Android Market's games and apps on Blackstone? Are they all working?
Thank you very much