BlackBerry + BES install. HOWTO? - MDA III, XDA III, PDA2k, 9090 General

Hi guys,
My company has MS Exchange and BES servers installed, and few of my co-workers are using the BlackBerry services with regular BB devices. Currently i'm trying to enable this on my XDA IIs (Asian, with latest ROMs). I got the service enabled on my SIM card via my local carrier (Orange Israel). I've tested the SIM on a regular BB device and it worked just fine.
I've installed Blackberry_1.2.4.19.cab (and also tried HTC_PocketPC_TMO_Austria_Germany_Load_Working-1.cab), but the service still does not work. Either the PIN number is not assigned, or the PIN number reported on the device does not match the one in the BES. When i run BBConfig on the desktop it reports that the PIN is not configured.
Also, where should i enter the "activation password", which is generated by the BES in response to a PIN?
Maybe someone can post a step-by-step guide on how to enable BB service on HTC Blue Angel with BES?
Thanks!

http://www.blackberryforums.com/forumdisplay.php?f=32

When used as a BB what are the cost like? Is it just a case of installing the cab? Where do i get the cab?
What protocols does it support? just exchange?

There's a small initial connectivity fee for enabling access to BB APN (blackberry.net), and then there's a monthly payment. I'm not sure about the real costs as its handled by my company.
In theory installing the CAB on the device and BB Config on the desktop should be enough if you have a BES server that pushes your e-mail. CAB can be downloaded from forum's FTP site (use the search function to find the exact link).
However, after installing and enabling everythin i still can not get it work. Hitting the "connect" button on the BBConfig results in an error message, and the BB client on the device can not connect to the server.
I know that some people managed to get it working. It would be great if one someone could post a detailed guide, as my operator would not provide any support for HTC-based devices.

Getting BES to work on T-Mobile
Some non technical experience:
I run the BES on my MDA III. Whilst I am on T-Mobile UK, our Corporate BES is Vodafone based.
After downloading and installing the BB PC desktop software from T-Mobile Germany (it is in English) for the MDA III, the client software is already resident on my MDA III (it is in the latest extended ROM), I had to get it enabled by T-Mobile. T-Mobile had to send the appropriate service books to the device AND enable the individual sim card at a network level (this latter issue took some discussion between my IT Department and T-Mobile UK).
Since then I have been up and running BES with no problems. The monthly service fee is around £30 from memory (so it is not cheap! :shock: )
Hope this helps.
J

Related

Blackberry - Cingular - PDA2K

I have followed the Blackberry-related threads, but a couple of questions remain. Forgive me if I missed an answer that's already posted.
First, I'm using the PDA2K with a Cingular SIM. I have the the "unlimited PDA data" plan, which a Cingular data support technician tells me should qualify me for Blackberry service. In fact, I used that plan when I had a Blackberry 7290 through Cingular before I got the i-Mate device.
I installed the O2 version of the Pocket PC Blackberry client software- with no problem (even though after the install a message appeared telling me that the client software might not display properly because it was meant for an earlier device).
Question 1: When the Blackberry client is running on the Pocket PC, the handheld won't sync with ActiveSync. Is this to be expected?
Question 2: My company's BES redirector software on my desktop doesn't see my Pocket PC even when the Blackberry client software is running on the handheld, the handheld's in its cradle and the cradle's connected via the USB port to my desktop. Is this because of some conflict with ActiveSync perhaps?
Question 3: In checking the settings on the Blackberyy client software on my handhled, I see no PIN #. Is this because Cingular's ROM doesn't serve up a PIN # for the device - because, in turn, Cingularl doesn't support Blackberry connect software? I take it there's no other way to load my old Blackberry PIN # (from my Blackberry 7290 days - it's still "alive" on the Cingular Blackberry website) short of through a ROM update of some sort?
Many thanks.
Charlie
We are in the same exact boat except for i am on AT&T. I tried the O2 version and had the same problem. That is because the PIN on blackberry devices are harcoded into the device it self and the PIN from blackberry connect is generated by the software(most likely in association with IMEI, which is the truly globally unique ID for mobile devices). Then I installed the .CAB file extracted from the German T-Mobile III(same device as ours) and the desktop software. Except for the Connect software on the device is in German, there is no problem. The software generated PIN when I opened it, and talkes to the desktop, so the BES side also get the new PIN. Seems like evrything should be working now but no--I think the blackberry APN and IP need to be changed from the BB Connect settings but I don't know how, since those are carried over from the German T-Mobile settings. I will try to contact German T-Mobile to see if T-Mobile US supports it or not, if yes, I will switch.
I know of Blackberry, but I never heard about a client on the PocketPC. I currently have the $19.99 Media Works Unlimited plan, can I use that application as well? What benefits would I have in using it? If I could use it, where can I download it? Thanks.

