yashsingh1/xdaforums huggingface dataset:
[Touch CDMA Windows Mobile ROM Development] boggsie:
I am really looking forward to this and am in no way trying to hedge or backout, but logistics may prove to be a bit difficult.

I am on EDT - my two toddlers bed-down around 8:00 P.M. EDT, so I'm not generally available before that. I'm sorry if it seems like I want the world to rotate around me ... I just have obligations that eat up my early evenings. I get 5-minute intervals to check-in, but to actually participate in and document the session, I would like to be able to committ to a 30-minute un-interrupted session.

Also, presuming we can agree to a schedule:

how do we facilitate? (chat, iirc, etc?)

common tool set? (some can be difficult to get ones hands on)

Best regards,

-boggsie
[Touch CDMA Windows Mobile ROM Development] fayfay392:
Boggsie please contact me via MSN = fayfay1234@gmail.com
[Touch CDMA Windows Mobile ROM Development] vetvito:
One problem, what dont you guys understand?

Tons of Guides out there, but you all still ask for step by step instructions.

First what is your problem or step do you feel you are missing?

----------------------------------------------------------------------------------

XIP Porting steps

1. Get a full XIP

2. Dump XIP

3. Package XIP

4. If porting, bring over everything except OEM and make your changes

5. Depends on your tools, M'reloc all modules

6. Update all .txt files

7. Unpackage XIP

8. Reloc

9. Write Maps

10. Go into Out folder and Check your Map txts for "Over", and "!". If you have any of those check which module it is, and correct it. Repeat Steps 4-6 until all is good.

11. Build XIP-Out.bin

12. Fill slots, first slot is where the file is to be written to, second slot is where the XIP is located in the file. Most XIPs for our Devices are 00320000

13. Write XIP-out.bin to OS.nb.payload, or nk.fat, or whatever contains your XIP

Enjoy.
[Touch CDMA Windows Mobile ROM Development] fayfay392:
Ive done this and everytime i do it, it never boots, so im looking for someone to walk through it with me thats all.
[Touch CDMA Windows Mobile ROM Development] vetvito:
Whats the problem, narrow it down because that was a walk through?

Which step are you missing?

What goes wrong? Besides the obvious

How about this:

How are you getting your XIP?
[Touch CDMA Windows Mobile ROM Development] fayfay392:
Im getting it from the Diamond OS WWE 20273
[Touch CDMA Windows Mobile ROM Development] vetvito:
No, I mean what method and tools do you use to get Extract and dump the XIP?
[Touch CDMA Windows Mobile ROM Development] fayfay392:
nbhextract then nbdump and rommaster
[Touch CDMA Windows Mobile ROM Development] vetvito:
Rom Master will only work on some official Roms, you are having problems with Step 1.

To test this out, extract a vogue XIP, dont make any changes, and write it back. Then build a rom with it and see if it works.

----------------------------------------------------------------------------------

This is what you need to do for Step 1(This is also what I got from DCD):

use a hex editor

extract whatever.nbh
then
nbsplit -kaiser os.nb

this gives you os.nb.payload and os.nb.extra.
your xip is in os.nb.payload- open it in a hexeditor

run imgfsfromnb os.nb.payload imgfs.bin
note the start of imgfs address

jump to that address in your hexeditor and delete from there to the end of the file
now move back to the beginning of your remaining data in hexeditor

search for the start of xip part: FE0300EA
(if not a custom rom the address is probably 0x00320000)

when you find that start of xip, delete from there to beginning of file
the data you are now left with is your xip. save it as xip.bin

hope this helps...

by the way I'm charging 700% :D
[Touch CDMA Windows Mobile ROM Development] fayfay392:
thanks, ill use this later when dcd helps us. Apprieciate it.
[Touch CDMA Windows Mobile ROM Development] vetvito:
you will get the same information.

Nothing else required.
[Touch CDMA Windows Mobile ROM Development] fayfay392:
If so, so be it, atleast he will walk me through it every step because hes doing it at the same time i will be also and we will do it in real time not through posting.
[Touch CDMA Windows Mobile ROM Development] dcd1182:
vetvito, to be honest, i have yet to see an xip porting guide without some sort of error.

yours is correct, but doesnt spell out how to reloc, and most make the error during reloc, or only reloc coredll, etc

since 5:30pm CST will not work for boggsie... why dont we come up with a new time (with more notice) that works for everyone?

