yashsingh1/xdaforums huggingface dataset:
[Windows Mobile] hilaireg:
Extracting the Base XIP.BIN Contents

At this point, we have extracted the xip.bin from the new (donor) device os.nb.payload file and copied it to the XIP Porting Kitchen.

We must now extract the xip.bin from the reduced os.nb.payload for the current (base) kitchen.

Tools Required

The following tools are required for the xip.bin file extraction activities.

XIPPorterEx

Procedure

The following procedure will extract the contents of the xip.bin from the current (base) kitchen os.nb.payload file.

Copy the os.nb.payload file from the C:\XDA\BASE_NBH_Kitchen\Tools\ReducePayload\ folder to the C:\XDA\BASE_NBH_Kitchen\Tools\XIPPorterEx\MyTools\os_nb.payload\ folder.

Navigate to the C:\XDA\BASE_NBH_Kitchen\Tools\XIPPorterEx\ folder.

Launch XIPPORTEREX.EXE.

Click the (Extract From .Payload) button.

At the XIP.BIN Successful Extraction From OS.NB.PAYLOAD message, click OK.

At the XIP.BIN Successful Written Into: "\xip.bin_old" Folder message, click OK.

Exit XIPPORTEREX.EXE.

Copy the extracted xip.bin file from the C:\XDA\DONOR_NBH_Kitchen\Tools\XIPPorterEx\MyTools\xip.bin_old\ folder to the C:\XDA\My_XIP_kitchen\MyTools\xip.bin_new\ folder.

References

Kernel Overview

http://msdn.microsoft.com/en-us/library/aa909237.aspx
[Windows Mobile] hilaireg:
Extracting the Donor MSXIPKernel

The Execute-In-Place (XIP) region is comprised of two significant regions – the MSXIPKernel, and the OEMXIPKernel. The OEMXIPKernel typically contains system drivers that are specific to your device. On very rare occasions, these drivers can be changed for newer ones.

The MSXIPKernel however, usually contains drivers that are specific to the version of Windows Mobile that you are using – in our case, Windows Mobile 6.1. There are many different methods for porting the MSXIPKernel drivers; each method may yield different build numbers. For example, some chefs use the 723*.DSM for the build number, others use the COREDLL.DLL module to obtain the latest build numbers.

For the purpose of this guide however, we will leave the OEMXIPKernel drivers as-is and use a simpler method of porting the MSXIPKernel drivers from a new (donor) device for use in your kitchen – and not concern ourselves with the build number.

Once the MSXIPKernel is extracted from the new (donor) device xip.bin, the OEMXIPKernel will be extracted from the current (base) kitchen. Both contents will be merged into a new xip.bin file. Additionally, the certificate store verification will have been disabled.

Tools Required

The following tools are required for the new (donor) device MSXIPKernel extraction activities.

XIPPorterEx

Procedure

The following procedure will extract the contents of the MSXIPKernel from the xip.bin of the new (donor) device, the OEMXIPKernel from the current (base) kitchen, and merge them into a new xip_out.bin file.

Navigate to the C:\XDA\My_XIP_Kitchen\ folder.

Launch XIPPORTEREX.EXE.

Clear the following check boxes:

Execute PP Patcher

Delete CACHEFILT.DLL

Delete MENCFILT.DLL

Delete ENCFILT.DLL

Change PP To MB

Don't Copy Xip Dsm

DEBUG Save Temp .BIN Files

Select the following check boxes:

Execute Cert Patcher

Port Only MSXipkernel

Create OEM Package From Unused Xip Modules/Files

Click the PORT IT! button.

At the Cert Patcher: Successfully Nocert Patched! message, click OK.

At the ALL DONE! Now Write New XIP.BIN Into Payload message, click OK.

Exit XIPPORTEREX.EXE.

References

Kernel Overview

http://msdn.microsoft.com/en-us/library/aa909237.aspx
[Windows Mobile] hilaireg:
Validating the XIP_OUT.BIN File

At this stage, we have a new xip.bin – currently named xip_out.bin. To ensure that the porting process occurred correctly, we will perform a quick validation of the xip_out.bin file.

If all is well, we will proceed to inject this new xip_out.bin file into our current (base) kitchen os.nb.payload file. In cases where the validation reveals problems, you will need to perform advanced XIP porting procedures – which are beyond the scope of this guide.

Tools Required

The following tools are required for the xip_out.bin validation activities.

XIPPort

