Sorry about creating a topic, but I can't find anywhere to ask.
Here I have some questions which I don't understand. Somebody please explains for me:
- What is AKU? It has any difference from ROM?
- BlueAngel doesn't has WM05 ROM, then where does it come from? Is it ported from others series (like Universe)?
Love you all ^_^
- AKU is like a patch for the WM5, take it like the SP2 for WinXp
- BA's WM5 are cooked up from the gurus here. There are attempts to get WM5 onto BA, officially, and "drivers" are written for it. Although the official finally dropped the idea of WM5 on BA, these "drivers" has been leaked to the wild, and the gurus picked them up to cooked up the WM5 for BA.
Hanmin, is my own extrapersonal opinion the these 'drivers' has bin leaked to the wild, like u say, just to create a test environment to valuate if is there the possiblity to solt an official WM2005 for this PDA...
Just an opinion
Thanks these guys very much.
But I still have some unclear things here:
- So where does the "drivers" sit in the ROM? Is that EXROM?
- According to the post of hanmin, then AKU3.2 absolutely is the ROM for BA ?
(Maybe this forum should have a topic like "History of WM5's BA" -_-")
I feel very confusing now.
- I have very vague memory on this, but as far as I can remember, these 'drivers' are information on how to function the hardware of BA. As such, these are definately sits in the main ROM, not the Ext ROM. Ext ROM stuff are generally not system vital stuff.
- AKU is a general term for WM5 upgrade, it does not tie with any device. However, the upgrade files does ties to specific device, example, AKU_version 1234_ROM_setup_for_charmer.exe.
Why do you want to learn history here? There is a good reading if you want to. Go to Magician forum, there is a thread on why there aren't (can't) WM5 for Magician, probably you can find the 'driver' reason for that.
Hie hie. You don't have to explain what drivers are
But there's nobody answer this question for me >_< :
- Who is the release-er of WM05 for BA? HTC or Microsoft
- Is WM05 for BA offical or unoffical?
Many thks
(Helmi, why don't you explain for this poor man? )
As I said in my first post up there, "BA's WM5 are cooked up from the gurus here.", not HTC, not Ms
unofficial
Is this ROM ever going to be leaked from microsoft (i presume this was how wm5 be started)?
Porting seems to be very unstable from what I have heard
A WM5 rom was never released by microsoft, although it was known to exist. It's highly unlikely MS will create a WM6 dev rom for the BA at all.
Remember, the BA originally shipped with WM2003SE. WM5 was a struggle to get working, WM6 should (by an unwritten law) be unable to run on the BA. But there are some gods out there so you never know.
Many drivers in WM6 are almost exactly the same as WM5 AFAIK. Drivers are normally the big problem, so if you have good drivers for the BA, then it's a possibility.... but don't hold your breath.
V
So was wm5 BA never really created by microsoft?
In that case, who did create it? Did someone do it from scratch?
If they did, why can't they do it in crossbow (wm6 Blue Angel)?
I think it's a bastard son of a Wizard leak.
V
hardingt0110 :
You still didn't read the wiki and the older threads as I told you few weeks ago
But Microsoft is the one who makes OS (WM5, WM2003SE,WM2003,...).
O2, Vodafone, T-Mobile, Cingular... are the ones who adapt WMx to devices.
WM5 for BA has been ported from different (but very similar) device that already comes with WM5 by xda-developers.
You cant buy it (WM6), even if you want So be patient
Biohead said:
A WM5 rom was never released by microsoft, although it was known to exist. It's highly unlikely MS will create a WM6 dev rom for the BA at all.
Remember, the BA originally shipped with WM2003SE. WM5 was a struggle to get working, WM6 should (by an unwritten law) be unable to run on the BA. But there are some gods out there so you never know.
Click to expand...
Click to collapse
The Roms never released for devices by microsoft, the producers use and adapt roms for him devices.
If HTC use Wm6 rom for him devices and Reproduce or advance BA to the WM6 or similar device then we can see WM6.
Other side If anybody can write or adapt device drivers that can be... Core software hasn't any driver i think. May be someone can syncronise Wm6 shell and BA (or resemble device) Wm5 drivers
And may be work
what a dream huh...
BA WM5 base rom is genuine created for BA, and just the OS (with AKU's and stuff) part was aded to this rom ported from another device.This base rom was leaked by one of the operators
I suppose that the needed kernel would be created by someone somehow someday, because basically Microsoft creates the new ROM, gives it to the manufacturers, then the manus will try to adapt the ROM to their devices.
As I saw somewhere on the net saying the ROM can be adapted and flashed to any device, as long as the manus manage to write the necessary drivers.v.v...those kinds of stuff. It sounds logical to me. What do you guys think 'bout this?
nht_max, that's what I thought as well but I never said anything, bowing to those who know more about these things. IMHO it is not needed to recompile the kernel unless it's for a new architecture. Proved the correct drivers can be located and they are compatible with WM6, then it should just work.
Recompiling may be necessary, I think because the new ROM is much different from the old WM5. Though I believe it'll be available some nice day.
Crossbow
nht_max said:
Recompiling may be necessary, I think because the new ROM is much different from the old WM5. Though I believe it'll be available some nice day.
Click to expand...
Click to collapse
You may be right about this, i have ported the OS part to BA rom without any changes in XIP section of rom (old core 5.1.195) and the device with this rom does not boot at all, so if the original core 5.2.x is ported to a BA rom it will work correctly, almost all OS files are related to the WM core, and if a function that they seek is not where it should be unpredicted crashes may occure.
But i think we should wait a lil more before try experiments like this, we have no any documentation about WM6, we don't know how the things work inside, it is similar to WM5 but defenately not the same. We must learn how it works and then port it and modify it to our own taste.
Also the leaked roms are from early beta stage, so they are not so stable and usable as the final version.We should wait a bit for the first official rom and build something stable enough from it for common usage. And i am not talking about BA here i am talking about rom cooking for all devices.
xplode said:
You may be right about this, i have ported the OS part to BA rom without any changes in XIP section of rom (old core 5.1.195) and the device with this rom does not boot at all, so if the original core 5.2.x is ported to a BA rom it will work correctly, almost all OS files are related to the WM core, and if a function that they seek is not where it should be unpredicted crashes may occure.
But i think we should wait a lil more before try experiments like this, we have no any documentation about WM6, we don't know how the things work inside, it is similar to WM5 but defenately not the same. We must learn how it works and then port it and modify it to our own taste.
Also the leaked roms are from early beta stage, so they are not so stable and usable as the final version.We should wait a bit for the first official rom and build something stable enough from it for common usage. And i am not talking about BA here i am talking about rom cooking for all devices.
Click to expand...
Click to collapse
Hi,
have u changed coredll.dll in xip boot?
the devices not boot in same mode if u try aku 3.5 and have coredll.dll of aku 3.2
@Tuatara,
please help me for relocating more space in xip boot
of course not, AKU 3.5 runs fine with the old core without problems, but for crossbow the coredll should be changed in order to work, the thing is that it is bigger than the old core.
I have no knowledge of editing XIP, thats why i am stuck at this point, but i have read here on the forums that the coredll.dll can be changed with one with the exact same size, and the crossbow one is bigger.
xplode said:
of course not, AKU 3.5 runs fine with the old core without problems, but for crossbow the coredll should be changed in order to work, the thing is that it is bigger than the old core.
I have no knowledge of editing XIP, thats why i am stuck at this point, but i have read here on the forums that the coredll.dll can be changed with one with the exact same size, and the crossbow one is bigger.
Click to expand...
Click to collapse
I have tried to run aku 3.5 with coredll.dll for aku 3.2 (not 3.3) and not working....(but perhaps I mistake method)
I know that there is a way in order to increase and relocate the files in xip with dumpromx but I do not know if it works for the modules (old post Tuatara on xda)
and however I have read that it must edit vdata and pdata in the modules for the just address (oki and sp3dev on buzzdev)
but sp3dev and oki not working on blu devices only tuatara have necessary experience on blu devices and I believe can help
xplode said:
Recompiling may be necessary, I think because the new ROM is much different from the old WM5.
Click to expand...
Click to collapse
You may be right about this, i have ported the OS part to BA rom without any changes in XIP section of rom (old core 5.1.195) and the device with this rom does not boot at all, so if the original core 5.2.x is ported to a BA rom it will work correctly, almost all OS files are related to the WM core, and if a function that they seek is not where it should be unpredicted crashes may occure.
Click to expand...
Click to collapse
I don't understand this. Recompiling is only required for a different architecture in my experience, but I've not done much with this platform myself. Is it linking in specific BA drivers or something?
Also the leaked roms are from early beta stage, so they are not so stable and usable as the final version.We should wait a bit for the first official rom and build something stable enough from it for common usage. And i am not talking about BA here i am talking about rom cooking for all devices.
Click to expand...
Click to collapse
I agree 100%, though I'm sure some of you will still tinker around. Interesting stuff.
we can use BA wm5 drivers, they should work fine, WM5 is 5.1.x and WM6 is 5.2.x not a major 6.0.x release do the changes are not so drastic and the drivers should work
look at windows windows 2000 uses the same drivers as xp, windows 2000 is NT5 xp is NT5.1
OK guys, thanks for your help.
So basically the main part of the wm5 rom for the BA was made by an unnamed operator, who decided not to release it, but it was leaked to xda-developers.
Then the developers made the aku's and customisations from scratch / ported from other devices, and combined them to make a full wm5 rom.
Some people (xplode and others) seem to think that the wm5 main part rom can be used to host all the bells and whistles from wm6.
So basically, all we need to do is wait untill an official very stable wm6 rom is made for a Blue Angel like device, port it, and we're all set!
Am I right?
Oh, and one last question: is the name for the main part of the rom a "kernel"? thanks,
Always be faithful in the xda-developers,
hardingt0110-1
Looking at other threads, some think it may be necesary to use sd cards as rom.
I have two sd cards (1gb and 2gb) which I swap between on my BA to allow me to have tomtom maps and movies on my device.
Untill now, I have ignored extrom.
Is it possible for me to install the extrom on both cards, so that I can swap them over when I want?
hardingt0110-1
Still Lurking ...
Hey There ... I thought I might just come out of the woodwork for a little bit ...
sostekit said:
have u changed coredll.dll in xip boot?
@Tuatara,
please help me for relocating more space in xip boot
Click to expand...
Click to collapse
sostekit said:
I know that there is a way in order to increase and relocate the files in xip with dumpromx but I do not know if it works for the modules (old post Tuatara on xda)
and however I have read that it must edit vdata and pdata in the modules for the just address (oki and sp3dev on buzzdev)
but sp3dev and oki not working on blu devices only tuatara have necessary experience on blu devices and I believe can help
Click to expand...
Click to collapse
I've been quite able to make some space in the XIP section by moving files around (to make space for larger boot registries, etc.), but I haven't had any luck with moving around modules. I think it was mamaich (and/or bepe) who managed to get the new core.dll (which has the new LASS_xxx entry points) into the BA XIP section ... but I haven't had the time to see how they managed it.
I do have the source for RomMaster & dumprom, and will be going through the details at some point - when I have the time (which is always lacking). In the same way as figuring out the Acer ROM for mamaich's tools - I'll need to see if we can dump out and 'move' modules & files around to make the space required. This may just have to be a 'one off' manual hex editing job though (fixing the tables).
While in theory the WM5 drivers should work just fine, a number of our "WM5" drivers are still 2003SE versions. How long we can keep using the old drivers is anyone's guess.
In short - as long as the XIP section contains all of the entry points and support calls required by the 'new' OS, and can start the "new" OS, then the OS portion of the ROM can be replaced. This is what we are doing with the BA now. The XIP section is still (effectively) the original leaked WM5 build, with very little, and as little replaced as possible, but just enough in order to boot the "new" OS, which has been put in the remainder of the ROM.
For reference, you can find a listing of the new functions in core.dll from here:
http://blogs.msdn.com/windowsmobiledocs/
As far as I know (from xda-dev & runour mill) the core.dll entry points have not changed between versions wm5/6 ... but that's not to say that some things don't operate differently.
Only time will tell if we can port/hack wm6 on to a Blue Angel.
Syed Ather's Windows Mobile 6 for Hima
1. Information:
ROM date: 11/11/2007
Program: 61.25MB
Storage: 30.53MB (after running HimaDOC tool)
RAMDisk: 79.64
2. Supported device:
O2 XDA II, T-Mobile MDA II, Qtek 2020, iMate Phone Edition, TSM500, and other PH10 device
3. Illustrative pictures :
3. Main Functions:
WM6 CE OS 5.2.2000 (Build 20000.1.0.0 ather90)
Comm Manager 6 buttons.
Windows Media Player for PPC Version 11.2 (Build 20000)
Device Lock Today Plugin
HTC Action Screen
BT Explorer v 1.2
Office 2007
Default Keyboard Selector
Keyboard skin (Black and White)
Download : http://rapidshare.com/files/69004141/SA_WM6_AKU_1.0.0.rar
Looking forward to it ...
But... what about the pagepool? The Ramdisk is way too big to have enough performance in my opinion.
Gonna test this right away
No the rom speed is good...i am uploading right now
(real)AKU1.0.0??
@ather90
what It can reflect the AKU1.0.0(real)?
How can get the 80M Ramdisk？The Program: 61.25MB??128-80=48M(60.25)??
and the pagepool is it loss??
the term "real" was meant for RAmdisk....the RAMdisk isnt affecting any feature of the ROM..first u guyz were complaining about low ramdisk and now Biger RAMdisk
Just test it out and u i'll know the difference
I will test it soon as I have time for it. Thank for your work
after a soft reset the ram disk loses all data.
not good, sorry.
This one is still based on the very old WM6 Wizard ROM.
It has lots of ghost-files in it.... (like touch.dll; *.dsm; ... )
Curious if this one is more stable then the others !
Thx for your effort... appreciate it (really)
Thank u guyz ..really appreciated it
Files in ramdisk lost after softreset
Hi ather90,
I've installed your ROM, its fast..
one problem though i find programs installed in ramdisk dissappeared after soft reset ...
Any chance for a quick fix ?
-Erman
What is your pagepool size and how did you manage to squeeze-in so much RAM Disk.
would it be possible that you release a 32mb ramdisc version?
Carkit not functional with this rom
Syed,
is the carkit functionality builtin this time? This because after flashing your newest rom there is no sound from the carkit speaker. I used wavedev2.dll and edited the register with taskmanager for wm6. This gives no result. Can you help me?
Greetz Frotter
i will see what i can do
@wertzui
I will release A.S.A.P
thanks, but could you also do something about the problem, that the ramdisc gets erased everytime, a soft-reset is done?
Little question:
What are the differences between AKU 0.7 and 1.0.0?
Thx.
does it have the problem of lost sms?
mine is a T-mobile MDA. I had 696 wm6(chn) rom and got lost sms. Is this new one ok with this issue? thx.
Hi, ather90! First, let me congratulate: nice good job!!! But, one question: this ROM is the only one i see with OS version number 5.2.2000. is that real or a 'personalization'? i'm searching for a kitchen to make my own cooked ROM, but i found only TofClock one... in case, have you planned a your kitchen for n00bs like me?
Hi mates...can i upgrade my WM2003 SE to WM5 or 6 in a Qtek 2020i???
Thanks
Macedo said:
Hi mates...can i upgrade my WM2003 SE to WM5 or 6 in a Qtek 2020i???
Thanks
Click to expand...
Click to collapse
There is no version of WM5 or 6 available for 2020i and there probably never will be.
BTW I do advice you, next time you visit a forum, first browse it so that you know that you're in the right section. 2020i is known here as Alpine and has its own section here http://forum.xda-developers.com/forumdisplay.php?f=249 to clearly seperate it from Himalaya. In that section your question has been asked and answered over and over again
hi i read some topic about it but if any go to Magician upgrading you will find wm6 for it and Magician have 64 mb memory but the developers make it so why no one make it for ipaq hw 6515c i hope if any one make it
Dream on Bro! They're never care anyway!
ABDALLA_WALLY said:
hi i read some topic about it but if any go to Magician upgrading you will find wm6 for it and Magician have 64 mb memory but the developers make it so why no one make it for ipaq hw 6515c i hope if any one make it
Click to expand...
Click to collapse
Ah.. Problem isin't in memory size, but in how the ROM is build.
There were never build tools for older HP iPAQ ROM dumping, You will always end up with a error. HTC tools don't work.
I have tried dumping and making ROMs for HW6500 / HW6900 / H6300 series iPAQs, but all ended up with nothing, as I where unable to get xip and imgs parts. Those ROMs are coded or compressed. WM2003 Tools ask for password, only HP engineers know that password.
Also ROM converting from WM2003 to WM5 is not easy.
cant you use rom from a 6915?shame if a rom can never be made because its a pretty solid phone.
i also read for a short while there was an update for wm5 surely someone must have it and can atleast post it?