sat/sun would be best for me. or m-th after 530pm CST.
[Touch CDMA Windows Mobile ROM Development] vetvito:
Post here because others are lurking, trust me. Plus it save everyone the repeated PMs.

If you haven't noticed I'm trying to walk you through it.
[Touch CDMA Windows Mobile ROM Development] fayfay392:
SBR and I are ready now, and would love to do it now. I have a screenshot thing ill do and send them to boggsie. Please do it now.
[Touch CDMA Windows Mobile ROM Development] vetvito:
Correct, but if we post here it will save us all the repeated PM's.
[Touch CDMA Windows Mobile ROM Development] fayfay392:
I will make a detailed tutorial after, im screenshotting the whole thing. If you want you can join the irc vet.
[Touch CDMA Windows Mobile ROM Development] vetvito:
When where?
[Touch CDMA Windows Mobile ROM Development] {SBR}_L3GION:
if its ok with dcd
[Touch CDMA Windows Mobile ROM Development] fayfay392:
DCD is making an irc and as to when i hope today but its up to DCD
[Touch CDMA Windows Mobile ROM Development] fayfay392:
Vet if you want to help us with DCD if its ok with him its kool.
[Touch CDMA Windows Mobile ROM Development] {SBR}_L3GION:
we will both pay 15 to make up for boggsie if we can do it today we will still send him the screen shots but we really want to do this today.
[Touch CDMA Windows Mobile ROM Development] dcd1182:
i will post here...

you guys understand what vetvito told you earlier? how to properly extract xip.bin from os.nb.payload ?
[Touch CDMA Windows Mobile ROM Development] fayfay392:
kinda, not really, i would REALLY prefer to post this in real time on msn of irc PLEASE i hate posting back and forth i will transfer info after if thats a problem.
[Touch CDMA Windows Mobile ROM Development] dcd1182:
well go back and read his paste of what i told him on how to obtain xip.bin - i cant really explain it any better a 2nd time.

let me know when you get that far and we will go from there. you must be able to obtain xip.bin before we can really start anything.

edit: donations are cool too but im not really concerned with the $30. vetvito has helped you more than i have thus far so it wouldnt be right for me to claim it anyways. im just tyring to spread the knowledge.
[Touch CDMA Windows Mobile ROM Development] fayfay392:
Ok i can do that now, can you set up a irc room or msn or something?
[Touch CDMA Windows Mobile ROM Development] dcd1182:
after 2nd thought i do agree with vetvito, posting here is much more productive. plus after i thought 5:30 was off i started another project and im in and out right now.

but im checking this thread.
[Touch CDMA Windows Mobile ROM Development] fayfay392:
Well crap man.. idk what to say. why can i port over all the info you give us into a precise tutorial after. Real time helps me learn way better. And as for the $30 bucks i will be giving it to you if you can just help me get this working
[Touch CDMA Windows Mobile ROM Development] {SBR}_L3GION:
we have gotten the xip.bin just the values are gettin me.
[Touch CDMA Windows Mobile ROM Development] dcd1182:
what values?

after you obtained xip.bin, open xipport and press "dump xip.bin"

what is the filesize of your xip.bin ?
[Touch CDMA Windows Mobile ROM Development] fayfay392:
the original is around 3 the new is like 5mb, what tool kit should we be using?
[Touch CDMA Windows Mobile ROM Development] {SBR}_L3GION:
m'reloc is where im messing up
[Touch CDMA Windows Mobile ROM Development] dcd1182:
dude i dont even know what youre talking about. tool kit?

you should have:

hex workshop

xippport from post #85 of g'reloc thread

nbhextract

nbsplit

ruu_signed.nbh

mreloc
[Touch CDMA Windows Mobile ROM Development] fayfay392:
Ok i have all of that. and i have Hview2000 as my hex editor program. im extracting the xip now.
[Touch CDMA Windows Mobile ROM Development] dcd1182:
what vogue rom is your base? please give me exact filename and i will use the same here.
[Touch CDMA Windows Mobile ROM Development] fayfay392:
RUU_PPST_Vogue_SPRINT_WWE_3.03.651.4_2_Radio_3.42.30_AM_NV_2.04_Ship WARRANTY

