Im looking for a clean os, preferably CE 5.2.19400 (Build 19199.1.0.0).
I want to have a clean base OS to start adding my fixes, applications and tools. I have tried to disect many of the "vanilla" versions from people, but even their clean versions still include a lot of garbage I dont want and is almost impossible to clean. I would rather start from a totally clean os and build up from there.
Thanks,
jay
I would also like to know this.
further, how can one be sure that a 'clean' os (or any freely downloadable rom for that matter) is free from software that snoops on you, etc?
Here is the 19400 dump
http://www.sendspace.com/file/kdincu
I wonder, is a Hermes dump usable to cook a Wizard ROM?
And you mention, "CE 5.2.19400 (Build 19199.1.0.0).". Is that newer or older than the custom ROMS that are advertised as WM 6.1 build 19209? I mean, does that mean CE 5.2.19209 build xxxxxx or CE 5.2.xxxxx build 19209?
Cheers!
CE 5.2.19400 (Build 19199.1.0.0) means OS from new build, XIP from old build.
However there are some fake ROMs that with modified OS version, this may be the case (Because official 19209 ROM is AKU 1.0.2, how come this ROM is still AKU1.0.0?)
ROMs for other devices can be used in Wizard after porting (at least OS(SYS+OEM) porting must be done). You may use XIP from other Wizard ROMs, but will show your old XIP build in the About screen.
Thanks for the explanation, it's clear now
Related
Are we ever going to see a ROM based on the latest stable CE OS 5.2.1933 (Build 18533.0.7.0)..? If I knew what I was doing, I would have been located this ROM and made it readily available to all as soon as it came out... It seems as if we almost got bamboozled into thinking the 1978 build was the latest ROM released which turned out to be a fake build in the long run...
New ROM of duttythroy is based on latest Build 18533.0.7.0. See ==>here<==.
duttythroy:
Its the latest Build 18533.0.7.0 with CE OS 5.2.1978 based on helmi_C pre-released rom.
It is based on the 18533.0.7.0 build but the CE OS is not based on CE OS 5.2.1933...
Anyone..?
CE OS 5.2.1933 is the latest build
the 1978 is an hex edited rom from 1918 build
I don't think there's a Kaiser rom based on 1933 is there yet?
all of these new roms are ports from other devices. personally i dont like this they are prone to bugs and other things which is still why i run my bistorage version of the Kaiser release rom. it is the most stable and has no bugs what so ever.
Okay... It kind of makes sense to me now. I could have sworn that all of the devices had access to the same ROM's once they become available and we (Kaiser/Tilt owners) just haven't paid any attention to the latest builds... I'm hoping we do get a real updated ROM in the near future though...
austinsnyc said:
all of these new roms are ports from other devices. personally i dont like this they are prone to bugs and other things which is still why i run my bistorage version of the Kaiser release rom. it is the most stable and has no bugs what so ever.
Click to expand...
Click to collapse
What exactly is your CE OS and Build?
I agree the ported roms may not be the best, but HTC is on a trend to release many msm7200 based devices, like the Touch Dual for exemple, which is extremely similar to the tytn2, and as such should profide a good source of updates.
Sounds good to me. I guess we just have to patiently wait if we want the best possible ROM's for our devices...
austinsnyc said:
all of these new roms are ports from other devices. personally i dont like this they are prone to bugs and other things which is still why i run my bistorage version of the Kaiser release rom. it is the most stable and has no bugs what so ever.
Click to expand...
Click to collapse
I have to agree with austin.... having tried every release for Kaiser so far I always go back to his bigstorage version as it´s rock solid. For your info the CE OS 5.2.1620 (Build 18125.0.4.2)
Hi there,
Anyone knows about any cleanest ROM with latest updates (OS patches, HTC patches) and no other stuff in it?
I would go for Alex's UltraCLEAN ROM but it looks like the OS is too old comparing to Helmi's/Dutty's/Schap's ones.
So far the best I ever used is Helmi's Clean ROM, no custom splashscreens, no custom graphics, just completely clean ROM (I appreciate any performance tweak, not bloody graphics )
But it looks like it's out of date these days...
Any hints?
Thanks,
Gabriel
ROM OS versions
To be clear:
Duttys New years Rom 2k8 Fixed [DualTouch v2] TouchFLO: v5.2.1933 build 18533.dutty
Dutty's SupaLite Rom v5.2.1948 build 20000.dutty
Alex.HTC.156.UC4.ROM v5.2.1620 build 18125.0.4.2
Schap's WM6 Pro 4.30 ROM v5.2.1948 build 18548.0.7.0
Helmi kaiser aku.0.7.0_04_clean v5.2.1978 build 18578.0.7.0
See the difference?
Hmm isn't Helmis the latest OS version rather than the most outdated?!?!
undac said:
Hmm isn't Helmis the latest OS version rather than the most outdated?!?!
Click to expand...
Click to collapse
Ha! You see? you got the point
How can he have such build (acting as a newest one) and be almost 3 months out of date?
Any fake going around?
FWIW, I stripped and released the Folders & OEM packages from the HTC ROM found in this thread.
thats not exactly how is works
Its not always the newest builds that are the best
But the builds usually is ported from other devices, like polaris, touch dual or w/e.
I have portet the build in my kaiser to herald, (norwegian) and I portet polaris os to herald (wwe) its the same build, I duplicated excatly same edits, removals of files...did exactly the same setup. But there is a very noticeable diffrence in speed and stability on the two ports, even though it has same apps, same setup, same os build.
I dunno if this explain anything to anyone
But do not make the mistake beliving newer os version is better.
cheers
IIRC (and I could be completely wrong here) the 5.2.1978 build was a fake.
Something to consider with these build versions is that not all of them are built for the Kaiser - some of them have been ported from other releases for other models of device.
Some people only believe in using builds that were intended for the Kaiser, others think that there are benefits from using new versions.
As with all things in software, with fixes come more bugs - newer revisions might have one thing fixed, but another three broken. You never can tell.
Beyond ROM versions, there's also software versions which can be even more significant. For example, we're seeing roms with a much newer version of the camera software now.
So there's an awful lot to consider really.
Alex 1.6 rom is using the most updated at&t rom which should include all the basic patches from bluetooth hot fix to the other stuff. If you want newest NetCF on there, you can cook that in. Many of those roms have been tweaked out, so using Alex's rom, I think is the cleanest. A little bit more understanding of these version numbers would help you understand more about these roms.
itje said:
thats not exactly how is works
Its not always the newest builds that are the best
But the builds usually is ported from other devices, like polaris, touch dual or w/e.
I have portet the build in my kaiser to herald, (norwegian) and I portet polaris os to herald (wwe) its the same build, I duplicated excatly same edits, removals of files...did exactly the same setup. But there is a very noticeable diffrence in speed and stability on the two ports, even though it has same apps, same setup, same os build.
I dunno if this explain anything to anyone
But do not make the mistake beliving newer os version is better.
cheers
Click to expand...
Click to collapse
Absolutely agree with you itje. The latest HTC OEM apps also go a long way in helping you determine how "latest" a ROM is. CE OS Build alone shows only part of the picture...
For example i have CE OS 5.2.19212 (Build 19212.1.0.3)
(Build 19212.1.0.3) = SYS
CE OS 5.2.19212 = OEM
How and why does we change the OEM number?
I noticed ex. Garmins DK2 have CE OS 5.2.20226( BUILD 20226.1.1.1)
How can it be 'CE OS 5.2.20226' ? If latest rom for Kaiser is 19214, meaning the latest OEM for Kaiser that is.
I am NOT implying that chefs on this board fake theyre CE OS build, but if its not legit we don't know what is real anymore. Sorry if the question is a bit blur but I am lost on this one.
they should be all real. It's not an official kaiser build. You are right with the last official kaiser build. The other numbers are ports from other phone roms. Sometimes those builds can even be better than the last official kaiser build, sometimes worse since incompatability. Some people are curious the new things in a new build even if its a port so they want the newest build. Good reason why chefs cook these ported roms. My honest opinion, speed wise, the ports and the latest kaiser official are the same.
well yes we can take dll's from other devices or apps to upgrade but changing the CE OS build?
Meaning, you can't port whole OEM dir! Because device drivers are there, so why change the CE OS build?
I believe the 20226 comes from the Sony Xperia X1 (made by HTC). Laurnetius26 made a statement about this in one of his ROM threads... basically, he said he wanted to experiment with the newest ROMs (not necessarily Kaiser based) to improve the performance of the Kaiser. I believe he starts with entire new ROMs and goes from there (my guess). Dutty used to make his "hybrid" ROMs where he would use parts from different ROMs and use them together. Some chefs just clean up official Kaiser ROMs. Examples of all of these are all over this board.
Well, this i know. But if you study all of Leo`s release you will notice he doesnt use a single CE OS build that is "off".
Meaning he always uses Kaiser officials, that way ie. I have no problem following up on what he uses.
As for the experiment, he just experiments with the dll's not the CE OS number.
the CE OS number comes from MSXIPKernel in XIP. OEM in imgfs has nothing to do with it.
Intresting conversation here.
I'm a noob in this as well.
Question 2 you please, maybe you can explain?
When I port I always use a shipped rom as source (OEM and XIP)
The SYS dir is ported and sometimes I port XIP as well.
How come when I do that the CE OS number is always the shipped source?
Only the (build....) changes, which I think is the SYS dir isn't?
Let's say for example CE OS 5.2.19212 (build 19588).
Are you telling CE OS 5.2.19212 is coming from XIP?
I ported XIP a few times but this number never changed.
Thanks,
Leo
dcd1182 said:
the CE OS number comes from MSXIPKernel in XIP. OEM in imgfs has nothing to do with it.
Click to expand...
Click to collapse
Laurentius26 said:
When I port I always use a shipped rom as source (OEM and XIP)
The SYS dir is ported and sometimes I port XIP as well.
How come when I do that the CE OS number is always the shipped source?
Only the (build....) changes, which I think is the SYS dir isn't?
Let's say for example CE OS 5.2.19212 (build 19588)Are you telling CE OS 5.2.19212 is coming from XIP?
I ported XIP a few times but this number never changed
Click to expand...
Click to collapse
Hey Leo. Kaiser not my teritory but couldn't resist putting in my 2 cents This indeed is an interesting conversation
The build no is determined by the "d0b41563-b345-4444-aa15-986e7c7fff99.dsm" in OS within SYS
The version is determined by "d92a4f0a-378a-4482-8fd3-bd127a05e4de.dsm" file in XIP (MSXIPKernelTlk)
Now some people hex edit these files to make the ROM look more recent, but an honest developer would use the SYS (may have altered some packs though) and XIP from the different builds and then cook
Laurentius26 said:
Intresting conversation here.
I'm a noob in this as well.
Question 2 you please, maybe you can explain?
When I port I always use a shipped rom as source (OEM and XIP)
The SYS dir is ported and sometimes I port XIP as well.
How come when I do that the CE OS number is always the shipped source?
Only the (build....) changes, which I think is the SYS dir isn't?
Let's say for example CE OS 5.2.19212 (build 19588).
Are you telling CE OS 5.2.19212 is coming from XIP?
I ported XIP a few times but this number never changed.
Thanks,
Leo
Click to expand...
Click to collapse
Yes the CE OS number comes from the XIP and the build comes from the sys to be more acurate the buld number is in the dsm file in the os folder of sys.
I'm not shure acactly where the XIP number is stored but my guess would be one of the dsm file in the xip folder
gullum said:
Yes the CE OS number comes from the XIP and the build comes from the sys to be more acurate the buld number is in the dsm file in the os folder of sys.
I'm not shure acactly where the XIP number is stored but my guess would be one of the dsm file in the xip folder
Click to expand...
Click to collapse
Tag!! Beat you to it brother
Nice to see you here!
So it's just a hack, that's what I was thinking as well.
Thank you for confirming this!
Grtz,
Leo
ababrekar said:
Hey Leo. Kaiser not my teritory but couldn't resist putting in my 2 cents This indeed is an interesting conversation
The build no is determined by the "d0b41563-b345-4444-aa15-986e7c7fff99.dsm" in OS within SYS
The version is determined by "d92a4f0a-378a-4482-8fd3-bd127a05e4de.dsm" file in XIP (MSXIPKernelTlk)
Now some people hex edit these files to make the ROM look more recent, but an honest developer would use the SYS (may have altered some packs though) and XIP from the different builds and then cook
Click to expand...
Click to collapse
one reason I havn't moved to the never builds is that they are originaly made for VGA so we need to use (old files) in some cases to get them to work on QVGA phones... this will often cause more problems then it's worth messing with.
This actualy means that even though these 20xxx builds look like they are clean ports they are in fact hybrate builds
Laurentius26 said:
Nice to see you here!
So it's just a hack, that's what I was thinking as well.
Thank you for confirming this!
Grtz,
Leo
Click to expand...
Click to collapse
for more info, read this
http://forum.xda-developers.com/showpost.php?p=2362796&postcount=350
Yeah.. you are talking about the 192 packages to 96 isn't?
Thanks Gullum.
gullum said:
one reason I havn't moved to the never builds is that they are originaly made for VGA so we need to use (old files) in some cases to get them to work on QVGA phones... this will often cause more problems then it's worth messing with.
This actualy means that even though these 20xxx builds look like they are clean ports they are in fact hybrate builds
Click to expand...
Click to collapse
Laurentius26 said:
Nice to see you here!
So it's just a hack, that's what I was thinking as well.
Thank you for confirming this!
Grtz,
Leo
Click to expand...
Click to collapse
Well it depends on the cook, if he has chosen to hack the nos or use the correct porting method by which you get the dsm files automatically and it is a true build
htctouchp said:
for more info, read this
http://forum.xda-developers.com/showpost.php?p=2362796&postcount=350
Click to expand...
Click to collapse
Oh right. I forgot to mention your research in this part of the world
Ok so let me get this straight...... using Garmin for an example...
He has his latest ROM as CE OS 20270 and build 20270. He has more and less ported the XIP and SYS folders to achieve this but in reality it is just a hack and not really a true 20270 build???
My thought on the matter is that this number is that...exactly a number!!! I have fully ported the SYS changing the 192 files to 92...and copying over the XIP (that is allowed). Sometimes I would not get the build number to change? Even though I know the files were transfered over as I replaced them.
ryncppr said:
Ok so let me get this straight...... using Garmin for an example...
He has his latest ROM as CE OS 20270 and build 20270. He has more and less ported the XIP and SYS folders to achieve this but in reality it is just a hack and not really a true 20270 build???
My thought on the matter is that this number is that...exactly a number!!! I have fully ported the SYS changing the 192 files to 92...and copying over the XIP (that is allowed). Sometimes I would not get the build number to change? Even though I know the files were transfered over as I replaced them.
Click to expand...
Click to collapse
Thats what I mentioned that when cooks port the SYS alongwith the XIP from a different build, they automatically get both the dsm files
Cooks who dont know or dont want to spend time in porting, they would hack and hex edit the nos by way which htctouchp explained in his post
ryncppr said:
Ok so let me get this straight...... using Garmin for an example...
He has his latest ROM as CE OS 20270 and build 20270. He has more and less ported the XIP and SYS folders to achieve this but in reality it is just a hack and not really a true 20270 build???
My thought on the matter is that this number is that...exactly a number!!! I have fully ported the SYS changing the 192 files to 92...and copying over the XIP (that is allowed). Sometimes I would not get the build number to change? Even though I know the files were transfered over as I replaced them.
Click to expand...
Click to collapse
well, i do not own a kaiser and am not first hand familiar with garmin's ROM, but i would still have to assume that it is NOT a "hack and not really a true 20270 build"
i would assume that garmin has properly dumped a 20270 ROM, and replaced *DPI_192* with *DPI_96*. he then moved modules into place for kaiser and theres SYS.
a properly ported XIP gets all of MSXIPKernel and MSXIPKernelLTK from the new source (and thus gets the new build number). these packages are not specific to any DPI. the only thing kept from your kaiser original is OEMXIPKernel, which has no effect on CE OS build numbers.
true in this scenario the newer CE OS source has been modified to adjust DPI but it is what i would personally consider a "true" build. gullum said that this can cause problems- i have not seen this in my experience and this is the first i have heard that. gullum can you provide any detail here?
ryncppr, i think you misunderstood here:
ababrekar said:
Now some people hex edit these files to make the ROM look more recent, but an honest developer would use the SYS (may have altered some packs though) and XIP from the different builds and then cook
Click to expand...
Click to collapse
i think we agree that a "hack" means fake build numbers, achieved by hex editing the dsm's mentioned. i very highly doubt any of the ROMs you see in this forum with well known CE OS numbers are "hacks" of this kind. they achieved that build number by properly bringing over the parts containing it.
i should also mention that in my opinion, purposely faking a MS build by hexedit is bad for our community. it does nothing positive for anyone.
Ok I understand what your saying....And I hope Garmin takes no offense to me using his name it was just the first post I saw with both the CE OS and Build numbers newer!!!
SO I fully understand then....sorry so many questions but this is what XDA-Developers forums should be like...!!!!
WHen I properly port an XIP address I should use M'reloc the check the old folders numbers against the new folders right. A majority of them seem the same but it appears there is only a few folders with different numbers?
i would just like to say that use cooked ROMs only from people whom u trust. better yet, cook a ROM for urself by porting from a shipped ROM rather than using an uploaded kitchen.
Since Msoft doesn't publish their AKUs...
Last year I compared different build ROM contents (with different AKUs) and when I was making new ROM I have "transplanted' some of the newer files from ROM with newer AKU to the ROM base with lower AKU (since I didn't want to cook ROM using untested and possibly unstable base, but I wanted few things there that weren't available with older AKU - and it worked).
I'd like to make a complete AKU in .cab file, so it could be used to update basically any older ROM build to the latest AKU version, if possible of course.
I'm thinking of AKU1.6.1 for WM6.1 (which is and most likely will be the very last AKU for WM6.1).
Has anyone tried to do something like this?
TIA
I have an old Kitchen and a base 6.1 build with lots of customisations and 3rd party apps. I really want to get WM 6.5 on my phone but want to build it myself to get my own apps and customisations in there by default
What is the best kitchen and are there any base 6.5 builds I can use? I remember trying to decompose a 6.5 ROM a while ago and the kitchen couldn't dump it sucessfully? I haven't tried in a while so want to know where to start (again?).
I did search and there is a lot of fragmented information...
Andy
i have the same problem. i hope someone can help.
i have searched some time now for a 6.5 base rom.