Re: Unofficial PPCK Build Updates 20954, 210xx, 21015
 

Of course. Please also consider sharing any additional OEMs and your selections.txt (that way people can make their own adjustments and it's a lot smaller download). If you don't know how to package up your additional OEMs, just ask. If you made changes directly to the base....I'll be happy to teach you how not to do that, too.

Re: Unofficial PPCK Build Updates 20954, 210xx, 21015
 

This is the microsoft catalog I removed from the sys of 21015 made it an oem. When I run it a message pops up saying "MarketPlace: No Catalogs Found On Device". I wonder if this is the new microsoft marketplace we have heard about lately. Oem is attached if anyone wants to try to figure it out.

gguruusa Can you implement this reloc tool that works with WM6.5 into PPCK syntax is "WMReloc.exe -gtemp\dump"

Tutorial is here http://babelfish.yahoo.com/translate...rUrl=Translate

Re: Unofficial PPCK Build Updates 20954, 210xx, 21015
 

Anyone know the difference between WMReloc and G'Reloc? Is WMReloc backwards-compatible with earlier builds? What doesn't G'Reloc do that WM6.5 requires?

And is the usage still the same?

1) Create dump directory using selected sys, and OEM
2) G'Reloc.exe -dump -doit
3) Build ROM

If there is a thread elsewhere that is more appropriate for this question, please direct me there.

Re: Unofficial PPCK Build Updates 20954, 210xx, 21015
 

Drellisdee

I built a rom for my Sprint Touch using 21015 build. I had 2 issues and I was not sure if it was the build or my Rom and was hoping you might help. I had used the Diamond keyboard oem in PPCK and after my flash I was unable to type anything on any of the diamond keyboards. They came up but was umable to type. The other thing was the backlight did not work.

Re: Unofficial PPCK Build Updates 20954, 210xx, 21015
 

Diamond KB oem is broken on newer releases so don't use it. Not sure on backlight as my backlight works fine on my vogue using 21015. The sys/xip is good just as always there may be oem conflicts with a new build. Unselect a few and try building again till you get a working one and try to narrow down the OEM that is causing it. Please post any known bad oems with these sys. I know the cambridge BT on Touch pro and possibly BT FTP and BT Print cause Pro roms to hang on splash with 20931 or higher. Can you add your selections.txt as an attachment?

Re: Unofficial PPCK Build Updates 20954, 210xx, 21015
 

Anyone had any issues with 21015 on Apache or Vogue with Bluetooth ActiveSync?

I currently have 19212 on my Vogue and can ActiveSync via Bluetooth fine, but my wife currently has 20931 on her Apache and lost that ability ... has anyone tried ActiveSyncing via Bluetooth with 21015 on either the Vogue or Appache? If so, does it work?

Re: Unofficial PPCK Build Updates 20954, 210xx, 21015
 

I will rebuild tonight and post results. Im not sure if I still have the txt on the last build.

Do you know of a good working OEM for the diamond keyboard with this build.

Re: Unofficial PPCK Build Updates 20954, 210xx, 21015
 

FWIW I am using XIP 21015 and SYS 21015 on CDMA HTC Touch Pro (Verizon) and am able to ActiveSync over Bluetooth. The MS SYS files require an OEM BT driver - perhaps that driver may be incompatible with 21015 on Apache. If you could identify the BT hardware in the vogue or TP as the same in the Apache, you could try the BT driver from OEMDRIVERS package on one of those phones.

Re: Unofficial PPCK Build Updates 20954, 210xx, 21015
 

Here is a backlight fix.U probably have manila in your user OEM folder,if so,then overwright that dll.Im also attaching txt doc with my selections, it will give u an idea to start with.I can upload my user oem folder if somebody want one,its messed up a little,but works with that selection txt

Re: Unofficial PPCK Build Updates 20954, 210xx, 21015
 

WMreloc is a replacement for g'reloc. Usage is a little different, but similar. It has it's own self-explanatory usage output.