Develop Bugs

BETA: Extended Artemis Kitchen for WM6.1

New extended Kitchen for Artemis
ARTEMIS_DEV_v2.1_Build_19199.rar
Related:
Extended Kitchen for Trinity
Extended Kitchen for Hermes
Extended Kitchen for Herald
Thanks to misar, FreePK for helping with this new set of tools!
About the Kitchen
Artemis base: HTC P3300 WWE 3.13.405.1
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!

bepe said:
Could someone please try this Kitchen, cos I dont have any device right now...
http://rapidshare.com/files/88860516/ARTEMIS_DEV_v2.1_Build_19199.rar
Related links:
Trinity: http://forum.xda-developers.com/showthread.php?t=364634
Hermes: http://forum.xda-developers.com/showthread.php?t=363721
Click to expand...
Click to collapse
Thanks bepe will give it a try and let you know

I'm on it too.
TNX!

bepe said:
Could someone please try this Kitchen, cos I dont have any device right now...
http://rapidshare.com/files/88860516/ARTEMIS_DEV_v2.1_Build_19199.rar
Related links:
Trinity: http://forum.xda-developers.com/showthread.php?t=364634
Hermes: http://forum.xda-developers.com/showthread.php?t=363721
Click to expand...
Click to collapse
Thanks bro

What does this Ext. ROM contains? Will it be suitable with BB5.0?

meschle said:
Thanks bepe will give it a try and let you know
Click to expand...
Click to collapse
I CONFIRM IT WORKS - MANY THANKS BEPE - I MADE THREAD A STICKY

it works here too!

EazyVG said:
What does this Ext. ROM contains? Will it be suitable with BB5.0?
Click to expand...
Click to collapse
Sorry about that... did not see that the name might be confusing...
It means that this is a ROM Kitchen with an extension to edit/build XIP sections
To edit the XIP section was no easy task until now, so this means a little revolution for porting new build to our devices.
meschle said:
I CONFIRM IT WORKS - MANY THANKS BEPE - I MADE THREAD A STICKY
Click to expand...
Click to collapse
NikMel said:
it works here too!
Click to expand...
Click to collapse
Thanks to both of you, great that it is working, happy cooking

Thanks bepe
Nice and great tools for Artemis.
thanks you so much.

dheewatara said:
Nice and great tools for Artemis.
thanks you so much.
Click to expand...
Click to collapse
P' Dhee ,Could you please make a tutorial ?.

Many thanks to Bepe for making the new toy
I tried several times building a rom using the kitchen but failed. What I did was simply put in OEM packages and build the OS, got a nb file, then used htcrt.exe to convert it to a nbh for flashing. Everything seems fine during the flash. But when it restarts it dies in the first splash screen.
Any hint for this?

mypleasure said:
I tried several times building a rom using the kitchen but failed. What I did was simply put in OEM packages and build the OS, got a nb file, then used htcrt.exe to convert it to a nbh for flashing. Everything seems fine during the flash. But when it restarts it dies in the first splash screen.
Any hint for this?
Click to expand...
Click to collapse
First try if a ROM without OEM packages is working, next you need to add one OEM package after another... I'm sure there is something wrong with one of the packages.

You are using the wrong drivers.
Do you any drivers installed??
Did you fill XIP up?
mypleasure said:
I tried several times building a rom using the kitchen but failed. What I did was simply put in OEM packages and build the OS, got a nb file, then used htcrt.exe to convert it to a nbh for flashing. Everything seems fine during the flash. But when it restarts it dies in the first splash screen.
Any hint for this?
Click to expand...
Click to collapse

Great. Will come up with some cooked stuff soon
Regards,
Carty..

Built a ROM without addidng anything but a music file to reach 50MB limit but the ROM never passes the splash screen on device. The same happens with extracting and re-building of cooked ROMs even without editing. What am I doing wrong?
But when I extract and rebuild an OEM rom, everything works fine!
Regards,
Carty..