Text Editor

Procedure

The following procedure will extract the contents of the newly formed xip_out.bin for validation purposes.

Copy the xip_out.bin file from the C:\XDA\My_XIP_kitchen\MyTools\XIP_new_ported\ folder to the C:\XDA\My_XIP_kitchen\MyTools\ folder.

Rename C:\XDA\My_XIP_kitchen\MyTools\xip_out.bin to C:\XDA\My_XIP_kitchen\MyTools\xip.bin.

Navigate to the C:\XDA\My_XIP_Kitchen\MyTools\ folder.

Launch XIPPORT.EXE.

Click the Dump XIP.BIN button.

Click the Write Maps button.

Exit XIPPORT.EXE.

Launch a text editor.

Select File, Open.

Navigate to the C:\XDA\My_XIP_Kitchen\MyTools\OUT\ folder.

Select the MAP.TXT file.

Compare the beginning (top) portion of the file to against the following tables.

References

[TUT] Manual Full XIP Porting (& MANY MORE TUTORIALS)

http://xdaforums.com/showthread.php?t=438676
[Windows Mobile] hilaireg:
Table 1.1: Validating the XIP_OUT.BIN File

The example below is of a favourable output, no overlaps or gaps.

00000000 - 01f801fc L01f801fc NUL

01f801fc - 01f801fc L00000000 Start: first DLL address
01f801fc - 01fc8000 L00047e04 NUL
01fc8000 - 01fca000 L00002000 initialized data of region_1 wce_rex.DLL
01fca000 - 01fcb000 L00001000 initialized data of region_1 smem.dll
01fcb000 - 01fcc000 L00001000 initialized data of region_1 MMMAP.dll
01fcc000 - 01fcd000 L00001000 initialized data of region_1 GxDMA.dll
01fcd000 - 01fd4000 L00007000 initialized data of region_1 FLASHDRV.DLL
01fd4000 - 01fd5000 L00001000 initialized data of region_3 FLASHDRV.DLL
01fd5000 - 01fed000 L00018000 initialized data of region_2 DDI.dll
01fed000 - 01fee000 L00001000 initialized data of region_1 ceddk.dll
01fee000 - 01fef000 L00001000 initialized data of region_1 cecompr.dll
01fef000 - 01ff0000 L00001000 initialized data of region_1 regenum.dll
01ff0000 - 01ff1000 L00001000 initialized data of region_1 pm.dll
01ff1000 - 01ff2000 L00001000 initialized data of region_1 mspart.dll
01ff2000 - 01ff3000 L00001000 initialized data of region_1 mencfilt.dll
01ff3000 - 01ff4000 L00001000 initialized data of region_1 imgfs.dll
01ff4000 - 01ff5000 L00001000 initialized data of region_1 fsreplxfilt.dll
01ff5000 - 01ff6000 L00001000 initialized data of region_1 fsdmgr.dll
01ff6000 - 01ff7000 L00001000 initialized data of region_1 fatutil.dll
01ff7000 - 01ff8000 L00001000 initialized data of region_1 fatfsd.dll
01ff8000 - 01ff9000 L00001000 initialized data of region_1 diskcache.dll
01ff9000 - 01ffa000 L00001000 initialized data of region_1 devmgr.dll
01ffa000 - 01ffc000 L00002000 initialized data of region_1 crypt32.dll
01ffc000 - 01ffd000 L00001000 initialized data of region_1 coredll.dll
01ffd000 - 01ffe000 L00001000 initialized data of region_1 certmod.dll
01ffe000 - 01fff000 L00001000 initialized data of region_1 cachefilt.dll
01fff000 - 02000000 L00001000 initialized data of region_1 busenum.dll
02000000 - 02000000 L00000000 End: last DLL address

[B]...[/B]
[Windows Mobile] hilaireg:
Table 1.2: Validating the XIP_OUT.BIN File

The example below indicates possible problems with the imageinfo.bin or imageinfo.txt files found in the C:\XDA\My_XIP_Kitchen\MyTools\SYS\.VM\ and/or C:\XDA\My_XIP_Kitchen\MyTools\SYS\.ROM\ folders of the XIP Porting Kitchen.

00000000 - 01f801fc L01f801fc NUL

01f801fc - 01f801fc L00000000 Start: first DLL address
01f801fc - 01fc8000 L00047e04 NUL
02000000 - 02000000 L00000000 End: last DLL address

[B]...[/B]

