Related
I have read and seen a lot about the ROM for the XDA2 but still can't understand everything abopuut it.
I understand that it is the Memory in the device that loads when you give it a hard reset. So what are the differences between the different ROM's around and is there one that stands up better than the rest?
Also how do you go about changing the ROM? And is it a safe procedure. Can I save the ROM I have and put it back with ease if a new one does not work for me?
All these questions I would love to know the answers to but could not find the answers directly here, is there anywhere I can point my navigator to to find out in simple non geekie language?
I wish I was a Geek but my brain will not cope with too much techkie stuff at one time and shuts down
Adam
Butler,
I understand your pain! But you have to begin somewhere...
Changing ROMs is a dangerous process that can lead even the most experienced " geek" through a lot of frustration and wasted time. It is however, in the nature of us, who are never contented with the normal out of the box" oftenly" flawed solutions, to tinker and experiment with the devices and create customized versions containing only the best for what we want to do.
The ROM is the software that makes your XDA work, the OS(operating system) for your device. It contains all the programs and applications needed to run the phone and PDA aspects. It also contains what is called a Radio Stack, which is what runs the Radio/ Phone version of the device.
Sometimes, these carriers will take the OS and make modifications such as installing their own time measuring/ messagin applications.These apps often cause a lot of issues in regards to performance and memory leaks and etc.
Our devices have an Operating System provided by Microsoft :twisted: and based on the Windows CE ( Compact Edition), which itself has many versions. The latest of these versions is what is called Windows Mobile 2003.
There are many ROM and Radio Stack versions ( like OS's) each with features and functionalities which work best for certain phone providers.
The XDA, MDA and XDAII are manufactured by a company called HTC ( called an OEM- Original Equipment Manufacturer) for many of our carriers.)
So playing with your ROM means potentially lobotomizing your unit :roll: , which is a thought that scares some and excites some! It is a great feeling to bring back a unit that was non-functioning or DEAD and have it working the way you want it to work...
My recomendation is that you read the posts in this and other boards before you decide to do an upgrade or tweak your XDA. Good Luck! 8)
Thanks for that Great Information. I had guessed a few of the things you wrote but it's nice to know these things from a real understandable Geek.
I love to mess with these things as well as long as I have an escape plan. Is there a way to save your exixting ROM on a PC and try others out, and if they don't work or I just dont like them put it back. I am sure there is but I have no idea how. How do you extract and load a ROM?? Also if the new ROM fails and the device does not start up can you still connect the XDA2 to a PC to put back your origional of another ROM. That is the bit that sounds scarry to me.
I use the O2 ROM that came with the phone and it really needs a bit of improving. There are several issues with it that could be looked at. Do you know of any great Radio Stacks out there???
Thanks again
Adam
By the way I am a photographer working for AP based in London and use my phone all the time to transmit my pictures back to the office. The phone does not work as well as a nokia in reliable GSM conections and GPRS and is slower have you any ideas about it?
it is possible? my htc hero can runn windows mobile??
smokeeboy said:
it is possible? my htc hero can runn windows mobile??
Click to expand...
Click to collapse
No you can not.
Why would you?
"There's so many ways for me to say this to you - Never, Not in a million years, absolutely not, no way hose, no chance Lance, net, negatorie, mm, nah, aa, and of course my own personal favorite of all time - man falling of of a cliff, Nooooooooouuuuu...!"
AdrianK said:
"There's so many ways for me to say this to you - Never, Not in a million years, absolutely not, no way hose, no chance Lance, net, negatorie, mm, nah, aa, and of course my own personal favorite of all time - man falling of of a cliff, Nooooooooouuuuu...!"
Click to expand...
Click to collapse
in french: NON lol
Jose...........
It's Jose.
*Slaps forehead*
That's what you get for copying quotes off facebook pages, peeps.
wow y would u even want to run windows mobile... I had a tmobile wing once - - - dont get me started on that phone lol.
lol im sry but even if i knew how i wouldnt tell ya cause its stupid idea.
why would you want windows mobile on your phone, well for decent media play back i.e films that you don't need to convert before you put on the phone, I've got both a android and windows phone, and personally I find the experience better on android, but converting films is a drag.
I don't see why you want to downgrade your phone
knowledge is power
I don't think this is such a bad idea actually it's kind of good for us having someone asking this...IS NOT ABOUT DOWNGRADING your beloved hero it's about the challenge it would be to do it and the KNOWLEDGE we would get by doing so...
Currently a lot of our great developers at XDA are focused on bringing android to our WM phones and they have done a great job so far using only reverse engineering methods, patience and a certainly huge amount of cups of coffee...so how about seeing things from a different angle? just imagine the possibilities if we can make WM work in an originally Android designed phone ,i bet you if someone dares to do it,not only the android porting project will benefit from this but several other open source mobile platforms that are already here[Maemo] and others to come [MeeGo], They all have one purpose bringing the end user a better and richer mobile experience which is the same reason i believe this forum was created for so...
Why not giving it a try?
up
up up up
sorry
android is a open source OS
windows mobile is not
so you can change android kernel to run on other device
windows mobile nope
I love android for this
I hate windows mobile for this
with a boot loader : you cant
and i know you don't want windows mobile on your brilliant android phone
hahaha
One time I saw a thread in the Rhodium forums where they were trying to find evidence of an Android user trying to port Windows Mobile to their phone. I didn't think it would ever happen...
Hmmm a challenge
Sounds like a great challenge, something to really upset the a few people who wander around bragging about they're "completed" operating systems (yeah right, 15 years as an IT Consultant and I've yet to hear Microsoft claim to complete anything).
Android is a PITA and not as flexible as I was told it would be - nowhere near as flexible as linux was meant to be - I wonder if its possible to go the rest of the way and compile a linux for our android phones that runs natively. Then we can really put windows phones to shame.
doofah said:
I wonder if its possible to go the rest of the way and compile a linux for our android phones that runs natively.
Click to expand...
Click to collapse
Well, of course it's possible, seeing how it's already been done. I don't know about your phone, but my CDMA Hero is most definitely running Linux natively.
So it's already running on a Linux kernel with a reasonable command line environment. It might be useful to compile a more complete set of GNU utilities for it.
Android is, in basic terms, just the GUI that's running on top of Linux. There are plenty of other GUIs designed for small devices with limited resources. Porting one of them over to run on top of the existing Linux environment shouldn't be too terribly tough.
The real trick, I would guess, would be getting all the hardware bits to work. Writing apps that can access the phone radio, gps, audio, etc.... All of those things are currently accessed through APIs that Android provides. If you remove Android, and those APIs, then there's a great deal of work to be done to make those things functional again.
So if you just want a handheld Linux box, that's easy. If you want all of the hardware features to work, and to still be able to use it as a phone, just with Android stripped out, then you've got a LOT of work ahead.
they have already ported android to win mobile it is possible to reverse see as win mobile does not have alot of anti piracy safeguards
wnathanball said:
they have already ported android to win mobile it is possible to reverse see as win mobile does not have alot of anti piracy safeguards
Click to expand...
Click to collapse
???
Maybe if you wrote complete sentences with proper punctuation, this might parse.
well am with original poster on this I for one would love and prefer to see Winmo on my hero.... I find android such a dam pain.... I have both winmo(on my kaiser) and android... But only use droid for a toy and playing games. where as I much prefer my winmo for Work and navigation... At least with Winmo theres no reliance on flippin data, Which isa pain in the butt with droid..
So come on you tech Geeks show us what you are made of...Port Winmo to hero... let us have the choice...
WM On Hero.......
say what you will about Android Vs WM but I believe WM is just perfect for me. If hero could support WM then please someone anyone help me get it on mine. I loved the convenience of WM. On my Blackstone Sync was not a problem. I get all my emails and my contacts in the same place. With Android I have to sync via G-Mail. For being open source this is a huge price for me to pay. Now I have to change my email address and redirect all my clients to G-mail so I get all my mail.
Is there any way i can flash windows mobile os on my o1. I am using "Launcher 7" right now. Love the big tiles,fonts and animation. But the style is not applied to applications
Okay, so yes, I'm rewriting my post. So sue me.
Yes, it's theoretically possible. The processors used are similar, as is most of the rest of the hardware. However, to do this, one would have to go in and rewrite the WiMo kernel to run on the hardware, then make certain that the shell would cooperate with the kernel, et cetera. I'm certain you could possibly pay someone to spend the time, energy, effort, and blood and sweat on doing so, but it'd be pretty much a waste of time.
If you're really attempting to get the programs to be visually 'aesthetic' in a similar fashion, I would suggest learning what you need to do to reprogram the apks.
I like windows ui
Guys (and girls ... if any are reading .. )
After some tinkering about (for days now) with Mango build 7720 (Thanks again YUKI + XBOXMOD!) I can confirm that the many of the issues present in Mango Beta are now gone ... Ok granted the MicroSD gets encrypted but its not meant to be removed on an original WP7! You can refer to Yuki's thread on how to unlock your MicroSD card if you don't fancy the likes Microsofts OS and want to revert back to Android .....
Now, it's a known fact that multitouch is an issue together with sound and camera. I was unable to find solutions to this issue. This thread seeks to ask / reply and hopefully implement some of the issues which remain for us to make the HD2 and hopefully run Android and WP7 natively without the abstraction layer present in the secondary bootloaders.
Question 1 - I am aware that CLK runs android only. Are the sound / camera / and multitouch issues present in WP7 also present in Android NAND roms running on CLK ?
Question 2 - How possible is it to modify CLK to run WP7 if the answer to above is NO?
Question 3 - If the issue iies in the secondary bootloader drivers (if any) ... Is there a way to modify/contribute for further development on them?
If we resolve these the HD2 would truly be a remarkable piece of hardware running virtually any OS. Presently the multitouch issue kills some of the enjoyment on WP7 ... and the source sound input gain is too high.
I really wish if we could get some serious thread going and if anyone is confident that he/she can help resolving the driver issue, feel free to pm me. I am a software developer (c#) if this can help in any way. Have been using it some years now on a daily basis. I am willing to provide my help. I hope that anyone could help along maybe we create yet another open source bootloader which does the trick.
Hoping to hear from you so we get something going ...
Regards
Al
I would really like to hear from some devs I am more than sure that the community would be very grateful.
Secondly (courtesy of warriorvibhu)
I suggest that you all Sign this Petition.. Kindly inform all fellow HD2 owners to sign it ... especially if they were impressed by WP7 on HD2.
Alcatrazx said:
Guys (and girls ... if any are reading .. )
Now, it's a known fact that multitouch is an issue together with sound and camera. I was unable to find solutions to this issue. This thread seeks to ask / reply and hopefully implement some of the issues which remain for us to make the HD2 and hopefully run Android and WP7 natively without the abstraction layer present in the secondary bootloaders.
Question 1 - I am aware that CLK runs android only. Are the sound / camera / and multitouch issues present in WP7 also present in Android NAND roms running on CLK ?
No there are some issues in camera and sound with android but is related to incomplete kernel. They are not related to each other for example no multi touch issues on android. All those issues are related to not perfect drivers hd7 is using another touchscreen panel I guess and maybe different speakers and camera. Anyway those drivers are complexed to write because we dont get source from microsoft on how to write them.
Question 2 - How possible is it to modify CLK to run WP7 if the answer to above is NO?
Theoritically yes but CLK is designed to load an linux kernel. So if we want that we need to write a complete new bootloader.
Question 3 - If the issue iies in the secondary bootloader drivers (if any) ... Is there a way to modify/contribute for further development on them?
Yes but you need to go backt to Windows 6.5 and read out the current drivers and port them to windows phone 7 properly. But you will need a JTAG for it and you must be very skilled.
If we resolve these the HD2 would truly be a remarkable piece of hardware running virtually any OS. Presently the multitouch issue kills some of the enjoyment on WP7 ... and the source sound input gain is too high.
I really wish if we could get some serious thread going and if anyone is confident that he/she can help resolving the driver issue, feel free to pm me. I am a software developer (c#) if this can help in any way.
Hoping to hear from you so we get something going ...
Regards
Al
Question
Click to expand...
Click to collapse
Hope this make some stuff clear.
You talk about a sound issue.
If your talking about the sound being too high, then a cab can be downloadeed to fix this. Doesnt limit the maximum volume, just reduces the minimum and puts bigger steps in placce.
We need an asm developer for try to fix multitouch problem... or the source code of driver...
Multi-touch is a bit better for me (don't know if the games which need two screen pressure work I didn't tried yet) but in Bing Maps and IE9 it's working most of the time.
Just hope that's will come soon, I cant wait it !
However, I also hope the Mango will worked with flash and include more apps in the marketplace.
Fisher_9511 said:
Multi-touch is a bit better for me (don't know if the games which need two screen pressure work I didn't tried yet) but in Bing Maps and IE9 it's working most of the time.
Click to expand...
Click to collapse
Its not working in any of multitouch Games.
Nice thread,curious to See the answers, definitely camera is a big issue for me, hope it get fixed soon.
Sent from my HTC HD2 using XDA App
Dont forget the need to use the "batterytrick"
good thread by the way
Unfortunately the thread won't lead to anywhere. Development on WP7/7.5 is not like development on Android. WP7 is closed source and so is the drivers.
So unless HTC themselves step in or a developer hacks new drivers up(which won't happen). We'll never see a native WP7.
We're using all the stuff that was leaked from the original LEO ROM. Also, CLK with WP7/7.5 boot support would not change this. And no, all these problems are not present in Android. But that's because the developers have more tools and open source code to work with, something we don't have.
Try to think positive man... Have you ever seen the arm listed file? We need to find a timer between the two finger... would not be so so so hard... but only hard...XD
TonyCubed said:
Unfortunately the thread won't lead to anywhere. Development on WP7/7.5 is not like development on Android. WP7 is closed source and so is the drivers.
So unless HTC themselves step in or a developer hacks new drivers up(which won't happen). We'll never see a native WP7.
We're using all the stuff that was leaked from the original LEO ROM. Also, CLK with WP7/7.5 boot support would not change this. And no, all these problems are not present in Android. But that's because the developers have more tools and open source code to work with, something we don't have.
Click to expand...
Click to collapse
Hi and thanks for the feedback. With a negative attitude the thread will lead to nowhere yes. That was what people said a year ago when they said that WP7 will never run on the HD2 but the devs ultimately got there. Thanks for answering the question re the Android drivers though.
You are RIGHT that the drivers in WP7 are closed source drivers ... so is MAGLDR. Rewriting another bootloader (if needed) which does not have all the frills of MAGLDR but which is open source could be a possibility.
I am not interested in getting into the WP7 ROM and modifying the drivers built in ... We have to use a technique similar to what they use when creating emulators by reverse engineering ... The most die hard emulators out there such as some of the Playstation emus out there were all closed source but it did not stop the devs from doing a proper emulation of the console.
I'd really appreciate if you could be more specific when you said that we are using the stuff which was leaked from the original "LEO" ROM ... as far as I know, is it not the Schubert which was leaked? Correct me if I'm wrong ... We got too far to give up just now...
Multitouch games do not work .. with the current Multitouch driver .. mainly due to the finger position bug .... This is explained in detail on youtube.
Sound is distorted because the input gain is too high ...
Let's not speak about the camera for now ... I think those are the two major issues which need to be remedied for now. Hopefully this thread will get us somewhere.
Regards
Al
Good initiative ! I hope we can make things work.
Also for those with the negative attitude...if you dont have anything good to say...dont say !
backlashsid said:
Good initiative ! I hope we can make things work.
Also for those with the negative attitude...if you dont have anything good to say...dont say !
Click to expand...
Click to collapse
Nicely said and many thanks
You talk about a sound issue.
If your talking about the sound being too high, then a cab can be downloadeed to fix this. Doesnt limit the maximum volume, just reduces the minimum and puts bigger steps in placce.
Click to expand...
Click to collapse
That is not exactly fixing the issue... It just modifies the maxima and minima ... The sound (input gain) is too high making it sound distorted from the HD2. The fix does remedy this a bit but its ... erm not really fixing the problem.
do think this would be a good idea, but its not being negative pointing out the obvious issue, its being realistic.
you see the point you made on MAGLDR and WP7 running of the HD2 is mute, and im not sure you fully understand its use, there are fundamental differences in making WP7 believe the HD2 is a native device and changing the actual drivers, you see, the SPL for the HD2 was opened up a long time ago with HSPL to be put in place which pretty much allowed us to do anything, the next critical piece was MAGLDR, which sat on top of the HSPL which gave us the potential to install android then WP, both HSPL and MAGLDR are very much programed by folk on here, they were not "hacked" or copied, they are closed source as you put it but they are built for a purpose of doing exactly what they do, enable custom ROMs, for WM, Android and WP to install. But that’s not the issue, the issue is a driver
To be clearer on the matter, IF WP7 had never been tested on the HD2 initially then we would never have had it.
The reasons for the bugs we talk about are because we have test drivers that were never supposed to see the end user. Had we not had that opportunity with the drivers on the HD2 then we would have been up the creek with it.
There are only a number of possibilities to get what we want
•HTC/OEMs go out of their way to finish the HD2 WP7 drivers and give them to use
•HTC/OEMs gives us the Relevant code and tools to do it ourselves
•We find native Windows phone devices that uses EXACTLY the same hardware which we can borrow
•Finally, the wildcard, someone who happens to know how to program for the hardware in question comes to help us.
That is it im afraid, its not being negative, you want to know what we need to do, well, there you go, the chances of HTC etc helping us are almost non-existent, finding devices with the same hardware, well i think we have more of a chance of HTC giving us them, BUT thats more to do with the very old digitiser we have, less so with the other hardware elements, so there is a possibility there.
Finding someone who can actually build a driver from the ground up? its possible, but short of putting adverts out on every developer website asking for help its not likely we will find one from this thread alone.
dazza9075 said:
do think this would be a good idea, but its not being negative pointing out the obvious issue, its being realistic.
you see the point you made on MAGLDR and WP7 running of the HD2 is mute, and im not sure you fully understand its use, there are fundamental differences in making WP7 believe the HD2 is a native device and changing the actual drivers, you see, the SPL for the HD2 was opened up a long time ago with HSPL to be put in place which pretty much allowed us to do anything, the next critical piece was MAGLDR, which sat on top of the HSPL which gave us the potential to install android then WP, both HSPL and MAGLDR are very much programed by folk on here, they were not "hacked" or copied, they are closed source as you put it but they are built for a purpose of doing exactly what they do, enable custom ROMs, for WM, Android and WP to install. But that’s not the issue, the issue is a driver
To be clearer on the matter, IF WP7 had never been tested on the HD2 initially then we would never have had it.
The reasons for the bugs we talk about are because we have test drivers that were never supposed to see the end user. Had we not had that opportunity with the drivers on the HD2 then we would have been up the creek with it.
There are only a number of possibilities to get what we want
•HTC/OEMs go out of their way to finish the HD2 WP7 drivers and give them to use
•HTC/OEMs gives us the Relevant code and tools to do it ourselves
•We find native Windows phone devices that uses EXACTLY the same hardware which we can borrow
•Finally, the wildcard, someone who happens to know how to program for the hardware in question comes to help us.
That is it im afraid, its not being negative, you want to know what we need to do, well, there you go, the chances of HTC etc helping us are almost non-existent, finding devices with the same hardware, well i think we have more of a chance of HTC giving us them, BUT thats more to do with the very old digitiser we have, less so with the other hardware elements, so there is a possibility there.
Finding someone who can actually build a driver from the ground up? its possible, but short of putting adverts out on every developer website asking for help its not likely we will find one from this thread alone.
Click to expand...
Click to collapse
ur right...man sometimes i so feel like bombarding Drew Bamford (product design HTC) emails about windows phone 7 and androi on HD2 and force him to be convinced to make drivers for us....its our right
but then again...can we really ???
backlashsid said:
ur right...man sometimes i so feel like bombarding Drew Bamford (product design HTC) emails about windows phone 7 and androi on HD2 and force him to be convinced to make drivers for us....its our right
but then again...can we really ???
Click to expand...
Click to collapse
I'd say... let's do this! If we get enough people, and those will send emails like everyday, then why not? There's nothing to lose
IF, and its a big IF, we are going to get it working better its going to need ideas like the comment from backlashsid to get unofficial support from these companies
In my humble opinion there is little chance of getting anything else working better without the support of people in the loop, essentially that means HTC and Qualcomm, but remember that by getting the HD2 running WP7 we are costing them money in lost sales, so there is little incentive for them to support us in an official capacity, what we're looking for is an insider!
it doesnt hurt hunting for new devices with the same hardware but its unlikely anyone would use old gear.
This would be nice so then we (as the community of XDA) can show off our HD2's as the beast-mode phone and bestest phone ever!
hi guys.
after trying out the UCCW software on my phone, and learned how awesome it is, i was hoping that someone knew of a design orientated software for widget developing ?
like dreamweaver for webpages that offers split screen design and code, i would love to have something similar that would allow me to get straight into design, but still have me learning the code.
Honestly i can't believe that there is not already something like this out there, well maybe there is, but i can't seem to find it.
Anyone has any good ideas about that?
i have tried running bluestacks and then UCCW in the bluestacks android emulator, but it is a bit of a mess to bounce files between photoshop and bluestacks. it is doable, but a bit messy. SO i was hoping there was a better alternative?
nothing?