I happen to agree with ABF here. I'm not a programmer, I'm good with electronics, computers and various low level programmable hardware. I work with the kind of guys who do firmware programming and have the kind of knowledge you need to begin properly working on these devices in a meaningful way and it is by no means a simple feat. We even have a PXA270 dev kit knocking around the place that one of them got asteroids running on, but even he would be stumped with all the proprietary hardware in the Axim. As ABF said, you need $$$$ and access to all the hardware info of the device to do it yourself.
Asking the question "Can sum1 hak teh WM6 ROM?!?!" Immediately marks you down as not having any comprehension of what is involved, and it is insulting to the people who work on these things that you think that it is as simple as one person sitting down and deciding to just "make it work" in their copious free time...
Sure you can cludge a load of files together in the right way using someone elses work as a base to create a ROM image that works. But what happens when one of the new files is not the same version or doesn't support something explicitly needed by by another system file, or you put a wrong file in? You get a crock of sh*t, that's what.
Yes, Football did incredibly well getting AKU3.5 to work, but CF doesn't work and from what I can tell there are other issues. Nice work, but even with his skill he is lacking either some of the necessary files or the ability to make working replacements.
I'm all for people pushing the boundaries and *making* it work, but the following has to be taken into account.
1) It's harder than you think it is.
2) There are very few people on this forum capable of it. xda-developers is different, it's based on hardware minded people coming together to support a device themselves. Aximsite is based on end users with little or no working knowledge of the internals of the device.
3) It is ILLEGAL. WM6 is commercial software and if you haven't paid for it then you have no right to use it. The fact that Dell isn't giving you a choice about paying for it is not an excuse for piracy.
4) Seriously, it is a LOT harder than you think it is to "just hakit plaese!"
So please, show some intelligence and respect for the people behind the scenes. It's childish and immoral to whine and plead for someone to do something that is not only difficult but also illegal just so you can play with the latest and greatest software.
__________________ pencil and paper: n.An archaic information storage and transmission device that works by depositing smears of graphite on bleached wood pulp. More recent developments in paper-based technology include improved ‘write-once’ update devices which use tiny rolling heads similar to mouse balls to deposit colored pigment.
I happen to agree with ABF here. I'm not a programmer, I'm good with electronics, computers and various low level programmable hardware. I work with the kind of guys who do firmware programming and have the kind of knowledge you need to begin properly working on these devices in a meaningful way and it is by no means a simple feat. We even have a PXA270 dev kit knocking around the place that one of them got asteroids running on, but even he would be stumped with all the proprietary hardware in the Axim. As ABF said, you need $$$$ and access to all the hardware info of the device to do it yourself.
Asking the question "Can sum1 hak teh WM6 ROM?!?!" Immediately marks you down as not having any comprehension of what is involved, and it is insulting to the people who work on these things that you think that it is as simple as one person sitting down and deciding to just "make it work" in their copious free time...
Sure you can cludge a load of files together in the right way using someone elses work as a base to create a ROM image that works. But what happens when one of the new files is not the same version or doesn't support something explicitly needed by by another system file, or you put a wrong file in? You get a crock of sh*t, that's what.
Yes, Football did incredibly well getting AKU3.5 to work, but CF doesn't work and from what I can tell there are other issues. Nice work, but even with his skill he is lacking either some of the necessary files or the ability to make working replacements.
I'm all for people pushing the boundaries and *making* it work, but the following has to be taken into account.
1) It's harder than you think it is.
2) There are very few people on this forum capable of it. xda-developers is different, it's based on hardware minded people coming together to support a device themselves. Aximsite is based on end users with little or no working knowledge of the internals of the device.
3) It is ILLEGAL. WM6 is commercial software and if you haven't paid for it then you have no right to use it. The fact that Dell isn't giving you a choice about paying for it is not an excuse for piracy.
4) Seriously, it is a LOT harder than you think it is to "just hakit plaese!"
So please, show some intelligence and respect for the people behind the scenes. It's childish and immoral to whine and plead for someone to do something that is not only difficult but also illegal just so you can play with the latest and greatest software.
Quoted for agreement over the legal issues over 'hacking' wm6 rom and i totally agree with ABF even though I have no idea about computer programming its plainly obvious you can`t do it easily if at all... after all you have drivers to think about and how much do big companies have to shell out to get there stuff working on Vista? And how many people work on them?
hopefully they get the wifi working on the X51v linux disto. Its open source, up to date, free, and runs from the SD card so there's no risk of bricking you axim. If ABF is such a good programmer maybe he should work on it.
I happen to agree with ABF here. I'm not a programmer, I'm good with electronics, computers and various low level programmable hardware. I work with the kind of guys who do firmware programming and have the kind of knowledge you need to begin properly working on these devices in a meaningful way and it is by no means a simple feat. We even have a PXA270 dev kit knocking around the place that one of them got asteroids running on, but even he would be stumped with all the proprietary hardware in the Axim. As ABF said, you need $$$$ and access to all the hardware info of the device to do it yourself.
Asking the question "Can sum1 hak teh WM6 ROM?!?!" Immediately marks you down as not having any comprehension of what is involved, and it is insulting to the people who work on these things that you think that it is as simple as one person sitting down and deciding to just "make it work" in their copious free time...
Sure you can cludge a load of files together in the right way using someone elses work as a base to create a ROM image that works. But what happens when one of the new files is not the same version or doesn't support something explicitly needed by by another system file, or you put a wrong file in? You get a crock of sh*t, that's what.
Yes, Football did incredibly well getting AKU3.5 to work, but CF doesn't work and from what I can tell there are other issues. Nice work, but even with his skill he is lacking either some of the necessary files or the ability to make working replacements.
I'm all for people pushing the boundaries and *making* it work, but the following has to be taken into account.
1) It's harder than you think it is.
2) There are very few people on this forum capable of it. xda-developers is different, it's based on hardware minded people coming together to support a device themselves. Aximsite is based on end users with little or no working knowledge of the internals of the device.
3) It is ILLEGAL. WM6 is commercial software and if you haven't paid for it then you have no right to use it. The fact that Dell isn't giving you a choice about paying for it is not an excuse for piracy.
4) Seriously, it is a LOT harder than you think it is to "just hakit plaese!"
So please, show some intelligence and respect for the people behind the scenes. It's childish and immoral to whine and plead for someone to do something that is not only difficult but also illegal just so you can play with the latest and greatest software.
>i am a very experienced programmer with more then 12 langs.
and English is not one of them ...
Let's just say trying to put WM6 on the X51v is like trying to put a 2007 F150 engine into a 2004 one. Unless you have the experiences, you aren't doing it.
Well, it CAN be hacked - in theory. In reality, it takes a lot more effort... because of the many things that AximBigFan and Mokubai have already posted. To add to their points, I'd like to point out the following arguments which may be marshalled against them:
1) "Why can't it be hacked? The phones at the XDA-Developers Forum get hacked all the time!" - I'll be the first to point out that most of those phones they're hacking have identical, or near-identical hardware, when it comes to the ROM image changes that they're posting. Most of them are at least in the same family, if not simply revisions of the previous model. This makes it a LOT easier on the people doing the homebrew - they can apply their knowledge of the previous ROM and its drivers to the current set and be reasonably certain that they won't completely screw up the ROM image when putting it together.
2) "Why isn't it legal? Windows Mobile 6 is available to download, and they post these at the XDA-Developers Forum!" - Recently, Microsoft took action against the people at XDA-Developers, basically sending them an email to 'cease and desist - or else'. In compliance with the demands of Microsoft, ROM images have been or are being removed from the site. This has previously been mentioned on this board, from what I remember.
3) "It can't be that hard - that Football guy did it." - he sure did, and he did an amazing job trying to translate a ROM from one device to another. However, even with his relatively well-done job, there were problems with the Broadcomm drivers, the CF card didn't work at all (and that's a very basic function), and there were other issues reported with the image in question. The problem is only compounded because ROM images are NOT the equivalent of a desktop Windows install CD; they're IMAGES of the OS, which is the equivalent of a CD or DVD with a Windows disk image shipped from a manufacturer for a specific model of computer - if you try to put it onto another system with different hardware... it may not work, and the drivers won't be handy.
To sum up - in theory, the ROM image can be 'hacked'... but it's less a 'hack job' that means bypassing some sort of security lock to allow it to be installed on another device, and more a dissection of the ROM image followed by careful reconstruction using a Frankensteinian-style collection of drivers and software modules, which might work on the device without screwing up anything in particular.
Well, it CAN be hacked - in theory. In reality, it takes a lot more effort... because of the many things that AximBigFan and Mokubai have already posted. To add to their points, I'd like to point out the following arguments which may be marshalled against them:
1) "Why can't it be hacked? The phones at the XDA-Developers Forum get hacked all the time!" - I'll be the first to point out that most of those phones they're hacking have identical, or near-identical hardware, when it comes to the ROM image changes that they're posting. Most of them are at least in the same family, if not simply revisions of the previous model. This makes it a LOT easier on the people doing the homebrew - they can apply their knowledge of the previous ROM and its drivers to the current set and be reasonably certain that they won't completely screw up the ROM image when putting it together.
2) "Why isn't it legal? Windows Mobile 6 is available to download, and they post these at the XDA-Developers Forum!" - Recently, Microsoft took action against the people at XDA-Developers, basically sending them an email to 'cease and desist - or else'. In compliance with the demands of Microsoft, ROM images have been or are being removed from the site. This has previously been mentioned on this board, from what I remember.
3) "It can't be that hard - that Football guy did it." - he sure did, and he did an amazing job trying to translate a ROM from one device to another. However, even with his relatively well-done job, there were problems with the Broadcomm drivers, the CF card didn't work at all (and that's a very basic function), and there were other issues reported with the image in question. The problem is only compounded because ROM images are NOT the equivalent of a desktop Windows install CD; they're IMAGES of the OS, which is the equivalent of a CD or DVD with a Windows disk image shipped from a manufacturer for a specific model of computer - if you try to put it onto another system with different hardware... it may not work, and the drivers won't be handy.
To sum up - in theory, the ROM image can be 'hacked'... but it's less a 'hack job' that means bypassing some sort of security lock to allow it to be installed on another device, and more a dissection of the ROM image followed by careful reconstruction using a Frankensteinian-style collection of drivers and software modules, which might work on the device without screwing up anything in particular.
yes and no.
i actully really doubt that it is even possible to get wm6 to work on an x5XX without COMPLETELY rewriting the microcodes.
then the x50 came out, HTC knew that they were going to release wm5 for it, so they made damn sure that they could get wm5 working on it, whereas, the x5XX was NEVER meant for wm6, there for it wasnt desgined to handle wm6. its kind of like this; the long ez was meant to be a small aircraft with a single engine/prop. you just cant take the turbine out of a boeing 747 and shove it in the back. it just sint possible. the landing gear would crush under the incredible weght, the airfram would not be able to handle the extreme thrust of the turbine, and the fual tanks would never be able to keep a turbine of that size feed for more then a few min (if that).
From what I can recall, the change from WM2003SE to WM5 was much more radical than the change from WM5 to WM6, as far as software architectures went; the PDA equivalent of the Win98 to WinXP jump, as far as underlying architecture and design concepts went. In theory, it may be possible to get WM6 working on the x50/51 series due to an apparent lack of fundamental changes to the codebase; the problem is always going to be the drivers, in any changeover.
However, that being said, I wouldn't trust anyone but HTC to really get a ROM together right - they've got all the design docs, all of the parameters, they know the hardware down to the last EEPROM and logic gate. ANyone else would basically be guessing - like trying to do brain surgery after reading about the topic on Wikipedia.
Follow Us
RSS Feed
Follow on Twitter
Facebook
YouTube