The following procedure may resolve the issue.

Remove the following files

C:\XDA\My_XIP_Kitchen\MyTools\xip.bin

C:\XDA\My_XIP_Kitchen\MyTools\XIP_new_ported\xip_out.bin

Remove the contents in the following folders – do not remove the folder:

C:\XDA\My_XIP_Kitchen\MyTools\OEMXIP_Package\*.*

C:\XDA\My_XIP_Kitchen\MyTools\Dump\*.*

C:\XDA\My_XIP_Kitchen\MyTools\OUT\*.*

C:\XDA\My_XIP_Kitchen\MyTools\SYS\Dump\*.*

Copy the contents of C:\XDA\My_XIP_Kitchen\Templates\SYS\ folder (sub-folder and files) to the C:\XDA\My_XIP_Kitchen\MyTools\ folder.

Repeat the donor MSXIPKernel extraction and validation procedures.

If the problem presists, you will need to perform advanced XIP porting procedures – which are beyond the scope of this guide.

References

[TUT] Manual Full XIP Porting (& MANY MORE TUTORIALS)

http://xdaforums.com/showthread.php?t=438676
[Windows Mobile] hilaireg:
Table 1.3: Validating the XIP_OUT.BIN File

The example below indicates an overlap problem; you will need to perform advanced XIP porting procedures – which are beyond the scope of this guide.

00000000 - 01f801fc L01f801fc NUL

01f801fc - 01f801fc L00000000 Start: first DLL address
01f801fc - 01fc8000 L00047e04 NUL
01fc8000 - 01fca000 L00002000 initialized data of region_1 wce_rex.DLL
01fca000 - 01fcb000 L00001000 initialized data of region_1 smem.dll
01fcb000 - 01fcc000 L00001000 initialized data of region_1 MMMAP.dll

[B]...[/B]

02000000 - 02000000 L00000000 End: last DLL address

02000000 - 03dbe000 L01dbe000 NUL
03dbe000 - 03dc7000 L00009000 Virtual base address of wce_rex.DLL
[COLOR="Blue"]03dc7000 - 03dce000 L00007000 Virtual base address of smem.dll[/COLOR]
[COLOR="Red"]03dc7000 - 03dce000 L00001000 !!!!!!!!!!!!!!!!!![/COLOR]
03dce000 - 03dd3000 L00005000 Virtual base address of MMMAP.dll

[B]...[/B]

References

[TUT] Manual Full XIP Porting (& MANY MORE TUTORIALS)

http://xdaforums.com/showthread.php?t=438676
[Windows Mobile] hilaireg:
Table 1.4: Validating the XIP_OUT.BIN File

The example below indicates a gap problem; you will need to perform advanced XIP porting procedures – which are beyond the scope of this guide.

00000000 - 01f801fc L01f801fc NUL

01f801fc - 01f801fc L00000000 Start: first DLL address
01f801fc - 01fc8000 L00047e04 NUL
01fc8000 - 01fca000 L00002000 initialized data of region_1 wce_rex.DLL
01fca000 - 01fcb000 L00001000 initialized data of region_1 smem.dll
01fcb000 - 01fcc000 L00001000 initialized data of region_1 MMMAP.dll

[B]...[/B]

02000000 - 02000000 L00000000 End: last DLL address

02000000 - 03dbe000 L01dbe000 NUL
03dbe000 - 03dc7000 L00009000 Virtual base address of wce_rex.DLL
03dc7000 - [U][COLOR="Blue"]03dce000[/COLOR][/U] L00007000 Virtual base address of smem.dll
[U][COLOR="blue"]03dcf000[/COLOR][/U] - 03dd3100 L00005000 Virtual base address of MMMAP.dll

[B]...[/B]

References

[TUT] Manual Full XIP Porting (& MANY MORE TUTORIALS)

http://xdaforums.com/showthread.php?t=438676
[Windows Mobile] hilaireg:
Preparing the New OS.NB.PAYLOAD File

As we have already disabled Certificate checking, we will not select Execute Cert Patcher; additionally, we will not apply the Execute PP Patcher and Change PP To MB options. As the Execute-In-Place (XIP) region for the Raphael is sufficient in size, we do not need to remove the cachefilt.dll, mencfilt.dll, and encfilt.dll drivers.

Tools Required

The following tools are required to perform the os.nb.payload file update activities.

XIPPorterEx

Procedure

The following procedure will create a new os.nb.payload file which will be used when cooking our ROM.

Navigate to the C:\XDA\MY_XIP_KITCHEN\ folder.

Launch XIPPORTEREX.EXE.

Clear the following check boxes:

Execute Cert Patcher

Execute PP Patcher

Port Only MSXipkernel

Delete CACHEFILT.DLL

Delete MENCFILT.DLL

Delete ENCFILT.DLL

Change PP To MB

Create OEM Package From Unused Xip Modules/Files

Don't Copy Xip Dsm

DEBUG Save Temp .BIN Files

Click the Find Start XIP Offset button; the offset value should indicate: 00320000.

At this stage, the os.nb.payload file has not been reduced; you can select one of the following procedures:

Reducing the Update Loader (ULDR) Partition and Updating the OS.NB.PAYLOAD File.

Updating the OS.NB.PAYLOAD File with No Update Loader (ULDR) Reduction.
[Windows Mobile] hilaireg:
Reducing the Update Loader (ULDR) Partition and Updating the OS.NB.PAYLOAD File

The boot loader can accommodate multiple execute-in-place (XIP) regions where individual modules can be updated after the initial operating system image file has been written to the device – the ULDR is an example of this use. The Update Loader (ULDR) provides Flash-Over-The-Air (FOTA) capabilities permitting your carrier to issue changes such as Hotfixes over the cellular network – generally, most carriers avoid this practice.

We will use the ROM Tools feature of the XIPPorterEx tool to adjust the ULDR and remove the debugging system library files. We will commit our changes which will replace the current (base) kitchen xip.bin contents with the new xip_out.bin contents resulting in a final os.nb.payload file – which we will use when cooking our kitchen.

Procedure

Click the ROM Tools button.

Clear the following check boxes:

Conservative Mode

Write NEW Xip Size Into MBR

Select the DEBUG Delete Temp .BIN Files check box.

Click the Give From Your XIP_OUT.BIN button.

Click the Write button.

At the os.nb.payload Was Successfully Reduced... message, click OK.

Click the Done button.

Move the os.nb.payload from C:\XDA\MY_XIP_KITCHEN\XIPPorterEx\MyTools\os.nb.payload_Reduced\ folder to the C:\XDA\MY_XIP_KITCHEN\XIPPorterEx\MyTools\os_nb.payload\ folder –overwriting the older version of the file.

Click the Find Start XIP Offset button; the offset value should indicate: 00020000.

Click the Write It button.

At the NEW os.nb.payload Was Updated Successfully... message, click OK.

Click the ROM Tools button.

Clear the following check boxes:

Conservative Mode

Write NEW Xip Size Into MBR

Select the DEBUG Delete Temp .BIN Files check box.

Click the Write button.

At the os.nb.payload Was Successfully Reduced... message, click OK.

Click the Done button.

Exit XIPPORTEREX.EXE.

Copy the os.nb.payload file from the C:\XDA\MY_XIP_KITCHEN\MyTools\ os.nb.payload_Reduced\ folder to your kitchen .\ROM\ folder.

Note

New (donor) devices are being released with updated resource strings in the NK.EXE module. As a result, you must not attempt to change the Date and/or ROM Version – doing so will corrupt your xip.bin file.
[Windows Mobile] hilaireg:
Updating the OS.NB.PAYLOAD File with No Update Loader (ULDR) Reduction

We will commit our changes which will replace the current (base) kitchen xip.bin contents with the new xip_out,bin contents resulting in a final os.nb.payload file – which we will use when cooking our kitchen.

Procedure

Click the Write button.

At the os.nb.payload Was Successfully Reduced... message, click OK.

Click the Done button.

Exit XIPPORTEREX.EXE.

Copy the os.nb.payload file from the C:\XDA\MY_XIP_KITCHEN\MyTools\os.nb.payload\ folder to your kitchen .\ROM\ folder.

Note

New (donor) devices are being released with updated resource strings in the NK.EXE module. As a result, you must not attempt to change the Date and/or ROM Version – doing so will corrupt your xip.bin file.
[Windows Mobile] hilaireg:
Unlocking and Resizing the Paging Pool

The Paging Pool serves as a limit on the amount of memory that can be consumed by pageable data. It includes an algorithm for choosing the order in which to remove pageable data from memory. Pool behaviour is typically determined by the OEM – Microsoft sets a default value for the paging pool, but the OEM can change that value. Applications do not have the ability to set the behaviour for their own executables or memory-mapped files.

For the purposes of this guide, we are going to apply a change to the os.nb.payload file which will permit us to change the Paging Pool size (initially set to 6MB) to other sizes using the PagePool Changer tool.

Tools Required

The following tools are required for the Paging Pool unlock activities.

Hexadecimal Editor

Procedure

The following procedure will change the os.nb.payload file to permit adjustments to the Paging Pool size via the PagePool Changer tool.

Navigate to the C:\XDA\MY_XIP_KITCHEN\Editors\xvi32\ folder.

Launch XVI32.EXE.

Select File, Open.

Navigate to your kitchen .\ROM\ folder.

Select All File (*.*) from the Files Of Type list.

Select the os.nb.payload file.

Select Search, Find.

In the Hex String box, type:

03 15 A0 03 02 15 A0 13

Click OK.

Change the following 4 bytes after the 03 15 A0 03 02 15 A0 13 string;

FROM: 00 10 82 E5

TO: 00 00 A0 E1

Select File, Save.

Select File, Exit.

Tip

Make a backup copy of the os.nb.payload file before editing; delete the backup file when done.

References

Paging Pool

http://msdn.microsoft.com/en-us/library/aa915364.aspx

Paging and the Windows CE Paging Pool

http://blogs.msdn.com/ce_base/archive/2008/01/19/Paging-and-the-Windows-CE-Paging-Pool.aspx

Change PagePool Through Hex Editing (For Diamond & Raphael)

http://xdaforums.com/showpost.php?p=2903704&postcount=5
[Windows Mobile] hilaireg:
Disabling Certificate Checking

During the startup process of your device, the operating system verifies that each system file against an internal certificate store to ensure that each file is signed with a trusted certificate; if the system file is not signed, the file is ignored.

To allow execution of non-signed system files, we need to disable the internal certificate store verification. Once disabled, the operating system will trust all code installed regardless of its signature. This provides more control over the code that gets installed on the device – you no longer need to load and manually sign additional certificates such as those from the sdkcerts.cab into the device root certificate store.

If you accidentally forgot to disable the certificate store verification during the XIP porting process, you can use the following procedure to apply a change to the os.nb.payload file.

Tools Required

The following tools are required to disable the internal certificate store verification.

AutoPatcher01

Procedure

The following procedure will disable the internal certificate store verification.

Navigate to the C:\XDA\MY_XIP_KITCHEN\Editors\AutoPatcher\ folder.

Launch AUTOPATCHER01.EXE.

Click the Cert Patch button.

Select All File (*.*) from the Files Of Type list.

Navigate to your kitchen .\ROM\ folder.

Select the os.nb.payload binary file.

At the Successfully Patched... message, click OK.

Exit AUTOPATCHER01.EXE.

Tip

Make a backup copy of the os.nb.payload file before editing; delete the backup file when done.

References

[RES] RILPHONE.DLL And "How To" With A Radio

http://xdaforums.com/showthread.php?t=481026
[Windows Mobile] hilaireg:
13/02/2010: Tutorial Statistics

Views: 1,390

Guide Downloads: 45

Kitchen Downloads: 72
[Windows Mobile] krogoth:
Well, great article! No offence, but why do you need 19 reserved posts? Even largest projects have less than half of that :P
[Windows Mobile] aruppenthal:
My Disclaimer :p

I take no credit for the kitchen. I just edited and recompiled several tools provided by many users.

Calkulin at PPCgeeks laid the base idea for the XIP kitchen. Ervius Bepe and several others did the real work creating the tools. I consider my role very minute at best. ;) Hilaireg took the time to write everything down. I think everyone should be appreciative of the extreme amount of time put into this.

Alot of the information was built upon all of Ameets hard work as well as the many contributors to the Manual xip porting thread made much of this possible.

I urge everyone that intends to cook to take the time to learn how to port a xip. There is much to be gained by knowing how things work behind all the fancy tools we have these days.
[Windows Mobile Development and Hacking General] smuppy:
I desperately need to delay the startup of services.exe from HKLM\init. I have fooled around with some values (changed value of Launch to 110 and Depend110 to 14 00) but the then device didnt start at all.

Does anyone have a working solution to this or an idea on how to approach this issue?

I need this because my application autostarts as a service and the current ROM (custom rom from MichyPrima for Athena 7500) I'm using is simply... too fast, the Microdrive isnt initialized when my application starts and since it reads a license from the microdrive, the application stops with an error.

All ideas are appreciated.

//Anders, .se
[Touch Pro, Fuze ROM Development] guym:
Nice rom. No bug found for the moment, but i don't managed to activate facebook's manila integration.

Have you planed a version with lasted manila 2 (V1E) ?
[Touch Pro, Fuze ROM Development] Qui-Gon Ginn:
If i could find a link for it :) cause i don't find it :(

Oups i find it now, i will see it :)
[Touch Pro, Fuze ROM Development] Qui-Gon Ginn:
I just update for V5 with the good link :)
[Touch Pro, Fuze ROM Development] guym:
Nice, i'll try it as soon as possible. Thanks.

[edit] Download links seems brockens...
[Touch Pro, Fuze ROM Development] Qui-Gon Ginn:
Wich one? The 3 links seems ok :)
[Touch Pro, Fuze ROM Development] guym:
I try later and it was working. Severs were down.
[Touch Pro, Fuze ROM Development] Qui-Gon Ginn:
Ok , give me your feedback when you flashed :)
[Touch Pro, Fuze ROM Development] hoyeah:
thanks for this, I'll try it later and I'll let you know about bugs or issues.
[Touch Pro, Fuze ROM Development] Noelch:
nice rom

i try after my travel
[Touch Pro, Fuze ROM Development] Qui-Gon Ginn:
Ok , i will wait for your try :)
[Touch Pro, Fuze ROM Development] guym:
After 24 hours testing non particular bug found. Just it was dificult to activate "all people" tab with the facebook integration in manila. Need to make change in registry and some missing tab descriptions in 26948339_manila file.
[Touch Pro, Fuze ROM Development] aaznak:
naruto_v5

Hello,

I download to the weekend naruto_v5 tf3d and test v2

Good works :)
[Touch Pro, Fuze ROM Development] paulovpinto:
Nice work!

Can this rom work in the diamond device?

Were can i find something like yours in PT-pt lang, for de diamond platform.

Cheers
[Touch Pro, Fuze ROM Development] Qui-Gon Ginn:
Alkyd , the TF3D 2.5 will come when the port will be full, for now i work to TF3D 2.1 that correct some bugs of TF3D 2.0

paulovpinto , this is only for Touch Pro , each rom is only for one device. You can see in the Diamond Section here to have rom for diamond. I hope you can find something you like

guym : With the new rom i make , there won't be some problems with Facebook integretion :)
[Touch Pro, Fuze ROM Development] guym:
I have noticed 2 problems

- On orange version, the vocal messagerie number is wrong (not 888)

- Dot net Compact Framework 3.7 have compatibility problems with some application require 3.5 and 3.5 wont install on 3.7.
[Touch Pro, Fuze ROM Development] Qui-Gon Ginn:
Ok , thx. Can you tell me witch application that doesn't work please :)
[Touch Pro, Fuze ROM Development] guym:
Strange the problem with the 3.7 .net framwork desapear on FLIX now it launch. but i had the problem on the V4 rom too. According to .Net configuration, the only framwork installed is 3.7, 3.5 installation faild.

I don't rember for the moment the other applications names. i'll do test and make a list
[Touch Pro, Fuze ROM Development] Qui-Gon Ginn:
Try with this cab :

http://www.megaupload.com/?d=EQBTEBRA

it's 3.5 version
[Touch Pro, Fuze ROM Development] DrQ-FR:
Hi Qui-Gon Ginn,

It is so good to see French version :) That's a good work.

I just have two questions :

Does the last version (Naruto V5) contain the Tachi PhoneCanvas in VGA mode as your screenshots ?

Does the SFR ROM is set up with SL2SFR connection ?
[Touch Pro, Fuze ROM Development] Qui-Gon Ginn:
Hi ,

for the screens , it's a beta version, i try to make it better , it will be in the next release if i or someone else port it good ;)

I don't have SFR so i don't know but i don't have no bad feedback with SFR :D
[Touch Pro, Fuze ROM Development] DrQ-FR:
Thanks and "vraiment bon boulot" :D
[Touch Pro, Fuze ROM Development] 2004yang:
je suis en train de télécharger ton ROM

Merci de ton travail
[Touch Pro, Fuze ROM Development] Qui-Gon Ginn:
Merci / Thx all :)
[Touch Pro, Fuze ROM Development] Qui-Gon Ginn:
Hi all , if all will be good in tests tonight , the new version will be finish in 1 week :)

Many changes