yashsingh1/xdaforums huggingface dataset:
[Touch Diamond, MDA Compact IV ROM Development] garymeg:
I Have all these installed, but i am getting the errors see above post for quote of error, everything else seems ok, i can build from a kitchen that has the xip already extracted (tested with old backup of t-mobile rom kitchen i had before my computer crashed)
[Touch Diamond, MDA Compact IV ROM Development] dipje:
Read the entire thread please. I even posted the ones I've used and where I got it from.
[Touch Diamond, MDA Compact IV ROM Development] dipje:
I just tried dumping the latest VIC rom (3.7) with Diamond Kitchen 0.4.

It failed on my machine too. The problem is the (OUTDATED!!) kitchen.

Try using bebe's or visual kitchen (which is based on bebe anyway). The XIP/SYS handling is way more flexible with playformrebuilder in the base of the kitchen.
[Touch Diamond, MDA Compact IV ROM Development] deeren:
deleted. wrong reply
[Touch Diamond, MDA Compact IV ROM Development] dipje:
http://rapidshare.com/files/217464596/21038try.rar.html

Yes I've deleted the temp folder :P.

But I didn't delete the os.nb.payload file (128mb) because I think it's needed.

Yes I know, you can reduce the os.nb.payload to the minimum XIP (3 to 7 mb) but I don't really know yet how and I don't need it on my own machine.

Remember, I've deleted duplicate files out of packages to get less warnings during the build. So you just can't copy some of the old packages, because there _might_ be something missing.
[Touch Diamond, MDA Compact IV ROM Development] garymeg:
I'm Glad its not just my computer, I have had a "QUICK" look at visual kitchen but up to now i have not been able to make any sence of it, will have a look for some good guide to using it, might have to trawl through all posts to work out how it works, I have managed to get rom dumped but the folder structure inside the "Kitchen" folder is all wrong at the moment will have another play with it and read through the thread.

Thanks for your help and trying the diamond kitchen 0.4 thats what i'm (Was) using.

Oh well, here comes another learning curve for me to fall off just as i get comfortable with it!!!!!!!!!

anyway thanks again for all your help, PS if you have any "tips" for the visual kitchen i would be also greatful.
[Touch Diamond, MDA Compact IV ROM Development] dipje:
Use bebe's kitchen.

http://xdaforums.com/showpost.php?p=3543174&postcount=16

The videos / animations bebe posted on his own forum explain everything very very very clear. And if you come from Surface Kitchen / Diamond Kitchen you'll get used quickly enough to bebe's, because it's both based on command-line bat files :)

Bebe's starts from an os.nb file though, so you'll have to use a tool like nbhutil first to extract your .nbh rom files to the needed os.nb file.

Visual Kitchen is _complete_. It contains tons of tools (advanced) cooks need, so everything is just a few clicks away. That's what people like conflipper like about it. But if you're learning, start with the base - bebe's kitchen / platformrebuilder - to get a feeling for it.
[Touch Diamond, MDA Compact IV ROM Development] deeren:
u can gain more mb's by reducing the ULDR. there is a thread on this forum concerning manual reduction but u can use xipporterex from ervius to do so.

just load your os.nb.payloadin its corresponding folder...

no need to use the xip functions and the rest.
[Touch Diamond, MDA Compact IV ROM Development] deeren:
hey dipje,

now that i know you use bepe's kitchen, i have a question for u.

have u tried and have u succeeding in porting any sys & xip provided by adwinp.

http://xdaforums.com/showthread.php?t=467460&highlight=adwinp

here's the post. i have been trying for months but :( no answers.
[Touch Diamond, MDA Compact IV ROM Development] dipje:
Dang, the forum must be acting up. The only thing I saw when I read your post was '21038?'. Really, that's it.

Kinda understand now that my answer would seem aggressive.

So to give a normal (:)) answer to your question:

