Related
Is this ROM ever going to be leaked from microsoft (i presume this was how wm5 be started)?
Porting seems to be very unstable from what I have heard
A WM5 rom was never released by microsoft, although it was known to exist. It's highly unlikely MS will create a WM6 dev rom for the BA at all.
Remember, the BA originally shipped with WM2003SE. WM5 was a struggle to get working, WM6 should (by an unwritten law) be unable to run on the BA. But there are some gods out there so you never know.
Many drivers in WM6 are almost exactly the same as WM5 AFAIK. Drivers are normally the big problem, so if you have good drivers for the BA, then it's a possibility.... but don't hold your breath.
V
So was wm5 BA never really created by microsoft?
In that case, who did create it? Did someone do it from scratch?
If they did, why can't they do it in crossbow (wm6 Blue Angel)?
I think it's a bastard son of a Wizard leak.
V
hardingt0110 :
You still didn't read the wiki and the older threads as I told you few weeks ago
But Microsoft is the one who makes OS (WM5, WM2003SE,WM2003,...).
O2, Vodafone, T-Mobile, Cingular... are the ones who adapt WMx to devices.
WM5 for BA has been ported from different (but very similar) device that already comes with WM5 by xda-developers.
You cant buy it (WM6), even if you want So be patient
Biohead said:
A WM5 rom was never released by microsoft, although it was known to exist. It's highly unlikely MS will create a WM6 dev rom for the BA at all.
Remember, the BA originally shipped with WM2003SE. WM5 was a struggle to get working, WM6 should (by an unwritten law) be unable to run on the BA. But there are some gods out there so you never know.
Click to expand...
Click to collapse
The Roms never released for devices by microsoft, the producers use and adapt roms for him devices.
If HTC use Wm6 rom for him devices and Reproduce or advance BA to the WM6 or similar device then we can see WM6.
Other side If anybody can write or adapt device drivers that can be... Core software hasn't any driver i think. May be someone can syncronise Wm6 shell and BA (or resemble device) Wm5 drivers
And may be work
what a dream huh...
BA WM5 base rom is genuine created for BA, and just the OS (with AKU's and stuff) part was aded to this rom ported from another device.This base rom was leaked by one of the operators
I suppose that the needed kernel would be created by someone somehow someday, because basically Microsoft creates the new ROM, gives it to the manufacturers, then the manus will try to adapt the ROM to their devices.
As I saw somewhere on the net saying the ROM can be adapted and flashed to any device, as long as the manus manage to write the necessary drivers.v.v...those kinds of stuff. It sounds logical to me. What do you guys think 'bout this?
nht_max, that's what I thought as well but I never said anything, bowing to those who know more about these things. IMHO it is not needed to recompile the kernel unless it's for a new architecture. Proved the correct drivers can be located and they are compatible with WM6, then it should just work.
Recompiling may be necessary, I think because the new ROM is much different from the old WM5. Though I believe it'll be available some nice day.
Crossbow
nht_max said:
Recompiling may be necessary, I think because the new ROM is much different from the old WM5. Though I believe it'll be available some nice day.
Click to expand...
Click to collapse
You may be right about this, i have ported the OS part to BA rom without any changes in XIP section of rom (old core 5.1.195) and the device with this rom does not boot at all, so if the original core 5.2.x is ported to a BA rom it will work correctly, almost all OS files are related to the WM core, and if a function that they seek is not where it should be unpredicted crashes may occure.
But i think we should wait a lil more before try experiments like this, we have no any documentation about WM6, we don't know how the things work inside, it is similar to WM5 but defenately not the same. We must learn how it works and then port it and modify it to our own taste.
Also the leaked roms are from early beta stage, so they are not so stable and usable as the final version.We should wait a bit for the first official rom and build something stable enough from it for common usage. And i am not talking about BA here i am talking about rom cooking for all devices.
xplode said:
You may be right about this, i have ported the OS part to BA rom without any changes in XIP section of rom (old core 5.1.195) and the device with this rom does not boot at all, so if the original core 5.2.x is ported to a BA rom it will work correctly, almost all OS files are related to the WM core, and if a function that they seek is not where it should be unpredicted crashes may occure.
But i think we should wait a lil more before try experiments like this, we have no any documentation about WM6, we don't know how the things work inside, it is similar to WM5 but defenately not the same. We must learn how it works and then port it and modify it to our own taste.
Also the leaked roms are from early beta stage, so they are not so stable and usable as the final version.We should wait a bit for the first official rom and build something stable enough from it for common usage. And i am not talking about BA here i am talking about rom cooking for all devices.
Click to expand...
Click to collapse
Hi,
have u changed coredll.dll in xip boot?
the devices not boot in same mode if u try aku 3.5 and have coredll.dll of aku 3.2
@Tuatara,
please help me for relocating more space in xip boot
of course not, AKU 3.5 runs fine with the old core without problems, but for crossbow the coredll should be changed in order to work, the thing is that it is bigger than the old core.
I have no knowledge of editing XIP, thats why i am stuck at this point, but i have read here on the forums that the coredll.dll can be changed with one with the exact same size, and the crossbow one is bigger.
xplode said:
of course not, AKU 3.5 runs fine with the old core without problems, but for crossbow the coredll should be changed in order to work, the thing is that it is bigger than the old core.
I have no knowledge of editing XIP, thats why i am stuck at this point, but i have read here on the forums that the coredll.dll can be changed with one with the exact same size, and the crossbow one is bigger.
Click to expand...
Click to collapse
I have tried to run aku 3.5 with coredll.dll for aku 3.2 (not 3.3) and not working....(but perhaps I mistake method)
I know that there is a way in order to increase and relocate the files in xip with dumpromx but I do not know if it works for the modules (old post Tuatara on xda)
and however I have read that it must edit vdata and pdata in the modules for the just address (oki and sp3dev on buzzdev)
but sp3dev and oki not working on blu devices only tuatara have necessary experience on blu devices and I believe can help
xplode said:
Recompiling may be necessary, I think because the new ROM is much different from the old WM5.
Click to expand...
Click to collapse
You may be right about this, i have ported the OS part to BA rom without any changes in XIP section of rom (old core 5.1.195) and the device with this rom does not boot at all, so if the original core 5.2.x is ported to a BA rom it will work correctly, almost all OS files are related to the WM core, and if a function that they seek is not where it should be unpredicted crashes may occure.
Click to expand...
Click to collapse
I don't understand this. Recompiling is only required for a different architecture in my experience, but I've not done much with this platform myself. Is it linking in specific BA drivers or something?
Also the leaked roms are from early beta stage, so they are not so stable and usable as the final version.We should wait a bit for the first official rom and build something stable enough from it for common usage. And i am not talking about BA here i am talking about rom cooking for all devices.
Click to expand...
Click to collapse
I agree 100%, though I'm sure some of you will still tinker around. Interesting stuff.
we can use BA wm5 drivers, they should work fine, WM5 is 5.1.x and WM6 is 5.2.x not a major 6.0.x release do the changes are not so drastic and the drivers should work
look at windows windows 2000 uses the same drivers as xp, windows 2000 is NT5 xp is NT5.1
OK guys, thanks for your help.
So basically the main part of the wm5 rom for the BA was made by an unnamed operator, who decided not to release it, but it was leaked to xda-developers.
Then the developers made the aku's and customisations from scratch / ported from other devices, and combined them to make a full wm5 rom.
Some people (xplode and others) seem to think that the wm5 main part rom can be used to host all the bells and whistles from wm6.
So basically, all we need to do is wait untill an official very stable wm6 rom is made for a Blue Angel like device, port it, and we're all set!
Am I right?
Oh, and one last question: is the name for the main part of the rom a "kernel"? thanks,
Always be faithful in the xda-developers,
hardingt0110-1
Looking at other threads, some think it may be necesary to use sd cards as rom.
I have two sd cards (1gb and 2gb) which I swap between on my BA to allow me to have tomtom maps and movies on my device.
Untill now, I have ignored extrom.
Is it possible for me to install the extrom on both cards, so that I can swap them over when I want?
hardingt0110-1
Still Lurking ...
Hey There ... I thought I might just come out of the woodwork for a little bit ...
sostekit said:
have u changed coredll.dll in xip boot?
@Tuatara,
please help me for relocating more space in xip boot
Click to expand...
Click to collapse
sostekit said:
I know that there is a way in order to increase and relocate the files in xip with dumpromx but I do not know if it works for the modules (old post Tuatara on xda)
and however I have read that it must edit vdata and pdata in the modules for the just address (oki and sp3dev on buzzdev)
but sp3dev and oki not working on blu devices only tuatara have necessary experience on blu devices and I believe can help
Click to expand...
Click to collapse
I've been quite able to make some space in the XIP section by moving files around (to make space for larger boot registries, etc.), but I haven't had any luck with moving around modules. I think it was mamaich (and/or bepe) who managed to get the new core.dll (which has the new LASS_xxx entry points) into the BA XIP section ... but I haven't had the time to see how they managed it.
I do have the source for RomMaster & dumprom, and will be going through the details at some point - when I have the time (which is always lacking). In the same way as figuring out the Acer ROM for mamaich's tools - I'll need to see if we can dump out and 'move' modules & files around to make the space required. This may just have to be a 'one off' manual hex editing job though (fixing the tables).
While in theory the WM5 drivers should work just fine, a number of our "WM5" drivers are still 2003SE versions. How long we can keep using the old drivers is anyone's guess.
In short - as long as the XIP section contains all of the entry points and support calls required by the 'new' OS, and can start the "new" OS, then the OS portion of the ROM can be replaced. This is what we are doing with the BA now. The XIP section is still (effectively) the original leaked WM5 build, with very little, and as little replaced as possible, but just enough in order to boot the "new" OS, which has been put in the remainder of the ROM.
For reference, you can find a listing of the new functions in core.dll from here:
http://blogs.msdn.com/windowsmobiledocs/
As far as I know (from xda-dev & runour mill) the core.dll entry points have not changed between versions wm5/6 ... but that's not to say that some things don't operate differently.
Only time will tell if we can port/hack wm6 on to a Blue Angel.
New extended Kitchen for Herald
HERALD_DEV_v2.1_Build_19199.rar
Related:
Extended Kitchen for Hermes
Extended Kitchen for Trinity
Extended Kitchen for Artemis
Thanks to misar, FreePK for helping with this new set of tools!
About the Kitchen
Herald base: HTC WWE 4.17.405.2
OS base: VF Kaiser UK 3.08.161.0 (Build 19199)
OEM Apps removed, but you need to clean up the OEMDrivers package
I did not do any changes to the OS, because it should be a clean base Kitchen for all of you
Full XIP editing supported by the Kitchen
New tool to merge all dsm files to one big file and delete all rgu's
I think the OEM package to SYS problem should be solved... but did not try it yet
How to use it
Requires Microsoft Visual C++ 2008 Redistributable Package
OEM and SYS can be used as known
The content of ROM\XIP will be used to create a new XIP section for the OS
You don’t have to worry about relocating modules... add/remove whatever you like and the new tools will take care of relocating modules or freeing RAM
.VM and .ROM is updated automatically
Actually this Kitchen runs in auto mode, which means you only need to run BuildNB.bat to create the ROM. You can change that by editing the bat files; made it this way, because I don’t use the options in BuildOS.exe
I consider this a perfect port of the new build to this device
Replaced all XIP SYS packages (I did not just changed coredll.dll to get the new build number)
There were also boot.rgu changes my MS, those have been added too
SYS is completely untouched
Read this for download:
All donations are very welcome!
I need to buy a new device, because this time my Trinity is gone forever and I cannot use my girlfriends Artemis without being killed (by mistake I deleted all contacts last time I used it for testing... she was not very happy about that )
When you are getting money for the ROMs you cook using my kitchen, I would really appreciate a donation.
I'm not talking about 50% of you incomes, but one small donation would be fair I think.
To download the Kitchen click at "All donations are very welcome"
!!! This was only meant for ppl never donated for these tools and expecting donations for ROM's created using my Kitchen !!!
Thanks to all those who have donated already!
Happy cooking!
Come on guys - the ROM (I installed a test version by bepe) has nothing inside - real barebone...
BUT it is BOOTING
And it is what I call "click n´get" = no lack when clicking start-settings
So start cooking...
And once again: IT is a KITCHEN === NO usable ROM!!!!
which one is the herald kitchen ?
nice release bepe, and misar
quick question...anyone know which phone the 19716 build came from
loco41 said:
which one is the herald kitchen ?
Click to expand...
Click to collapse
Check the bottom of the post and read carefully
wow Bepe, great work. Downing now
Nice. Downloading now, too. My firefox decided to bloat up to 1gb of RAM randomly and then crash... so I have to sit here waiting 17 minutes for Radipshare to let me download again. >.<
neptune said:
nice release bepe, and misar
quick question...anyone know which phone the 19716 build came from
Click to expand...
Click to collapse
Forget about 19716, it is a very old build! Dont ask me about this logic.
19199 seams to be the final build, so please use this one. It's more stable, not beta like 19716, faster.
Now all I need is a way to bypass the flash center's 51.2mb limit and I'm in heaven. ;-) Awesome release. Cooking as we speak, instead of sleeping...
bepe said:
Forget about 19716, it is a very old build! Dont ask me about this logic.
19199 seams to be the final build, so please use this one. It's more stable, not beta like 19716, faster.
Click to expand...
Click to collapse
good to know
cheers
great job guys!
I'll strip it a little more, trying to get the smallest possible (working) rom for building my own one.
**********
edit: do we have to add some drivers or something? No matter what i try, the touchscreen doesn't work so i can't get past the "Tap the screen to set up your...."-screen.
mmh, adding the old drivers from 6.0 doesn't work. Am i missing a step? Can anyone confirm that it works out of the box?
Strange...
OK and Startmenu Buttons are not working,any one have the same problem.
Settings\buttons is clear, can not assiging any button.
Please advice
shafez said:
OK and Startmenu Buttons are not working,any one have the same problem.
Settings\buttons is clear, can not assiging any button.
Please advice
Click to expand...
Click to collapse
have you cooked a rom with this kitchen. because it is NOT a usable rom!!
you have to add EVERYTHING
The OEM folder is pretty empty here...
missing/you must add:
Camera
MMS
Taskmanager
AudioManager
ConnectionSetup
ev.touchflo
Dialer
CommManager
etc
etc
etc
etc
.....
you have to add EVERYTHING
The OEM folder is pretty empty here...
missing/you must add:
Camera
MMS
Taskmanager
AudioManager
ConnectionSetup
ev.touchflo
Dialer
CommManager
etc
etc
Click to expand...
Click to collapse
yeah sure... but the touchscreen should work out-of-the-box, right? Or does it need a package? Couldn't find something suitable...
stahlsau said:
yeah sure... but the touchscreen should work out-of-the-box, right? Or does it need a package? Couldn't find something suitable...
Click to expand...
Click to collapse
I'm working on a stripped version as well... For the touchscreen to work, make sure you have the touch.dll driver in your OEMDRIVERS or a TOUCH package with the needed touch.dll.
papamopps said:
have you cooked a rom with this kitchen. because it is NOT a usable rom!!
Click to expand...
Click to collapse
itje said:
you have to add EVERYTHING
The OEM folder is pretty empty here...
missing/you must add:
Camera
MMS
Taskmanager
AudioManager
ConnectionSetup
ev.touchflo
Dialer
CommManager
etc
etc
etc
etc
.....
Click to expand...
Click to collapse
Thanks, I will give it a go.
Regards
After you run buildnb.bat, and it completes successfully, what is the next step? I was looking for a OS.nb but didnt find one.
Thanks
JLine05 said:
After you run buildnb.bat, and it completes successfully, what is the next step? I was looking for a OS.nb but didnt find one.
Thanks
Click to expand...
Click to collapse
take a look in \tem\
run pagepoolchanger
run htcrt
flash the ruu_signed....
maybe
So I set my phone to use a dynamic pagepool that resizes itself to whatever size it deems necessary and the phone seems much snappier, even though I'm using a LZX compressed ROM. The only draw back is that it uses as much RAM as it wants at any given time... or so theory goes...
How'd you do it? I want to try it out.
Just set the page pool to 0.
that.is.cool
gotta try this. How much ram do you usually have?
and do we use the same page pool technic to set it to 0 because i dont think i ever seen 0?
no. There is a pagepool setter included with some kitchens, and i'm sure you can download it somewhere.
it allows you to set the pagepool of a .nbh file, which means you will have to reflash to do it. Just choose "custom value" and pop in "0".
I'm sure you CAN do it with the .bat file powered one, but it would take just a tiny knowledge of batch code.
Does anybody actually have this tool and is willing to share it? I would like to set my Vogue ROMS to have a dynamic pagepool but can't seem to get my hands on this tool anywhere...
This is my favorite pagepool changer. It's a really well written one. I haven't used the newer versions, but I still actively use the older versions. (Just noticed there was a newer version.)
ivanmmj said:
This is my favorite pagepool changer. It's a really well written one. I haven't used the newer versions, but I still actively use the older versions. (Just noticed there was a newer version.)
Click to expand...
Click to collapse
Hmm so all I should need to do, theoretically, is set my pagepool to 0 and it will be dynamic? I want to avoid re-flashing my phone if it can be helped so unless I have accurate information...
I'm sure you get the idea.
Main reason for this is because I recently had a Vogue brick because of a corrupt sector caused by flashing 10-15 times a day. Not a pleasant experience.
that sets the pagepool on a .nbh rom file, so you will have to reflash.
you dont have to flash your herald in order to change the pagepool you can use this tool and it only takes seconds to do it. I recommned you change it to 6mb, more stable and faster.
Here is how:
1)download the files
2)extract the zip file
3)connect ur wing using ur usb cable
4)open the folder called page pool size
5)doble click on backup dos icon(u should look @ ur wings screen for a message, click installe on ur wing)
6) after the phone fished n is go n dobleclick on which ever pool sizeu want (6 is the best n most stable)
7)ur doing 2 c a pop up on ur computer for about 5 sec then after thepop up is gone simply disconnect ur wing n soft reset
8)enjoy more program space...
did you do this yourself? What rom are you using, because i've heard that this method does NOT work for wm6.1, but they might have updated it.
Here is the original thread....
http://forum.xda-developers.com/showthread.php?t=324955
No updates yet and your right it does not work with wm6.1.
It might work if you cook the WM6.1 ROM with a pre-"bepe's extended kitchen" kitchen. But if you're using any wm6.1 ROM except for my LZX one, you probably ARE using one that was made with bepe's extended kitchen. And my LZX isn't compatible anyways, since it has a different base as regular Herald Bases.
translation from whatever language ivan just posted in
it won't work with wm6.1
fzzyrn said:
translation from whatever language ivan just posted in
it won't work with wm6.1
Click to expand...
Click to collapse
lol. It won't work with your ROM, no.
fzzyrn said:
translation from whatever language ivan just posted in
it won't work with wm6.1
Click to expand...
Click to collapse
No man! It's working! I just tried this on WM 6.1. It does work.
Can anybody tell me how to decrease the boot time of my WM 6.1?
ArniRoy said:
Can anybody tell me how to decrease the boot time of my WM 6.1?
Click to expand...
Click to collapse
That's completely unrelated to the Dynamic Pagepool...
Please post a separate thread AFTER having searched.
HINT: There's a HUGE sticky thread in one of the Herald subforums.
Anyhow, if it's a cooked ROM, it might already be moving as fast as it can. The only other thing you can do is recook it with less files. A cleaner Windows folder = a faster device.
hi i read some topic about it but if any go to Magician upgrading you will find wm6 for it and Magician have 64 mb memory but the developers make it so why no one make it for ipaq hw 6515c i hope if any one make it
Dream on Bro! They're never care anyway!
ABDALLA_WALLY said:
hi i read some topic about it but if any go to Magician upgrading you will find wm6 for it and Magician have 64 mb memory but the developers make it so why no one make it for ipaq hw 6515c i hope if any one make it
Click to expand...
Click to collapse
Ah.. Problem isin't in memory size, but in how the ROM is build.
There were never build tools for older HP iPAQ ROM dumping, You will always end up with a error. HTC tools don't work.
I have tried dumping and making ROMs for HW6500 / HW6900 / H6300 series iPAQs, but all ended up with nothing, as I where unable to get xip and imgs parts. Those ROMs are coded or compressed. WM2003 Tools ask for password, only HP engineers know that password.
Also ROM converting from WM2003 to WM5 is not easy.
cant you use rom from a 6915?shame if a rom can never be made because its a pretty solid phone.
i also read for a short while there was an update for wm5 surely someone must have it and can atleast post it?
I THINK I HAVE SUCESSFULLY MADE A WINDOWS PHONE 7 ROM, I DONT WANT TO TEST IT JUST IN CASE.
Is there any way i can test it without flashing it to a himalaya????
EDIT: HERE IS THE LINK IF YOU WANT TO TRY IT. (I AM NOT LIABLE FOR ANY DAMAGES CAUSED BY THIS ROM BEING FLASHED TO YOUR DEVICE):
http://cid-b9d125e8c5ede9e3.skydrive.live.com/self.aspx/Public/WP7^_flyboyovyick.rar
thanks
No way, because you know the drivers ....
The best test on the Himalaya, but the drivers in XIP, you must be ensured
so the drivers might be wrong?
Do could i just change the XIP with one from a 6.5 rom?
This is the directory of the XIP folder below attached, the second one is the folder of a 6.5 XIP folder.
flyboy
flyboyovyick2k9 said:
I THINK I HAVE SUCESSFULLY MADE A WINDOWS PHONE 7 ROM, I DONT WANT TO TEST IT JUST IN CASE.
Is there any way i can test it without flashing it to a himalaya????
thanks
flyboy
Click to expand...
Click to collapse
Do you have winmo 7 nk.exe compiled to himalaya?
If not, no chance to boot.
If you used emulator build, it won't run at all, because it is compiled for x86 and our himalayas have arm
Ye its the emulator build!
flyboy
consider me skeptical
flyboyovyick2k9 said:
so the drivers might be wrong?
Do could i just change the XIP with one from a 6.5 rom?
This is the directory of the XIP folder below attached, the second one is the folder of a 6.5 XIP folder.
flyboy
Click to expand...
Click to collapse
I understand.
I invent something just with my Himalaya, then I will help in this process
yoooo hooooo
finally himalaya gone to wm7
keep it up brothers
note
Hi guys
Well it's my understanding that WM7 is a 64bit system and needs a 64bit CPU.
himalaya arm CPU is 32bit so it's not gona work guys, If someone makes a driver to patch 64bit to 32bit it may run but so slowly it'll be unusable,
If it was gona work sundream would have done it by now
regards
swampy395
Hi swampy395
I understand ....
But remember, everything is possible my friend
wm7 i
himalaya up to wm7 is a welcome friend if possible.
Himalaya won't upgrade to WM7 (at least with a year)
Hello aeroflyluby
Hello
aeroflyluby you think it is possible the ideas in this forum.
i didnt realise it was 64 bit.
flyboy
my ferst reply
why you can teste in himalaya am so intersting by wm7 plz try again
yamozander said:
why you can teste in himalaya am so intersting by wm7 plz try again
Click to expand...
Click to collapse
Man! No chance for that! Forget this, go to sleep, drink much, to forget!
No ARM verion of WM7 says DIRECTLY : THERE IS NO WINDOWS PHONE for himalaya.
So how come the rom that i made got successfully built?
flyboy
flyboyovyick2k9 said:
So how come the rom that i made got successfully built?
flyboy
Click to expand...
Click to collapse
There's a world of differance in building a rom and it working,
IF your so sure that 64bit os will work with a 32bit cpu then flash the darn thing and see,
Iam dont think it will work. After learning the the hardware needed is 64bit.
I dont want to flash it beacause i paid £80 for the phone in march 2009 (with other bits)
Plus an xda II isnt widely availiable cheaply. So theres not much chance il get another like this one.
flyboy
flyboyovyick2k9 said:
Iam dont think it will work. After learning the the hardware needed is 64bit.
I dont want to flash it beacause i paid £80 for the phone in march 2009 (with other bits)
Plus an xda II isnt widely availiable cheaply. So theres not much chance il get another like this one.
flyboy
Click to expand...
Click to collapse
Flashing won't break your device since size of rom goes above 32 mbs or sectors will exceed 1a16. 1 sector is 4 kb of compressed data.
Also 64 bit os not needed but arm compiled code, is.