Related
I need someone to test this ROM, because I dont have a BA.
OS 5.1.195 (Build 14847.2.0.0)
STOP !!! ROM IS NOT WORKING
"ftp://xda:[email protected]/Uploads/BLueAngel/WM5_BA_-_AKU2 TEST.rar"
It is possible that you have to reflash the old rom!
Is this based on the Himalaya rom?
How likely is it to turn my BA into a paperweight? LOL
I am donloading it now mate.. Will post any results in about 2 hours
Gruß aus Malta!
Juggs
I used the the newest QTEK Wizard Rom.
There would not be any difference between Him or Wiz OS. Same build same files.
bepe said:
I used the the newest QTEK Wizard Rom.
There would not be any difference between Him or Wiz OS. Same build same files.
Click to expand...
Click to collapse
?? no omap or xscale code optimalisation ?? files can not be the same :|
I ported the German Wizard rom successfully to my Himalaya and I did the same with the WWE version at this rom.
But there could be differences. In this case, the rom would not work.
First Impressions..
OK.. bearing in mind that i only installed the Ivan Rom about 3 hours ago.. My MDAIII is getting a beating tonight.. However...
Ok.. Standard stuff.. Bootloader mode.. Set operater..
The update was relatively quick.. only took about 8 minutes,
Formatted the hive and storage OK..
And it hang on the Windows Mobile Screen!
and it keeps on hanging on the windows Mobile Screen.. :?
No New device Setup.. No shimmer of life.. No backlight.. Just the on/Off button Works
Sorry mate.. Back to the drawing Board!
I have not changed the drivers, only the OS.
I compared a Univesal and Wizard rom and the OS is exactly the same.
That may well be bepe.. But it doesnt install past teh windows Mobie screen...
Something is wrong mate.. normally it should give you that screen you get when the device need to be setup the fist time.. and it doesnt.. It just hangs..
Sorry..
Ok thanks and I'm sorry.
Ahh well! Thanks for your attempt Bepe. It seems he got to the same stage as Mamaich & Tuatara.
bepe said:
I need someone to test this ROM, because I dont have a BA.
OS 5.1.195 (Build 14847.2.0.0)
"ftp://xda:[email protected]/Uploads/BLueAngel/WM5_BA_-_AKU2 TEST.rar"
It is possible that you have to reflash the old rom!
Click to expand...
Click to collapse
***NOTE: To all wanting to test this, the ROM will not finish the BOOT sequence. This is the same or similar problem both mamaich and I have had with undertaking the Himalaya AKU2 Port to date. ***
The device will initialize, gets to the 'boot splash' screen, runs that ...
The "coldinit.exe" is started, since we hear the 'ding' happen ...
At this point the device locks - an animated "dialog" appears to want to be displayed.
The boot process proceeds no further. Presumably crashed.
Additionally, the LEDs are dead/disabled so I can not tell if the phone (RIL, BT, etc.) is still available/operating. Power button or screen taps do NOT relight the backlight, or enable the screen. Presumably locked up.
Ok ... excellent work so far, however the same problem(s) seems to be arising which both mamaich and I have run into when using the Himalaya AKU2 port.
My guess is that this is probably due to the same missing DLL interface calls being available in coredll.dll. There are now 5 additional entry points in the XIP portion of this DLL, and this could be causing the 'hang'.
It looks VERY promising though ... I'm definitaly going to be taking a VERY close look at this ROM as well. The boot sequence is quite dramatically different, and may lead to some possibilities in merging ROMs to avoid the requirements of changing XIP section modules.
P.S> TuMa v1.4 will be out shortly ... it's now combining elements from the Wizard, Himalaya 1.7x & 2.0, Jasjar, Atom, Acer, and the original v3.1 BA from mamaich now. Trying to merge the 'best' of the available elements for a well performing and stable device.
Not a problem.. Just let me know when you want another one tested!
Gruß Aus Malta..
OT: has anyone tried porting Universal rom? is it possible?
@Saintraziel:
Would be the same result.
And a lot more work to do because of the VGA resources.
aku2
Would this give AKU2 functionality for blueangel? (PH20B)
If so I would be happy to test any builds, I am dying to get my hands on a working WM5 with push email on BA.
Cheers...
This is my first cooked ROM, will be compatible with G4 wizard device as it doesn't contain SPL and IPL part, as long as you have SPL 2.xx and IPL 2.xx, then you'll be ok. This is an operator independent Rom also.
ftp://xda:[email protected]/Uploads/Wizard/Roms/Wizard_Love_2.26.10.2_WWE_Novii+CF2.rar
Wizard_Love 2.26 AKU 2.3, A2DP Rom details:
ROM version: 2.26.10.2 WWE
ROM date: 6/7/06
Radio version: 02.25.11
Protocol version: 4.1.13.12
ExtRom version: 2.26.10.105
Extended Rom contains: CF2 SP1, latest NoviiRemote Deluxe 4.0 (wizard compatible - 5 metres range), Total Commander 2.0, RegistryWizard, Omapclock and Omapclockplus, SmartDialing, etc.
Cert_Disable
Disable_security
Enable_NTIZ_
Intent_MIDlet_manager
Java_Session_Fix
MP-Shorcut-MMS1-Java5xx-Voice-CV-TMUS-060406
MP_SmartDialing_enable_0915_signed
NETCFv2.wm.armv4i
NRDeluxe.arm
Omapclock and Omapclockplusv0[1].0.4
P_WIFI-Issue-Fix_Wizard
RegistryWizard_PPC[1].ARMV4
tcmdpocketarm
I also attach a small program (merelease) which is used to release device's memory. Open zip file and copy the merelease.exe file to somewhere on your device and run it.
So far, so good, fast, stable and much better battery life compare to 2.24 Rom, no problem yet !!!
-------------------------------------------------------
mod edit, it is no longer alowed to upload roms to the xda .....read the stiky please...
G4 MDA VARIO
SPL: 2.21.0001
IPL: 2.21.0001
ROM version: 2.26.10.2 WWE
Radio version: 02.25.11
Extended Rom: Wizard_Love
thanks for a nice lookin rom. i'll let you know how it goes
just have a try and let me know your opinions. I think you will like it.
I have already installed 5 "heavy" programs, apart from the ones from extended rom, but it still run very smoothly. Battery life seems to be better as well, used internet for about 15 minutes through WiFi but still %100 battery remaining (after a full charge). However, I will see how it goes later on.
i am using your rom,can say only good words about this
THNX!
crap and i just finished doing a hard reset on my wizard! arg!
merelease?
WLove said:
I also attach a small program (merelease) which is used to release device's memory.
Click to expand...
Click to collapse
What is the program?
I did not find it somewhere else
I have been using this ROM for about a week and it is stable, fast and leaves about 21mb of RAM after a soft reset.
WLove - as in my thread, i hope you cook a AKU 3.2 based ROM as yours is the best so far on my device.
Wlove,
i'm downloading your rom now and will tell how good it was. now i used the Moski's rom. i like to test with a different version.
W Love,
already install ur rom, but can't find the mereleave program, and tested with NR deluxe software, it worked but in a disappointed distance just only 5cm, i don't know i do the configuration wrong or something else!!!
can you advice?
magicer said:
W Love,
already install ur rom, but can't find the mereleave program, and tested with NR deluxe software, it worked but in a disappointed distance just only 5cm, i don't know i do the configuration wrong or something else!!!
can you advice?
Click to expand...
Click to collapse
The memrelease program is a zip file in the first post. You have to be logged in to see/download it.
noob question regarding this rom
i have the original 2.26 t-mobile rom. would i need to cid and sim unlock my mda first before attempting to flash it with this rom?
Ok, so what is wrong with my Extended Rom
I just flashed to your rom (G4 8125) and all seemed to flash ok, but I didn't get the extended rom. This happened to me with 2 other roms, shogunmarks, and molskis. WTF, what am I doing wrong ?
cptcafne said:
I just flashed to your rom (G4 8125) and all seemed to flash ok, but I didn't get the extended rom. This happened to me with 2 other roms, shogunmarks, and molskis. WTF, what am I doing wrong ?
Click to expand...
Click to collapse
You dind't get my Extended Rom?
Are you sure you didn't see the "Customization Tools" after the 1st boot when upgrading is ready?
Molski
molski said:
You dind't get my Extended Rom?
Are you sure you didn't see the "Customization Tools" after the 1st boot when upgrading is ready?
Molski
Click to expand...
Click to collapse
Nope. I saw nothing. From yours or anyones. Not sure why, kinda confusing.
No extended Rom loaded either
T mobile MDA G4
Flashed with T mobile official 2.26.10.105 before.
After flashed with Wizard_Love_2.26.10.2_WWE_Novii+CF2, no extended rom application loaded.
ftp://xda:[email protected]/Uploads/Wizard/Roms/Wizard_Love_2.26.10.2_WWE_Novii+CF2.rar
The /wizard folder is missing or I just can't access it...this is a 1st for me.
ftp://ftp.xda-developers.com/Uploads/Wizard/Roms/ is as far as it goes...........
Is this ROM located somewhere else????
Thanks
dwny said:
ftp://xda:[email protected]/Uploads/Wizard/Roms/Wizard_Love_2.26.10.2_WWE_Novii+CF2.rar
The /wizard folder is missing or I just can't access it...this is a 1st for me.
ftp://ftp.xda-developers.com/Uploads/Wizard/Roms/ is as far as it goes...........
Is this ROM located somewhere else????
Thanks
Click to expand...
Click to collapse
The FTP has been cleaned up you will find the files in the /Wizard/Roms directory...it is most likely in the unknown roms directory
Kirby
rkwhyte2 said:
The FTP has been cleaned up you will find the files in the /Wizard/Roms directory...it is most likely in the unknown roms directory
Kirby
Click to expand...
Click to collapse
Got it ... Thanks ... It was right where you said it was.
Moderators .... When you guys move an item from it's original location on the FTP, can you also update the link?
Thanks again
Hi guys, can u please upload this ROM to the ftp server or somewhere else?
Wizard_Love_2.26.10.2_WWE_Novii+CF2.rar
My Qtek s200 doesnt start
Thank you in advance
Is this the crossbow rom? If not, would you guys suggest this rom over the WM6 crossbow roms? I haven't seen too many opinons with a list of pros and cons yet for this rom update. Please post
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.
As I understand "Also the Breeze Hardware shares most of the Parts with the Hermes" is it possible to convert it's WM 6 for Breeze?
(sorry for my bad English)
Probably it is, need to look into it. at first we need to crack spl to avoid nbh check
hi,
maybe hard spl v7 works...
i have experimented today... but i need my phone, because of that i finaly didn't click on the "flash now" button
Hermes is a PocketPC and Breeze is a Smartphone...
Both WM5 and WM6 have separate OS editions for PocketPC and Smartphone. If I were you, I wouldn't try to force "WM6 Professional" (Pocket PC) for Hermes on a Breeze (Smartphone - "WM6 Standard").
So, you need to decompress the xip segment and get a memory map of breeze. if memory addresses are the same as hermes, you need to replace a coredll.dll in second xip segment and you need to build imgfs using wm6 os from excalibur/vox and breeze wm5 drivers and applications. to load this into the phone, you need to avoid nbh check
how can we decompress the xip segment ???
what is exactly the coredll.dll ???
HI,
today i have played a little bit with bootloader...
task 32 says FF ... so its definitly not supercided... but i don't really know why a few other persons here can flash a dopod rom.. maybe they are all the same cid ??
also i'm searching for a usb sniffer ... have found a few in the web but all costs money and noone had give me understandable commands while using the romupdate tool from the actuell htc rom...
ok found some other interresting info..
the RUU_BREE100_1.34.251.1_1.38.00.10_HTCEUR_SHIP ROm has a QTEK_Z12 CID ....
but we all can update it to breeze device...
quite interesseting is also that:
Cmd>info 2
HTCSQTEK_Z12Û.oÂHTCE
... as we can see i my HTC Device has a QTEK_Z12 CID ... maybe someone can check what CIDS und the Breeze's out there...
Hi, could you explain how have the CID of the phone. Because i tried with info2 but it didn't work. Thanks. ++
----------------------------
just go in bootloader:
turn off device and restart it with hold cam button...
attach usb cabel the serial line on the 3color screen should change to usb...
also you have to deactivate the activesync usb connection...
then start the mtty app choose the usb connection...
then youll see the cmd> line... after this enter info 2 ... and you should become a output like mine...
------------------------
what ipl/spl version's are shown on the 3 color screen ??
i read that HTC announced S730 (wings)
it is like s710 but with MTeoR's hardware and WM6
I hope that it is possible use s730 ROM to take WM6 for MTeoR
So we need wait for s730 i think
I hope that i can see WM6 on my MTeoR :-[
concerning to his thread: http://forum.xda-developers.com/showpost.php?p=1257924&postcount=10
i say it a second time now...
we need the excalibur wm6 rom
why...
simply ... the excalibur has likley the same hardware as breeze !!!
all other devices are based on the hardware like wizard... (200mhz cpu etc.)
I'm just working on all the needs...
cookin with wm5 works!! i had cooked a German only version from the actuell rom! with a few tools on it...
also cooked an costumized bootscreen:
also there has to be somewhere in rom a "Shutdown" Screen.. i flashed the 2 Bootscreens and when shutting down the phone theres the old htc screen...
excalibur (s620) based on Tornado. So it have OMAP chipset, other radio w/o 3G etc.
at this time there is no MTeoR's based smartphones on the market as I know. Announcement only (Wings/Erato/"excalibur replace")
... damn ... what t.. f...
i searched a few days a ago and i had a website where the info was that excalibur is like the mteor...
....
ok so far i can see the next mteor hardware like phone should be the s730 (Wings)....
sorry that was my fault...
...
ok maybe i tought that excalibur was the right because this is the only one where i can find a wm6 rom for download... on all others there are no shipped roms available??
hmm
Hi,
ok just played a little bit with the excalibur rom...
the mainproblem is that i cant extract the files out of the nbh file...
because of that i can't modifiy a hermes rom...
i will look forward and hope to find an solution for it...
ok...
extraced excalibur rom...
cooked a bit...
but no working rom yet!!
also have flashed a wm6 hermes rom with a few files modified to breeze...
device didn't boot on bootscreens...
when flashing an unmodified excalibur rom, breeze directly goes to bootloader ....
next thing i want to try is to use the original 1,34.251.1 Rom ...
wow... I hope you manage to get a working WM6 rom for the MteoR...
Hi guys!
i have cooked today the wm6 rom with base wm5 ... but windows did not start up after 2nd boot screen!
i think that all goes to hard work ....
if anyone knows what the real core file of winmobile are then please post it!!
futureshock said:
Hi guys!
i have cooked today the wm6 rom with base wm5 ... but windows did not start up after 2nd boot screen!
i think that all goes to hard work ....
if anyone knows what the real core file of winmobile are then please post it!!
Click to expand...
Click to collapse
No, it`s not the way. Just contact me via ICQ and we`ll work. but now no time for that
HI, first sorry ofr my englis, i am from argentina, and i have a t-mobile SDA and i need know if with programs i can make a wm6 rom or if i can custimize the wm5 rom por my tornado. thank
I made this thread to know if anyone of you making the developments on new builds of Windows mobile 6.5 for HTC Himalaya such as Windows Mobile 6.5 build 21054 and 23037? curious to know if any one like swampy, ather, sundream and other masters can port these build on himalaya
i tried, but relocation of imgfs failed always.
there is no use of running WM6.5 on Himalaya's because you arent left with much memory..im currently working on porting the latest WM6.1 Build, WM61 21054 CE OS 5.2.3026
hi Ather . .
Ather said:
there is no use of running WM6.5 on Himalaya's because you arent left with much memory..im currently working on porting the latest WM6.1 Build, WM61 21054 CE OS 5.2.3026
Click to expand...
Click to collapse
are you planning to included M2D inside the rom??
Regards
havent thought about it, but i could
Ather said:
havent thought about it, but i could
Click to expand...
Click to collapse
That would be awesome.
I yould suggest latest M2D version from HTC mega as it seems to be less of a memory hog.
Sascha
Ather, can you tell my why I can't realloc? Are you using ervius or normail buildos kitchen?
im using 4 types of kitchen
1. my own C# kitchen
2. CRBuilder2
3. Avis Kitchen
4. Swampy's kitchen
aeroflyluby said:
i tried, but relocation of imgfs failed always.
Click to expand...
Click to collapse
try PPCGeeks XIP Kitchen, i think it auto relocates , just slect donor XIP and your XIP thats it
Ather said:
try PPCGeeks XIP Kitchen, i think it auto relocates , just slect donor XIP and your XIP thats it
Click to expand...
Click to collapse
I mean imgfs relocation, not xip But I can't port 6.5 xip at all, so I will try, thanks!
Also, Ather, did you found that if you use G'reloc in avis kitchen, your rom will not boot? Tried on oryginal too.