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.
Hey all
My charmer has arrived, and im picking it up tomorrow.
I recently had the joy of playing with two different XDA II handsets, one with an AKU 2.0 rom update and the other with an AKU 3.5 update on it. the AKU 3.5 both looked and performed a LOT better.
What i want to do is the following:
Cook and release a streamlined minimalist AKU 3.x (any AKU 3 version rom, be it 3.1,3.3,3.5)
however, my knowledge in this department is a little lacking.
is there ANYBODY in here who runs a charmer and has a little knowledge in cooking roms?
I'm thinking it would be as simple as the following:
1) extract AKU2.0 ROM from Charmer
2) Remove 'OS' part from the rom
3) extract AKU3.5 ROM from prophet (as this is the closest device)
4) insert the OS from the prophet into the charmer rom
5) Patch with drivers for charmer
6) recompile and away you go!
is there ANYBODY here who is willing to help?!
thank you
helmi_c is seems to be working on it. I have downloaded his AKU3 rom with nottice that it is not yet designed for regular user - and it really isn't Spent two days ressurecting my poor charmer...
nocturne.op.15 said:
helmi_c is seems to be working on it. I have downloaded his AKU3 rom with nottice that it is not yet designed for regular user - and it really isn't Spent two days ressurecting my poor charmer...
Click to expand...
Click to collapse
ive been looking at it too. only 2 things ive noticed is a problem with the sound and internet sharing apart from that its seems fine.
well, i'll be happy if you can provide me a copy for testing - i will send you feedback, of course
Hey
well, once my charmer comes back from repair, needless to say, i will be beta testing a good, clean, stable aku 3.3 wm5 release!
dave, could you provide some sort of quick guide on how to modify the extended rom please?!
thanx
Oh boy, if this gets uploaded would i be able to upgrade to it?
I have tried a few times with dave's other rom but had no luck as i cant unlock my phone due to, i believe, upgraing using the tmobile original file. before cid unlocking it. As i understand it i now have v2 bootloeaders which cant be cid unlocked.
Hi
Hows development of this going now? not heard anything, have PM'd Helmi
would really like to release an AKU3.x rom for the charmer, would be perfect!
an have you any response from helmi? waiting for aku 3.x so long
Well, who needs Aku3 anyway if there's a rom with wm6? ;-)
I wrote a mail to T-Mobile (Germany) and asked them about any planned updates for the Charmer. As soon as I get a response, I'm gonna post it of course.
youser, i wouldnt hold out any hope for a wm6 rom for anything currently out apart from the VERY high end like the universal/hermes
i havent had a response from helmi yet, going to wait out a little while longer.
dave106 appears to have had a 'semi-working' rom on his device albeit minor things not working like camera, but im *hoping* that shouldn't be too difficult to fix.
if dave or helmi could please please please please please (pretty) please post an update on the status of an AKU 3.x update it would be extremely helpful!!
well i'll be jumping ship soon, replacing the casing and ebaying up my charmer as im moving onto the trinity.
is there NO hope for any charmer users at the moment?! will you not help us develope a little?!
if you could provide me with a *test* rom, that has bugs in it, i could probably work on ironing out the bugs (worth mentioning that i only use my charmer solely as a PDA, not as a phone)
please dave! we need help from the masters of xda-devs!
Well, helmi's aku 3.3 rom is available on pdamobiz.com. Speed is excellent, but unfortunately this ROM contains a lot of stuff included :-(
If you can live without some regional settings, which are missing (eg. czech), this ROM might be useful for you.
Hey there, i am using an HTC p3600 (trinity) for about 2 months now
i have the following firmware:
ROM version: 1.23.405
Radio version: 1.38.00.11
ExtROM version: 1.23.405.103
my main problems is the occasional hanging of the phone
my media card being unusable from media player from time to time until deleting the WMDRM and MSMETADATA folders, and a slow GPS lock time.
would you recommend me to update my ROM? and if so to what ROM?
Is it recommended to upgrade to WM6 (I'm not that hyped about it)
my p3600 is American.
I would recommend upgrading to reading mode. (ABR mode is still a little buggy and produces unpredictable results).
Your question has been answered so many times here.
Anyway. WM6 faster. More functionality. - which ROM? depends on your needs.
Set aside some time. Read. Flash. try before you buy - and I'm sure you won't be disappointed with the upgrade. (Go with a cooked ROM - the WIndows Mobile 6 for Trinity page: http://forum.xda-developers.com/forumdisplay.php?f=359)
Some (but not all (some of the best are missing IMHO) ROMS for your Trintiy here: http://wiki.xda-developers.com/index.php?pagename=Trinity_Upgrades
what does reading/ABR mode mean?
and whats the best ROM to upgrade to?
can i upgrade without loosing all my software installs?
also, whats the best ROM if i want to stick with WM5?
Dimmmmmm
rootbit said:
what does reading/ABR mode mean?
and whats the best ROM to upgrade to?
can i upgrade without loosing all my software installs?
also, whats the best ROM if i want to stick with WM5?
Click to expand...
Click to collapse
WOWWWWWWWWWWWW-----Definitley NOT the brightest bulb in the box!!
Spend hours reading my friend!!!!
Steven2420 said:
WOWWWWWWWWWWWW-----Definitley NOT the brightest bulb in the box!!
Spend hours reading my friend!!!!
Click to expand...
Click to collapse
Hey, thats not that nice man,
you can just enlighten me with some sentences.
or a link maybe.
Sorry for being new in this business, but I'm sure Its something you can tell me about
rather then telling me to read for a couple of hours.
rootbit said:
what does reading/ABR mode mean?
and whats the best ROM to upgrade to?
can i upgrade without loosing all my software installs?
also, whats the best ROM if i want to stick with WM5?
Click to expand...
Click to collapse
Asking Before Reading mode. was a joke. It makes the information easier to find if people read relevant threads - (where often the answer to their question can be found) - and if necessary ask a question in a relevant thread (or one where the same question has been asked even)
By creating a new thread to ask this age old question - read what people have already contributed first.
To give you a head start - Best ROM is the one that does what you want on your device. I would say for a WWE ROM (World Wide English) any of AX3L, mUn (Indogo), LVSW, bepe (sticky thread in the Trinity mobile 6 forum), PDAVIET, dopod WM6 ROMs are faster than WM5 and all OK (well the dopod one's not so clever). Threads with info for all these ROMs is available in the Trinity mobile 6 forum: http://forum.xda-developers.com/forumdisplay.php?f=359
You cannot upgrade ROM without losing your sofware installs (and anything else on the Trinity's memory).
And if you're sticking to WM5 don't bother flashing.
Check out: http://wiki.xda-developers.com/index.php?pagename=Trinity_Upgrades and http://forum.xda-developers.com/forumdisplay.php?f=359
And always start here: http://wiki.xda-developers.com/index.php?pagename=HTC_Trinity. If you don't know that one then you're lost.
Great
Great, Thanks alot
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?