and for the new xip im using Diamond_20273_WWE_OS
[Touch CDMA Windows Mobile ROM Development] dcd1182:
ok, then your vogue xip.bin should be 3,538,944 bytes when extracted
[Touch CDMA Windows Mobile ROM Development] fayfay392:
ok im working w the hex editor now.
[Touch CDMA Windows Mobile ROM Development] fayfay392:
ok i extracted the sprint xip and its 2,984,212 bytes ..... the hex editor is to difficult to understand.
[Touch CDMA Windows Mobile ROM Development] dcd1182:
i suspect you do not have the right values because your xip.bin extracted is too small in size.

use hex workshop instead.

were you able to find the start of imgfs (the place you want to remove from it <-> EOF)

the directions posted said you should use imgfsfromnb to obtain this address.

so basically you are finding out where your xip starts, and where it ends.

you have those values now? what are they? lets just focus on the vogue xip right now.
[Touch CDMA Windows Mobile ROM Development] fayfay392:
ImgFs partition starts at 0x00680000 and ends at 0x059c0000
[Touch CDMA Windows Mobile ROM Development] dcd1182:
ok but you dont care where imgfs ends.

0x00680000 is the start of imgfs. thus 0x00680000 is the end of your xip.

now, do you understand where xip starts at?
[Touch CDMA Windows Mobile ROM Development] fayfay392:
Yes i get that, how do i jump to 0x00680000 in hex workshop and delete from there down, im not familar with this program.
[Touch CDMA Windows Mobile ROM Development] dcd1182:
ctrl+g to go to an address.

holding shift on your keyboard selects everything between where your cursor is and where you click next.

use this method to select everything between *end of xip* and *end of file*

then, when that is what you have selected, delete it.
[Touch CDMA Windows Mobile ROM Development] fayfay392:
it wont let me type 0x.. is it just 00680000?
[Touch CDMA Windows Mobile ROM Development] dcd1182:
yes, make sure youre putting that in as a hex address.

no offense, but i think it would help both of us alot if you become familiar with hex, and using a hex editor, before attempting any of this. it really is required for working with xip.

especially when you start moving modules, its just not happenning if you dont understand hex. can you subtract A000 from F000 ?
[Touch CDMA Windows Mobile ROM Development] fayfay392:
ok, please dont give up on me, i have the xip.bin and its the same size as yours. Now onto to dumping it with xipport correct or should i get the xip from the 20273 build
[Touch CDMA Windows Mobile ROM Development] dcd1182:
well go ahead and get your diamond xip since now you know how to do that.

i do have to leave soon and we are not even started really so ... this wont get done tonight.

but you didnt answer my question, i do not mean to offend you at all, but can you add/subtract hex? i will not be able to explain it to you as well as wikipedia im sure or anywhere else you could read up on it first. im a bad teacher..
[Touch CDMA Windows Mobile ROM Development] fayfay392:
I will read up on it. When will you be back?

Edit: dumped Diamond XIP size is 4,718,592 bytes.
[Touch CDMA Windows Mobile ROM Development] dcd1182:
diamond should be bigger than vogue. i am not sure of the exact size but thats probably correct.
[Touch CDMA Windows Mobile ROM Development] fayfay392:
Ok, im going to dump both with xipport now and move the files over except the oem, is this correct.
[Touch CDMA Windows Mobile ROM Development] dcd1182:
um, yes sort of, but instead read up on hex now and we will continue later.

id rather you fully understand what is really going on (and spell it out in this thread)
[Touch CDMA Windows Mobile ROM Development] fayfay392:
ok, sounds good. when can we continue? after all is done im going to compile all this info and make a large detailed tut on it.
[Touch CDMA Windows Mobile ROM Development] vetvito:
I'm good, I dont want the money. That 700% was a joke.
[Touch CDMA Windows Mobile ROM Development] vetvito:
Dont worry about porting anything yet. Just focus on the Vogue XIP, and ensure that it is working.

After your hex learnings, try dumping and rebuilding with the same Vogue XIP.

Rome wasn't built in a day.
[Touch CDMA Windows Mobile ROM Development] a2k:
I tip my hat to all of you!

I tip my hat to all of you, KNOWLEDGE is POWER!

Next time, let's get a WebEx conference going :-)
[Touch CDMA Windows Mobile ROM Development] boggsie:
credit ameet for exposing me to this method

With all due respect, this is my idea of a what a guide would look like. Step by step, with commands and instructions - along with some narrative. I am more than happy to work with somebody to end up with the right set of steps, but as I alluded to in a prior post, there are a number of prerequisites ... which tools, for example.

