Related
I've been reading the forum, and based on the information and the tools there I have been able to modify my extended ROM, which is great. Now of course I'd like to modify the main ROM as well, but despite the many hours I've spent searching the forum, I can't find the necessary information to do it. There's always something essential missing, something which probably is obvious to a programmer, but not to a normal user. As I've been able to modify the extended ROM, I guess I should be able to modify the main ROM too. Who can point me in the right direction?
from what i understand it's not even 100% possible with xda1 since people cant seem to make the extracted files back to a nbf file
and there are no tools that i know of that even extract the main rom from a xda2
As I understand it, when you upgrade the operating system, you're actually modifying the ROM. Some people here like to call it to "flash", I think, and there are a lot of messages about it in here. I just haven't found the information necessary to do it. I want to modify the ROM on my XDAII.
no the operating system is the rom which is in a eeprom in the device
when you flash the rom you replace the operating system with the new one
when you say modifying it mean more in the way of exchanging different files inside the rom
but if you just mean flashing the rom with a newer then here is a guide
http://wiki.xda-developers.com/wiki/HimalayaRomFlashing
What does EEP stand for? How many ROMs are there?
I've seen a ROM created here for the XDAI, containing more programs than what the devices normally come with. I would like to have a ROM on my XDAII containing the programs I use, so that I don't need to reinstall them every time the device is hard reset. Isn't this possible?
What does EEP stand for?
Click to expand...
Click to collapse
huh what does EEP have to do with this ?
suppose it could stand for
Executive Excellence Publishing
or
European Environmental Press
how many roms there are i think there are 1.5 1.6 1.66 and 1.72
about extra programs then they are not! in the rom they are in the extended rom any CAB file you copy to the extented will install after automatic after a hardreset
you should take a look at the romkitchens ( specifically for xda1, but can be made for xda2 as well ).
and mkrom, and the other romtools
EEPROM stands for "electrically erasable programmable read only memory".
this is sort of the predecessor of flash memory.
"electrically erasable programmable read only memory" sounds like a contradiction, but thanks for that, it makes more sense than EEPROM.
What about all of us users who don't have a Unix machine? I suppose we're stuck with the original ROM then, and have to install our programs over and over again for every hard reset. Of course you can put a few of them in the extended ROM, but it becomes full too quickly and you're left with installing the rest of them manually.
well you can upgrade to a newer rom as they come out
like i have 1.66 but if i wanted 1.72 i could upgrade
about contradiction heh yeah suppose so but then if it was 100% always READ ONLY then it would be random was what in it as how the transistors randomly set when it was produced
A newer ROM wouldn't contain the programs I want.
no :/ but it could contain bug fixes for ms and radiostack and such
i suspect that extented rom was made so it would be easier for the phonecompanys' and other 3th party resellers to get programs preinstalled fast without having to mess around too much in the rom
this is at the cost of memory though
but then some programs dident like to be in the rom i believe here i mean if setting files were places in the rom aswell and the program could not write to the setting file
mkrom also works on cygwin under windows.
( now I also wrote this in the wiki page )
Isn't that just for XDA I?
it works for windows ce in general.
that doesn't mean that there is no work involved in getting it to work, but it is possible to make it work for the xda2. I use it to build custom roms for the devices we sell, that is why I wrote it in the first place.
What's cygwin?
How much space is there in the ROM to add extra programs? In the ROM that this forum developed for XDA I they added quite many programs from what I could see.
http://www.google.dk/search?hl=da&ie=UTF-8&q=cygwin&btnG=Google-søgning
Thanks for that, Rudegar.
To Itsme: I don't mind the work, but it looks like its written for programmers and that if you're not a fairly skilled programmer, you wouldn't be able to do it.
and Who is The BEST ROM ?
There is no such thing as a "best ROM" - it's all up to personal preference
Hi -
There is no one right ROM for Trinity. Here's a quick explanation for what a ROM really is. There are many people on this board who know more about ROMs than I do, so if anyone sees any errors in what I've written, please let me know.
A ROM is a collection of software packaged together that when flashed to your phone installs the software. ROM packages generally consist of four categories of software:
1.) An operating system (some flavor of Windows Mobile, 5 or 6)
2.) Radio software (Radio ROM)
3.) Phone software (Dialer, Task Manager, Multimedia, SMS/MMS software, contact list)
4.) All other software (Adobe Reader, TomTom, etc.)
People create new ROM packages by gathering an operating system, a radio, and a collection of software, and "cooking" them into a single distribution file, usually in the form of a CAB compression file.
The differences between AXL and Mary are in the OS, radio and other software they have mixed together. You have to look at the contents of each ROM yourself and compare to see the exact differences. Although it would be nice, I'm not aware of anyone listing out the differences between the software choices made by each of the main ROM cookers, so you have to do it yourself.
Some important notes on ROM packages:
1.) Any software that is "cooked" into the ROM can't be removed or updated, it's in there permanently until you change your ROM. This is something to consider if you want to be able to upgrade to future versions, and is the reaosn many ROM cookers also make a "lite" version of their ROM.
2.) I'm pretty weak on this, but from what I understand in addition to the normal physical ROM memory, there is a section of physical ROM called "hidden" or "extended" ROM, and the cookers have figured out how to make that ROM available for use. This is why some ROMs show 70+ megs of ROM/RAM available. I think this extended ROM can also be used to store software.
3.) The operating systems (OS's) do continue to change. People get new phones from their telecom operator, and when they dissassemble the phone's ROM, they can extract the new OS's and check the version numbers. There is no way I know of currently to update the OS without flashing a completely new ROM. Different ROMs include different versions of the operating system, although many of the ROM cookers are quick to re-release their ROMs when a new OS comes out.
4.) Any software that can be installed manually can be installed in a ROM. This includes "trial" or "unregistered" versions. For that software, it may be installed on your phone when you install the ROM, but it is a limited-use version and you will need to purchase the software and get a registration code to unlock the full software. If the software is "cooked" into your ROM and you decide not to use it, YOU CAN'T UNINSTALL IT without reflashing to a new ROM. It won't do any harm, but it will use up memory that could be put to better use.
5.) A suggestion on other software: If you flash your OS often, it makes things easier to keep copies of the CAB files for your favorite other cab installations on your SD card, so you can easily reinstall them when you reflash the OS.
6.) Most of the ROMs use the same installer software,which works well and can recover from some errors (just follow the instructions or if no instructions retry the flash procedure). However, some telecom operators install something called a Service Provider Lock (SPL) to prevent people from installing "unapproved" software on their phone. Removing or otherwise getting around this SPL is a process called "unlocking" - if you try to reflash your phone's ROM, and something goes wrong, this SPL could prevent you from being able to fix your phone, making it useless (or "bricked"). There are software packages that should be able to fix a bricked phone (search the board to find), but it is easier to remove the SPL first, so you never have to worry about crashing your phone.
7.) If you remove your SPL, you have technically violated the terms of your contract with your service provider!!!! In daily use, it really doesn't affect them, so they probably won't make a stink about it, and probably can't tell you've done so. But, if you bring it in for service, send it in under warranty, call their service line to get support, the technician will probably see you have removed your SPL, and can refuse to provide service or warranty support. However, the techs are people and depending on the issue may or may not make a big deal about it, but it's certainly within their right to refuse to service for free.
8.) There are differences in telecom providers!!! This is particularly important with respect to Radio ROMs. If you think about it, your phone has to send the right signals to your service provider's radio tower to make a call. The specific information it has to send and the manner in which it sends it are determined by the radio protocol, which is built into the radio software. As a result, some radio software will not work with some providers, and some will work better than others. This difference willbe regional, so consider where you will be using the phone (Asia, Europe, SA, Africa, NA). Some radios could even be configured to specific providers (but I don't know for sure).
9.) Latest vs. most stable - sometimes, the latest versions introduce new bugsor are less stable than others, so consider this as well.
10.) Most of the differences between the ROMs seem to revolve aroudn the cooker's choices for phone software - the dialers, the contact managers, etc. These primarily change the "look and feel" of the phone rather than the raw performance or capabilites. Since look and feel is the big difference, it's impossible to say which look and feel everyone will like - it's a matter of taste / personal preference.
11.) Don't bug the cookers!!!! The people cooking ROMs for us are doing it in their spare time. They're not getting paid to do it, they're just trying to help each other out. While they seem to be interested in hearing about bugs so they can fix their ROMs, pestering them with requests to make some piddly change just for you is rude. Don't pester them with change requests and customizations, and then throw a hissy fit when they don't want to do it your way. If you don't like their ROM, then cook your own.
So, to pick the ROM that works for you, you're probably going to have to try a few out. The combination of OS and Radio will likely be regional (some will not be able to use the latest radio, for example), and form there on in you have to choose which has the dialer/contact manager you like the most, and includes the software you want to have (or go with a lite version).
Good luck!
Mike
to Mike (landshark),
thank you and congratulations on your excellent explanation. I wish I read this when I bought my device, would make things much easier.
Great post!!!!
Good work!!!!
will be very usefull!
Thank you!
Wonderful post!!!!
Beautiful work!!!!
will be bloody usefull!
Orz
Sticky pls !
Thanks! Very useful for a noob like me
Question about SSPL
landshark said:
Hi -
There is no one right ROM for Trinity. Here's a quick explanation for what a ROM really is. There are many people on this board who know more about ROMs than I do, so if anyone sees any errors in what I've written, please let me know.
A ROM is a collection of software packaged together that when flashed to your phone installs the software. ROM packages generally consist of four categories of software:
1.) An operating system (some flavor of Windows Mobile, 5 or 6)
2.) Radio software (Radio ROM)
3.) Phone software (Dialer, Task Manager, Multimedia, SMS/MMS software, contact list)
4.) All other software (Adobe Reader, TomTom, etc.)
People create new ROM packages by gathering an operating system, a radio, and a collection of software, and "cooking" them into a single distribution file, usually in the form of a CAB compression file.
The differences between AXL and Mary are in the OS, radio and other software they have mixed together. You have to look at the contents of each ROM yourself and compare to see the exact differences. Although it would be nice, I'm not aware of anyone listing out the differences between the software choices made by each of the main ROM cookers, so you have to do it yourself.
Some important notes on ROM packages:
1.) Any software that is "cooked" into the ROM can't be removed or updated, it's in there permanently until you change your ROM. This is something to consider if you want to be able to upgrade to future versions, and is the reaosn many ROM cookers also make a "lite" version of their ROM.
2.) I'm pretty weak on this, but from what I understand in addition to the normal physical ROM memory, there is a section of physical ROM called "hidden" or "extended" ROM, and the cookers have figured out how to make that ROM available for use. This is why some ROMs show 70+ megs of ROM/RAM available. I think this extended ROM can also be used to store software.
3.) The operating systems (OS's) do continue to change. People get new phones from their telecom operator, and when they dissassemble the phone's ROM, they can extract the new OS's and check the version numbers. There is no way I know of currently to update the OS without flashing a completely new ROM. Different ROMs include different versions of the operating system, although many of the ROM cookers are quick to re-release their ROMs when a new OS comes out.
4.) Any software that can be installed manually can be installed in a ROM. This includes "trial" or "unregistered" versions. For that software, it may be installed on your phone when you install the ROM, but it is a limited-use version and you will need to purchase the software and get a registration code to unlock the full software. If the software is "cooked" into your ROM and you decide not to use it, YOU CAN'T UNINSTALL IT without reflashing to a new ROM. It won't do any harm, but it will use up memory that could be put to better use.
5.) A suggestion on other software: If you flash your OS often, it makes things easier to keep copies of the CAB files for your favorite other cab installations on your SD card, so you can easily reinstall them when you reflash the OS.
6.) Most of the ROMs use the same installer software,which works well and can recover from some errors (just follow the instructions or if no instructions retry the flash procedure). However, some telecom operators install something called a Service Provider Lock (SPL) to prevent people from installing "unapproved" software on their phone. Removing or otherwise getting around this SPL is a process called "unlocking" - if you try to reflash your phone's ROM, and something goes wrong, this SPL could prevent you from being able to fix your phone, making it useless (or "bricked"). There are software packages that should be able to fix a bricked phone (search the board to find), but it is easier to remove the SPL first, so you never have to worry about crashing your phone.
7.) If you remove your SPL, you have technically violated the terms of your contract with your service provider!!!! In daily use, it really doesn't affect them, so they probably won't make a stink about it, and probably can't tell you've done so. But, if you bring it in for service, send it in under warranty, call their service line to get support, the technician will probably see you have removed your SPL, and can refuse to provide service or warranty support. However, the techs are people and depending on the issue may or may not make a big deal about it, but it's certainly within their right to refuse to service for free.
8.) There are differences in telecom providers!!! This is particularly important with respect to Radio ROMs. If you think about it, your phone has to send the right signals to your service provider's radio tower to make a call. The specific information it has to send and the manner in which it sends it are determined by the radio protocol, which is built into the radio software. As a result, some radio software will not work with some providers, and some will work better than others. This difference willbe regional, so consider where you will be using the phone (Asia, Europe, SA, Africa, NA). Some radios could even be configured to specific providers (but I don't know for sure).
9.) Latest vs. most stable - sometimes, the latest versions introduce new bugsor are less stable than others, so consider this as well.
10.) Most of the differences between the ROMs seem to revolve aroudn the cooker's choices for phone software - the dialers, the contact managers, etc. These primarily change the "look and feel" of the phone rather than the raw performance or capabilites. Since look and feel is the big difference, it's impossible to say which look and feel everyone will like - it's a matter of taste / personal preference.
11.) Don't bug the cookers!!!! The people cooking ROMs for us are doing it in their spare time. They're not getting paid to do it, they're just trying to help each other out. While they seem to be interested in hearing about bugs so they can fix their ROMs, pestering them with requests to make some piddly change just for you is rude. Don't pester them with change requests and customizations, and then throw a hissy fit when they don't want to do it your way. If you don't like their ROM, then cook your own.
So, to pick the ROM that works for you, you're probably going to have to try a few out. The combination of OS and Radio will likely be regional (some will not be able to use the latest radio, for example), and form there on in you have to choose which has the dialer/contact manager you like the most, and includes the software you want to have (or go with a lite version).
Good luck!
Mike
Click to expand...
Click to collapse
Sow basicly if I use Soft SPL and install a rom that has no radio and something goes wrong I can return to my original ROM. Is that right?
Thread renamed: added [Q] tag.
Please read the Announcements in the forums regarding posting rules!
Hey guys was wondering about flashing my HTC Touch Diamond, But I want a decent ROM.
Something that's not too packed up full of junk, Easy to use and a better performance.
Also maybe a guide to unlocking/debranding this phone along with a flash guide if that's not too much?
cheers.
xelasha said:
Hey guys was wondering about flashing my HTC Touch Diamond, But I want a decent ROM.
Something that's not too packed up full of junk, Easy to use and a better performance.
Also maybe a guide to unlocking/debranding this phone along with a flash guide if that's not too much?
cheers.
Click to expand...
Click to collapse
From one newbie to another, you should read the sticky posts... they are full guides and information about flashing your phone's ROM / Radio etc.
The forum 'Search' facility is your friend, it like's to be used. That's what I did and found all I needed to know about the available ROM's and Flashing process without having to ask a single question.
The New World ROM introduced a much-improved version of the Open Firmware interpreter, version 3.0, which added many missing features, fixed most of the bugs from earlier versions, and had the capability to run CHRP boot scripts. The Toolbox ROM was embedded inside a CHRP script in the System Folder called "Mac OS ROM", along with a short loader stub and a copy of the Happy Mac icon (in Mac OS X 10.2 and higher, this was replaced with a silhouette of the Apple logo on a blank gray screen) suitable for display from Open Firmware. Once the ROM was loaded from disk, the Mac boot sequence continued as usual. As before, Open Firmware could also run a binary boot loader, and version 3.0 added support for ELF objects as well as the XCOFF files versions 1.0.5 and 2.0 supported. Also, version 3.0 (as well as some of the last releases of version 2.x, starting with the PowerBook 3400) officially supported direct access to the Open Firmware command prompt from the console (by setting the auto-boot? variable to false from Mac OS, or by holding down Command-Option-O-F at boot).
rajas
new rom
Just for your info:
I got in contact with Myn for porting his Warm Eclair on Diamond + compatible devices. We want to bring this up on our Diamonds as he also has a Diamond device. So far I get Warm Eclair running til boot animation and then it stucks and reloops. His Donut build is a very fast and stable one and he cooks very good roms for the Vogue / Kaiser devices. So stay tuned, I will inform you when this gets updates.
I'll be watching this closely. I've used Myn's Warm Donut on my Vogue and was extremely pleased with it.
ByteWrencher
vatoloco said:
Just for your info:
I got in contact with Myn for porting his Warm Eclair on Diamond + compatible devices. We want to bring this up on our Diamonds as he also has a Diamond device. So far I get Warm Eclair running til boot animation and then it stucks and reloops. His Donut build is a very fast and stable one and he cooks very good roms for the Vogue / Kaiser devices. So stay tuned, I will inform you when this gets updates.
Click to expand...
Click to collapse
so if you can port it, will you also release a flashable rom?
actually isn't possible to flash an android rom..the main problem(i think)is that we can't make linux bootable without using haret
HELICOPTER88 said:
actually isn't possible to flash an android rom..the main problem(i think)is that we can't make linux bootable without using haret
Click to expand...
Click to collapse
but what about htc vogue or kaiser?
there it is possible to flash an android rom. What are the differences between these 2 devices and our diamond? If the differences aren´t too big (but I think they are) it shouldnt be so hard to make a Rom.
who said its impoassible guyz NAND=Porting i guess correct me if i am wrong experts..the only reason its still not NAND on diamond is there are still some loopholes but i think definitely the experts are working at it and crack will crack it soon
Dunnera said:
but what about htc vogue or kaiser?
there it is possible to flash an android rom. What are the differences between these 2 devices and our diamond? If the differences aren´t too big (but I think they are) it shouldnt be so hard to make a Rom.
Click to expand...
Click to collapse
to make a nand flash possible, xdandroid must be able to initialize ALL the (important) hardware on ALL the phones, becuase winmo won't be there to do it for us. I don't think we have that yet. then someone'll have to port dzo's bootloader, or write one, get a working nbh, etc... I'm sure people are hard at work on it, but there's probably some other things still pending that are more important.
vogue NEEDED nand to compensate for lack of memory. getting data on nand was huge for us. but the xdandroid devices don't have the resource constraints that vogue has... even running an unoptimized build from sqsh with minimal hardware support, my vzw tp runs as fast or faster than my vogue.
all that to say: all things will come in time.
mrkite38 said:
to make a nand flash possible, xdandroid must be able to initialize ALL the (important) hardware on ALL the phones, becuase winmo won't be there to do it for us. I don't think we have that yet. then someone'll have to port dzo's bootloader, or write one, get a working nbh, etc... I'm sure people are hard at work on it, but there's probably some other things still pending that are more important.
vogue NEEDED nand to compensate for lack of memory. getting data on nand was huge for us. but the xdandroid devices don't have the resource constraints that vogue has... even running an unoptimized build from sqsh with minimal hardware support, my vzw tp runs as fast or faster than my vogue.
all that to say: all things will come in time.
Click to expand...
Click to collapse
thx for your explanation.
i think its now better with the haret bootloader, cos you can update rootfs or zimages easily. A flashable rom would only be useful if everything works. so youre definitely right
Just a quick update for you:
I've sent out the Warm Eclair package to Myn. He will look into the thins and hopefully get the relooping boot animation working.
anyone help me how to make partition onwindow xp in my internal storage???
i cant understand from that android site...
anyone help me how to make partition onwindow xp in my internal storage???
i cant understand from that android site...
Click to expand...
Click to collapse
What don't you understand? It's stated several times in several threads and also on my website that you will need Linux for partitioning. So Windows won't work! You may use a LiveCD, though I recommend you to install Virtualbox and Ubuntu on your windows machine.
vatoloco said:
What don't you understand? It's stated several times in several threads and also on my website that you will need Linux for partitioning. So Windows won't work! You may use a LiveCD, though I recommend you to install Virtualbox and Ubuntu on your windows machine.
Click to expand...
Click to collapse
oh thanx for that...
but i am tierd of downloading..
so plz bear me...
thanx a lot i will try today..
Please let's keep this thread clean. It is intended for Porting Myn's Warm Eclair to our Diamonds (first post)
Hi
First of all I'll apologise if the flavour of this post is similar in nature to a few others but I haven't quite found an exact match for what I need when searching through the other posts and I really need a definitive answer.
The background.....
My company use a third party forms application for passing data between our field service technicians and our office. This application had been specifically designed to be run on Windows Mobile devices. Up until very recently has been perfect for the task.
With the arrival of WP7 and Android in the phone market I have been finding it increasingly difficult to source devices running windows mobile. Those which I am still able to get hold of have varying versions of WM running which presents me with a variety of continuity issues. Providing support over the phone can also be quite challenging due to slight version descrepancies.
Recently one of my suppliers has been able to source me a large number of HTC Touch Pro 2 devices, however they are again running slightly different versions of the OS.
I would like to be able to use a standard WM6.5 ROM accross all the TP2's regardless of the original version or region of the device. I have been in touch with HTC without a great deal of joy. They simply refer me to there download page where invariably I am only able to download and install the ROM which corresponds to the individual device serial number.
Finally the Question.....
If I download a custom WM6.5 ROM can I run it accross all my GSM TP2's and if so then can you point me in the right direction?
Thanks for any help you can give
if these are all unbranded phones i suggest hard spl on all of them, and download a stock rom for one of them extract the .nbh file and flash them all to the same build...easiest way....
WC
Wild Child said:
if these are all unbranded phones i suggest hard spl on all of them, and download a stock rom for one of them extract the .nbh file and flash them all to the same build...easiest way....
WC
Click to expand...
Click to collapse
Are you really suggesting a stock ROM to this guy over your ROMs?
@Si_UK If you want the stock look without the bloat and with more speed, go with Wild Child's Illuminati ROMs. They retain the functionality of the the stock ROMs, but are tweaked for better performance and stability across the board. These ROMs are a very nice business choice. Like he said, though, you will need to Hard SPL the devices to be able to flash anything other than stock ROMs.
Thanks guys
I managed to download a standard rom from HTC using one of my UK device serial numbers and gave it a try to see if the RUU would work on one of the non UK devices. It did and works fine. I was planning on replicating this now with all the devices to ensure they're all the same.
I am now going to try and Hard SPL a device and use custom ROM as recommended. I like the idea of being able to improve the speed and lose some of the crap.
Fingers crossed as I've not done this before
cajunflavoredbob said:
Are you really suggesting a stock ROM to this guy over your ROMs?
Click to expand...
Click to collapse
Hmm, Sense 2.1 roms where... ehmm... usable... Not THAT bad after all.
However those S2 Sense 2.5 aren't capable of being used more then one day.