Page 1 of 3 123 LastLast
Results 1 to 8 of 23

  1. #1
    Klypr is offline BlackBerryOS Enthusiast
    Join Date
    Mar 2009
    Device
    9530
    Posts
    57

    Trouble With All 5.0 OS's and Activating on BES *Experienced BES Admins Apply Within*

    So I'm no stranger to leaked OS's on blackberries and have done many successful installs over the years, but I've run into a problem I cannot solve and need the assistance of a few more brains to help me figure it out.

    I am running on a BES v4.1.6.23 (ugh I know) and am able to use both the 4.7.1.40 and .53 OS's without any problems. Whenever I install any of the 5.0 OS's and begin the BES activation, my device starts to randomly reboot every 5 or 10 minutes. This only starts to occur after I begin the activation process as I have left the install alone for over an hour with no problems before attempting to activate. When I check my device logs on the BES, it seems like whenever the IT policy starts to apply is when the reboots are occurring. My first thought was obviously that the older versions of BES are not compatible with 5.0 handheld software however, I cannot find this information anywhere. Then I figured they are using different types of encryption but that does not seem to be the case as both use AES.

    This is really frustrating me as I hate being behind the times when a new OS is out there and everybody raves about how good it is. Below is some additional information that will answer the obvious questions.

    Yes, I deleted the vendor file.
    Yes, I uninstalled Internal Tools.
    Yes, I wiped with JL_Cmdr and loaded the OS fresh.
    No, I am not installing any third party software.
    The only features I'm loading are BBM, DocsToGo, Memopad and Taskpad. My BES does not require S/MIME.
    We run 2 BES' with a total of about 900 users and, to the best of my knowledge, I am the only one trying to activate with a 5.0 OS.

    Any help or information on why this is not working and what I would need to do with the BES to correct it (other than upgrade to 5.0) would be much appreciated.



  2. #2
    olta777 is offline BlackBerryOS Wizard
    Join Date
    Apr 2009
    Device
    VZW Droid
    OS
    Custom ROM
    Posts
    4,702
    I would also recommend doing a security handheld wipe. Make sure you back up first (phone and apps), then go to options> security options> handheld wipe/security wipe.

    As far as BES specific issue, I will let others answer this for you since I am not familiar with it.

  3. #3
    Klypr is offline BlackBerryOS Enthusiast
    Join Date
    Mar 2009
    Device
    9530
    Posts
    57
    Yeah I did a wipe via the security options but that does not clear the IT policy set by my BES. JL_Cmdr performs a lower level wipe of the device and clears some of the IT Policies but not all of them. Regardless, the problem does not seem to be with the IT policy in place on my handheld, only when it is pushed during activation.



  4. #4
    shockaholic's Avatar
    shockaholic is offline BlackBerryOS Friend
    Join Date
    Apr 2009
    Location
    Carlsbad, CA
    Device
    9550 & Droid
    OS
    5.0.0.428
    Posts
    15
    I had a similiar issue a while back on BES 4.1 using OS 5 on my 9530. I ended up clearing the PIM data for myself off the BES and that solved the issue. The BES pretty much backs up all of the security settings and application settings along with the contacts and calendar. For some reason, the restore of the backed up data from a 4.7.x OS does not mesh well when restored on a device running a 5.0.x OS on BES. I have probably 15-20 users that I have installed the 5.0 OS and haven't had any issues. I have done this with 9530's, 9630's and even the 8330 since the latest leak. I have not had any issues or have any of the end users. We are running the same version of BES as you with Exchange 2003 with about 100+ users.

  5. #5
    jnepsa's Avatar
    jnepsa is offline BlackBerryOS Wizard
    Join Date
    Apr 2009
    Location
    ohio
    PIN
    ch me then
    Device
    9550 Storm 2
    OS
    5.0.0.428
    Posts
    4,387
    Quote Originally Posted by Klypr View Post
    So I'm no stranger to leaked OS's on blackberries and have done many successful installs over the years, but I've run into a problem I cannot solve and need the assistance of a few more brains to help me figure it out.

    I am running on a BES v4.1.6.23 (ugh I know) and am able to use both the 4.7.1.40 and .53 OS's without any problems. Whenever I install any of the 5.0 OS's and begin the BES activation, my device starts to randomly reboot every 5 or 10 minutes. This only starts to occur after I begin the activation process as I have left the install alone for over an hour with no problems before attempting to activate. When I check my device logs on the BES, it seems like whenever the IT policy starts to apply is when the reboots are occurring. My first thought was obviously that the older versions of BES are not compatible with 5.0 handheld software however, I cannot find this information anywhere. Then I figured they are using different types of encryption but that does not seem to be the case as both use AES.

    This is really frustrating me as I hate being behind the times when a new OS is out there and everybody raves about how good it is. Below is some additional information that will answer the obvious questions.

    Yes, I deleted the vendor file.
    Yes, I uninstalled Internal Tools.
    Yes, I wiped with JL_Cmdr and loaded the OS fresh.
    No, I am not installing any third party software.
    The only features I'm loading are BBM, DocsToGo, Memopad and Taskpad. My BES does not require S/MIME.
    We run 2 BES' with a total of about 900 users and, to the best of my knowledge, I am the only one trying to activate with a 5.0 OS.

    Any help or information on why this is not working and what I would need to do with the BES to correct it (other than upgrade to 5.0) would be much appreciated.
    Do you IT's have a password on the BES? If so the passwords have not been playing well with the newer 5.0 builds.. It seems almost every user with reboots has a password.



  6. #6
    miiike is offline BlackBerryOS Friend
    Join Date
    Sep 2009
    Posts
    39
    Whenever I run into activation problems clearing the PIM Sync on the user usually fixes the problem.

    I haven't had any issues activating any 5.0 devices (8330, 9630, a couple of both, 5.0.0.230) on my BES, however I didn't do any until I was at 5.0 MR1, either.

    I would start there, with even goin as far as deleting the user and re-creating them on the BES to see what happens.

  7. #7
    Klypr is offline BlackBerryOS Enthusiast
    Join Date
    Mar 2009
    Device
    9530
    Posts
    57
    Quote Originally Posted by miiike View Post
    Whenever I run into activation problems clearing the PIM Sync on the user usually fixes the problem.

    I haven't had any issues activating any 5.0 devices (8330, 9630, a couple of both, 5.0.0.230) on my BES, however I didn't do any until I was at 5.0 MR1, either.

    I would start there, with even goin as far as deleting the user and re-creating them on the BES to see what happens.
    Yeah, I was hoping I could find a fix without deleting my profile. I'll try clearing out the PIM sync first and come back to let you know if it works. Thanks.
    Posted via BlackBerry device

  8. #8
    TemperamentalMan's Avatar
    TemperamentalMan is offline BlackBerryOS Addict Follow TemperamentalMan On Twitter
    Join Date
    Aug 2009
    Location
    Raleigh, NC
    PIN
    's and nee
    Device
    9550
    OS
    5.0.0.607
    Posts
    937
    I'm not trying to jump on anyone's toes, but have you tried:

    launcher /resettofactory

    from the command line?

    That removes all IT policies set in place by the BES server. Your profile will have to be re-initiated (with a new password) unless the current password is less than 48 hours old.

Page 1 of 3 123 LastLast

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •