Related
I'm looking at http://3ppc.net/index.php?showtopic=2089 and I see that Remember ported it to our wizard but it's in russian!
I can also say that he's currently porting 5.2.1620...
So the question is anyone working on WWE build?
=D
could you post the direct links directly
i hope its simple just replacing the mui's
I'm not sure whether that forum allows posting direct links but here it is
http://3ppc.net/Users/remember/HTC_Wizard_WM6Pro_RUS_The_present_fairy_tale.7z
About that rom:
It is build on the XIP/imgfs of 1437..
Regarding the XIP, it's the old XIP, so the new kerneldll.dll hasn't been used (that is why the OS version shows 5.2.1437, and it's causing some other problems too)
Also the drivers are not rebased for this 5.2.1620 ROM, that will be causing some more errors..
So in short, it's the "old" 1437 wrapper with the new SYS package inside.
But the wrapper will cause some problems..
The original 18125 (that IS the 5.2.1620 ) has a lot of bugfixes, would be nice to see a real port.
My advice is to wait till a propper Chef ports the XIP, the Rom and did a full rebase of the drivers.
Okey so I obviously lied when I said that 1437 was my last rom heh
Im on the job
Just downloading now, then some sleep, then will start creating the new XIP.
(Damn! I need to think of a new offensive version now....)
Then will rebase drivers and release, I expect about 1 week..
Whiterat said:
(Damn! I need to think of a new offensive version now....)
Click to expand...
Click to collapse
Why? I hope you are kidding...
Whiterat said:
Okey so I obviously lied when I said that 1437 was my last rom heh
Im on the job
Just downloading now, then some sleep, then will start creating the new XIP.
(Damn! I need to think of a new offensive version now....)
Then will rebase drivers and release, I expect about 1 week..
Click to expand...
Click to collapse
Dude,
Excellent work on your ROMS. Now, I am just waiting for your kitchen.
new build rom(5.2.1620(Build 18125.0.4.2)
alread be ported to wizard sucessfully one week ago
http://bbs.pdafans.com/thread-395528-1-1.html
Whiterat said:
Okey so I obviously lied when I said that 1437 was my last rom heh
Im on the job
Just downloading now, then some sleep, then will start creating the new XIP.
(Damn! I need to think of a new offensive version now....)
Then will rebase drivers and release, I expect about 1 week..
Click to expand...
Click to collapse
Aw well... I finally decided to live with the latest ROM from you. I visited the site to change my sig. After seeing the above post, I am tempted to wait for some more time.
kernelguy
cool
very cool!
whiterat thanks for your good news.it would be nice to have new base rom...
email123 said:
new build rom(5.2.1620(Build 18125.0.4.2)
alread be ported to wizard sucessfully one week ago
http://bbs.pdafans.com/thread-395528-1-1.html
Click to expand...
Click to collapse
if it english, could we have the direct link??
its right said:
if it english, could we have the direct link??
Click to expand...
Click to collapse
it's chs version!!!
ftp://pdafans:[email protected]/wizard 5.2.1620(Build 18125.0.4.2)chs.nbf
Serjnyak said:
I'm looking at http://3ppc.net/index.php?showtopic=2089 and I see that Remember ported it to our wizard but it's in russian!
I can also say that he's currently porting 5.2.1620...
So the question is anyone working on WWE build?
=D
Click to expand...
Click to collapse
I have this KitChenROM OS 5.2.1437 (B 18125.0.4.2) English, but it's not good so i don't have post it.
i'm an ignorant!
email123 said:
it's chs version!!!
ftp://pdafans:[email protected]/wizard 5.2.1620(Build 18125.0.4.2)chs.nbf
Click to expand...
Click to collapse
what's CHS????
I think that CHS mean Chinese...
WR you rock as always. Let me know when you are done and I will mirror for you.
XIP Built and Working Wehay
I have another uber secret rom which I am going to go try but then Im back to all attention onto the XIP.
Funny thing is coredll doesnt seem to be updated in the hermes tmobile uk test rom....I am about to try from kaiser
Keep your Eyes Peeled folks
p.s There are no updated OEM packages I am afraid
WhiteRat still alive! Yeah! Keep up the good work mate!
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
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.
Hi guys,
Well, I know it's been a while since I asked how to port the SYS and XIP. I can do those both great now, but I was wondering how you can change the OS build?
Thanks
mbarvian said:
Hi guys,
Well, I know it's been a while since I asked how to port the SYS and XIP. I can do those both great now, but I was wondering how you can change the OS build?
Thanks
Click to expand...
Click to collapse
Just a suggestion, you might want to change the title of the thread to "changing OS builds" just to catch people's attention. I don't have the answer to your question though or i'd gladly share
EDIT:
You may have already read this, but this seems to be what you're asking about:
http://forum.xda-developers.com/showthread.php?t=409845
scotchua said:
Just a suggestion, you might want to change the title of the thread to "changing OS builds" just to catch people's attention. I don't have the answer to your question though or i'd gladly share
EDIT:
You may have already read this, but this seems to be what you're asking about:
http://forum.xda-developers.com/showthread.php?t=409845
Click to expand...
Click to collapse
thanks, lol, I took your device
I have followed some solutions found in that thread, but the BuildOS is not changing...
mbarvian said:
I took your device
Click to expand...
Click to collapse
Maybe you should give it him back???
Dave
DaveShaw said:
Maybe you should give it him back???
Dave
Click to expand...
Click to collapse
LOL!
anyone else? I tried replacing the .dsm file as suggested in the thread, but that didn't work either...
you can hexedit and change the build number, i think there is something in the hermes Wiki that explains how to do this.
mbarvian said:
LOL!
anyone else? I tried replacing the .dsm file as suggested in the thread, but that didn't work either...
Click to expand...
Click to collapse
What do you mean build number here?
the CE OS 5.2.20273 or the Build 20273 ??
For the CE OS you need to port and update XIP part to make it changed,.
Well, you cant only change the .dsm, it wont change anything,.
You could always make a fake build, just like CE OS 5.2.66666 BUILD 66666 ,.
all you need just learning to use IDA and HEX Calculator !
Hope it help,.
CE OS version is stored in XIP/coredll.dll and OS build is stored in SYS/Base_Lang_xxxx/shellres.xxxx.mui. not in dsm. DSM files are merely package information files and OS can run without them.
hi guys. thanks for the input. im not going to hex edit anything, but thanks for that info anyway lol
the thing is, i AM porting the XIP AND SYS and the ce os build is not changing. how does everyone port the xip?
mbarvian said:
hi guys. thanks for the input. im not going to hex edit anything, but thanks for that info anyway lol
the thing is, i AM porting the XIP AND SYS and the ce os build is not changing. how does everyone port the xip?
Click to expand...
Click to collapse
You have to do full port XIP,.
Export ALL XIP from the new build, and re insert it to your NEW XIP,.
ababrekar have already teach us about how to do this bro,.
Garmin said:
You have to do full port XIP,.
Export ALL XIP from the new build, and re insert it to your NEW XIP,.
ababrekar have already teach us about how to do this bro,.
Click to expand...
Click to collapse
yes, ive read his tuts
ill try this you guys, thanks for the input
sorry guys, but this is what I really want to know.
how do you super-chefs like Garmin, Dutty (don't expect an answer from him , Leo, etc.) change your Ce OS build number? I tried M'Reloc but all the module's addresses are all the same, and I have changed the Build # millions of times...
thanks a ton for the input so far guys, and I'm sorry for the double post
I just want to know if anybody heard anything on WM6.5 and if it will be released for kaiser phones?
Just in case here is the link
http://www.neowin.net/news/main/08/11/07/windows-mobile-65-confirmed
-post removed-
mbarvian said:
I have actually extracted the Imgfs.bin from the WM6.5 emulator, but I don't know why you would want to use it. I'll post it here if anyone wants it
Click to expand...
Click to collapse
wm6.5 ? emulator was 6.1.4 where did u get wm6.5 ?
post it
anryl said:
wm6.5 ? emulator was 6.1.4 where did u get wm6.5 ?
post it
Click to expand...
Click to collapse
whoops. sorry for making empty promises
my apologies
mbarvian said:
whoops. sorry for making empty promises
my apologies
Click to expand...
Click to collapse
Good luck putting that cat back in the bag, brother
J
I've heard that certain recent builds contain bits and pieces of the 6.5 kernel, but this could be entirely speculation and rumor.
Travito said:
I've heard that certain recent builds contain bits and pieces of the 6.5 kernel, but this could be entirely speculation and rumor.
Click to expand...
Click to collapse
I know for sure that the Blackstone build (20757) is the same build as WM 6.1.4
yes but I'm referring to certain builds that are in your PM box and in a couple ROMs in the community.
Is out a WM6.5 rom for Blue Angel!!!
http://forum.xda-developers.com/showthread.php?t=428030
He links also a zip for modules!
Who will port this ?
wow, to think MS was mad about just little bits and pieces of the 6.5 Kernel that are supposedly in 21109 supposedly according to some stuff i saw concerning PPCGeeks.
a whole 6.5 beta ROM? MS isn't going to be happy about that being released to the world. I wonder if he removed the timebomb they like to stick in with beta releases...
HA HA
Travito said:
wow, to think MS was mad about just little bits and pieces of the 6.5 Kernel that are supposedly in 21109 supposedly according to some stuff i saw concerning PPCGeeks.
a whole 6.5 beta ROM? MS isn't going to be happy about that being released to the world. I wonder if he removed the timebomb they like to stick in with beta releases...
Click to expand...
Click to collapse
Actualy at PPCGEEKS was 21014 not 21109.
We are monitored by MS and nobody wanted us to remove nothing yet SO .... ?
The BA 6.5 ROM is the same as my 21014 compared modules so dont worry there is no WM6.5 released yet .
And if they were WM6.5 the first to get it will be again xbeta.cn --- after that xda-dev's
what MS should do i give us the kernel and the all the programs and we will compile the roms for them
at list they will have tons of free testers
Ah, figured you'd be the one to clear that up Anryl.
21109 is actually a bit speedier it seems even than 04, with or without the supposed kernel inclusions.
thanks again for the ports and help, phoenix is shaping up extremely, extremely well.
anryl said:
Actualy at PPCGEEKS was 21014 not 21109.
We are monitored by MS and nobody wanted us to remove nothing yet SO .... ?
The BA 6.5 ROM is the same as my 21014 compared modules so dont worry there is no WM6.5 released yet .
And if they were WM6.5 the first to get it will be again xbeta.cn --- after that xda-dev's
Click to expand...
Click to collapse
SYS is an hibryd betwin 6.1 & 6.5 but 6.5 OEM i'm cooking a 6.5 rom too see...maybe a beta relased today...
Like 2 play
HERE U GO kitchen 21139 from Da_G ported
http://rapidshare.com/files/188176657/AK65.7Z.html
Enjoy
6.5 kaiser ROM
ok 6.5 rom boot I have some bug to fix...
need beta testers, people can help me to solve bugs don'y need people just want to test...PM me
Thx
whoa, are you talking about an entire WM 6.5 ROM, or just some modules from a beta build?
this sounds interesting
mbarvian said:
whoa, are you talking about an entire WM 6.5 ROM, or just some modules from a beta build?
this sounds interesting
Click to expand...
Click to collapse
read my thread my friend http://forum.xda-developers.com/showthread.php?t=474869
utopykzebulon said:
read my thread my friend http://forum.xda-developers.com/showthread.php?t=474869
Click to expand...
Click to collapse
I saw your thread, but there's not much information over Windows Mobile 6.5?
mbarvian said:
I saw your thread, but there's not much information over Windows Mobile 6.5?
Click to expand...
Click to collapse
sys is an hybrid btw 6.1 & 6.5...i have some fix to do...