[spblat]

I'm investigating a wifi issue with my 8320, and part of the process has been to wipe the device and re-activate. This has not gone well: once I stuck at 11% for an hour or two, then I wiped again and got stuck at 0%. One last time I wiped, and I'm still stuck at 0% activation. I have two bars and EDGE, and my browser gives me access to my company's intranet. So I have connectivity.

Any suggestions for troubleshooting or fixing this problem? Must I involve my BES administrators?

[spblat]

Anyone? Going out of my mind here. Am I asking the wrong forum?

[hdawg]

What happens if you disable wifi? Sorry, I dont have a sassy new 8320 :(

[spblat]

I've kept wifi disabled since the latest wipe this morning. At the moment I'm receiving and sending e-mails over EDGE, but activation is still at 0%, "Synchronizing service Desktop."

ETA: when I first got the device, activation completed successfully.

[mk3013]

You initially asked whether you needed to get BES administrators involved. I don't see how it could hurt. I've had similar problems before. Not sure what they did on their end, but activation went much quicker after the call!

[spblat]

Good advice. My case is most unfortunate: 1) My company is gargantuan; 2) Blackberry team is overworked and understaffed; 3) I've recently upgraded to a new version of our mail client which is not fully compatible with our BIS, so I've been told not to expect BlackBerry support; 4) The security team hasn't certified the 8320, and so my device is basically prohibited.

So there's no good reason to expect this to work. But it *was* working for several days before I went and wiped my #$#$%^@#^ unit. I am so bummed over this: I'm going to end up reverting to the old mail client and my old 8700.

[Ugg]

Unfortunately the information about why activation isn't working will be in the MAGT log on the server. To make it easier for your BES guys you could go to them with the exact times that your pressed the button to start activation, and the exact time that any on-screen changes occurred.

Not that it's relevant to the problem that you're having, but I've noticed (with 4.2.2 on an 8820, both over GPRS and WiFi) that the activation process seems slightly different to 4.1 / 4.2.1 - it gets to 100% complete before the email prepopulation is complete.

Oh - and what email system / version, by the way?

[spblat]

We're using Lotus Notes.

We're running a version of BES that's shy of 4.1.4, but I don't know which.

[John Clark]

It seems like I've heard of issues like that with low signal. Have you tried with better signal?

[spblat]

I have had a low signal for the last few days. Now I'm back home and I have an excellent signal. In fact I've put my SIM back in my old 8700 (and can I tell you what a brick it feels now? man I used to adore my 8700) and am experiencing the very same problem.

Guess I'll be asking my BES folks to peek at the MAGT log.

[John Clark]

How are you starting EA? Are you using DM or OTA with a password? I've been told that OTA with a password is more reliable, but using the DM has usually worked for me. The couple times it hasn't, I just wipe the device, and plug it in again and it usually goes through. Also, I believe that the 8320 needs to be in the device.xml file on the BES. If they haven't updated it you may not be able to activate. I'm not a BES admin so one of them may elaborate or correct me if I'm wrong--just trying to give you some ideas.

[spblat]

Yeah I guess our BES must hate me now. Still no love on the 8700. I've always used the DM because I don't know how to start activation OTA. Maybe I'll play with that for awhile.

[John Clark]

Your BES admin needs to set a password for OTA. You can't start it yourself. You can start it via DM/USB and then when it starts, unplug from the computer and it will finish OTA.

[spblat]

Oh, I see. Yeah, when I switched to the 8320 that's what I did: I got it started using the DM, then unplugged it and watched in smug satisfaction as it finished OTA. Not so smug now!

[spblat]

87% OTA a day later. Patience I guess

[rivettmj]

running 4.1.3HF1 for Domino here ...

Had to install the handheld software on the BES to get the apploader to the latest version. then has to add the 8320 to the Device.xml file (located in the apploader directory)

The firmware install got the 8300 entrie, I had to customize myself an 8320 entry

I was always able to activate the phone (OTA) but I could not push software to the device with out the updated files.

<!-- 8300 -->
<os radio="GPRS" series="8300" Colour="True" Theme="Normal" JVMLevel="1.0" Camera="True" VoiceNotes="True" pttApp="True" Memory="Large" KeyboardType="Qwerty" Sound="Tunes8700g" SystemSize="normal" Bluetooth="True" MMS="True" ThemeSupport="Enhanced" VAD="True" JPN_Input="False">0x96000F03</os>

<!-- 8320 -->
<os radio="GPRS" series="8300" Colour="True" Theme="Normal" JVMLevel="1.0" Camera="True" VoiceNotes="True" pttApp="True" Memory="Large" KeyboardType="Qwerty" Sound="Tunes8700g" SystemSize="normal" Bluetooth="True" MMS="True" ThemeSupport="Enhanced" VAD="True" JPN_Input="False">0x84000F03</os>

[spblat]

Bricked my 8320 messing with themes last night. Did a javaloader wipe and reinstall of the T-Mo OS, and this morning I was fully activated. Go figure.

[John Clark]

That was a tough fix! Makes you smack head and wonder why you didn't try sooner. I hate when that happens!