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.
Related
Its not for wizard but wanted you all to know that there's a new build for wm6 and has a lots of improvement..
http://bbs.pdafans.com/thread-349265-1-1.html
I need to make learning japanese one of these years "New Year's Resolution". About all I know is ecchi suru.......... it's a very useful phrase though LOL!
lolx.. watch a japanese novel..
and btw, its not japanese.. its chinese..
OOOOOH!!! well I watch a lot of anime so words I can make out; writings are a different story though.
Testing this ROM on Wizard
I have acquired this ROM and am doing my first test burn onto my Wizard. Wish me luck...
ouch ........
Gets to 90% and then the RUU just quits. Hmmm. Anyone seen this?
Restored known good ROM. Now trying to force the new OS in with pdocwrite.exe...
baarod said:
Restored known good ROM. Now trying to force the new OS in with pdocwrite.exe...
Click to expand...
Click to collapse
are you serious or are you just a plank? this rom is not for the wizard.
A plank? I reworked it with imgfs tools using a base wizard image. If it doesn't work then I'll flash it back. Not like I'm messing with the bootloader or anything...
baarod said:
A plank? I reworked it with imgfs tools using a base wizard image. If it doesn't work then I'll flash it back. Not like I'm messing with the bootloader or anything...
Click to expand...
Click to collapse
nevermind the xip section etc........but hei....good luck!
I believe mUm can extract some files and put it into a Wizard rom.
What will be about the Htc P4350? The hardware is not really different to the wizard. Will there be a way to extract the WM6 ROM (comming on O2 germany in 2 weeks) and transform to wizard????
So what about the XIP section? ;(~
I had to reflash from SD, heh. Trust the expert. But at least I knew enough to backup... Funny but as you said, with many of the files the bin diff was equal. Only 39 files actually changed after all that "progress". So I guess your ROM is different If a way newer Universal ROM is only 39 files different than my baseline Orwell dump then it makes me wonder what the heck Microsoft is doing with all those thousands of people and billions of dollars...
AFAIK mun already ported this rom to wizard, but he won't give it to other ppl=)
faria, any chance of you using this as a base rom for your crossbow releases?
duke_stix said:
faria, any chance of you using this as a base rom for your crossbow releases?
Click to expand...
Click to collapse
yes there is....but there is a lack of time to so
Windows Mobile 6 Pro CE OS 5.2.1413 JPN
Windows Mobile 6 Pro CE OS 5.2.1413 JPN for p51
link:
http://rapidshare.com/files/23473590/P5120600.rar.html
I hope it's good.
kobin75 said:
Windows Mobile 6 Pro CE OS 5.2.1413 JPN for p51
link:
http://rapidshare.com/files/23473590/P5120600.rar.html
I hope it's good.
Click to expand...
Click to collapse
I'm not that familiar with the BenQ ROM, but I'm looking in to it now. It has some interresting programs, wonder if one can rebuild it to a wizard........... ファイルまたはアイテムを検索する デバイスの My Documents フォルダまたはメモリ カードに保存されている、ファイルやその他のアイテムを検索します。ファイル名またはアイテムに含まれている単語を使って検索できます。たとえば、メモ、予定、連絡先、仕事に含まれている単語を検索できます。 、[プログラム]、[検索] の順にタップします。 検索するファイル名、単語、またはその他の情報を [検索] に入力します。 同じ項目を以前にも検索したことがある場合は、[検索] ボックスの矢印をタップし、一覧からその項目を選択します。 検索を絞り込むには、[種類] でデータの種類を選択します。 [検索] をタップします。 My Documents フォルダとサブフォルダが検索されます。 [結果] 一覧で、開く項目をタップします。 language is a little funny too. Still, thanks for sharing.......... Question, where did you get this...( WM6 ?? Smartphone ROM for a P51 BenQ)
hi all
i'm looking for a way to edit the rom number and date please
Why? For blackberry application support or for deceiving users?
neonkoala said:
Why? For blackberry application support or for deceiving users?
Click to expand...
Click to collapse
ROTFL
Anyway...i'd like to know how to change the build number. I ported XIP over my old CORE 2.0n and i see
OS 5.2.1620 (Build 15341.2.0.0)
...so ..how to edit the build in the imgfs ?
I understand that's in the cplmain ...
Also interested in the ROM version and date too...mine looks old
EDIT:
maybe this can help you
http://wiki.xda-developers.com/index.php?pagename=Wizard_version_hack
Sorry - never thought of that scenario, Anichillus. Perhaps you could speak to Molski - he'd probably know. Else I think that Wiki reference is the only documentation you'll find.
anichillus:
Naughty naughty for not updating coredll.dll in the XIP.
That is why the build is wrong, I made a 1620 xip (Version 5.5.5.555 so as not to offend lol) which you are welcome to use if you give credit.
I dont particularly fancy explaining how to change the rom version (date is easy enough) since it involves some basic understanding of ARM assembly.
its right:
I'll happily do it for you as a one off thing.
Whiterat said:
anichillus:
Naughty naughty for not updating coredll.dll in the XIP.
That is why the build is wrong, I made a 1620 xip (Version 5.5.5.555 so as not to offend lol) which you are welcome to use if you give credit.
I dont particularly fancy explaining how to change the rom version (date is easy enough) since it involves some basic understanding of ARM assembly.
its right:
I'll happily do it for you as a one off thing.
Click to expand...
Click to collapse
you caught me lol . I tried to follow all steps .... but it appears that i missed something between the lines....
I am not an assembly guy ... i prefer things i can see easy how they're engine is working. Well, not too easy ...that would be dull
I am lazy ...i'll just go with this build ... hacked and slashed as is. Besides exams are closer than i'd want them to be
@whiterat: Are you planning on releasing XIP and a ROM for kitchen fodder? Would be nice to see
neonkoala:
I'm Tempted just to release a XIP or BaseRom.
But I am playing with my new 'secret' build at the moment
Whiterat said:
neonkoala:
I'm Tempted just to release a XIP or BaseRom.
But I am playing with my new 'secret' build at the moment
Click to expand...
Click to collapse
you're like " Muhahahaha ! "
You're making me curious ..
Whiterat said:
neonkoala:
I'm Tempted just to release a XIP or BaseRom.
But I am playing with my new 'secret' build at the moment
Click to expand...
Click to collapse
Drool....!!! Now i'm gonna be checking in even more often... **** there goes a few hours of study...
anichillus said:
ROTFL
Anyway...i'd like to know how to change the build number. I ported XIP over my old CORE 2.0n and i see
OS 5.2.1620 (Build 15341.2.0.0)
...so ..how to edit the build in the imgfs ?
I understand that's in the cplmain ...
Also interested in the ROM version and date too...mine looks old
EDIT:
maybe this can help you
http://wiki.xda-developers.com/index.php?pagename=Wizard_version_hack
Click to expand...
Click to collapse
now, i want to edit Build 15341 to build 19174.
how to do it?
Extended Kitchen for Elf/Elfin
Elfin base: New Elfin 2.xx
OS base: VF Kaiser UK 3.08.161.0 (Build 19199)
Completely rebuild the XIP section based on:
- Kaiser: MSXIPKernel, MSXIPKernelLTK
- Elfin: OEMXIPKernel
adjusted boot.rgu by adding the 19199 related changes
OEM packages except of OEMDrivers are clean 19199 packages
Requires the Microsoft Visual C++ 2008 Redistributable Package
Full XIP editing support
I've added a tool that removes the RGU's from the rom and moves all the DSM content to one DSM
Please read:
For the case that you are a cooking ROMs and getting donations for it, I would really appreciate a small donation,
cos I'm saving money for a new device. (I thing that would be fair )
Download: ELFIN_DEV_v2.1_Build_19199.rar
elfin rom not work on elf and viceversa, but I am not sure.Because there are some rom that can be used with elf and elfin.
bepe said:
WORK IN PROGRESS
I would need some information and rom testers to create this Kitchen, cos I dont have this device (no device right now )
First I would need to know if Elfin roms work on Elf?
Click to expand...
Click to collapse
That is good news....
The new 2.20.x.x Elfin ROMs work with both devices.
I asked swiftblade a while ago. It has something to do with the XIP.
pkoper said:
That is good news....
The new 2.20.x.x Elfin ROMs work with both devices.
I asked swiftblade a while ago. It has something to do with the XIP.
Click to expand...
Click to collapse
ok, great
could someone try if this rom is booting on Elf/Elfin:
http://rapidshare.com/files/89216919/OS-ElfIn.rar
it is the final 19199 build... I know it is confusing, cos there exists 19521, 19716, but this one is much newer (much faster, more stable, not beta)... don't ask my what MS is doing with this numbers, I've looked into all this builds and non of those is fake (only the 20000 build was fake, but that was not even AKU1 )
bepe said:
ok, great
could someone try if this rom is booting on Elf/Elfin:
http://rapidshare.com/files/89216919/OS-ElfIn.rar
Click to expand...
Click to collapse
I'll try after work
Hella Yeah
Great to see You over here on the Touch side Bepe.
I'd be honoured to give tis a whirl.
Just came back from sabatical and vacation.
I was just looking for a new Base to Cook and test with anyways to, Great Timing.
Bepe You Da Man, I'm Downing Now let you hear soon.
Answer to your question
bepe said:
First I would need to know if Elfin roms work on Elf?
Click to expand...
Click to collapse
I am using an Elf (Wasabi 64/128), I have flashed 2.20 ROM (for Elfin) for sometimes. It did worked on my Elf with the result that Program Memory became bigger than what it should be and extended over Storage Memory (less Storage Memory).
It also consumed higher memory.
BTW, it did work.
+++
There is one thing that I cannot do, I cannot make an OS.nb smaller than 50MB. It cannot be flashed to my Elf.
suracha said:
I am using an Elf (Wasabi 64/128), I have flashed 2.20 ROM (for Elfin) for sometimes. It did worked on my Elf with the result that Program Memory became bigger than what it should be and extended over Storage Memory (less Storage Memory).
It also consumed higher memory.
BTW, it did work.
+++
There is one thing that I cannot do, I cannot make an OS.nb smaller than 50MB. It cannot be flashed to my Elf.
Click to expand...
Click to collapse
Correct 50MB is the Limit which should give you a pretty nice Big Storage Anyhoos.
50MB limit
Noonski said:
Correct 50MB is the Limit which should give you a pretty nice Big Storage Anyhoos.
Click to expand...
Click to collapse
Yes, I known. I wish I can go lower than that.
Nice work again bepe.!
Made sticky..
@Bepe..It is great pleasure to see your wonderful kitchen at this forum.. And yes, I can confirm that all the 2.20.xxx.xx ROMs work on both the ELFs and ELFins without any hitch.
I am downloading your Build 19199 now and will try it out after work....
@Noonski... Welcome Back! The ELF forum was never the same without you..
Report
Already flashed OS-ElfIn to my Elf, it does work and it is much better than install Elfin 2.20 ROM on my Elf.
Camera doesn't work.
What pool does it have 4Mb or 8Mb???. Lately to those who we have ELF have us forgotten because 8Mb of pool it is great for us that our machine has few RAM, and nobody can say to me like to change the pool to 4Mb.
Thank you
suracha said:
Already flashed OS-ElfIn to my Elf, it does work and it is much better than install Elfin 2.20 ROM on my Elf.
Camera doesn't work.
Click to expand...
Click to collapse
Ok, thanks for testing
There are no apps installed on this rom, cos I'm not releasing an Elf ROM without having an Elf.
I'm just making a Kitchen the other ROM cooks can use.
This Kitchen is just a "perfect" port of the new OS and to add the OEM apps is job of the cooks.
tiggerbcn said:
What pool does it have 4Mb or 8Mb???. Lately to those who we have ELF have us forgotten because 8Mb of pool it is great for us that our machine has few RAM, and nobody can say to me like to change the pool to 4Mb.
Thank you
Click to expand...
Click to collapse
I dont know... to addjust that is also part of the ROM cooks
ok, so now that it is working it is time to upload the Kitchen
Upload done, happy cooking
bepe said:
Upload done, happy cooking
Click to expand...
Click to collapse
Great, Thanks.
Will try it today ...
Bad Boy Bepe.
Now you got me cooking at work.
Checking it out.
haha, this is nice Bepe!!
Finally a very clean kitchen to play with!!!
@ noonski: He gotme playing on my work also, damn cook/flash aholics!!
gr. bram
btw. is this wm 6.1?
bram_smulders said:
haha, this is nice Bepe!!
Finally a very clean kitchen to play with!!!
@ noonski: He gotme playing on my work also, damn cook/flash aholics!!
gr. bram
btw. is this wm 6.1?
Click to expand...
Click to collapse
yes, it is WM 6.1. Build 19199, forget about the other WM 6.1 builds... this one is the newest one, more stable, much faster, not beta.
19716 Is beta build and very slow
19521 Is a very old build... I've known this build for about 4 months
191xx Also old and some of them beta
19400 Also new... but no idea what exactly that is... it is somehow different from the other build
19199 Is the new build ported from a leaked HTC Kaiser rom, it seams to be something like final AKU 1; Try it, it's very fast
I have no idea were all this builds higher than 19199 come from, but all of them are real and not fake numbers. So I'm thinking MS is working with different teams on this builds. Build 195xx 197xx seam to have a newer kernel, 191xx have newer SYS stuff, 19199 is the perfect one with new kernel and SYS
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
Hi,
My name is Baron. I own a HTC P4350 PPC. I was wondering if there is any port of the Original WM 6.1 version for the Herald without any customizations. I have been trying different versions of each cook's 6.1 versions but I don't know. I like them but I guess I like things to be original lol. I really like the TouchFLO, its awesome. But if there is anyone who can help me out or even let me know how to aquire 6.1 and teach me how to port it would be nice. Maybe I can be a cook or something. But I guess that would need the help of all of you. I am familiar with flashing Heralds at the moment and of course last year I was flashing Motorolas with Motorola's custom OS not the ones with WM. Anyway thanks for your time and I hope I can be seen as a cook around here or something. Oh, don't forget about the original WM 6.1
baronmxc said:
Hi,
My name is Baron. I own a HTC P4350 PPC. I was wondering if there is any port of the Original WM 6.1 version for the Herald without any customizations. I have been trying different versions of each cook's 6.1 versions but I don't know. I like them but I guess I like things to be original lol. I really like the TouchFLO, its awesome. But if there is anyone who can help me out or even let me know how to aquire 6.1 and teach me how to port it would be nice. Maybe I can be a cook or something. But I guess that would need the help of all of you. I am familiar with flashing Heralds at the moment and of course last year I was flashing Motorolas with Motorola's custom OS not the ones with WM. Anyway thanks for your time and I hope I can be seen as a cook around here or something. Oh, don't forget about the original WM 6.1
Click to expand...
Click to collapse
There was never an original WM6.1 for the Herald. You'll have to cook your own ROM using a WM6.1 base and port it using a stock 6.0 Herald ROM without any kind of customizations except for a lot of the customizations needed to fix all the bugs that will arise from simply sticking both bases together. The original ROM tends to be slow and buggy, though... What about the original ROM do you like? There might already be a ROM that has those features.
Thanks for your fast response. I knew there was never a actual 6.1 release for the Herald, I was just wondering if anyone ported the original release to work with a Herald. But with what you said about it being buggy, I never thought about that but I guess that would make sense, but I have seen some custom ROMs with 6.1 and flashed them myself to see how it would work and these 6.1 versions were not bad at all, especially with TouchFLO. So I guess my question is, how were they able to cook a 6.1 version? They had to have picked up an original to modify it if I'm correct. As I said I would like to learn how to cook as well so if anyone has time to help me learn at least the basics that would be appreciated. I can learn more myself if I know the basics.
baronmxc said:
Thanks for your fast response. I knew there was never a actual 6.1 release for the Herald, I was just wondering if anyone ported the original release to work with a Herald. But with what you said about it being buggy, I never thought about that but I guess that would make sense, but I have seen some custom ROMs with 6.1 and flashed them myself to see how it would work and these 6.1 versions were not bad at all, especially with TouchFLO. So I guess my question is, how were they able to cook a 6.1 version? They had to have picked up an original to modify it if I'm correct. As I said I would like to learn how to cook as well so if anyone has time to help me learn at least the basics that would be appreciated. I can learn more myself if I know the basics.
Click to expand...
Click to collapse
I have a few threads dedicated to teaching how to cook. It's just the basics but it's enough to get you started.
Every 6.1 ROM here has been made by porting a 6.1 from another phone (there is no "original" per say as new versions are released all the time.) using the OEM of an original HERALD 6.0 ROM but modifying it heavily, making a custom XIP (kind of like the kernel and all the stuff related to it) from both the ported ROM and the older ROM, and then adding their own apps and tweaks.
In my case, I also do a heavy amount of stripping of useless files.
I'm kind of on the same page. I'd love to find an unmodified wm6.1. I've tried a couple of them, and they're all great, but they also have a bunch of stuff loaded in them or different versions of apps. I'd like to find a wm6.1 load that JUST has the org wm6.1 apps in it and nothing else. No mods, no alternative apps, skins, etc.
vgpclife said:
I'd like to find a wm6.1 load that JUST has the org wm6.1 apps in it and nothing else. No mods, no alternative apps, skins, etc.
Click to expand...
Click to collapse
then take an original WM6 and behappy with that...belive me ivansstripped wm6.1 ONLY have tweaks that are really useful...to correct the crappy MS waste....
If you do NOT wantto correct that crap...go with an original WM6...it the same
same here
I am also looking for this...
I am VERY new to cooking and have not been able to manage to Dump any of the 6.1 ROMs. (I must be missing something)
I would like to start with an "original" ROM that I can play with and try to build my own custom ROM
leapfrogg said:
I am also looking for this...
I am VERY new to cooking and have not been able to manage to Dump any of the 6.1 ROMs. (I must be missing something)
I would like to start with an "original" ROM that I can play with and try to build my own custom ROM
Click to expand...
Click to collapse
I guess I'm having a hard time understanding what "original" means. If you just want something clean and stripped that you can add whatever you want into it, then any of my ROMs will do.
To ivanmmj
I guess by original I meant base 6.1 ROM but since there is not an official 6.1 base ROM for Herald I was just trying to figure out how the other cooks were able to get 6.1 in their releases so I could cook up my own 6.1 for me and possibly upload it for someone to test or use. But it's ok, you already answered that for me but maybe you can point me in the right direction. I've been hearing that a Kaiser 6.1 ROM is easy to port to the Herald. But let me know how you were able to port it. I read some of your tutorials and I'll definately give it a try as soon as I get the time. Possibly this Sunday or so.
baronmxc said:
To ivanmmj
I guess by original I meant base 6.1 ROM but since there is not an official 6.1 base ROM for Herald I was just trying to figure out how the other cooks were able to get 6.1 in their releases so I could cook up my own 6.1 for me and possibly upload it for someone to test or use. But it's ok, you already answered that for me but maybe you can point me in the right direction. I've been hearing that a Kaiser 6.1 ROM is easy to port to the Herald. But let me know how you were able to port it. I read some of your tutorials and I'll definately give it a try as soon as I get the time. Possibly this Sunday or so.
Click to expand...
Click to collapse
If you're looking for a bug free base, you might be better off just using one of my ROM as a base (since I tend to release the kitchen files for my ROMs.)
I have a post somewhere here about SYS and XIP porting. Find it and follow that. It works fine with kaiser ROMs.
Thanks! I don't know if I have tried your ROMs yet. I'll give it a go.
From what I have been able to gather (not very much) is that some ROM have their RGU files removed, making it imposible to Dump the ROM. When I try to open with the Package Tool nothing happens?
leapfrogg said:
Thanks! I don't know if I have tried your ROMs yet. I'll give it a go.
From what I have been able to gather (not very much) is that some ROM have their RGU files removed, making it imposible to Dump the ROM. When I try to open with the Package Tool nothing happens?
Click to expand...
Click to collapse
Actually, some ROMs are even encrypted...
In my case, all my ROMs are released WITH the kitchen files in case you want to make your own version. All that I ask is that you mention where the base came from since the base took a long time to make.
I don't know if this is the right place for this post.... and forgive my ignorance again.
I just can't get the Kitchen to work with any 6.1 ROM. I have tried JustMe and I follow exactly the same steps as with the original ROM. I just can't get a poputated OEM or SYS folder. What am I missing?
Leapfrogg
leapfrogg said:
I don't know if this is the right place for this post.... and forgive my ignorance again.
I just can't get the Kitchen to work with any 6.1 ROM. I have tried JustMe and I follow exactly the same steps as with the original ROM. I just can't get a poputated OEM or SYS folder. What am I missing?
Leapfrogg
Click to expand...
Click to collapse
Download the JustMe mini kitchen.
...Original rom?
There isnt a true original rom. Theres a base, which cannot be loaded on herald unless is ported with original 6.0 (which is ment for herald).
So. basically it looks like this:
Base 6.1 + Original 6.0 = herald 6.1
(original) (port)
you cant just use a base for a rom. you can port it, then extract what u want and dont want though (which theretically will turn yer ported 6.1 into an "original" one)
I managed to port a 6.1 rom following ivanmmj tutorial, quoted below.
" How to port a SYS folder
1. Open your old SYS folder and copy the .VM and WinCENLS_WWE folders into your new SYS folder
2. Go to your old SYS\Shell and copy shell32.exe and shellres.dll into your new SYS\Shell
3. Replace the old SYS folder with the new one. "
but I only did step 1 and did not do step 2. It worked and seems stable.
f1rick said:
I managed to port a 6.1 rom following ivanmmj tutorial, quoted below.
" How to port a SYS folder
1. Open your old SYS folder and copy the .VM and WinCENLS_WWE folders into your new SYS folder
2. Go to your old SYS\Shell and copy shell32.exe and shellres.dll into your new SYS\Shell
3. Replace the old SYS folder with the new one. "
but I only did step 1 and did not do step 2. It worked and seems stable.
Click to expand...
Click to collapse
The Shell32.exe doesn't always have to be ported, but if you port a ROM that comes with a different dpi, you need to use your old shell32.dll (unless you want to manually convert it into the proper DPI...)