NikMel said:
You are using the wrong drivers.
Do you any drivers installed??
Did you fill XIP up?
Click to expand...
Click to collapse
Thank Bepe and NikMel a lot for your kindly help.
Should I keep the drivers in the kitchen, or replace them with the drivers from wm6.0? And how to fill the XIP? Sorry I am a newbie to the kitchen.

Most of the ROM do not include the rgu files.
You need rgu files to make your own rom.
Carty said:
Built a ROM without addidng anything but a music file to reach 50MB limit but the ROM never passes the splash screen on device. The same happens with extracting and re-building of cooked ROMs even without editing. What am I doing wrong?
But when I extract and rebuild an OEM rom, everything works fine!
Regards,
Carty..
Click to expand...
Click to collapse

the easyst way is to copy "OEMDrivers" map from wm6.
You should copy XIP files one by one from other rom and put it in a map with the same name.
mypleasure said:
Thank Bepe and NikMel a lot for your kindly help.
Should I keep the drivers in the kitchen, or replace them with the drivers from wm6.0? And how to fill the XIP? Sorry I am a newbie to the kitchen.
Click to expand...
Click to collapse

NikMel said:
the easyst way is to copy "OEMDrivers" map from wm6.
You should copy XIP files one by one from other rom and put it in a map with the same name.
Click to expand...
Click to collapse
Thx again NikMel, these hints should be able to get me going...

What is the map you guys talking about? Where do i find it?
Regards,
Carty..

20924, Sys and Xip, Big bug help.

Hi all, i have complety translated, .rgu / .dsm / .bmp / dpi 96 to 192 / 0409 to 0406.
from 20924.
But, when i cook it, and flash my phone, it dosen't book. I can see the version, but i can't not come to wm6 startscreen.
Do some1 know what it could be ?
Could some1 please look at my files maybe :/?
http://rapidshare.com/files/161467646/sys.rar

Bump, no one want to look in it and help me ??

Search for and download a tool called G'reloc.
A common issue with ported OS builds is that they fail to boot due to improperly coded/placed files. G'reloc will fix this for you. Just run it right before cooking, and then once compiled and flashed, your ROM should boot fine.
*You will need to find the correct codes for G'reloc and a Diamond ROM. I have only used this tool on the Kaiser, so I cannot tell you what they are.

NotATreoFan said:
Search for and download a tool called G'reloc.
A common issue with ported OS builds is that they fail to boot due to improperly coded/placed files. G'reloc will fix this for you. Just run it right before cooking, and then once compiled and flashed, your ROM should boot fine.
*You will need to find the correct codes for G'reloc and a Diamond ROM. I have only used this tool on the Kaiser, so I cannot tell you what they are.
Click to expand...
Click to collapse
As I can see, my package builder+buildos run it before it is done.
But anyway, could allways try it ), what shall i put in ? Some1 knows it ?

danny_and_2 said:
As I can see, my package builder+buildos run it before it is done.
But anyway, could allways try it ), what shall i put in ? Some1 knows it ?
Click to expand...
Click to collapse
I tried using a newer BuildOS for the Kaiser that included G'reloc, and it never worked properly. I would run G'reloc on it's own, and then uncheck the box to run it as part of BuildOS.
If those values are auto filled in for you, then give it a shot with them. Worst case, the phone still doesn't boot.

NotATreoFan said:
I tried using a newer BuildOS for the Kaiser that included G'reloc, and it never worked properly. I would run G'reloc on it's own, and then uncheck the box to run it as part of BuildOS.
If those values are auto filled in for you, then give it a shot with them. Worst case, the phone still doesn't boot.
Click to expand...
Click to collapse
Yes they just came automatic, so. Yes i will try that one, will report back if it dosen't
--- Edit ---
I couldn't i get an I/O error 105. ? Some1 knows what this it ?
--
Run-time error 105: File not open for output.
This error occurs if you try to use standard input and output functions
like Readln and Writeln without the Uses WinCRT; statement.
To correct this error, add Uses WinCRT; to your program.