I've tried, but platformrebuilder.exe kept on crashing. I switched to a 21042 build/SYS somewhere and that one worked instantly.

So I browsed around for another 21038. Found one (can't remember where, probably ppcgeeks.com) and that one worked perfectly. I just replaced the whole directories from my XIP folder with the ones supplied, and left the others alone. Tadaah.
[Touch Diamond, MDA Compact IV ROM Development] Dqix:
dublicated post.
[Touch Diamond, MDA Compact IV ROM Development] deeren:
yeah, i got that same error too trying to port from adwinp. i've read the whole thread and everybody seemed to have succeeded in porting the xip n sys. so i made a comparison. eventually, my stock xip had in each of its folders an extra file. ( each folder in xip stock had s000,s001,s002,s003 but in that of the provided xip it had only s000 s001,s002)

if anybody here can provide an answer how to port in such a situation.. thanks.
[Touch Diamond, MDA Compact IV ROM Development] deeren:
By the way, everything else failed...ie. xipport failed, xipporterex failed, ervius multivisual kitchen failed, bepe's kitchen failed. so i finally ported with an xip and sys(21028) provided by davideuck in the blackstone forum.
[Touch Diamond, MDA Compact IV ROM Development] megahenebi:
Its would be a biggest pleasure to have it. 178MB its not a problem for me. If it possible to upload on rapidshare.com

Thank you very much!
[Touch Diamond, MDA Compact IV ROM Development] deeren:
hi, dipje already provided you generously with his kitchen a few posts away. take a look.
[Touch Diamond, MDA Compact IV ROM Development] dipje:
Well, I didn't have a clue. I was a noob then (still am :P) so I really didn't know what I was doing with porting. What got patched, what do we do? Where does the XIP hook into the SYS? What does the SYS needs to be Relocated when you change the XIP and how does that tool know where the XIP is and in what format :).

Normally if you download an os.nb.payload as XIP it should be completely ported and ready to go for _a_ device. That would mean that just injecting it into your os.nb.payload should be enough. Bebe's kitchen uses a commandline tool for that. So whichever kitchen you use, eventually it generated a os.nb.payload for about >90mb (depending on your ROM content ofcourse). That is the time that you inject your xip.bin into your new payload and finish it up as an OS.nb, and finally a NBH file.

I've tried renaming the small os.nb.payload files to xip.bin and injecting them. I've tried extracting them and using the resulting xip.bin to inject them.

I also tried ignoring the 'ready to cook' statement and going along with xipporterex but I simply didn't manage to cook it back in properly.

DiamondKitchen / SurfaceKitchen build a filesystem for your ROM on a _template_ os.nb.payload file. You gotta use the one from your dumped ROM for that. But it generates an os-new.nb.payload. I managed by modifying to bat files a bit to modify the line where the final OS-new.nb is generated by including my new os-new.nb.payload _AND_ the ready-to-cook-downloaded os.nb.payload with the newer XIP.

That way I finally noticed adwinP's version-info on the bootscreen, so I knew it finally had the XIP working. But it wouldn't boot further into the OS. Now I know that should be because I didn't relocate my SYS files to the new XIP, but I didn't really know how to do that.

Bebe's kitchen is easier in the way it generates your xip.bin from just the loose files in your ROM dump. It actually _Generates_ a xip.bin. So whatever file you download from a XIP (being rar'ed up folders, xip.bin or os.nb.payload file), just extract them so you've got your MSXipKernel (and maybe MSXipKernelTK) and place them in your ROM/XIP folder and your ready to go.

If you got it working with the other (older?) tools, please let me know. Because I think it'll help me quite a lot in understanding what goes on in my device :)
[Touch Diamond, MDA Compact IV ROM Development] iago_00:
thanks a lot man! this will almost complete my ROM. :)
[Touch Diamond, MDA Compact IV ROM Development] deeren:
well all i know is that the missing files in the xip, well its something like reducing uldr. it is not needed and it is done with bepe's platformrebuilder but till now don't know how to port it using a normal xip. anyway i abandoned the idea of using the rhodium xip and sys. i didnt quite like them. i tried the new 21042. and the 21028.

