Originally Posted by no2chem (Post 122717)

maybe I should do a little write-up on how to port xip. essentially:

don't dump with rommaster (manually extract the rom)
to do this, first nbsplit, then on payload...
run imgfsfromnb. write down the imgfs start location.
open os.nb.payload with hex editor. go to the imgfs start location, and delete to end. go to the beginning of the file, and search for FE 03 00 EA (unconditional branch to 00 03 FE), and find the second / last occurance. (this is the second xip).
delete everything from the beginning to just before the second branch.
save this as your xip.bin

open xipport. press dump xip.bin. move stuff around, checking the maps between the donor xip and your xip. when you're done, press realloc p, and write maps. if any area shows !!!, fix it. (usually, modify realaddress[r] in imageinfo.txt, where r is the xipregion).

technically, you might need to check the nk.exe pointer in S000 of nk.exe, but i think realloc p fixes that (maybe). if you're worried, from the old map of the xip (not from the donor, but your device), search for the rom_00 header, look at where it starts, check if it matches with the new map If it doesn't you'll have to do this: if the old start address is 8ABCDEF9, search S000 of nk.exe for F9 DE BC 8A (just an example), because of the endianess of arm. replace with new start address, be sure to reverse it as well.

once you're done, write xipout.bin, and write it to os.nb.payload at the right xip2 address (for the titan, its 3200000) (sleepy and not sure if i put the right amount of zeros, but the default is 3100000, so change the 1 to a 2.)

hopefully everything boots up after this. I've used this technique to change everything except nk.exe... which is device dependent, so you'll have to do other stuff...

http://www.airscanner.com/pubs/fogieDC11.pdf is a good reference for arm assembly opcodes

Originally Posted by bigray327 (Post 122820)

no2chem, I had bluetooth shut off on its own after about 2 hours of PDA operation. I didn't connect to any BT devices in that time. The blue light keeps blinking but when I go into the BT settings, the two check boxes on the mode tab are unchecked. No dpad issues so far.

Edit: another shutoff, several instances of the dpad lockup (which I agree is fixable by hitting the red button), and no auto-connect with my BT device (which is the only thing I care about, I know you guys have different goals).

Edit 2: FWIW, I tried the Qwest ROM for a couple of days and didn't have any BT turnoffs or dpad lockups.

Thanks for your work,

- Ray

Originally Posted by rvashi (Post 122867)

no2chem, everything works great so far! I have not experienced any issues so far. As a note, I am using Radio 1.47 and have the Roam settings to 'Automatic' not Sprint Only. Even with that, no issues with Bluetooth drop or DPad freeze.

But I have one question, since you made the ROM completely plain, how come you included the Touch/Big Button dialer? This dialer is preventing me from correctly changing it to some other dialer (i.e. buttons out of place and no numbers on the buttons). I can turn off the Big Button dialer skin from the registry HKLM\Security\Phone\Enabled --> 0 But that makes that ugly little window appear above the dialpad which shows call log and Contacts.

I think you should leave the Big Button dialer out and keep the original WM6 dialer and make it a very plain and simple ROM which is fully customizable for some people like me who may not like the Big Button dialer. I would really appreciate it if you acknowledge this request.

Originally Posted by no2chem (Post 122932)

I'll take your advice into consideration. The reason I put the big button dialer was because I thought that it would be easily replaceable, and that the original wm6 dialer was hard to use anyway.

Originally Posted by phuangk (Post 123107)

Hmm is this me or something else.. I can't seens to find an option to turn on the flash light in the new camera software.. and with this version, the slide/turn function in HTC Album doens't seens to work either... correct me if i'm wrong about this.