How exactly did you translate the 96.DPI files?
Safe yourself the headaches and use the Diamond 1.96 as a base.
That would give you all the SYS 192 dpi files you need.
Are you making the ROM true 0406?
Or just translating or renaming the 0409.mui files?

Noonski said:
How exactly did you translate the 96.DPI files?
Click to expand...
Click to collapse
I have copyed the files from the diamond (192) to it.
Noonski said:
Safe yourself the headaches and use the Diamond 1.96 as a base.
That would give you all the SYS 192 dpi files you need.
Click to expand...
Click to collapse
I also would, but it ain't released on danish
Noonski said:
Are you making the ROM true 0406?
Or just translating or renaming the 0409.mui files?
Click to expand...
Click to collapse
I have copied the danish 0406.mui files, and changed it in every .rgu and .dsm file.

Bump, bump, bump.

Must be some1 out there, there can help me find my mistake ;/

danny_and_2 said:
Must be some1 out there, there can help me find my mistake ;/
Click to expand...
Click to collapse
HI
For port this os build i've made this:
first try to port only the xip
Delete folder from your old working kitchen:
MSXIPKernel
MSXIPKernelLTK
AND OEMXIPKernel if exist
Delete your old OS.NB in ROM folder of your kitchen
Now you need to Extract OS.NB From a diamond ROM 20924 protected or not !
(My rom for exemple)
take the 20924 OS.NB in your ROM folder
then just cook with your old sys and oem folder without the folder mentioned on top. flash & verify xip version.
if this work ,change your sys with the 20924 you have
but keep some files from your old working sys
if i have a good memory i've keep this:
.ROM folder
.VM folder
.Metadata folder
.hd.dll folder
.osaxst0.dll folder
.gwes.exe folder
possible some other files...
if you have Greloc error replace files mentioned in error
try this.
ask if you need help

xboxmod said:
HI
For port this os build i've made this:
first try to port only the xip
Delete folder from your old working kitchen:
MSXIPKernel
MSXIPKernelLTK
AND OEMXIPKernel if exist
Delete your old OS.NB in ROM folder of your kitchen
Now you need to Extract OS.NB From a diamond ROM 20924 protected or not !
(My rom for exemple)
take the 20924 OS.NB in your ROM folder
then just cook with your old sys and oem folder without the folder mentioned on top. flash & verify xip version.
if this work ,change your sys with the 20924 you have
but keep some files from your old working sys
if i have a good memory i've keep this:
.ROM folder
.VM folder
.Metadata folder
.hd.dll folder
.osaxst0.dll folder
.gwes.exe folder
possible some other files...
if you have Greloc error replace files mentioned in error
try this.
ask if you need help
Click to expand...
Click to collapse
Hi there.
Thanks for you guide, I'll try it right away.
And I will say if I run into a problem.

xboxmod said:
HI
For port this os build i've made this:
first try to port only the xip
Delete folder from your old working kitchen:
MSXIPKernel
MSXIPKernelLTK
AND OEMXIPKernel if exist
Click to expand...
Click to collapse
They aren't in my kitchen with this rom. Don't know why.
xboxmod said:
Delete your old OS.NB in ROM folder of your kitchen
Now you need to Extract OS.NB From a diamond ROM 20924 protected or not !
(My rom for exemple)
take the 20924 OS.NB in your ROM folder
then just cook with your old sys and oem folder without the folder mentioned on top. flash & verify xip version.
Click to expand...
Click to collapse
It boot, and it works. Haven't looked so much on the rom, just verify'ed the xip version.
xboxmod said:
if this work ,change your sys with the 20924 you have
but keep some files from your old working sys
if i have a good memory i've keep this:
.ROM folder
.VM folder
.Metadata folder
.hd.dll folder
.osaxst0.dll folder
.gwes.exe folder
possible some other files...
Click to expand...
Click to collapse
I have tried what you said, but the mobile just won't boot, and i don't know why ! /:
I think i need some more files?
xboxmod said:
if you have Greloc error replace files mentioned in error
Click to expand...
Click to collapse
I don't have that.