At any rate, this may not be correct, but it is in a usable format - I didn't link to the tools, because I expect that this method and tools would be corrected as appropriate for the Vogue.

:)

In my case, I want to use the most current stuff from HTC as a base for my effort. Thus, I begin with 3.07 from the Telus.

RUU_Vogue_TELUS_WWE_3.07.661.1_Radio_3.41.00_Ship.exe (75,134,909 bytes)

Use WinRAR or WinZip to get the Vogue nbh file out of the RUU/WWE.

Input.nbh (101,879,088 bytes)

Starting with input.nbh

Goal is to break input.nbh into pieces that can be used.

nbhextract.exe input.nbh

The result is the following files:

00_SPL.nb
01_MainSplash.bmp
01_MainSplash.nb
02_SubSplash.bmp
02_SubSplash.nb
03_Unknown.nb
04_OS.nb

The XIP is in 04_OS.nb

nbsplit.exe –kaiser 04_OS.nb

The result is the following files:

04_OS.nb.extra
04_OS.nb.payload

The XIP is in 04_OS.nb.payload

You need to get the start address for the XIP

rename 04_OS.nb.payload to OS.nb.payload
imgfsfromnb OS.nb.payload imgfs.bin

Use the address from imgfsfromnb.exe for the next command:

RomMaster.exe -x -w 5 -s 0x00320000 -e 0x006c0000 04_OS.nb.payload -o xip.bin

xip.bin (3,801,088 bytes)

Break Down the XIP using 32k dumprom.exe

dumprom.exe xip.bin -5 -d xip

output is:

\romhdr.bin
\XIP\50b2a436-8d0f-e91d-2b05-d45affbe55b6.dsm
\XIP\723fb954-d931-4348-b672-82a188e587b5.dsm
\XIP\723fb954-d931-4348-b672-82a188e587b5.rgu
\XIP\bmui.nb0
\XIP\boot.hv
\XIP\boot.rgu
\XIP\boot_ms.rgu
\XIP\d92a4f0a-378a-4482-8fd3-bd127a05e4de.dsm
\XIP\mxip_lang.vol
\XIP\sysroots.p7b
\XIP\busenum.dll <DIR>
\XIP\cachefilt.dll <DIR>
\XIP\cecompr.dll <DIR>
\XIP\ceddk.dll <DIR>
\XIP\certmod.dll <DIR>
\XIP\coredll.dll <DIR>
\XIP\crypt32.dll <DIR>
\XIP\device.exe <DIR>
\XIP\devmgr.dll <DIR>
\XIP\diskcache.dll <DIR>
\XIP\fatfsd.dll <DIR>
\XIP\fatutil.dll <DIR>
\XIP\filesys.exe <DIR>
\XIP\FLASHDRV.DLL <DIR>
\XIP\fsdmgr.dll <DIR>
\XIP\fsreplxfilt.dll <DIR>
\XIP\hd.dll <DIR>
\XIP\htcfsfilter.DLL <DIR>
\XIP\imgfs.dll <DIR>
\XIP\initvmmap.exe <DIR>
\XIP\mencfilt.dll <DIR>
\XIP\mspart.dll <DIR>
\XIP\nk.exe <DIR>
\XIP\osaxst0.dll <DIR>
\XIP\pm.dll <DIR>
\XIP\regenum.dll <DIR>
\XIP\relfsd.dll <DIR>
\XIP\wce_rex.DLL <DIR>

So, how am I doing so far!?!?!

Best regards,

-boggsie
[Touch CDMA Windows Mobile ROM Development] vetvito:
^ Lose RomMaster and stick to this:
[Touch CDMA Windows Mobile ROM Development] vetvito:
RomMaster Gave you 2,984,244 bytes

Real XIP for 3.07 is 3,801,088 bytes
[Touch CDMA Windows Mobile ROM Development] boggsie:
Telus 3.07 RUU/WWE (75,134,909 bytes)

os.nb.payload (88,866,816 bytes)

Open with Hex Workshop

CTRL+G -

search offset HEX <0x00680000> from beginning of file

Hex Workshop finds the address

hold shift key

press end key

press delete

search offset HEX <0x00320000> from beginning of file

Hex Workshop finds the address

hold shift key

press home key

press delete

save file as xip.bin

