yashsingh1/xdaforums huggingface dataset:
[Touch GSM ROM Development] humrod:
Rom translated

Hi guys, finally I goal in translation. At this time I'm redacting a tutorial about how i can translate the elf/elfins roms to share in this tread. Thanks all of you for your answers and advices, especially to Demo95 for share his knowledge.

The only thing i have to resolve modifying the iniflashfiles is that autoshortcut doesn't make the job.

Can anyone give here a little explanation about how it works?

I miss something cause there are some roms in spanish (diamond) that works....
[Touch GSM ROM Development] Arlanthir:
Wow, amazing work on this thread!

I think I'm going to start tweaking some ROMs and see if I can get the hang of it :)
[Touch GSM ROM Development] Demo[95]:
Ok gurus, i need your help once again.

I'm trying to port a WM 6.5 SYS folder without success :mad:

Here are the steps i'm following :

1 - I run G'Reloc on my original SYS folder, and write down Slot 1 and Slot 2

(i.e SLOT 1 = 01F90000; SLOT 2 = 03DB0000)

2 - In my original SYS folder i delete every folder except .VM

3 - I copy all folders (except .VM) from WM 6.5 SYS Folder to my original SYS folder.

4 - Start G'Reloc again. (SLOT 1 and SLOT 2 have the correct value); and click Do it!

{G'Reloc tell me it has relocated ~250 modules. But if i click again on Do it! it keeps sayins it has relocated modules... is it normal?}

5 - Build the rom and flash...

But the problem is that the phone freeze even before the smart mobility.

Any suggestions?
[Touch GSM ROM Development] !Aman!:
which build are u working on?
[Touch GSM ROM Development] Demo[95]:
My original rom build is 19972.1.2.7

and for the donor.... heu... don't know for now, i just know it's a WM6.5 leaked beta.
[Touch GSM ROM Development] !Aman!:
i've heard that our current kitchens (even bepe's latest kitchen) dont support any WM 6.5 builds higher than 21139 or 21140
[Touch GSM ROM Development] Demo[95]:
Ok in fact i'm using the lastest Bepe kitchen.... that could explain why i'm having problem since several day in porting the SYS.

Could you tell me which build version i should keep using?
[Touch GSM ROM Development] !Aman!:
build 21139 worked for me, thats the only WM 6.5 build that i've tested. right now i'm using WM 6.1's build 21015

PS: u don't need to run G'reloc if u are using bepe's latest kitchen. i didnt even replace the .VM folder with the original .VM folder of Elfin while testing any of the 21XXX builds.
[Touch GSM ROM Development] Demo[95]:
whaaou, didn't know i could bypass reallocation with latest bepe kitchen!

ok, i've found a 21139 diamond's SYS folder.

will try again tonight, and i'll post to say how it went!

thanks for your help htctouchp
[Touch GSM ROM Development] letama:
You ported the Xip also, right ? It won't work with an old xip.

I ported 21139 with XipPorterEx, I had to reallocate the partition to fit the new xip, maybe your issue is there ?

I have a question on my side, is there a way to diagnose a boot failure?

I think I saw somewhere that some devices are able to log the boot, how does it work?

Thanks,

LeTama
[Touch GSM ROM Development] !Aman!:
if i'm not wrong, this is supported only on the newer devices like Diamond etc. this functionality is in the SPL and our poor old Elf/ins SPL doesn't support this.
[Touch GSM ROM Development] humrod:
I'm working on a 3.07.720.03 about the "butterfinger" effect described by Dxisda, change the touch.dll, the Boitouch.exe and the starBiotouch.exe by an older sistem WM6 and the touch flo works great.....but now no play sounds, ringer, alarm, etc. where to look?
[Touch GSM ROM Development] letama:
Ok, it will be good for my diamond, I'll search for some info there...

Thanks!

LeTama
[Touch GSM ROM Development] Demo[95]:
Yep, i've ported the XIP also but still no success :(

I'm using this Diamond rom as base file for cooking.

I'm using XipporterEx_1_2_Revision_37 to port the XIP, and it do not complain about partition space.

ok now i've tried to use Diamond SYS Files except *192.dll and replacing them with my original 2.XX Elfin *96.dll... without any chances.

Is there a way to port Diamond SYS to an Elf? Or should i search for a vga device 6.5 ROM?

Any tips, links would be appreciated.
[Touch GSM ROM Development] letama:
You can probably port from diamond, but is it really worth it? As far as I know, Diamond 21139 was ported from QVGA to VGA, and now you need to return back to QVGA.

If you want, you can start from mine here: http://xdaforums.com/showthread.php?t=474866, you have my kitchen at the bottom of the first post.

It was ported from the original blue angel leak, I did the minimal modifications to make it work. Or if you want to do the port yourself, you can start from the blue angel kitchen if you can find it somewhere (it seems to have been removed following a complaint from Microsoft).
[Touch GSM ROM Development] dsixda:
The Blue Angel kitchen might still be available in one of the threads, I was able to download it over a week ago. If you can't find it then PM me... ;)

I was able to port the XIP from the Diamond port of the Blue Angel WM6.5, but it wasn't very stable.. if I tried to install CHome it would freeze. I used the Hybrid Kitchen to port the xip.bin.
[Touch GSM ROM Development] vadyarik:
I suggest you use this package instead of your default AutoRun. It is taken from the latest OEM HTC. This customization will be much faster. This theme in your config.txt will be immediately following the first calibration screen, standart Windows does not even appear.

The file runcc.lua enter your config.txt. If you have a few config.txt, you need to write them sequentially, such that:
[Touch GSM ROM Development] trueg:
Are there any other benefits to runcc or just the theme initialization?
[Touch GSM ROM Development] Ameet:
Can this also run mortscripts at startup? What would be the commands for that? Take for instance I have a file called 1.mscr that runs on startup and then it runs the CheckAutoRun and deletes itself. Do I need to specify 1.mscr to run this RunCC instead of CheckAutoRun and delete the CheckAutoRun OEM from my ROM?
[Touch GSM ROM Development] vadyarik:
I think RunCC replaces only AutoRun.exe. CheckAutoRun serves only for the animation. You can leave it as is.
[Touch GSM ROM Development] Ameet:
So replacing the AutoRun.exe with this package and specifying to run CheckAutoRun.exe in the startup script will still run this file? :)
[Touch GSM ROM Development] vadyarik:
Ameet, sorry!

I can not catch up with your great mind!:D
[Touch GSM ROM Development] dsixda:
Now I am confused LOL
[Touch GSM ROM Development] Ameet:
Sorry brother if I must have sounded a bit confusing :D

I meant to ask will this work in this scenario having these files and packages in the ROM

1. CheckAutoRun.exe

2. RunCC package

3. NO AutoRun.exe in ROM

CheckAutoRun runs at startup.. Will it now detect and run this RunCC.exe instead of AutoRun.exe during 1st boot? :D
[Touch GSM ROM Development] dsixda:
Yeah, I was wondering about the same thing.

Does CheckAutoRun call Runcc.exe?
[Touch GSM ROM Development] vadyarik:
Absolutely! So it should be.:)
[Touch GSM ROM Development] dsixda:
I just tried the LUA script in my cooked ROM, build 21018, but the ROM freezes at the last screen before autorun ("Tap the screen to begin using your device" - then won't do anything if I tap).
[Touch GSM ROM Development] Ameet:
Hmm.. I'll test it out tonight at home.. :D
[Touch GSM ROM Development] texture:
On my Blackstone i remove Autorun,Checkautorun and Autoshortcut and RunCC works fine.
[Touch GSM ROM Development] trueg:
In my ROMs I always have connectionsetup run at the end of customization (before it reboots). Would this still work with runcc?

"autorun"="\\windows\\connectionsetup.exe"

"autorunarg"="fullscreen"
[Touch GSM ROM Development] dsixda:
Oh.. Ok, I didn't remove Checkautorun..

What is Autoshortcut for?
[Touch GSM ROM Development] trueg:
HTC uses autoshortcut for creating shortcuts...

<wap-provisioningdoc>
<characteristic type="Registry">
<characteristic type="HKLM\SOFTWARE\HTC\AutoShortcut">
<parm name="\Windows\Start Menu\Programs\Java.lnk" value="\Windows\Java.lnk" datatype="string" translation="install"/>
</characteristic>
</characteristic>
</wap-provisioningdoc>
[Touch GSM ROM Development] dsixda:
Oh yeah, that's right. Duh :) I'm not going to remove that then.
[Touch GSM ROM Development] vadyarik:
Autoshortcut just delete? Do I have something else to run .provxml?

And without CheckAutorun animation at boot will work?
[Touch GSM ROM Development] dsixda:
I thought animation at boot is run by HTCAnimation.dll and the appropriate registry keys.
[Touch GSM ROM Development] dsixda:
Nope... removed autorun.exe and checkautorun.exe and Runcc.exe still doesn't work.
[Touch GSM ROM Development] Ameet:
I removed Autoshortcut, Autorun and left CheckAutoRun but it didnt call the RunCC at boot :(

Will try calling the RunCC instead of CheckAutoRun

EDIT: It works in this scenario and its really speedy :)

1. Need CheckAutoRun.exe

2. Need AutoRun.exe

3. Delete this from rgu:

[HKEY_LOCAL_MACHINE\Comm]
"AutoRun"="\\Windows\\autorun.exe"
"AutoRunCFG"="\\Windows\\config.txt"

4. Call RunCC.exe at startup instead of CheckAutoRun.exe (in my ROM I have a script which runs this file at startup)
[Touch GSM ROM Development] Noonski:
Why not?

My Diamonds running just fine with no practicly no provxml at all:p.
[Touch GSM ROM Development] dsixda:
Ha, I was actually thinking of you when i said that ;) But you have mortscripts creating your shortcuts.. i just can't be bothered with the extra work ;)
[Touch GSM ROM Development] dsixda:
Nice work!

So how does RunCC get prevented from running a second time afterwards? For example, CheckAutoRun has the autorun Flag set to 1 after the first run.
[Touch GSM ROM Development] Ameet:
Well, somehow this RunCC calls CheckAutoRun and thats how the latter sets the flag back to 1 to prevent it from running the second time onwards

I cant decode stuff, so cant know for sure through hex editing or reverse engineering this RunCC.exe why and how it calls for CheckAutoRun. I can be sure of that since I tried once with the AutoRun & CheckAutoRun removed from the ROM and it threw up an error while running RunCC
[Touch GSM ROM Development] vadyarik:
I checked. AutoShortcut can also delete everything works as before.:)
[Touch GSM ROM Development] Ameet:
AutoShortcut has nothing to do with this :) It only creates shortcuts based on the provxml files entries :)

If you meant AutoRun, then good, coz I didnt test that :D
[Touch GSM ROM Development] vadyarik:
I immediately deleted the AutoRun.
[Touch GSM ROM Development] GPRS:
CheckAutoRun is need.the run will check the reg to find wheather the checkautorun had runned.

but i can't find the diffrence of run*.dll in runcc.can anybody tell me?
[Touch GSM ROM Development] NeoS:
Wait, let me get this straight:

1. keep the checkautorun oem but edit it's rgu file and remove "AutoRun"="\\windows\\AutoRun.exe"

2. Cook your rom and flash

3. CCrun will now customize your rom, just like autorun would?

Is that correct? I can't seem to get it working. :s
[Touch GSM ROM Development] Ameet:
Deleting this Autorun.exe doesnt work (not atleast with me)
[Touch GSM ROM Development] trueg:
Deleted files from \Windows with provxml

I've been trying to see if it is possible to remove redundant files using a provxml. For example, all of the graphic files that JBed needs are copied to \Windows\appdb. A copy of the files are left behind in \Windows. I tried the following bit of code to remove the files, but it doesn't seem to work. Is this not possible?

File name - mxipupdate_autoupdate_100.provxml

<wap-provisioningdoc>
<characteristic type="FileOperation">
<characteristic type="%CE2%\_ack_2.png" translation="install">
<characteristic type="Delete">
<parm name="ForceDelete"/>
</characteristic>
</characteristic>
</characteristic>
</wap-provisioningdoc>

If I can get this to work, then there would be a lot of files that could be removed from \Windows.

Thanks,

TrueG

note: I've found various instances of this being using by Microsoft in \SYS. Does this only work from \SYS and not \OEM?
[Touch GSM ROM Development] dsixda:
This is a very good idea. I wonder if only certain files, such as shortcuts, can only be removed.
[Touch GSM ROM Development] trueg:
I'm starting to think that if it was possible, it would have been done already. Things like pictures, music and ringtones are often copied to other folders, so you end up with extras in \Windows. If there was no way to remove them from \Windows and all you are doing it making extra copies, why bother? Why would Esmertec move JBed graphics to appdb if there are already copies in \Windows?

I got excited after noticing a few instances of Microsoft doing it in \SYS so I figured it had to work somehow.

example: \SYS\AUTOUPDATE\mxipupdate_autoupdate_100.provxml

Why would Microsoft have this here if it did nothing?

Update: Hmm, looks like every instance of this is to remove a *.lnk. It may be a special property of shortcuts that allows the system to delete it. What a shame. =(

I guess the benefit of moving files to a different folder is to speed up access to those files since the system doesn't need to access \Windows to get it, but at the cost of having duplicate files.
[Touch GSM ROM Development] trueg:
Unless someone comes back to say that you can in fact delete files during flash using provxmls, I had a couple of questions I hope someone can answer for me.

When Autoshortcut is used to copy files during flash, are those files flashed to ROM or copied to RAM? For example, with JBed all of the files are flashed to the ROM (\Windows). Then the graphics are copied to \Windows\appdb. Are the files in \Windows\appdb stored in ROM or RAM? Traditionally, ROM is faster to read from than RAM. I'm guessing the benefit of having these files in a separate folder in RAM allows the system to access them faster than having to access \Windows (files stored in their own folder in RAM vs stored with everything else in ROM aka \Windows).

Now, assuming the JBed graphics files in \Windows are never accessed (as an example), can they be compressed? For example can they be compressed before cooking (ex: _logo_8.png becomes _logo_8.pn_) and then uncompressed while copying to \Windows\appdb? This would allow for less ROM space to be used. Or perhaps stored as a cab in \Windows and extracted to \Windows\appdb during flash?

If the graphic files in \Windows never need to be read, I would rather have 1 35kb cab then 28 little pngs. In the example of HTC Home, I can tell HTCHome.dll to look in \Windows\HTCHome for graphics and have the 200+ graphics normally found in \Windows compressed as a cab.
[Touch GSM ROM Development] letama:
Only a guess here, not an expert at all, but I think it does copy files in flash, not ram. My guess is that the shell wants shortcuts in \windows\start to avoid browsing a 1000+ files directory to react quickly.

As all files in rom have to be in windows directory, we in fact ends up with duplicates in flash.

I've been playing with that idea, relocating files out of windows directory with cabs that I loaded with a script from SD with UC. I was able to remove a few but a lots of HTC apps are hard-coded with \windows\ path in executables and dlls. Not sure it helps so much, but I like the concept.
[Touch GSM ROM Development] trueg:
So far I have been able to clean up JBed and HTCHome. Any program that can load resources in a different folder can be cleaned up in this way.

For these two applications, the OEM folder contains the exe, dll and other files that would normally load into \Windows. As well there is a cab containing the graphics. During customization (autorun not UC), I extract the cab to the required folder (for example JBed \windows\appdb). In the case of HTCHome, instead of 203 resource files in \Windows, I have 1 cab. The resource files are extracted to \HTCHome.

I believe this could also be done for Manila2D and maybe even Manila3D. It's just an idea. =)
[Touch GSM ROM Development] letama:
I did it for Camera and DotNet runtime also, it' works fine. Just a few registry entries to fix.
[Touch GSM ROM Development] Demo[95]:
Trueg, if you're already using UC, why don't you install your ressources cab (from Memory card) as part of the UC process, instead of just uncompressing a cab present in \Windows folder?

BTW, for a version of my ROM i provide Album, AudioManager, CommManager EnlargeStartMenu, LargeTitleBar, TaskManager, WLANSettings, GoogleMaps, IContact, S2U2 and Manila2D which are installed during UC...
[Touch GSM ROM Development] trueg:
I don't use UC, but your right in that it would eliminate the extra cab in \Windows.
[Touch GSM ROM Development] vadyarik:
HTC Rhodium Menu Enhancement

Hi guys!

Who has a working HTC Rhodium Menu Enhancement(QVGA) for Elfin?

What conditions are necessary?:confused:
[Touch GSM ROM Development] Noonski:
I think i saw someone working on a Qvga version of that.

or you could go for FingerSuite.

RunCC Is called by a registry Init so this runs before the files in \Windows\StartUp.

So

Nope.

CheckAutorun Checks if the Autorun Registry flag is set to 0, if it is it will execute Autorun.exe.

It should then delete the CheckAutorun.exe from the startup folder.

So RunCC should run without checkautorun.

And at the end of RunCC it should remove it's registry init value (order 58)

Just Geussing trying out Runcc just now for the first time.

So you need..

REGEDIT4
[HKEY_LOCAL_MACHINE\init]
"Launch58"="RunCC.exe"

As for reducing Files i use Zip files with strong compression that get unzipped through mortscript. It's cleaner then using cabs,

I tried everything, even thought i knew it wasn't possible to remove files from ROM ;)
[Touch GSM ROM Development] dsixda:
Noonski, I like that Microsoft article you linked in your signature..... So true!
[Touch GSM ROM Development] Noonski:
I don't know how I bumped into that article, But it's so cool MS actually took the time to do some Flaming.
[Touch GSM ROM Development] dsixda:
Good for them, I hate being used by lazy people or wasting time trying to guess what their problem is.
[Touch GSM ROM Development] Noonski:
Well I got a grip on RunCC now. (it does run faster then the old Autorun)

I'm still testing and playing around on how to still use SDAutorun with it.

If and when that works i'll try to write a little Tutorial/Explanation on the new

RunCC (might even call it RunUCmEX for mortExtended)

Hopefully it will be easy enough to finally convince everyone to include Mort into Cooked Roms.
[Touch GSM ROM Development] Noonski:
Here's the Sort of Cleaned out Package i use.

Also attached the draft for the Tute.

Still a little bit of, work in progress.
[Touch GSM ROM Development] Ameet:
Awesome for the first cut :D Though someone like me needs a bit of in depth reading to understand :)

I'll link up your tutorials in my tut thread so it can be refered easily by everyone :)
[Touch GSM ROM Development] Noonski:
Does it need to be even more in depth then what i've been writing in that other zip file?

(real question)

It's not finished yet, i needed to sleep.
[Touch GSM ROM Development] itje:
hmm, I cooked a rom with this, and I get to the part with running reset.mscr and my x1 just "hangs there"
[Touch GSM ROM Development] Ameet:
Well I just took a brief look at the pdf file. Could not download the other zip file. I'll take a closer look tonight :)
[Touch GSM ROM Development] fcukmayank:
can i take onyx or win6.5 rom as base rom
[Touch GSM ROM Development] madsurfer1:
I have Hypercore kitchen installed, And I would like to use the touch of HD rom to modified a few things, like remove some progs, put in a few new ones and update some.

Can someone instruct me how to do that, i've read all the things in the first post, and still dont know how to do this.

Thanks, and regards
[Touch GSM ROM Development] Noonski:
To both the last repliers.

If both the roms you are talking about are cooked, there's a big chance you won't get them extracted to recook.

The attachment is For Itje (and whoever wants to try RunCC with SDAutorun support)
[Touch GSM ROM Development] fcukmayank:
so do we have always take a cooked rom or dumped rom or cooking

den where do i get a win6.5rom
[Touch GSM ROM Development] itje:
thx noonski, im flashing my rom right now with this package

interesting :)
[Touch GSM ROM Development] fcukmayank:
can somebody help me on how can i use a cooked rom

or do i always have to use a dumped rom
[Touch GSM ROM Development] itje:
not working for me though, all runs well until its supposed to run customization..it dont..

hmm
[Touch GSM ROM Development] Noonski:
Using a cooked ROM is an impossible place to start.

Unless the Cook made it so it is extractable.

When using the old Hypercore kitchen you will get a lot of missing files erros.

Or it might not even extract at all.

To cook WM6.5 your going to need a newer kitchen.

Now it might look like everyone is holding on to their secrets, but if you ask a cook of a rom you like. There is a change he might provide you with some of the packages he's using for that rom.

But you always have to start from a Stock Shipped rom.
[Touch GSM ROM Development] Noonski:
Which Custization do you mean? the RunCC or SDautorun?

I didn't expext the Experia to react so differently oposed to the Touch Pro with this. Because i know it should work but i can't figure out what is interfering. Can you maybe upload yout non Package OEM folders?

So i can check the provxml files in there?

I'm going to rewrite the instructions maybe it will help.
[Touch GSM ROM Development] fcukmayank:
do u mean to say that i should start from the original rom i.e 3.10

change the xip/sys to the latest and add my packages and then flash it

is this correct???
[Touch GSM ROM Development] Noonski:
Yes.

Indeed that is the true way of the warrior.

Gluing back another cooks ROM is a whole other class.

Itje i made a thread for the whole RunCC, Autorun and SDAutoRun thing

http://xdaforums.com/showthread.php?p=3611693
[Touch GSM ROM Development] fcukmayank:
THANKX NOONSKI

i will start from base then

can u plz guide me how to port the new xip

i have tried the repalcement method but due to this my elfin stuck at smart mobility screen
[Touch GSM ROM Development] madsurfer1:
whats better to start working on my new rom?

RUU_Signed.nbh(Including IPL,SPL,ExtendedRom,PrimarySplash,Radio,OS)?

or

RUU_Signed.nbh(Including ONLY OS) [62.9 MB]?

Regards
[Touch GSM ROM Development] Noonski:
OS Only should be sufficient IPL,SPL, Ext rom are not needed.

If you Click through to Ameet's public profile then statistics and Threads started by Ameet you will find some usefull guides on XIP porting.
[Touch GSM ROM Development] Xtriny:
Hi Noon,

no, I didnt flash uspl in this ROM (I did CID unlock a few weeks ago)

In missing Folder I had three folders - I put them to its place, as provided in PKGTool (but it was only when I used another custom ROM. In original ROM nothing missing)

I tried to use RUU_Signed file with another RomUpdateUtility (from working ROM) but still the same

One more thing - flash process of this rebuilded ROM is much slower, than other ROMs, but it goes to 100%

P.S. In PKG tool it shows this:

[Missing Manifests]

d92a4f0a-378a-4482-8fd3-bd127a05e4de.dsm

723fb954-d931-4348-b672-82a188e587b5.dsm

4e71f192-a1e0-da69-6fa4-eef7baef76bd.dsm

I found this three files in XIP directory. Do I have to do anything whit it?
[Touch GSM ROM Development] Swiftblade:
Hi Xtriny.. You seems to be doing everything right then the most likely explantion for this is that you have a missing file "wince.nls" inside the WinCENLS_WWE folder under SYS. Go check Build-->SYS-->WinCENLS_WWE and see whether you have the "wince.nls file. Without this file the Windows CE can't start...
[Touch GSM ROM Development] Xtriny:
You're right man :-) I cant find it anywhere. So what to do?
[Touch GSM ROM Development] Noonski:
Here it is attached.
[Touch GSM ROM Development] Xtriny:
Thanks Noon, but still the same. BTW, in your attached folder, I found only .dsm file, option.xml file, but no wince.nls file....