frankly i prefer the iolite ones.20765 or 20771 . i succeeded in making the new notification manager and the fingerlike menu work on these builts.
[Touch Diamond, MDA Compact IV ROM Development] iago_00:
I cooked my rom but after flashing my Dimond didn't pass the "TOUCH diamond" screen.

can anyone help?

@dipje

can you post your ported xip and sys, ROM? so that I can try my oems with those? thankis in advance
[Touch Diamond, MDA Compact IV ROM Development] deeren:
what kitchen did u use? bepe's one?

1) did u run greloc before building the rom?

2) make sure you use the wince folder from ur original xip when porting.

3) if still not good, use the vm and sys folder from original sys folder when porting sys
[Touch Diamond, MDA Compact IV ROM Development] dipje:
Easiest question first: I posted my entire bebe-kitchen a page back or something on rapidshare. It should have everything you need :P.

From what I know (correct me if I'm wrong):

- You only see the Touch Diamond (splash screen actually).

WITHOUT the version numbers in the lower right

You really messed up your XIP :P.

- You only see the Touch Diamond (splash),

but WITH the version numbers in the lower right.

It seems your XIP is ok, but the 'link' between XIP and SYS isn't right.

Things to check:

* Did you leave your OEMXipKernel folder alone in your ROM/XIP folder?!

* Did you leave your original WinCENLS.. folder aline in your ROM/XIP folder!?

* If your using Platformbuilder 2.1 update for bebe's kitchen, make sure you have set the 'OLDKERNEL=1' variable in the build_rom.bat file! Otherwise it's running in WM6.5 mode

* Did you leave your original os.nb.payload in the ROM/XIP folder? Don't overwrite this file with any newer os.nb.payload files you might get of the net!

* Did you run GReloc on your SYS after changing it? (don't know if this is needed with bebe's kitchen)

- If you see the Windows Mobile welcome screen, and maybe even make it past the first setup and calibration... but it eventually just hangs at the (green?) Windows Mobile screen

You messed up your SYS

* Kinda hard to do this I guess. Did you use the correct SYS package?

* Did you delete your old SYS entirely before placing the new SYS in place.

* Did you maybe delete too much out of your SYS trying to strip it clean?

Is this still needed on bebe's kitchen? He doesn't show it on the 'howto' video's and I believe platformrebuilder builds everything from the ground up anyway, so no modules need to be relocated.
[Touch Diamond, MDA Compact IV ROM Development] dipje:
and if anyone can help me.. I'm trying to get a 21202 build working. Got a SYS/XIP off from ppcgeeks.com somewhere, but getting mixed results with crashing platformrebuilder.exe, not showing XIP versionnumbers while booting, hanging at the versionnumbers, or even nicely booting up but getting messed up graphics and startmenu will not work.

It's actually a SYS used for 480x800 resolution devices, so maybe I'm in over my head trying to get it to work :)
[Touch Diamond, MDA Compact IV ROM Development] danny_and_2:
Download Da_G's kitchen newest kitchen based on 6.5 21202. And then, you only have to port the XIP . :)
[Touch Diamond, MDA Compact IV ROM Development] danny_and_2:
You have to replace the GWES.EXE & .MUI from a 21xxx build. Then you will get it working easly :).

Happy cooking.
[Touch Diamond, MDA Compact IV ROM Development] deeren:
i believe it is needed in some unfortunate cases. i know with the 2018 build i had some errors and then seatone advised me to use greloc and that worked perfectly.

i know he doesnt show it on the videos but hey, it doesnt cost u anything just to double check.:)

by the way, how are you porting with a sys of a diff resolution? so what about the resolution dependant sys folders? u removed them and replaced them?
[Touch Diamond, MDA Compact IV ROM Development] deeren:
yeah i kinda figured this out . well i got it to work by replacing gwes and gx.dll . but good to know about the .mui.

also, good to see that a famous chef is keeping an eye on this thread in case we say any nonsence, please correct us. hehehe.
[Touch Diamond, MDA Compact IV ROM Development] danny_and_2:
You replace the DIR from SYS ex. "640x800" with the diamond res. 640x480. Then you got it working proberly :)
[Touch Diamond, MDA Compact IV ROM Development] danny_and_2:
Hey no problem.

Maybe I get some more knowledge from you, when you guys get better. Who knows. :)
[Touch Diamond, MDA Compact IV ROM Development] deeren:
by the way danny, are you leaving the diamond forum??????? cause in your signature i can see that u have put more emphasis on the xperia thing.
[Touch Diamond, MDA Compact IV ROM Development] danny_and_2:
I'm not leaving, "yet". I'm thinking about it, mostly stop cooking. I don't see reasons why these days that I should continue. It have become so easly to cook your own roms.

So you have your own personal rom with all the things you need.
[Touch Diamond, MDA Compact IV ROM Development] dipje:
In your SYS folder you see multiple _DPI_ suffixes behind the folders.

DPI_192 is 'our' DPI for 640x480 like devices.

Start with the right DPI-sys will get you a long way.

But we have folders named 'base_dpi_192_resh_480_resv_640', but there are SYS' out there with folders names 'base_dpi_192_resh_480_resv_800'.

Surprise surprise :), they are 480x800 specific files.

Leaving them out, and/or replacing them with the proper resolution folders you have from other SYS' will get it working pretty much all the time.

But you ARE replacing newer files with older versions in a SYS.

For example, replacing the 480x800 folders in a 21202 WM6.5 sys with the ones I got from a 21042 WM6.1 build will give you trouble :P.
[Touch Diamond, MDA Compact IV ROM Development] iago_00:
Thanks for your kind reply. In fact i think i messed up with my XIP!

I downloaded your kitchen. do you think I can use your kitchen with my OEM folder?
[Touch Diamond, MDA Compact IV ROM Development] deeren:
Wow. so u r into the windows 6.5 now? i don't think i would shift to that for the moment. so far the roms i had flashed didnt quite please me. they were kind of buggy,

who knows . maybe u'll make a better one and release it.

good luck my friend,
[Touch Diamond, MDA Compact IV ROM Development] danny_and_2:
Yes you can. Just remember to keep the os.nb.payload file & SYS. Then it should work proberly. :)
[Touch Diamond, MDA Compact IV ROM Development] iago_00:
Ok it booted. Thanks a lot man
[Touch Diamond, MDA Compact IV ROM Development] eangulus:
OK. FIrstly I know I started this thread, but been busy for past couple of days. Still been reading whats been happening thou, hence why I am posting now.

A few posts back someone was yaking about the different folders for different resolutions.

I was wondering if it is a res you don't need can it be deleted altogether from the ROM to save space. And if we can what are the folders to keep for the Touch Diamond Res.
[Touch Diamond, MDA Compact IV ROM Development] dipje:
the sys contains only one resolution most of the time.

So that's not something that can be erased.

What I delete normally, from SYS:

- Autoupdate

- NetCF (replacing it with 3.5)

- OneNote

- Sometimes whole Office

- SampleMusic

- SqlCeMobile (not the SQLCE Folder)

- Transcriber

- WindowsLive

those I just tested out myself and it seems to work ok.

FWUPDATE I found out that way is something you need to keep :P.

From OEM I mostly delete:

- Album (replacing it with 3.0 or not at all)

- AdobePDF

- Cyberon voice speed

- Google Maps (replacing it)

- JbedJava

- Manila (replacing it)

- MP3Trimmer

- Opera (replacing it)

- PhoneCanvasSlider (replacing it)

- RSSHub

- YouTube (replacing it sometimes)

- Zip

Deleting album also deletes the sample pictures & videos I think.

Search the default ringtones and alert sounds, and delete all you don't want.

You could also delete dictionaries (.ldb files) that you don't need.

To give an example, I have a pretty loaded ROM now, with RhodiumManila, GoogleMaps, Opera, FlashLite, Album 3.0, _all_ WWE dictionaries, FMRadui, All 'enhancements' (like Outlook, Message, Notification, Menu..), newer PhoneCanvas, Topaz PowerOff warning, newer Comm Manager and setting-screens, 6 programs I normally use directly cooked in.

The resulting ROM is 10 mb _smaller_ than the stock HTC rom, and it got loads more cooked in.

My WM6.5 test ROMs which I did as stock as possible (even removing a lot of HTC stuff I consider 'part of Windows Mobile' :)) were as big as 78mb. And thanks to Titanium / CHome and the new start menu WM6.5 is pretty usable stock + lite.

So if you want to remove more for your light ROM (your original starting question in this thread :P) you gotta and google around a bit more to see where you can shave off a megabyte or so.

edit: Sorry for my long posts, I ramble on for too long :(
[Touch Diamond, MDA Compact IV ROM Development] eangulus:
I was just talking about the DPI folders.

The ones that specify a resolution are you able to delete the resolutions not needed?
[Touch Diamond, MDA Compact IV ROM Development] gxg:
What do you mean by newer phone canvas? sounds interesting!
[Touch Diamond, MDA Compact IV ROM Development] deeren:
the stock phonecanvas comes only with the slide to answer. you might want to replace that with a phonecanvas of ur choice . for example mine is blackdialer+ black slider + curtain.

also, probably, we would be having a new phonecanvas in some weeks' time. thanks to the geniuses of xda
[Touch HD Themes and Apps] tru88:
hello

all of us know that u can't view the sender name in bluetooth unless u use programs such as Dr.YAR or AlirezA

the problem now lots of new roms with the new manila they come with different bluetooth software such as OBEX

and once u install Dr.YAR there will be a conflict and none will work

so is there any solution ?

is there a better program to view the sender name in bluetooth ?

thanks ..
[Tilt, TyTN II, MDA Vario III General] freewind29:
I have flashed many different 6.5rom int my kaiser, but with some roms, the titanium couldn't be showed even the titanium plugin was selected, I had tried hard reset, reflash with no joy, anyone know what cause this and how to fix it?

Thanks a lot!
[Tilt, TyTN II, MDA Vario III General] denco7:
First of all. you should probably post this in one of the 6.5 rom threads, from the roms that you have flashed.

Secondly......................Beta ?....................

If it doesn't work, flash another rom and wait until the actual M$ upgrade comes out.
[Tilt, TyTN II, MDA Vario III General] xavierf:
Settings --> System --> Large Display --> Uncheck "Use large Start Menu" ;)

Hope it's help you
[Tilt, TyTN II, MDA Vario III General] freewind29:
Thanks, you are the one really try to help! Whatever this work or not, thank you very much!

Edit: Just flash back to the rom has the problem I mention, and I can't find the large display option in system.
[Touch HD General] BenBen_:
Hi :)

Could you please tell me how i can change the mac adress of my HTC Touch HD?
[Touch HD General] Gisbourne:
You can't...

As far as I'm aware you cannot change a physical MAC address as it is hardwired into the network interface card, therefore, the only way you could change it is by swapping out the main board.

Why would you want to change it?
[Touch HD General] gadgetwizard:
You can't change it it's embedded into the wireless hardware, why would you want to?
[Touch HD General] Mm&Mm:
I found this program Macshift for XP http://devices.natetrue.com/macshift/.

Maybe someone can change it to work on wm.
[Touch HD General] twisted-pixel:
but the same question exists...why do you want to change your MAC address?

the Mac address is a combination of the manufacturers code and the device serial number. The result being that no two devices anywhere in the world have the same Mac address....should this happen in real life..all sorts of problems can occur with web based communications.
[Touch HD General] Rudegar:
this been asked since the first htc device with wifi was released search

networking forum for info

as far as i know nobody ever managed to do it

also it would be a problem as 2 devices with the same mac address (mac addresses being the only truly unique identifier for 2 network devices could mess up network traffic pretty much)

the other person whos ½ packets you may intercept and his yours giving you both network instablity may feel strongly against you chanting your mac address to the same as his
[Touch HD General] gadgetwizard:
I'd still like to know why BenBen_ wants to change the MAC address?
[Touch HD General] Xeon:
Maybe he cracked the wep key of an access point which uses MAC filtering and then analyzed the packets to find out which MAC has access to the AP .. And now he wants to use that MAC.. ( I am just assuming :cool: )
[Touch HD Windows Mobile ROM Development] johnpatcher:
Hi,

I'm trying to port the sys of the rhodium 21040 build. Porting the xip wasn't a problem at all, and worked just fine, but porting the sys doesn't want to work for me, as I get the message "There is no Bluetooth hardware installed on this device.", after flashing the cooked rom.

I retried it a few times already, and get the same result every time.

Everything else seems to work great.

Any ideas?

Best regards

johnpatcher
[Touch HD Windows Mobile ROM Development] lpause:
the 21040's SYS is no "Bluetooth" module

maybe you can get it from other build

or you can try 21042
[Touch HD Windows Mobile ROM Development] johnpatcher:
How do you know this? In the 21040 Sys there are some files containing "bt" in their name.

Is there already a 21042 build with wvga resources?

Best regards

johnpatcher
[Touch HD Windows Mobile ROM Development] pkoper:
Bluetooth is missing in the sys, I use one from 21028.
[Touch HD Windows Mobile ROM Development] johnpatcher:
Ok, now I figured it out :), thanks!

I have taken the bluetooth from 21042 and will try to cook it now.

€dit: Works just great :).
[Touch HD Windows Mobile ROM Development] geekbuddha:
please share the ROM you cook. Thx.
[Touch HD Windows Mobile ROM Development] johnpatcher:
I will :).
[Touch HD Windows Mobile ROM Development] panosha:
What files or folders you changed ? :confused:
[Touch HD Windows Mobile ROM Development] hellonasty:
copy this to your sys folder!!!

http://rapidshare.com/files/213920337/SYS.rar
[Touch HD Windows Mobile ROM Development] johnpatcher:
I have just added the Bluetooth package from the 21042 build.
[Touch HD Windows Mobile ROM Development] panosha:
Thank you.

I have already these files in my base ROM, bluetooth has a lot of problems. I think I am going back to 1.4.3. It is more stable than 1.6 beta.
[Touch HD Windows Mobile ROM Development] johnpatcher:
Sorry, but what versions are this? I thought that the build number is the only one?
[Touch HD Windows Mobile ROM Development] panosha:
Official HD OS version it is build 20764.1.4.3.

Topaz beta OS it is build 21038.1.6.0.
[Touch HD Windows Mobile ROM Development] johnpatcher:
Thanks for cleaning this up.
[Windows Mobile Software Development] Spiderm@n_:
Go go go :):):)

So, does this mean, that iGO will find TMC info and use it, because it currently doesn't find any TMC hardware.
[Windows Mobile Software Development] 4irm:
the most desired thing would be using TMC on iGO or TomTom; definitely possible but no one knows exactly how; there is already a thread:

http://xdaforums.com/showthread.php?t=454281

regards

IRM
[Windows Mobile Software Development] 4irm:
well, its not about finding hardware, there are already iGO versions finding the correct fm transmitter on my touch hd, if not you can easily edit sys.txt.

The issue is simply that it cant extract the required information.

@flywhc: would be great to see you coming up with some results! Thx!

-