xip.bin (3,538,944 bytes)

:(

BTW: doesn't using Hex Workshop to bite off the beginning and end of the file serve to reproduce what RomMaster does with the -s (start XIP) and -e (end XIP) command line arguments?

RomMaster.exe -x -w 5 -s 0x00320000 -e 0x00680000 04_OS.nb.payload -o xip.bin
[Touch CDMA Windows Mobile ROM Development] vetvito:
^I think you are deleting the wrong thing.

You want to delete the start of Imgfs address

Then

Delete everything before the start of the XIP address.

--------------------------------------------------------------

One can think that, but RomMaster doesn't always give full XIP. You can see the big difference. Its best to Hex because you will always have full XIP, and you can see exactly what you are doing.
[Touch CDMA Windows Mobile ROM Development] vetvito:
To be clearer;

Imgfs usually starts with:

F8 AC 2C 9D

XIP starts with:

FE 03 00 EA
[Touch CDMA Windows Mobile ROM Development] boggsie:
hrm ... there isn't much room for error, here - if we are doing the exact same thing.

I open Hex Workshop.

I open the file os.nb.payload

I key CTRL+G to open up the GoTo dialog

I click on the Hex radio button

I click on the Beginning of File radio button

I paste in the Hex Address 0x00680000

A that location, I hold the shift key and press the end key, which selects everything from that point to the end of the file.

I hit delete.

I key CTRL+G to open up the GoTo dialog

I click on the Hex radio button

I click on the Beginning of File radio button

I paste in the Hex Address 0x00320000

A that location, I hold the shift key and press the home key, which selects everything from that point to the beginning of the file.

I hit delete.

Essentially, everything between the two positions comprises the XIP.

How precisely do you delete the extraneous information from os.nb.payload to get xip.bin.

Best regards,

... & Thanks!

-boggsie
[Touch CDMA Windows Mobile ROM Development] vetvito:
Once you do this you will understand:

You want to delete the start of Imgfs address

Once you do this, you should be at the end of your XIP, and you should see nothing but FF for some lines.

Then

Delete everything before the start of the XIP address.

I don't use Hex Workshop,so I cant help there.
[Touch CDMA Windows Mobile ROM Development] boggsie:
xip.bin (3,801,088 bytes)

:)
[Touch CDMA Windows Mobile ROM Development] boggsie:
Ok, do you use a different hex editor, Jedi Mind tricks or a raw disk editor?

:D
[Touch CDMA Windows Mobile ROM Development] boggsie:
Very interesting, Vet ... I see what you mean.

You can go to address 0x00680000 and see a number of FF FF FF FF items that follow, up to the point that you get to F8 AC 2C 9D.

Leaving all of those FF FF FF FF items in the XIP.BIN increased the file size:

from

xip.bin (3,538,944 bytes)

to

xip.bin (3,801,088 bytes)

and more importantly, when I dumprom the two xip.bin files, I get differences in all of the imageinfo.bin and imageinfo.txt files for each of the resulting dlls. Some of the S0*** files are different as well.

Very interesting!

Time for sleep!
[Touch CDMA Windows Mobile ROM Development] boggsie:
credit to ... bepe - dcd - vetvito - dogguy - ameet

Now I have an xip folder of my target (19208 - 3.07.661.1) and I need a source input.nbh (20273)!

:)

@echo Ensure a clean work area ...

@rd /s /q .\extract
@rd /s /q .\temp
@rd /s /q .\xip

@echo Cleanup complete ...

@echo Processing Input.nbh ...
@echo ...
@echo Locating Starting .nbh ...
@ren *.nbh Input.nbh
@mkdir .\Temp
@cd .\Temp
@echo .... Done.

@echo Extracting os.nb from input.nbh ...
@mkdir extract
@cd extract

@..\..\tools\tools\NBHextract.exe ..\..\Input.nbh > nbhExtract.log

@REM Rename and Move OS.nb, then Clean up Junk.
@move *_OS.nb OS.nb
@move OS.nb ..
@cd ..
@rd /s /q extract

@echo .... Done.

@ECHO Split the OS.nb into os.nb.extra and os.nb.payload

@..\Tools\tools\NBSplit.exe -titan OS.nb > nbsplit.log

@if errorlevel 1 goto error

@ECHO Delete os.nb.extra
@del OS.nb.extra