Blackberry Connect On IMate PDA2K/MDA III/XDA III/Blue Angel

Here is a very complete guide for everybody who is using blackberry but tired of the limited functionality and want to switch to pocket pc using blackberry connect. I have IMate PDA2K, also named as Blue Angel, XDA IIs, MDAIII and some other names and I am trying any possible solution to have blackberry connect work on this device
1. At the current time, blackberry connect is officially offered in the following countries: A. UK by O2, supported device is XDA II/MDA II or the same device under other names, but essentially all are the same, manufactured by HTC, but the support and connectivity from O2 is ver poor. The blackberry version on this is 1.2, designed to work with pocket pc 2002. It's english version so the cab file should install on WWE version. B. Germany by T-Mobile, supports both MDAII and III. The software is blackberry connect version 2.0, designed to work with pocket PC 2003. The software is in Germany and the ROM update will not install on WWE version devise. C. Austrlia and Netherland also by T-Mobile under the same capacity.
2. There is no U.S. carrier right now who supports blackberry connect officially right now, either on the pocket PC or Palm platform. Might be available on Sony-Ericson 910, which is Sybiam based. Even if that is the case, it's of no value to pocket pc users.
3. There are examples of the O2 version BB connect working on MDA II here through T-Mobile. Go to www.xda-developers.com and looking for articles posted by cbrow51. He has detailed guide on how to make it work(Through BWC, not BES)
4. All installable .CAB and desktop BB can be found from the xda site.
5. I installed the german version of the BB connect .CAB file on my device as well as the desktop software(that can be installed in English version). The device talkes to the desktop PC and the BES side getts the correct PIN. I put my SIM card from my AT&T blackberry handheld on my new device. It's not working yet, I think I need to change the built in APN and IP address for connection from the BB connect software(which should be connecting to German) through someway to make it work.
Anybody interested in this, Let me know
Let's make it work!
Latest update on Blackberry Connect in the U.S.
Talked to AT&T support and the BES support from my company today. This is especially relevant to SX66/MDA III/XDA III/Blue Angel/QTeq 9090/IMate PDA2K, basically all the same device manufactured by HTC for different branding, which runs Pocket PC 2003. And it is related to BES.
1. The wireless carrier should have no problem with the connection. The only thing realte to the carrier side is your SIM, which doesn't really affect the connection as long as your BES side have your correct PIN. The carrier automatically recoganize your PIN when it's registrated in your BES. And it does not use IMEI at all.
2. The BES side should not have problem either since once you have your BB Client on your device talk to your desk top, the PIN should automatically recoganized by the BES
3. The trick is that all PINs on blackberry devices are hardcoded in the device, while through BB Client, it is generated from the software. The RIM server need to recoganize your PIN. I think the BB Connect i am using, which is the the .CAB extracted from the German MDA III(T-Mobile), has some utility to register the software generated PIN with RIM if you are on the T-Mobile German GPRS network, while other carriers don't have.
I will talk to RIM on Monday to see if they can register my PIN. I will keep you guys updated.
Any one interested in this topic, please let's form a ring
Re: Let's make it work!
rwu said:
Latest update on Blackberry Connect in the U.S.
Talked to AT&T support and the BES support from my company today. This is especially relevant to SX66/MDA III/XDA III/Blue Angel/QTeq 9090/IMate PDA2K, basically all the same device manufactured by HTC for different branding, which runs Pocket PC 2003. And it is related to BES.
1. The wireless carrier should have no problem with the connection. The only thing realte to the carrier side is your SIM, which doesn't really affect the connection as long as your BES side have your correct PIN. The carrier automatically recoganize your PIN when it's registrated in your BES. And it does not use IMEI at all.
2. The BES side should not have problem either since once you have your BB Client on your device talk to your desk top, the PIN should automatically recoganized by the BES
3. The trick is that all PINs on blackberry devices are hardcoded in the device, while through BB Client, it is generated from the software. The RIM server need to recoganize your PIN. I think the BB Connect i am using, which is the the .CAB extracted from the German MDA III(T-Mobile), has some utility to register the software generated PIN with RIM if you are on the T-Mobile German GPRS network, while other carriers don't have.
I will talk to RIM on Monday to see if they can register my PIN. I will keep you guys updated.
Any one interested in this topic, please let's form a ring
Click to expand...
Click to collapse
This is great news! I'm getting my SX66 on Tuesday and I was just going to hack at it till I could get the BB Connect to work.. I've been reading several posts about converting the German to English and people who have problems generating PINs that come up with a "0". The problem is all I can do is research at the moment and just think about how it should work. Do you have any tips for a newbee who will probably blowup the unit a few times??
Any help or guidance will be appreciated.
Very interested in this! I have successfully installed the BB Connect cab on my XDA2i and now just need to know if the pin issue can be sorted.
Do you think this is possible?
I believe the PIN issue can definitely be resolved as long as RIM is willing to take the software PIN, since they are doing so in German already. I am also attaching the BB Connect .CAB file extracted from the German T-Mobile ROM for MDA III. Just copy it to your device and click install it from there shouldn't cause any problem to your SX66
Also, here is the BB Desktop softie, this does have the English installation.
Hokay,
I've installed the BB COnnect on my XDAIIi and the desktop configuration sofware on my laptop, but the BB connect software says the PIN is 0 and the config software on the PC says that the PIN is "Not Configured".
How do you get it to generate a PIN in the 1st place?
squiggs1982 said:
Hokay,
I've installed the BB COnnect on my XDAIIi and the desktop configuration sofware on my laptop, but the BB connect software says the PIN is 0 and the config software on the PC says that the PIN is "Not Configured".
How do you get it to generate a PIN in the 1st place?
Click to expand...
Click to collapse
Do you have the latest radio on your IIi? I know on the MDA III the radio has to be upraged as well for the BB Connect software to read the IMEI and generate the soft PIN #.
Again this is only from what I can gather from forums that I have been reading. I will not be able to verify anything until next week when my SX66 comes in.
Hope this helps you.
As follows:
ROM Version 1.10.00 WWE
ROM Date 24/12/04
Radio Version 1.00.00
PRotocol VErsion 1337.39
ExtROM VErsion 1.10.124 WWE
squiggs1982 said:
As follows:
ROM Version 1.10.00 WWE
ROM Date 24/12/04
Radio Version 1.00.00
PRotocol VErsion 1337.39
ExtROM VErsion 1.10.124 WWE
Click to expand...
Click to collapse
Have you run any firmware updates on your unit?
I have read on this forum that the Radio needs to be upgraded for the BB Connect to read the IMEI properly in order to generate a PIN#. Most of the reasearch I have been doing is on the Blue Angel. But I do know that there is a higher rev of the Radio than 1.00.00.
Hope this helps.
squiggs1982 said:
As follows:
ROM Version 1.10.00 WWE
ROM Date 24/12/04
Radio Version 1.00.00
PRotocol VErsion 1337.39
ExtROM VErsion 1.10.124 WWE
Click to expand...
Click to collapse
Here is a link with a doc on how to get started with the BB Connect client.
http://forum.xda-developers.com/viewtopic.php?t=12589&highlight=blackberry+pin+radio
But again, I think the Radio has to be upgraded first.
I'm not sure if you have done so or not but there is one section on Page 15 of the PDF file that talks about creating a pin.
Tap Start > Settings.
Tap the System tab.
Tap the BlackBerry icon.
On the BlackBerry Introductory screen, tap next.
Read the End User License Agreement carefully, and scroll to the very bottom.
To accept the terms of the End User License Agreement, tap Accept. Your PIN is created and the
service is started.
Good luck.
Hmm...
Looks like it might be the end of the road then. As far as I can tell, there is no newer radio version ...
So at risk of sounding silly.
Has anyone managed to succesfully configure a BlueAngel with Blackberry and if so, what levels of ROM were they using, what version of the client and what carriers as I would also like to be able to set this up.
Thanks
What is the BB Connect version u r using? I had the same problem with the 1.2 version stripped from O2's ROM. But the 2.0 version generated PIN with no problem.
Hi there,
Using version 1.2. Where would I come accross v2? I'm assuming the one you posted above is in German? Sadly, I don't speak any!
version 2 generates a pin fine - but the only one i've been able to get was using the german client and although this sounds picky, i'd quite like to use a client that I can understand the settings properly (to any german readers, please dont take any offence from what i've written, its my own fault I didnt study german more at school!!)
also, the german client uses the t-mobile access point settings. i'm on o2 uk so how do i go about changing the ap's over?
Ta
Actually, for me, the GErman client still doesn't generatethe PIN correctly? :?
Contacted RIM a couple of time and seems like the German version of BB Connect from T-Mobile is not working for AT&T, at least. The problem is that it automatically look for the german T-Mobile net work to connect to the blackberry APN and IP. It is possible to change that from the CAB file though so it looks for defferent carrier's network. Bottom line, the data transfer is through the SIM card, which is carrier dependent. That is why on your blackberry device you will see the carrier's screen when you power it on. The BB devices' PIN are pre-assigned to carriers. It won't work if you shift carrier. Now, come back to our problem, we need somebody who knows how to cook the CAB file. Who can help here?
squiggs1982 said:
Hokay,
I've installed the BB COnnect on my XDAIIi and the desktop configuration sofware on my laptop, but the BB connect software says the PIN is 0 and the config software on the PC says that the PIN is "Not Configured".
How do you get it to generate a PIN in the 1st place?
Click to expand...
Click to collapse
Answering you purely from my experience.
I got BB client installed on my XDA2 and the desktop BBconfig s/w on my PC connecting to my office network. While my XDA2 is on my cradle and pressing the BBconfig connect button, I supposed the BBConfig establishes the connection to my company BES and generated a PIN which is also registered with the BES server. If any of these steps should fail (e.g. PC not connected to BES) , I suppose the PIN will not be obtained.
In any case, I haven't gotten it to work. My company BES server refuse to recognise my PIN as a valid one.
Hmm... so we need to find out how to register the PIN that is generated with the BB service.
Action points then, guys!
1. Find out how to register the software generated PIN with BES
2. Find out how to switch APNs for different carriers

PUSH EMAIL

i remember being able to get push email from my SE p900 a few years ago so does this mean that my service provider(globe) here in the philippines supports blackberry connect and if so how do i get this feature onto my BA?
so far, BA doesnt support push mail...many people are waiting for updated rom with the added.
BA does support push email. I am using it on my MDAIII. With T-Mobile UK it is called Instant Email from Blackberry.
So far only T-Mobile UK and T-Mobile Germany seem to be supporting Push Email in both the BES and BWS flavors.
Otherwise you can try Smartner at http://www.alwaysonmail.com/ .
BA does support push email. I am using it on my MDAIII. With T-Mobile UK it is called Instant Email from Blackberry.
So far only T-Mobile UK and T-Mobile Germany seem to be supporting Push Email in both the BES and BWS flavors.
Otherwise you can try Smartner at http://www.alwaysonmail.com/ .
Hi
I have been using Smartner for a while and it is not bad but current version does not sync Calendar.
There is a new version coming that will but it is not here yet.
This software does require you to have a PC permenantly connected to your network but if you have a Desktop machine this will do the job fine.
BUT I really would like Blackberry software as we have a corporate server.
I just wish I could find an easy to install version of the Blackberry client to try.
Robin
European subscribers are doing well with KPN through Visto. I used to work for them, and they sync pretty well.
Visto Tech Support is done from the Philippines.
Smartner
the Pro version of Smartner supports calendar sync.
i will post it on the ftp site on Monday
It does BUT does not work for everyone.
I installed it and could not get it to work.
For me The Client and push server would not connect.
Smartner support where very helpful and I supplied them a number of logs files which they told me had allowed them to find a problem that stops the Pro version working with 'some' not all installs.
HOWEVER they will not provide a fixed version until late this year because they are upgrading the Server/Corporate version.
Robin

how can i use email-push-service /blackberry on my MDA pro

Hi there!
How can I use Bleckberry Software on my MDA pro?
I have the option of email-push with my contract, but can not use it, because there is no software for the MDA Pro
There is software for the MDA II, vor MDA III and for Compact but not for the Pro. If i try to install the software for MDA III (others are in the rom-upgrades only) i get a messege that the software is not certified for this device.
Any Idea how to use it anyway? Or any other Blackberry-Client for my MDA Pro??
Thx
Hi! you will have to wait for the first rom update by t-mobile. I am waiting for it since August last year...
You better don't count on getting the update in the next months. T-mobile really sucks with updates.
really really sucks
The BlackBerry connect software is currenly not availabe on the MDA Pro. Expected Q1 ‘ 2006
Click to expand...
Click to collapse
http://www.iris-global.com/t_mobile_download/download_manager_mda_pro.html
dunno if it will come the same time as the first service release that is listed as January
I´m raly no great fan of T-Mobile, but the release is not a probleme of t-Mobile, but one of RIM.
They have problems with the 3G because they normaly only use GPRS
That´s what i read in a magazin for GSM-Users.
But is there no way to use the Blackberry-software of the MDA II?
I found this, I wonder if our resident guru's can do something with this info:
http://www.pocketpchow2.com/
Solving the Phone Synchronization Problem End-to-End
One of the anticipated features with Windows Mobile 5 is the "Blackberry-like" push email capability. This capability does NOT exist with the current Windows Mobile 5 devices, and it requires two components. First is Exchange 2003 Service Pack 2, which has shipped in the last couple of months, and second is the Messaging and Security Feature Pack (MSFP) that needs to be installed on the devices, and will only be available via device manufacturers. MSFP is scheduled to be available early 2006. Note that it will require an installation on the device. (MSFP targets enterprise requirements such as the messaging feature described here, and over-the-air erase of devices.)
Those that prefer Blackberry or Good Technologies will note that this new capability is not truly push. Windows Mobile 5 devices will initiate the request for updates by sending an HTTP request to the Exchange server. (This is how Outlook Web Access and RPC over HTTP work today.) During the time that that the Exchange server is processing the request, the server will notify the device that new items have arrived and then the device will initiate a synchronization of the folders in which the items are contained.
In the end I believe this argument is all about semantics. What matters is whether or not one receives updates on the device in a timely manner. Regardless of the process, if I compare a Blackberry to Windows Mobile 5 and both devices receive email in about the same amount of time, end-users will be happy.
The Microsoft solution requires fewer components for the overall service. Blackberry requires additional servers, Blackberry Enterprise Servers (BES), on the comporate network. BES monitors mailbox folders of Lotus Domino and Microsoft Exchange servers, and when new items arrive it grabs a copy, and sends them to the Blackberry Network Operations Center (NOC). The NOC provides the bridge between the Blackberry devices and the corporate email server. The NOC does the important task of keeping track of devices so that whenever new mail arrives, it is sent. The devices, in turn, are keeping in constant contact with the NOC so that the NOC knows that the devices is available to receive mail. This is why if you have a Blackberry you will see it constantly polling.
Another dependency in the Blackberry solution is the interface between the mobile provider networks and the Blackberry NOC. In essences what happens is that the device communicates on the providers network, the provider network routes to the NOC, the NOC sends email that it receives from BES. If you have Blackberry service provisioned by T-Mobile you can't then just move the device over to Cingular (soon to be AT&T) and expect Blackberry to work. Rather Cingular has to set up your device to work via it's connection with the Blackberry NOC. (In contrast, take an unlocked GSM/GPRS device replace the T-Mobile SIM with a Cingular SIM and the e-mail service will work, completely within the control of an end user.)
The NOC is at the heart of the threat to people losing their Blackberry service due to the patent infringement case. If required by the courts, RIM will have to shut off the NOC, which will effectively shut off the Blackberry service.
Microsoft's solution does not have a NOC nor does it have separate servers like BES. All you need is Exchange 2003 SP2 and devices provisioned with MSFP. Clearly these are fewer components for systems administrators to maintain and that will make it an appealing solution to corporations. The service will be entirely within a company's control, and companies won't be at risk of having the service disabled if the NOC is offline either intentionally or due to an outage.
Have a look at this Thread - Its about a Outlook-Transfer that uses Imap-idle
The Beta looks quite good.
m.zielinski said:
Have a look at this Thread - Its about a Outlook-Transfer that uses Imap-idle
The Beta looks quite good.
Click to expand...
Click to collapse
????? at wich Thread?????
http://forum.xda-developers.com/viewtopic.php?p=211074#211074

BB Connect

BB Connect with TMO Dash - repost in the correct forum
Hi All,
I am trying to replace my company issued BB 7520 (Nextel) with a T-mobile Dash. (my personal cell)
-I have downloaded the BB Connect Cab file to the Dash and installed. Ver2.1.2.39
-I have downloaded the BB Connect for Windows Mobileto my desktop and synched the Dash ver 2.1.1.9.
- I synched my Dash, it recognized the new PIN and I created a new encryption key
- I have called Tmo and had them add the BB service to my account.
The Dash is connecting to the TMO BB Network. The identity, Status Services and IT Policy all look OK.
However, I cannot send or receive emails, and my calender is not synching. I have turned off Calender synch in Activesynch. I don't have Activesynch synching anything.
Am I missing something? When I run the BB Connect Desktop for Windows Mobile, I only get panel that looks like the redirector settings on the BB Desktop Manager.
Do I need to run the Desktop Manager when I run the BB Connect for WM?
Thanks in Advance
James
I haven't been able to get BB Connect on my Excaibur afterthe first restart of the device. It does work though if I deselect the radio button for wireless PIM. Anyone know why this (I think the BBconnect service is CICAL) is preventing BBConnect from working?
Help, I am lost now.. I had BB Connect work on my Dash, then I flashed the ROM. I have BB installed and I can receive all my emails no problem, but I can't create new or reply to emails the action is greyed out. Since this is the only way I can email I really need to get this working.
Please help!!
Thanks
I fixed it, I just had to send a service book to my phone and everything works now..
"Tmobile" Dash and BB Connect Problems Please help
I have bb connect (smartphone edition) on my dash with the blackberry plan on my account.
It works great alot better then the trigger system !
I have a issue with the internet not working properly it is really slow I have to suspend the bb connect to get it to work normal ( pain in the butt )
And also my mms messages come in as a text that directs me to a web link as instead of downloading the pictures
Any help I know a couple other people posted this issue but there was no fix
Please help Thanks
****UPDATE*****
Fixed the mms messages not coming in.
The problem was I selected the blackberry 8100 on my tmobile account so I can add the blackberry and set it up. Once I switched it to the dash. The picture messages come in just fine.
Any one out there that can help with the slow internet problem ?
Was the slow Internet problem ever figured out? I installed BB Connect 4.0 and im noticing the same problem too.
disable the bb connect when ur using the internet through status in the bb connect menu...and when u finished surfing just enable it again( disabling it is not closing it...its just suspends until ur ready to use again)
Blackberry Connect using BIS (not BES) on WM6, possible?
I am using a Rogers S621 Excalibur (Carrier, CID, & App unlocked).
On my phone I am running WM6 standard 5.2.1238 (Russian ROM)
On my computer I am running Vista.
I do have a BB Connect data plan on my account.
I have installed the BB Connect software seen here:
http://www.sems.org/entry.asp?ENTRY_ID=228
and here: http://www.sems.org/entry.asp?ENTRY_ID=225
If I try to run the Blackberry Connect Desktop for Windows Mobile it begins to start up and then says "The account is not provisioned properly on the server" and then shuts down. I don't think that is an issue as I believe the desktop client is only for BES.
On my phone when I try to select the BB Connect app and select Register now it says:
Blackberry: Not Connected
Blackberry: Network Available
Blackberry: Data Tunnel Available
Blackberry: Not connected
On the BIS (www.rogers.com/bis) when I select "Change Device" and then enter my PIN & IMEI (found on my phone by selecting Blackberry>Settings>Identity ) it says: "The information you have provided could not be verified. Please check your information and try again".
On my phone when I select Start>Blackberry>Settings>Email Settings it says "Email settings unavailable".
What have I done wrong, or what can I try?
bb connect dont work with wm6...i had it on wm5 but once i updated the rom to wm6 it stopped..happened to all of us.. some ppl got it to work by editing stuff ...but thats jsut too much to go through
My HTC S621 is running BBC for WM5 under WM6! It´s ok.
johnmud said:
My HTC S621 is running BBC for WM5 under WM6! It´s ok.
Click to expand...
Click to collapse
What carrier are you on? Rogers?
BES? or BIS?
does this means you are confirming that your S621 is indeed CID & APP unlocked ?? and this is a "software" issue ??
I was starting to get confused with other posts of yours going back & forth not knowing yes or no
http://forum.xda-developers.com/showthread.php?t=322486
&
http://forum.xda-developers.com/showthread.php?t=322486&page=3
UnicornKaz said:
does this means you are confirming that your S621 is indeed CID & APP unlocked ?? and this is a "software" issue ??
I was starting to get confused with other posts of yours going back & forth not knowing yes or no
http://forum.xda-developers.com/showthread.php?t=322486
&
http://forum.xda-developers.com/showthread.php?t=322486&page=3
Click to expand...
Click to collapse
What are you talking about? When was I "going back & forth"?
And why are you rolling your eyes at me?
And wasn't it a "software" issue the whole time? It certainly wasn't a hardware issue.
crazygman said:
I fixed it, I just had to send a service book to my phone and everything works now..
Click to expand...
Click to collapse
How did you know that the service book transfered to your handset? I did the same but there were no new service books.
BB Connect 4 and WM6
I've just installed BlackBerry Connect 4.0 on my T-Mobile Dash with WM6. It works like a charm...!!!.
Regards.
Pedro.
Hi, in order for the BB connect to work on the Dash you have to have the BB data plan through your carrier. After you install the cab, go to your website where you can manage your device, pick a blackberry as your current device and then you can send the service books. You can also call your company and ask them to send the, just tell em your using a pearl or something. ANy way after that make sure you update the pin and then your good to go. Oh by the way the current US smartphones cant multitask APN's so you will not be able to access the blackberry.net apn for mail and the wap apn for internet at the same time. In order to use the internet you must suspend the bb connect software. I have a .cab for for smartphones which works if you want one. It was designed for the dash, excalibur, etc. It works great.
cellfonejoe said:
Hi, in order for the BB connect to work on the Dash you have to have the BB data plan through your carrier. After you install the cab, go to your website where you can manage your device, pick a blackberry as your current device and then you can send the service books. You can also call your company and ask them to send the, just tell em your using a pearl or something. ANy way after that make sure you update the pin and then your good to go. Oh by the way the current US smartphones cant multitask APN's so you will not be able to access the blackberry.net apn for mail and the wap apn for internet at the same time. In order to use the internet you must suspend the bb connect software. I have a .cab for for smartphones which works if you want one. It was designed for the dash, excalibur, etc. It works great.
Click to expand...
Click to collapse
I am using 2.1.2.39 and I can get the software running, where I seem to have the problem is with the service books. TMO has another PIN and IMIE number and will not let me change it.
I can send a new service book but they are not showing up on the handset.
BB Connect 4.0 not working on WM6
Hi there,
I have my HTC S621 from Rogers with Blackberry plan and recently upgraded to WM6. When loaded with BBC 4.0. It will not connect (works well under WM5). I have seen some ppl say it works and some ppl say it does not work.
Not sure if there is a way to fix it ?
Here is the info of my HTC:
ROM: 1.27.405.1
WM6 CEOS: 5.2.1238 (build 17745.0.2.3)
radio : 4.1.13.44_02.94.90
Thx.
BB Connect question: Is it possible to change (or get a different) PIN?
Long story short, my BIS won't accept my PIN and tech support has no idea why, so changing my PIN or getting a new phone seem to be my only options.

Categories

Resources