[johnny2678]

LONG POST, SORRY

Ok Colonel, in short, I got it to work. Here's was my method:

I removed the btd.dll module out of the apache drivers folder and copied in the btd.dll file from the cab I used to get BT PAN working... flashed... and it didn't work (Unable to detect service)

Then I remembered that BP PAN worked right out of the kitchen (no modifications needed) with the Unified 3.5 ROM. So I searched through that ROM, pulled out the btd.dll file and threw it in the apache folder. The file size was the same but the date was different, so I thought it was worth a shot... reflashed... and still unable to detect service.

Then I thought to compare the reg entries the R2 kitchen made to the reg entries that were found in the working cab, and there were some:

BTPAN differences
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\pa n
key: ActivateOnBoot
kitchen dword=1
cab dword=0

HKEY_LOCAL_MACHINE\Comm\BTPAN1\Parms
key: AdapterType
kitchen string=PANU
cab string=NAP

key: Description
kitchen string=Bluetooth PANU service
cab string=Bluetooth NAP service

key: FriendlyName
kitchen string=Personal Ad-hoc Network
cab string=Network Access Point

key: MaxConnections
kitchen dword=16
cab dword=1

key: ServiceID
kitchen string={00001115-0000-1000-8000-00805f9b34fb}
cab string ={00001116-0000-1000-8000-00805f9b34fb}

I was going to start changing one by one restarting the phone and checking BT PAN functionality. Good thing I started from the bottom because as soon as I changed the ServiceID string (basically a 5 to a 6) and restarted, it worked!

what I should probably do is change the 6 back to a 5 and confirm that the change again disables BT PAN... and further more I should change the ServiceID value in the OEM_BT_PAN RGU, reflash and check that BT PAN works up startup... but I'm too tired tonight and my phone is finally back to normal.

Hope this helps with future kitchens.