@..\Tools\Tools\ImgfsFromNb.exe OS.nb.payload imgfs.bin

@echo using RomMaster to extract XIP.BIN from OS.nb.payload
@start /wait ..\Tools\Tools\RomMaster.exe -x -w 5 -s 0x00320000 -e 0x006c0000 OS.nb.payload -o xip.bin

@echo running dumprom_32 to dump the contents of xip.bin into an xip folder
@start /wait ..\Tools\tools\dumprom_32.exe xip.bin -5 -d xip
@cd ..
@attrib *.* -r -s -h -a /s
@MD XIP
@xcopy /e /q temp\xip\*.* XIP
@rd /s /q .\Temp
[Touch CDMA Windows Mobile ROM Development] boggsie:
nbhextract
nbsplit
imgfsfromnb (to get addresses for extracting xip.bin out of os.nb.payload

use addresses from imgfsfromnb in hex editor

-or-

use those addresses as command line arguements for RomMaster

(the only way to know if they are the correct addresses, is to view os.nb.payload in a hex editor - as long as you are there in a hex editor, best to edit manually)

result = xip.bin

dumprom_32
-or-
xipport

PkgToolsBuildos
-or-
xipport

a little bit more explicit, please ...

for later
[Touch CDMA Windows Mobile ROM Development] lennysh:
I have an XIP Kitchen I'm making that would work if BuildXIP supported the devices. Been told it's being worked on. So as soon as it's done, it'll be a 5 to 6 second process for everybody...
[Touch CDMA Windows Mobile ROM Development] vetvito:
if i had the source code for buildXip Im sure i could edit it for us, or make a new tool.i have a new kitchen as well

be back later
[Touch CDMA Windows Mobile ROM Development] boggsie:
M'Reloc.exe for each of the modules in the 3.07 / 19208 dumped XIP:

busenum.dll
03FFA000
01FFF000

cachefilt.dll
03FF0000
01FFE000

certmod.dll
03FE2000
01FFD000

coredll.dll
03F4C000
01FFC000

crypt32.dll
03EDA000
01FFA000

device.exe
00010000
00012000

devmgr.dll
03ECE000
01FF9000

diskcache.dll
03EC8000
01FF8000

fatfsd.dll
03EB5000
01FF7000

fatutil.dll
03EAC000
01FF6000

filesys.exe
00010000
0004B000

fsdmgr.dll
03E97000
01FF5000

fsreplxfilt.dll
03E8D000
01FF4000

hd.dll
80086000
802D9000

imgfs.dll
03E81000
01FF3000

initvmmap.exe
00010000
00012000

mencfilt.dll
03E71000
01FF2000

mspart.dll
03E69000
01FF1000

osaxst0.dll
8008A000
802DA000

pm.dll
03E5A000
01FF0000

regenum.dll
03E56000
01FEF000
[Touch CDMA Windows Mobile ROM Development] lennysh:
eh... I don't have it... Nor do I think I could get it. But, this kitchen is for XIP only... Sys is in a separate kitchen... In case you got confused. This one, you point it to a working xip for the device, and a new xip that has the new build you want, and thats about it... It'll combine the needed files into a single new xip bin. It builds the XIP folder now, but it's still in alpha because it's using BAT files. I plan on getting an actual app to do this all, but at a standstill with buildxip not working..
[Touch CDMA Windows Mobile ROM Development] boggsie:
:eek:

... sounds too good to be true ...

Not that I doubt anyone's ability; I just spent 45 minutes M'Reloc-ing modules.

Best regards,

-boggsie
[Touch CDMA Windows Mobile ROM Development] lennysh:
If you must know of a secret thats not really a secret, most newer builds modules are all at basically the same addresses... So if you just m'reloc the device oem modules to address above those, then xip porting basically becomes drag/drop from then on out. I've been doing that for about 4 devices for a while now... Really only takes me a matter of minutes unless some of the new modules are a lil bigger than they were in the last xip. So it's a good trick to put about a 2000 gap between msxipkernel and oemxipkernel...
[Touch CDMA Windows Mobile ROM Development] dcd1182:
+1

thats what i wanted to get everyone to eventually here :)

msxipkernel seems to be increasing by 1000 with every 1.x aku
[Touch CDMA Windows Mobile ROM Development] fayfay392:
yea man thanks for all of your help ! im going to go through and take screenshots for yall today. Also i will keep going on porting.