Hello Everybody,
Made this thread so that there be a common point where you can find all the Roms either cooked or upgraded ones. I would like all of you to get involved and use this thread and paste the links of all the Roms along with their snapshots so that who so ever flash a new rom knows how it looks.
Hope this thread be a useful one for all of us.
manila 2d
http://forum.xda-developers.com/showthread.php?p=2790304
no nonsense
http://forum.xda-developers.com/showthread.php?t=455241
clean
http://forum.xda-developers.com/showthread.php?t=465291&highlight=clean
clean(GERMAN)
http://forum.xda-developers.com/showthread.php?t=489911
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
(shamelessly copied and then modified from junkdruggler's post here)
This is a DEVELOPMENT section, not GENERAL. Do NOT post questions here!
Before continuing, read this post: http://forum.xda-developers.com/showthread.php?t=729511. It also contains a link to XDA's rules, read those as well !
Let's try to post our ROMs and threads the following way to make the forum quicker and easier to access:
Code:
[KITCHEN][WWE][08.08.08] KOKOTAS ELF(in) Hybrid Kitchen (version 1.3)
[PRJ][WWE][BETA] BRAM / NOONSKI Touch Surface 6.1 Public Beta Release Candidate Unskinned
[REF] NOONSKI Cooking Class Class of 2008/09
[UPG] HTCTOUCHP New USPLs & IPLs for Elf & Elfin
[ROM][EUR][UPD][11-07-10] Doc's BareboneGalaxy v6 [2.1-u1~XWJG3][LauncherPro BETA] Optmized APKs [Barebone]
[ROM][ARA][UPD][11-07-10] ??? v1.1 [2.1-u1~XWJG3][TouchWiz 3.0] ??? [FullArabic]
[ROM][EUR][UPD][06-07-10] MoDaCo r2 [2.1-u1~XWJG1][TouchWiz] JG1/SwypeFix [OnlineKitchen]
For ROM releases, use:
Code:
[ROM][%region%][%variant%][dd-mm-yy] %name% %version% [%Androidbuild%~%baseROM%][%launcher%] %mchangelog% [%specialfeature%]
Variables as follows:
%region% - If this is an update.zip the region of base firmware. If you focus your ROM on a specific language/country put it here. Use abbreviations: EUR (Euro), ARA (Arabic), USA (United States)
%variant% - Not very useful right now since we can only use update.zip. Will become important once we get complete android builds. Use abbreviations: UPD (Update), FW (Firmware)
%name% - Name of your ROM. Whatever you want to call it.
%version% - The version of your ROM.
%Androidbuild% - This is the basebuild of android that the firmware uses. 2.1-update1 for the firmwares we have available right now. (Make it short: 2.1-u1)
%baseROM% - This is the last five symbols of the firmware you base your ROM on/that is required to install your update.zip. for example: XWJG3
%launcher% - This is the launcher you use (preferably with the version used).
%mchangelog% - Give one or two of the most important changes in this update.
%specialfeature% - One special feature of your ROM. Barebone or Online kitchen or something like that qualifies
Just some examples based on the available ROMs
[ROM][EUR][UPD][11-07-10] Doc's BareboneGalaxy v6 [2.1-u1~XWJG3][LauncherPro BETA] Optmized APKs [Barebone]
[ROM][ARA][UPD][11-07-10] ??? v1.1 [2.1-u1~XWJG3][TouchWiz 3.0] ??? [FullArabic]
[ROM][EUR][UPD][06-07-10] MoDaCo r2 [2.1-u1~XWJG1][TouchWiz] JG1/SwypeFix [OnlineKitchen]
For upgrade tools (HSPL, SSPL, CID, SIM, etc.), use:
Code:
[UPG] Description
For complete kitchens, use:
Code:
[KITCHEN][Language] name and version (Build)
For projects, use:
Code:
[PRJ] description
For utilities, use:
Code:
[UTIL] name and version
For reference threads (tutorials, guides, etc.), use:
Code:
[REF] description
A good start to a good structure
I have tried creating a standard for the ROM naming before but for lack of a sticky, there is so far only one "chef" who uses it.
http://forum.xda-developers.com/showthread.php?t=723745
Interesting. I've just copy/pasted a different post who'se layout reminds me of other sections I've moderator, and which will look familiar to users coming from the WM forums to here. I am of course open to suggestions!
Let's discuss, critisize, and formalize. Your way of naming looks smart to me, so let me share my comments.
Your original:
[%variant% ~ %region%] [dd/mm/yy] %Name% {%version%} [%Androidbuild% ~ %baseROM%] {%launcher%} %mchangelog% [%specialfeature%]
Variables as follows:
%variant% - Not very useful right now since we can only use update.zip. Will become important once we get complete android builds (Update or Firmware)
%region% - If this is an update.zip the region of base firmware. If you focus your ROM on a specific language/country put it here.
%Name% - Name of your ROM. Whatever you want to call it.
%version% - The version of your ROM.
%Androidbuild% - This is the basebuild of android that the firmware uses. 2.1-update1 for the firmwares we have available right now. (Make it short: 2.1-u1)
%baseROM% - This is the last five symbols of the firmware you base your ROM on/that is required to install your update.zip. for example: XWJG3
%launcher% - This is the launcher you use (preferably with the version used).
%mchangelog% - Give one or two of the most important changes in this update.
%specialfeature% - One special feature of your ROM. Barebone or Online kitchen or something like that qualifies
Just some examples based on the available ROMs
[Update ~ Europe] [11/07/10] Doc's BareboneGalaxy {v.6} [2.1-u1 ~ XWJG3] {LauncherPro BETA} Optimized APKs [Barebone]
[Update ~ Arabic] [11/07/10] ??? {v1.1} [2.1-u1 ~ XWJG3] {TouchWiz3.0} ??? [FullArabic]
(Sorry for the questionmarks. I don't speak/read arabic. I wish I could :/)
[Update ~ Europe] [06/07/10] MoDaCo {r2} [2.1-u1 ~ XWJG1] {TouchWiz} JG1/SwypeFix [OnlineKitchen]
Click to expand...
Click to collapse
I would keep the [ROM] prefix, just to distinguish it from normal programs, utilities, upgrades, tutorials, etc.
I would also use abbreviations to keep things short, and cut down on whitespace. variant = [UPD/FW], region = [EUR/ARA/USA/....], AndroidBuild / baseROM, without the spacing. To prevent overkill of brackets, I would not bracket the version. Also as we are using dd/mm/yy notation, AFAIK it is more common to use - instead of /. And I really just hate curly brackets, but that's personal
Example:
[ROM][EUR][UPD][11-07-10] Doc's BareboneGalaxy v6 [2.1-u1~XWJG3][LauncherPro BETA] Optmized APKs [Barebone]
Comments ? Suggestions ?
Chainfire said:
Interesting. I've just copy/pasted a different post who'se layout reminds me of other sections I've moderator, and which will look familiar to users coming from the WM forums to here. I am of course open to suggestions!
Let's discuss, critisize, and formalize. Your way of naming looks smart to me, so let me share my comments.
Your original:
I would keep the [ROM] prefix, just to distinguish it from normal programs, utilities, upgrades, tutorials, etc.
I would also use abbreviations to keep things short, and cut down on whitespace. variant = [UPD/FW], region = [EUR/ARA/USA/....], AndroidBuild / baseROM, without the spacing. To prevent overkill of brackets, I would not bracket the version. Also as we are using dd/mm/yy notation, AFAIK it is more common to use - instead of /. And I really just hate curly brackets, but that's personal
Example:
[ROM][EUR][UPD][11-07-10] Doc's BareboneGalaxy v6 [2.1-u1~XWJG3][LauncherPro BETA] Optmized APKs [Barebone]
Comments ? Suggestions ?
Click to expand...
Click to collapse
Those sound to me like sensible modifications. Now that I think back on it the curly brackets weren't really necessary ;-) And the date... my version of Windows displays the date as dd/mm/yyyy so I'm really at a loss what is convention here. but it really doesn't matter. I like the dashes too
Alright, updated first post with the changed information.
Structure is badly needed! all people are polluting this forum with topics with only questions!
Nice kang
I think most of what I said came from a stericson post... not sure though... I like READ MEs... and stickies... and FAQs...
I see only 2 ways you are EVER gonna be able to enforce this:
1) you go modo crazy and start deleting/moving stuff massively
tho you might get tired of doing so after a week or 2 ^^
2) you find somone that can modify the vbulletin post/reply form, so that it integrates the exact syntax you'd like ppl to use to post, and deny posts if it's not correctly filled out.
GL
This does not require enforcing, nor is it an exact science.
Conventions like there are used all over XDA and are generally followed. As soon as a number of the top releasers start following it in a subforum, the rest will eventually follow. It will take a while, sure... but it will happen, once the beginners realise that a structured life is a better life.
You have the option to do things nice and structured, or you can make a mess of things, but hey it'll be the mess you have to wade around in
Well said, I like the XDA naming scheme, seems to work well. Is there a mod for this section yet? someone to sticky important posts for now would do
There's an official mod, yes, and there's me. But I'll be off on vacation in a few days, for several weeks ...
Dear Friends.
I am using GoaTrip Rom on my SGS GT i9000. Now that this rom has loads of problems, I want to install Darky's ROM.
Cud somebody help with the procedure to do the needful.
Step by Step procedure will be helpful.
Plz reply to my PM - [email protected]
Regards
M Fahim
You need to study the step-by-step of whatever ROM you choose.
Hi everyone. I'm a long time observer on xda (from win mo) but am very new to android. While I'm familiar with my device and the basics, I'm very unfamiliar with android terminology. For example, I'm eager to try some of the themes I see here but don't know which files to download as they are all labeled for cm6 only, etc. and then I see they need to be "flashed".
Can someone explain the language of the elites pertaining to android please? I'm assuming they are all codes for different roms, etc.
Fyi, I have an evo running froyo, not root or anything. Everything up to date as supplied from htc/sprint
Thanks in advance
cm6 is for this ROM:
http://forum.xda-developers.com/showthread.php?t=735596
the "zip" files will work with most any ROM as long as you stay with in the OS version. Much like WM 6.1 themes would not work in 6.5. SO Android 2.1 themes will not work Android 2.2 (aka FroYo). Of course some things like Kernels are designed for certain ROMs. Like a kernel for Freshs ROM vs. a general population.
PPCUserT said:
Hi everyone. I'm a long time observer on xda (from win mo) but am very new to android. While I'm familiar with my device and the basics, I'm very unfamiliar with android terminology. For example, I'm eager to try some of the themes I see here but don't know which files to download as they are all labeled for cm6 only, etc. and then I see they need to be "flashed".
Can someone explain the language of the elites pertaining to android please? I'm assuming they are all codes for different roms, etc.
Fyi, I have an evo running froyo, not root or anything. Everything up to date as supplied from htc/sprint
Thanks in advance
Click to expand...
Click to collapse
you need to be rooted to apply themes and ROMs. Currently though, there is no way to root if you already have Froyo.
Flashing a new ROM, theme, or anything with the same regards simply means to wipe away what exists and replace it with something new.
So when you are flashing a new ROM, you are taking away the old one (with a data wipe aka factory reset) and then installing the saved zip file (contains the ROM) onto the computer.
Unfortunitly themes can't just be installed like they could on WM they need to be "flashed". These means you need to enter the phones bootloader. If you don't know what all that means then you have some more reading before you can get into themes. Much of which was said in the post above this.
Thanks everyone. And thanks for not flaming me, lol
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.