yashsingh1/xdaforums huggingface dataset:
[Upgrading, Modifying and Unlocking] 1loudsvt:
Update: the verizon rom does not show a missed call but if you get a call while in a call whether you answer or not it shows up as a missed call.
[Upgrading, Modifying and Unlocking] Kyusaku:
Not sure on second half, but first half is also true on Sprint ROM.
[Upgrading, Modifying and Unlocking] NightRaven:
Anybody out there any good at building XIPs? I need one for 20924. Everytime I make one, they don't boot.
[Upgrading, Modifying and Unlocking] NightRaven:
Alltel/Bell/Telus - Beta 12 Build 20924 - http://www.4shared.com/file/6969155...x_WM61_5220273__Build_20924150__Napaboth.html

Verizon - Beta 12 Build 20924 - http://www.4shared.com/file/6969290...x_WM61_5220273__Build_20924150__Napaboth.html

Sprint - Beta 12 Build 20924 - Use Verizon ROM for now.

CE OS 5.2.20273 (Build 20924.1.5.0)

Beta 11 with the following changes.

Updated SYS build. (That's right, AKU 1.5)

No Appointment Categories.

Bluetooth Activesync still not working. (Thinking it may be the xip at this point. Need to port a 20924 xip.)
[Upgrading, Modifying and Unlocking] lennysh:
Send me that last XIP I made you, and I'll update it.
[Upgrading, Modifying and Unlocking] NightRaven:
LennySH to the rescue! Here's a link to the 20273 xip in the beta 12 rom. http://www.4shared.com/file/69728061/81211206/20273xip.html

Thank you, you are a god!
[Upgrading, Modifying and Unlocking] elroy303030:
Im still a nOOb to this stuff, and I was woundering if this will work on a 700w?

Its a Verizon phone that im useing on Alltel service. I was woundering if this would help with my problems getting on the internet?
[Upgrading, Modifying and Unlocking] lennysh:
Sorry it took so long to reply, I just now seen your post. Its attached below.
[Upgrading, Modifying and Unlocking] NightRaven:
I would not recommend running anything higher than 5.0 on the 700w.
[Upgrading, Modifying and Unlocking] NightRaven:
Just added it to the rom. Testing now.
[Upgrading, Modifying and Unlocking] NightRaven:
Thank you! Just added it to the rom. Testing now.
[Upgrading, Modifying and Unlocking] ziggystar:
20924

Neat! What's new in 20924 Xip?

Where did it come from?
[Upgrading, Modifying and Unlocking] NightRaven:
Excellent! New XIP boots! I rebuilt the ROM just to be sure, and it still boots. Testing bluetooth activesync now. Hopefully this fixes it, as I am running out of ideas.
[Upgrading, Modifying and Unlocking] lennysh:
Did you really expect any less? Check the about screen to make sure both numbers are now 20924.
[Upgrading, Modifying and Unlocking] NightRaven:
I never doubted you for a second. I expected I would screw-up importing it into the rom. XIPs don't like me... Yep, the new version string is CE OS 5.2.20924 (Build 20924.1.5.0).
[Upgrading, Modifying and Unlocking] NightRaven:
Alltel/Bell/Telus - Beta 13 Build 20924

Verizon - Beta 13 Build 20924

Sprint - Use Verizon ROM for now.

CE OS 5.2.20924 (Build 20924.1.5.0)

Beta 12 with the following changes.

New 20924 XIP! LennySH provided the XIPs for these roms. Show your support for his work by donating to him here.

Option + Send issue fixed.

No Appointment Categories.

Bluetooth Activesync still not working. :(
[Upgrading, Modifying and Unlocking] laplacian123:
Hello to everyone! This is my first post on the forum, but I have been following this thread since the beginning. I am both a programmer and a sys-admin, and I just thought of something about the BT activesync...before I make any assumptions, I need to know one piece of information: who all is using "Windows Mobile Device Center" with Beta 13 (or any of them, for that matter)? If my hunch is correct, it may be possible that the problem is on the PC end -- not WM6.1.

I know it sounds kind of strange and stupid, but it is quite possible that the PC is not providing the necessary bluetooth service information to the 700wx, therefore making it so the phone thinks that it has no activesync partner.

I went through all of the registry settings on the 700wx (I know, it's been tried), and nothing looks wrong, and with all of the work that NightRaven has put forth (NightRaven -- you are my hero, by the way), I thought that I would take a different viewpoint on the issue.

The reason that I am jumping to this conclusion is that I had the EXACT same issue on PPC2003 with bluetooth activesync, and it ended up being rectified by a little PC-based registry hacking, as well as an upgrade of the ActiveSync software from Microsoft. I know that WM6.1 does not innately support 'serial' activesync (which is how I initially fixed it), but, hey, it's worth a try to see if the **PC end** is messed up.

This link is what kind of sparked the idea:

http://blogs.msdn.com/windowsmobile/archive/2008/09/09/trouble-getting-your-activesync-provider-to-work-with-windows-mobile-device-center.aspx

Again, THANK YOU NIGHTRAVEN!!!

Just trying to help....:)
[Upgrading, Modifying and Unlocking] NightRaven:
I'm not very convinced it's the PC side that is the issue. Bluetooth activesync worked just fine in my 19202 build.
[Upgrading, Modifying and Unlocking] laplacian123:
See, that's the thing. Back when I had PPC2002 on my iPaq, I couldn't get bluetooth activesync to work -- it gave me the EXACT same error: 'Cannot find a Bluetooth ActiveSync partnership, Would you Like to Create One?'.

I finally upgraded the PC software (at the time, it was XP and ActiveSync; eventually I used WMDC), and the SPP/ActiveSync Bluetooth Service finally found the PC and synced.

I believe that I also had to mess with the SPP side of the issue, as the 'ActiveSync' service would not work at all. If we could find some way to get WM6.1 to TRY to use the serial sync service (again, I don't know 6.1 that well -- this may not be possible), then the connection would be initiated by the BT serial port, not just Bluetooth ActiveSync.

I think that if the build of WM6.1 is too 'new' for the WMDC, it doesn't know how to advertise the ActiveSync service to the 700wx, and therefore, no sync.

This was just a hunch, however; I just wanted to see how many people are actually using WMDC in an effort to find some kind of commonality between users.
[Upgrading, Modifying and Unlocking] NightRaven:
I know some people on 20755 had to first sync using the USB cable and then create the bluetooth partnership. Even that didn't work in my roms. What we need to prove this is for someone using ActiveSync on an xp machine to try this. As for the registry entry on the PC, I don't even know where to begin to look for it. Did your the bluetooth hardware in your XP machine actually support the ActiveSync profile, or did you use it as a bluetooth com port connection?
[Upgrading, Modifying and Unlocking] ziggystar:
No it's not that. The Phone finds the PC no problem, shows it has active sync as a service no problem. The PC sees it also. But every time you try to select the connect via bluetooth option in the active sync window it states "cannot find a existing bluetooth partnership that supports activesync. Would you like to seup now?" clicking yes brigns you to bluetooth where you can see it's already set up. That's as far as I can get.

Maybe "back porting" the active sync program and registry settings would fix it?
[Upgrading, Modifying and Unlocking] laplacian123:
Both. I just found an interesting little piece of information...The 'Bluetooth ActiveSync" menu option that is available in the ActiveSync app: it's just a link that is in the registry. Somehow (seriously, I don't know), I managed to accidentally REMOVE the bluetooth sync option from ActiveSync. I'm going to see if when I get it back, it had some kind of editable information in the key as to what to sync with.
[Upgrading, Modifying and Unlocking] laplacian123:
One thing that some people mentioned on Windows Mobile boards was Linux syncing -- is there a program out there that enables Linux syncing? If so, I could try to pair with the phone in my Linux installation and see if it likes that any better. Just a thought...
[Upgrading, Modifying and Unlocking] smokeingit:
May not be useful information... but i do use Windows Mobile Device Center with my 700w and it works flawless. i dont have a XP PC at the moment so i dont really care for any other issues.
[Upgrading, Modifying and Unlocking] NightRaven:
I've already tried bring the 19202 activesync pieces over, and that also did not work.
[Upgrading, Modifying and Unlocking] laplacian123:
Somehow I got the 700wx to connect TO the computer (not recognize; CONNECT) via bluetooth...I'm seeing if I can get ActiveSync to work now that the 700wx realizes that my PC is there.
[Upgrading, Modifying and Unlocking] elroy303030:
Thank you for your response.
[Upgrading, Modifying and Unlocking] laplacian123:
Update - the connection led to a dead end. The only other thing that I can think of that would be common for everyone is the Microsoft Bluetooth Stack.

The MS Bluetooth Stack does have some innate downfalls. My friend bought a laser keyboard and tried connecting via bluetooth on XP and Vista -- to no avail. For some reason, the Microsoft Bluetooth Stack has MAJOR issues with service discovery and passkey exchange; the latter of which caused the issue with the keyboard.

We ended up doing this huge workaround that involved using the Widcomm bluetooth stack instead of the MS one. The keyboard instantly connected.

I do have an IPaq with PPC2003 on it that I tried to get to sync with WMDC, and it has the same problem as the Treo, although it cannot even find the ActiveSync service AT ALL.

I'm going to try the Widcomm workaround with the Treo, because I find it hard to believe that despite the exhaustive efforts of NightRaven, the device has a problem.

I know that there are issues with the versioning of the bluetooth stack in Windows (including Windows Mobile). I think that in the latter two builds, some handshaking parameter changed, and therefore, we cannot sync.

Anyway, I put my two cents in...I'll keep trying.
[Upgrading, Modifying and Unlocking] laplacian123:
GOT IT!!!

I tried Bluetooth ActiveSync in Linux: IT WORKED!!!

Of course, most of you don't have linux, so I am going to attempt to make a write-up or some kind of fix. I have not gotten it to work with Windows -- yet, but I think I know how. At least now we know that BOTH of the bluetooth stacks are to blame: not the device alone!

When I used "Pocket Bluetooth Utilities" on the phone and paired in Linux, the special configuration screen from Pocket Bluetooth Toold showed up...AND SYNCED VIA BLUETOOTH...Here's what it will look like to all of you:

I will post the howto later!
[Upgrading, Modifying and Unlocking] laplacian123:
Ok, so it works on Windows as well...

First, the disclaimer: I AM NOT RESPONSIBLE FOR ANY DAMAGE DONE TO YOUR COMPUTER OR PHONE!!! THIS HOWTO IS TO BE FOLLOWED AT ONE'S OWN RISK..

First:

Before you download the stuff, make sure that when you install, you select ALL BLUETOOTH SERVICES upon setting up the Widcomm stack!!

Follow the instructions on the following page.

http://www.dev-toast.com/2007/01/05/uncrippling-bluetooth-in-vista-rtm/

FOLLOW THEM CLOSELY!!! THIS IS AN IMPORTANT STEP!!!

NEXT:

Download "Pocket Bluetooth Tools" from the following link. Install it.

http://bluetooth.i-networx.de/download_e.html

Once this is installed, let the package do its thing...Perform a soft reset.

THEN:

ONCE YOU HAVE GOTTEN EVERYTHING INSTALLED:

Go through the pairing process using the Widcomm stack. SELECT THE ACTIVESYNC SERVICE as well as all of the other ones that you wish to use.

Now, once you complete the pairing on the device, you will see the Pocket Bluetooth Tools "Service Selection" screen.

CHECK THE ACTIVESYNC BOX.

You will then see the BEAUTIFUL "Sync With XXXXX via BT" option in the ActiveSync menu.

Enjoy!:)

EDIT:

Make sure that you right click to the tray icon and select "Bluetooth Configuration" and take note of the PC's ActiveSync COM port. You will need to tell WMDC or ActiveSync to use this COM port -- NOT the "BLUETOOTH" option.

Just in case anyone has any doubts...
[Upgrading, Modifying and Unlocking] NightRaven:
While the above solution does work, I would like to find a solution that is easier for the masses to implement. I loaded 19202 on one of my test phones, and 20924 on the other. In order to compare the registry after boot. I found that there are several RAS devices missing in the 20294 build. I think that this may be the problem. Below is a table of the RAS devices on each phone.

Build 19202

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

Cellular Line

QCT Data Interface

Native IR:

Infrared Port

Serial On USB

Generic IrDA

Hayes Compatible on COM 1

Bluetooth

Bluetooth device

RAS VPN Line 0

RAS VPN Line 1

RAS VPN Line 2

RAS VPN Line 3

RAS VPN Line 4

Build 20924

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

Cellular Line

QCT Data Interface

Native IR:

Infrared Port

RAS VPN Line 0

RAS VPN Line 1

RAS VPN Line 2

RAS VPN Line 3

RAS VPN Line 4

L2TP Line 0

I am going to try to restore the missing RAS devices on the 20924 build to see if that corrects the problem.
[Upgrading, Modifying and Unlocking] Mungo888:
In Beta 13 for Verizon, the Option + Send is still not working by default without first changing it to another function & then changing it back.
[Upgrading, Modifying and Unlocking] NightRaven:
Sorry, I forgot to update the rgu file in the verizon and sprint rom. That's the problem with having three roms. They are updated now. It will work in beta 14.
[Upgrading, Modifying and Unlocking] kocoman:
Can you also look into a "Bluetooth LAN Access Profile"? I could never get the 700wx to connect to my picoblue Bluetooth access point because it doesn't need to 'dial a number', while 700wx always insists it needs a phone number..

Also whats new in the AKU 1.5? where to find the info?

thanks
[Upgrading, Modifying and Unlocking] NightRaven:
Bluetooth Issue Update!

I think I found the problem. I was able to restore Serial on USB. I also found that the rest of the devices are missing in the default.hv and user.hv registry files. I have manually edited them. I will test and post the results in about an hour. If all goes well, you'll see Beta 14.

Update:

I'm closer, but still no luck...
[Upgrading, Modifying and Unlocking] flipfone:
ok so 'how to' in linux? i cant install ms AS in wine as it uses the propritary windows installer... .msi
[Upgrading, Modifying and Unlocking] laplacian123:
Sorry about the lack of clarity of that post...The instructions that I provided are for Windows XP AND Vista. PM me if you are interested in finding out the Linux instructions.

Hopefully NightRaven will find a better solution, but this DOES work both on XP and Vista.

Update to NightRaven:

I actually tried the RAS device thing, and actually, the reason that my method works is because Pocket Bluetooth Tools is able to create the RAS device ONLY with the Widcomm Bluetooth Stack.

The whole reason that the bluetooth is not working is because Microsoft's Bluetooth Stack has MAJOR issues negotiating. Normally, the MS bluetooth stack should negotiate with the WM device, and subsequently, create the RAS device upon pairing -- this does not happen with Microsoft's current implementation of the Bluetooth Stack. The only reason that it works is because with Widcomm's stack, the device is actually able to negotiate the service to create the space in the driver memory for the RAS device.

Note that in the WM registry, the RAS device is not just a simple registry entry -- it contains a pretty lengthy key consisting of some kind of memory address. I don't think that it's possible to just 'create' an RAS device without first finding the space in the driver memory that the Bluetooth Stack created when it paired with the computer.
[Upgrading, Modifying and Unlocking] NightRaven:
This has proven to be extremely difficult. I tried to port bluetooth from several earlier builds. However, it then said there was no bluetooth hardware in the device. I am beginning to think this may not be possible until microsoft releases a newer build.

I'm going to take the night off. Tomorrow night, I will work on the sprint oem. Sprint users, be prepared to test...

Once I get the Sprint OEM working correctly, I will post the new kitchens.
[Upgrading, Modifying and Unlocking] Kyusaku:
I'll be ready, if possible, provide a list of issues to confirm as fixed.
[Upgrading, Modifying and Unlocking] pdawg17:
Sprint customer ready for testing...
[Upgrading, Modifying and Unlocking] m4f1050:
Same here... Sending hangs when opening the composer... I can send with version 3.0.22 though but it won't receive. Software limitation I guess... Wonder if we can mix dll's around, say use version 3's composer? I have version 5.0.70.16? and it works fine on 6.1 on a Sprint HTC Touch, so I guess I will wait for the bug to be solved...
[Upgrading, Modifying and Unlocking] NightRaven:
On a side note, I just read that Windows Mobile 6.5 is coming first quarter next year. Microsoft decided to put out an interm release because 7.0 has been pushed back to 2010.

http://www.neowin.net/news/main/08/11/07/windows-mobile-65-confirmed
[Upgrading, Modifying and Unlocking] Danyan:
Faster Calling Like Wm5

Will there ever be a faster calling (dialing) experience like there was in WM5? It takes a couple of seconds to connect. Same when answering the call. I'm sorry but that freaks me out!
[Upgrading, Modifying and Unlocking] m4f1050:
I think the problem with sending MMS is that the phone is running out of memory or resources, I just tried to install Opera 9.5 and it is sluggish. Does anybody have ArcSoft MMS 3.0.26.12 cab? That one is a known to work but I don't have the install to verify it.
[Upgrading, Modifying and Unlocking] m4f1050:
NightRaven, can you make a WM5 version like the WM 6.1 you have, I like what you've done but would like to have it on WM5,... Faster, MMS works and Opera 9.5 is smooth. Whatever you did with the MMS on WM 6.1 enables it to receive. :)
[Upgrading, Modifying and Unlocking] m4f1050:
Oh, and by the way, ArcSoft MMS 3.0.6.22 for Verizon works both sending and receiving for me, I'm using MetroPCS. I had to add a few registry entries, change a few entries and create MetroPCS server under MMS Configuration to make it work.

http://rapidshare.com/files/161702092/VzW_ArcSoft_MMS_3.0.6.22.cab

Change the following keys...

HKLM\Software\ArcSoft\ArcSoft MMS UA\Config\UI
EnableServerEdit = 1

HKLM\Software\ArcSoft\ArcSoft MMS UA\Config\mm1
EnableMSISDN = 1

Create or change the following keys...

HKLM\Software\ArcSoft\ArcSoft MMS UA\Config\mm1\WspHeader\
Accept = */*
Accept-Charset = us-ascii,utf-8,iso-10646-ucs-2,iso-8859-1,gb2312,gb13000
Accept-Language = en
User-Agent = ArcSoft/MMSUA/PPC/v5.0
X-Device-Min = 1xxxxxxxxxx (this is for metropcs, xxxxxxxxxx=your phone #)
X-VzW-MDN = 1xxxxxxxxxx (this gets created with your phone #)
X-Wap-Profile = http://www.arcsoft.com/mobile/UAProf/ArcSoft-MMSUA-PPC-v40.xml

Run MMS Configuration... and create your server entry under Servers tab and Set As Default.
[Upgrading, Modifying and Unlocking] 1loudsvt:
the above instructions for mms are confirmed working :D thanks
[Upgrading, Modifying and Unlocking] nickdollahz:
So far no roaming been running the rom for about 3hrs now so its still not long enough to tell.

My phone is set to Home.

I followed this thread: http://discussion.treocentral.com/showthread.php?t=164457

Also I reset the radio with the correct settings while in WM6. Also updated my Powervision information. I also soft and hard reset and reset settings to make sure they stuck.

to flash to stock but replaced the Napaboth.nb0 from that thread with the one from this thread. (which follows that threads instructions for custom firmware.

It is more of a complete flash then to just flash the Napaboth.nb0 file.

This way its more of a clean flash if you know what I'm saying.
[Upgrading, Modifying and Unlocking] ianandamy:
lol I am currently using the sprint update and replaced the wm6 nap with the one in the update.

so to go back I can just use the sprint update right?

I am updateing the msl msn and ##rtn now and then I will call sprint to try and get my power vision re activated. I will do it manually. and I will see if you can switch to auto roam home mode.

just curious when you did the downgrade back to wm5 were you able to use the roaming feature? and go back to home without loseing all sprint signal, i guess what i am saying is if you switch to allow auto roaming then back to home only it will not switch back to sprint at all.

wanted to know if you would check that on your wm6 setup if this happens all you have to do is ##rtn to get it back but that is the bug I was trying to describe.
[Upgrading, Modifying and Unlocking] nickdollahz:
Yes you are correct. There is that bug. I was trying the rom again to see if I could permantly fix it. Or try to pin point what is exactly happening.

It is a good thing i really dont use roaming. Although both Sprint and Verizon has the same signal strength but Verizon doesnt have Evdo in my area.

I'm 80% sure it has something to do with the homenid and homesid. In theory this is what I think is happening. I think while in roaming the tower give the phone its homesid and homenid. So when you put the phone on home and it tries to connect to the home tower it uses the ids of the roaming tower. If this is true. All we need to do is manually set the homenid and homesid. So that the phone can operate properly but this is all theory. Or maybe never roam. (my solution). Also the radio reseting will fix this (ur solution) I am in no means incline to know what the hell I talking about. lol Semi-joke

PS. Now this sounds like a letter from me to you. Other forum users feel free to reply! Also would like to say that the Treo 700wx is a awesome device to be able to run this stuff with it being so old and all.

Oh yea.. Its good to know your powervision username and password during this process.

I'm sticking with wm5 until there is a new rom released. As the RTN reset does not help. After the glitch happens you have to flash back to stock. This glitch is too much for me to continue using so I'm staying on wn5 until the verzion wm6 is released or another fixed and found.
[Upgrading, Modifying and Unlocking] kocoman:
Is this WM6 coming from the Verizon 1.24 update?

http://discussion.treocentral.com/showthread.php?t=165893
[Upgrading, Modifying and Unlocking] nickdollahz:
I'm not sure but i dont think it is.this version reads Windows Mobile 6 Professional CE OS 5.2.1620 (Build 18125.0.4.2) copyright was 2007. Software version for my Sprint 700wx reads TREO700WX-1.15-SPNT. Although the quick guide is that of a treo. and the icons are of another device. so idk.

All I know after reading that thread is to keep stalking Ebagg for a release. (Another semi-joke)
[Upgrading, Modifying and Unlocking] ianandamy:
funny thing is I installed the alltel rom and on home id it switched to roam and to home and back and forth while set on home only so if we leave it then it will work the only thig I noticed was I was never able to get it working on the evdo but I have my info now so I am going to retry tonight. I think the verison rom locks to home only I think I will try verison one too once again.
[Upgrading, Modifying and Unlocking] ianandamy:
ok I installed the verison one withthe 1.15 update stuff on the phone the phone had to be activated and the net entries worked I left it on home and went to a raoming area and sure enough it roams too. and works so we are gold.

I am going to test for a few days and check it out.