have a look here :
http://forum.xda-developers.com:80/showthread.php?t=379598

TekTonik said:
have a look here :
http://forum.xda-developers.com:80/showthread.php?t=379598
Click to expand...
Click to collapse
Hi there, trust me. I have looked the thread many times ..
Anyway, i got an update.
I have get the phone to boot, with the orginal OS & OSFILES.. Now i just need to find what files i need to have, to get it boot..
But i still got a bug, when it boot, touchflo3d won't start, it just skips. ?

The problem you are facing might be (99%) because of improper XIP porting. Just for suggestion, go through my XIP porting guide (in my signature) and try again with a working 20924 XIP (if you cant find one then I'll up the xip.bin from which I ported and am using)
Using original OS folder would not qualify as SYS porting If you check the SYS build no, you will see the original no and not the ported build

ababrekar said:
The problem you are facing might be (99%) because of improper XIP porting. Just for suggestion, go through my XIP porting guide (in my signature) and try again with a working 20924 XIP (if you cant find one then I'll up the xip.bin from which I ported and am using)
Click to expand...
Click to collapse
Hi there.
I finally got it to work (more or less), someone, know the files i have to keep in the shell ?, it wont lunch flo3d. :S ?
Some1 know why ?
ababrekar said:
Using original OS folder would not qualify as SYS porting If you check the SYS build no, you will see the original no and not the ported build
Click to expand...
Click to collapse
But i needed to find out, witch folder there was stopping me from booting, and that was my answer , now i just need to find out what files i have to keep, and there are only 587 files..
I will report back soon

anything new about an issue, I try to port build 20757 from BlackStone and I'm facing the same problem too : replacing SYS only doesn't boot

XIP Repository diamond | Last 5.2.20765. YES WE SHARE!!

Full Xip Porting with original OEMXIPKernel
-NEW FROM HTC IOLITE 5.2.20765
View attachment 152516
Please Feedback!
-5.2.20769 Xip
View attachment xip_out20769.zip
-5.2.21014 Xip
View attachment xip_out.zip

Try to download SYS 1,5 kb/s ....

media fire
nothing about new direct 3d driver?

magic55 said:
Try to download SYS 1,5 kb/s ....
Click to expand...
Click to collapse
Here you go:
http://forum.xda-developers.com/showthread.php?p=3120826
You'll have to port it though. It's for a Hermes.

adwinp said:
Here you go:
http://forum.xda-developers.com/showthread.php?p=3120826
You'll have to port it though. It's for a Hermes.
Click to expand...
Click to collapse
Dzięki / Thanks

new 5.2.20769 available !

New xip.bin from htc Iolite on post #1

for SYS 20765? any news?

I used search and find this
http://forum.xda-developers.com/showthread.php?t=476828&highlight=20765+sys&page=2

How to import the xip_out.bin to the OS.NB.payload.
Have tried XIPPort.exe and Insert.exe, none working?

infido said:
Full Xip Porting with original OEMXIPKernel
Click to expand...
Click to collapse
Good initiative brother But for complete porting, we also need to Gwes.exe from same XIP builds, remember? Details can be read from my tutorial thread

What must i do to change the xip? Where must i copy the xip.bin?
thanks a lot!

write xip_out.bin in to os.nb.payload ,address 00320000,with XipPort Tool.
best tool to port and replace original Xip is XipPorterEx made by Ervius
GWes.exe???

infido said:
write xip_out.bin in to os.nb.payload ,address 00320000,with XipPort Tool.
best tool to port and replace original Xip is XipPorterEx made by Ervius
GWes.exe???
Click to expand...
Click to collapse
i'm so sorry, but i don't undestand anything. i'm new in this type of changes.
can you explain it to more slowly?
Thank you!

Searching for tool XipPorterEx made by Ervius
Hello,
where i can find this tool.
i search for an hour, and no download-link is working for this tool.
thanks
everal
german glofiish m800 rom-customizer.

WM 6.5 Native Kernel/nk.exe/xip.bin for Hermes

Hi friends!
I think the topic pretty much says it all;
This is a native WM 6.5 Hermes OEMXIPKernel/xip.bin/nk.exe - aware of the new Slot 60/Slot 61 virtual memory layout - what does this mean for you as a chef?
Now you don't have to recmod any modules in \SYS anymore, to port over WM 6.5! And you have 64mb free to convert more files to modules!
But you will need to use a relocation tool that is aware of the new memory layout;
Ervius Visual Kitchen + Bepe's New Kitchen do this with the "Real WM 6.5 AKU" checkbox
There's also a build of "WMReloc" 2.0 floating around that may support this, that would be compatible with the "old style" kitchen (buildos + g'reloc, it would replace g'reloc)
http://rapidshare.com/files/245803085/HTCHermes-WM65-nk-xip.zip

Da_G said:
Hi friends!
I think the topic pretty much says it all;
This is a native WM 6.5 Hermes OEMXIPKernel/xip.bin/nk.exe - aware of the new Slot 60/Slot 61 virtual memory layout - what does this mean for you as a chef?
Now you don't have to recmod any modules in \SYS anymore, to port over WM 6.5! And you have 64mb free to convert more files to modules!
But you will need to use a relocation tool that is aware of the new memory layout;
Ervius Visual Kitchen + Bepe's New Kitchen do this with the "Real WM 6.5 AKU" checkbox
There's also a build of "WMReloc" 2.0 floating around that may support this, that would be compatible with the "old style" kitchen (buildos + g'reloc, it would replace g'reloc)
http://rapidshare.com/files/245803085/HTCHermes-WM65-nk-xip.zip
Click to expand...
Click to collapse
wow thanx 4 this toolS!

Da_G said:
Hi friends!
I think the topic pretty much says it all;
This is a native WM 6.5 Hermes OEMXIPKernel/xip.bin/nk.exe - aware of the new Slot 60/Slot 61 virtual memory layout - what does this mean for you as a chef?
Now you don't have to recmod any modules in \SYS anymore, to port over WM 6.5! And you have 64mb free to convert more files to modules!
But you will need to use a relocation tool that is aware of the new memory layout;
Ervius Visual Kitchen + Bepe's New Kitchen do this with the "Real WM 6.5 AKU" checkbox
There's also a build of "WMReloc" 2.0 floating around that may support this, that would be compatible with the "old style" kitchen (buildos + g'reloc, it would replace g'reloc)
http://rapidshare.com/files/245803085/HTCHermes-WM65-nk-xip.zip
Click to expand...
Click to collapse
thank you. I have been following your topic for some time and I must admit its way over my head. So do we just not use the \SYS folder anymore? I'm really confused on this.

over my head too... does this mean improved memory performance for 6.5 ROMs on Hermes? Storage or RAM? Could use a RAM boost with most ROMs...

Thanks DA_G u rock! i'll see if i can get it working on my old hermes!

anyone got that new wmreloc kicking around?

Its just a .exe file right?

need somone to flash new nk.exe 6.5 kernal rom
Can someone let me know if it boots?
I'm uploading a rom HERE with new nk.exe from 6.5 kernal
it will be doné uploading in about 5 mins.. i gotta go hit the dentist and get a root canal.. just lemme know if it boots
peace.

joshkoss said:
Can someone let me know if it boots?
I'm uploading a rom HERE with new nk.exe from 6.5 kernal
it will be doné uploading in about 5 mins.. i gotta go hit the dentist and get a root canal.. just lemme know if it boots
peace.
Click to expand...
Click to collapse
Bad news...
Couldn't Boot
Only the right green led is on and nothing...

Ditto
Same here, flashed but would not boot. But I'm game for another try!

joshkoss said:
i gotta go hit the dentist and get a root canal.. just lemme know if it boots
Click to expand...
Click to collapse
OOOOOUUUUUUCCCCCCHHHHHHHHH!

jajajaja
yeah it sucks!!!! i just went to dentist once.. to have a middle implant to one tooth... what da heck is the worst i ever experiment!
hope this works at the end.

maybe a noob question but how do I add this to my kitchen?
just the xip.bin, or do I need to copy the contents of the OUT folder too?

Search for Manual XIP porting using the search link in my sign!

this is great news! hopefully tai / irfan / joshkoss release a new rom using this!

ok Da_G
Are you saying that the memory could be changed from 64 to 61?
And we could have 3Mb more to use?
Mmmm any link to learn a little more about this... of course and the usage of this.

Ok lets try this baby!
goona redo the kitchen for 21807 with the nk.exe that nurkamol gaves me... oemxipkernel here must do the trick inthe ervius last kitchen just lemme get rid of the big admin folders there! a little confusing... but with a nice master chef ould be posible...
SYS 21807... Josh with my NK.EXE by nurkamol
Xip With this oemkernel and lets see what happend
Edited: first try was a failure! i set all the kitchen with all the 21807 modded of course... The thing i change was... the nk that nurkamol gaves me, and I couldnt find where to place the .ROM folder (it was on the sys, but in new kitchen where to place it?) and set kitchen to Imagestart at 0 PP 6mb not works... then i Add tehe default wincenls of course it was verwrited by OEM and chenge Startimagfs at 340000 and PP to 8mb and not works...
Next attempt...
Dont delete any folder from 21807 and let the xip ported nk by josh...
night!

It works as expected! Thank you very, very much
For others: don't panic, it has 15MB of PP set so you have to change it. btw, implantxip can't do that, you have to do it with osnbtool - or manually
Once again: thank you!
upd.:
for all those who can't get pp right:
Edit your TOOLS\kitchen_build_rom.bat and find the line with implantxip and replace it with those two lines:
Code:
..\TOOLS\osnbtool -ap xip.bin %pp%MB -y
..\TOOLS\implantxip -xip xip.bin -payload OS.nb.payload -imgstart %imgstart% -%uldr% -%nocert%
Of course you have to have osnbtool.exe in your tools directory

Great!
So this kernel works?!!!! we must to check real aku as i red your post on Da_G's kitchen thread... use the lastest MSXIPkernel ... Use the Romhdr and os.nb.payload for any other build cause its special for Hermes... I ask you this cause the OEMxipkernel modules are different, are many more on this kernel by Da_G.
Will try this... wich pp do you use.. 8?
thanks a lot dude! you have wonderfull ideas... my rom boots and its efficient... with some troubles about initflashfiles but works fine, because of your advice there on raphael forum.

I've took from Da_G only nk.exe, ceddk.dll and flashdrv.dll. You have to either take his boot.rgu, too - or ensure you have this line in yours:
Code:
[HKEY_LOCAL_MACHINE\System\Loader]
"EnableUpperModules"=dword:1

XIP Extract

Hi!
I'm a rom developer and i've managed to cook a rom for my Benq E72 using the build 23017, but now i want to use the build 23090.
I'm trying to extract the "XIP" of an Standard Emulator Image from MS SDK 6.5.3 using this command:
nbsplit -emu os.nb
os.nb.payload
RomMaster -w 5 os.nb.payload -x -o xip.bin >NUL
But i always get an error....
[Info] It is a common ROM.
[Error] Load nb00 failed.
Also i have a rom for this device that use the build 23090, but i cannot extract the xip either
Hope someone could help me! Or tell me where i can get the XIP and SYS 23090 for Smartphone!
Thanks!!!

Why do you want to use an ancient build?
It's from November 2009
The new builds are available here... But it's your choice anyway.
The closest think I have is 23092. If that will make you happy - get it
http://dl.dropbox.com/u/3324710/23092_XIP.BIN_MSXIPKernel_SYS_DPI_96_192_0409_0419.7z. Only Eng and Ru - no Spanish

AndrewSh said:
Why do you want to use an ancient build?
It's from November 2009
The new builds are available here... But it's your choice anyway.
The closest think I have is 23092. If that will make you happy - get it
http://dl.dropbox.com/u/3324710/23092_XIP.BIN_MSXIPKernel_SYS_DPI_96_192_0409_0419.7z. Only Eng and Ru - no Spanish
Click to expand...
Click to collapse
Thanks!
I want to use that build because is the only one i know that works well on my device....
Thanks for the file, i'll try it!
I can mix that XIP 23092 and SYS 23090 right? i have the spanish resources from the emulator rom

samWMEmuKitchen v0.2b - ROM Kitchen for Windows Mobile Emulator

nickleby said:
I can mix that XIP 23092 and SYS 23090 right?
Click to expand...
Click to collapse
Sure you can. And it's not a mix - xips in 23089-23094 were the same modules with different dsm. So the only difference will be number of the build - it will look like CE.OS 5.2. 23092 (Build 23090.x.x.x)
Alexx~, dude , I think nick has problems with extracting the stuff from emulator.

AndrewSh said:
Sure you can. And it's not a mix - xips in 23089-23094 were the same modules with different dsm. So the only difference will be number of the build - it will look like CE.OS 5.2. 23092 (Build 23090.x.x.x)
Click to expand...
Click to collapse
Ok! Thanks for all your help!!

Oh, just to be sure....
All the things posted here http://forum.xda-developers.com/showthread.php?t=544445 works on Smartphones

nickleby said:
Oh, just to be sure....
All the things posted here http://forum.xda-developers.com/showthread.php?t=544445 works on Smartphones
Click to expand...
Click to collapse
You have to check it by yourself. Normally everything should work, why not. All the issues described in the topic are for 20% device-dependent and for 80% user-dependent
For me and of course for Alexx~ (he knows much more than me about the things) - every build works

AndrewSh, i realized what the problem is. In samWMEmuKitchen have the opportunity to extract dump, after the dump will be created os.nb, from which they can then extract xip.bin the usual way.

It is still easier, nbImageTool extracts xip.bin directly from the emu image.bin

nickleby said:
Oh, just to be sure....
All the things posted here http://forum.xda-developers.com/showthread.php?t=544445 works on Smartphones
Click to expand...
Click to collapse
NO! Those builds does not work on Smartphone devices.
BenQ E72 does have WM Standard.
Those resources are for touchscreen devices (WM Professional).

Alexx~ said:
It is still easier, nbImageTool extracts xip.bin directly from the emu image.bin
Click to expand...
Click to collapse
How??
nbimagetool SP_ESP_GSM_QVGA_VR.bin
Files is not an NBH!
Checking for .nb
Error reading MBR
Forget it! xD i've solved the problem....
Thanks

nickleby said:
How??
nbimagetool SP_ESP_GSM_QVGA_VR.bin
Files is not an NBH!
Checking for .nb
Error reading MBR
Forget it! xD i've solved the problem....
Thanks
Click to expand...
Click to collapse
run the program as an administrator

I am writing in this way directly, since I have not received help in the forum, and that maybe I have not been very specific in my request to place it in the forum.
I own a Smartphone, brand MWG Zinc 2 Rom and all I own are in English.
Just explained on the website of the creators of the ROM for my device, the entire procedure for Cook ROM.The page es PDAGismo.com
My question is very different from the way this process is done for different devices because they do not know much about it.
The page is in Thailand but you can translate, I do not understand is the whole process of the preparation of the ROM.
Someone could explain all this ?
It is so hard to accomplish this task by a person with basic computer knowledge and without any programming domain?
Help me, please.
Thanks