1. batkinson001's Avatar
    hey all

    i upgraded to try out the latest beta build of 2.1, now i want to go back to the latest non beta version...

    following the steps from:
    Downgrading From Beta PlayBook OS to the Current N... - BlackBerry Support Community Forums

    does not work for me as the desktop software says that an error has occurred.

    any ideas on how i can get my playbook back to 2.0.1.whatever?
    08-27-12 12:04 PM
  2. DOCTOREVIL8's Avatar
    Find a 2.0.1.668 image and use Dingleberry or cfp to downgrade. There are other threads on this, FYI.
    08-27-12 12:36 PM
  3. BB_Bmore's Avatar
    Same problem and we should not have to use Dingle Berry to go back. There has to be a fix.
    08-27-12 09:16 PM
  4. diegonei's Avatar
    Out of curiosity, did you guys wait 24 hours before trying to debrick?
    08-27-12 09:43 PM
  5. smartie88's Avatar
    hey all

    i upgraded to try out the latest beta build of 2.1, now i want to go back to the latest non beta version...

    following the steps from:
    Downgrading From Beta PlayBook OS to the Current N... - BlackBerry Support Community Forums

    does not work for me as the desktop software says that an error has occurred.

    any ideas on how i can get my playbook back to 2.0.1.whatever?
    BB10 is around the corner, just wait a bit
    08-27-12 09:43 PM
  6. BB_Bmore's Avatar
    Out of curiosity, did you guys wait 24 hours before trying to debrick?
    Yes I did. Actually I have been trying for 3 days now. Although I don't get an error like the OP. I get no updates are available :/
    08-28-12 12:24 AM
  7. BB_Bmore's Avatar
    I'd just leave the beta on my 16 gig but although it says 2.1.0.840, there is no portrait pim apps and android apps won't launch. It sux because I gave it to my wife after I got the 64 and I cannot get it to work properly for her.
    08-28-12 12:26 AM
  8. diegonei's Avatar
    Yes I did. Actually I have been trying for 3 days now. Although I don't get an error like the OP. I get no updates are available :/
    I almost feel like trying >< But I don't wanna mess up with my PB when it's actually working...
    08-28-12 12:36 AM
  9. BB_Bmore's Avatar
    I have cfp writing a older os as we speak. I give up on DM
    08-28-12 02:24 AM
  10. FF22's Avatar
    How easy/hard or error proof or error prone is using this CFP tool in upgrading/downgrading or changing the OS on the pb?
    08-28-12 10:11 AM
  11. Stephen_TX's Avatar
    I'd just leave the beta on my 16 gig but although it says 2.1.0.840, there is no portrait pim apps and android apps won't launch. It sux because I gave it to my wife after I got the 64 and I cannot get it to work properly for her.
    In another thread, I learned how to fix this. Assuming you got to this point by either a Security Wipe and/or DM Update, because your BB ID is tied to 2.1.0.840, it reinstalled that. But it was an incomplete version with an old Android player. Go back to Beta Zone, whitelist your BB again, and wait for Update notification (either it will appear or go to Check for Upgrades option). It will send you the complete 2.1.0.840, and everything will work again.
    08-28-12 10:28 AM
  12. Stephen_TX's Avatar
    In another thread, I learned how to fix this. Assuming you got to this point by either a Security Wipe and/or DM Update, because your BB ID is tied to 2.1.0.840, it reinstalled that. But it was an incomplete version with an old Android player. Go back to Beta Zone, whitelist your BB again, and wait for Update notification (either it will appear or go to Check for Upgrades option). It will send you the complete 2.1.0.840, and everything will work again.
    And, if this doesn't work, do the Security Wipe (as painful as that may be), which will put you back to basic PB. It will then automatically load what it says is 2.1.0.840, but in fact is missing components. Then do the whitelist (you shouldn't have to wait 24 hours on this one). I just did this over the weekend. It gave me a "clean" PB, and even things that weren't working properly when I upgraded to 2.1.0.840 (from 2.0.668) worked perfectly when I re-loaded them, including sideloaded Android apps.
    08-28-12 10:35 AM
  13. DOCTOREVIL8's Avatar
    The problem lies with the 'pulled' 2.0.1.668 OS. The Beta 2.1.0.840 can be debricked back down to 2.0.1.668, but only if 2.0.1.668 was the latest release. Since it was 'pulled', 2.0.1.358 is the latest release and messes up the debricking. Therefore CFP or Dingleberry is the only way to drop back from the Beta. I guess it all depends on the next 'official' release to solve this problem. Will it be a newer 2.0, or 2.1? I'm fairly confident whichever it is will resolve this problem.
    08-28-12 10:44 AM
  14. Stephen_TX's Avatar
    The problem lies with the 'pulled' 2.0.1.668 OS. The Beta 2.1.0.840 can be debricked back down to 2.0.1.668, but only if 2.0.1.668 was the latest release. Since it was 'pulled', 2.0.1.358 is the latest release and messes up the debricking. Therefore CFP or Dingleberry is the only way to drop back from the Beta. I guess it all depends on the next 'official' release to solve this problem. Will it be a newer 2.0, or 2.1? I'm fairly confident whichever it is will resolve this problem.
    DoctorEvil, that's what I faced too. I had backed up 2.0.1.668, but it was gone when I decided to step back. But a clean 2.1.0.840 is working beautifully. I does give me a bit of concern that I may have to do a wipe again on formal release of 2.1, but I guess that's the risk of playing in the Beta world!
    08-28-12 10:54 AM
  15. DOCTOREVIL8's Avatar
    Now, the "magic" question.... After performing this downgrade from 2.1.0.840 to 2.0.1.668, what happens if a security wipe is performed? What version of OS is reloaded at setup, and is it complete?
    08-29-12 08:18 AM
  16. DOCTOREVIL8's Avatar
    Answered my own question. After downgrading from Beta .840 to .668, I performed a security wipe to see what would happen.

    I'm happy to announce that during the OS update portion of the Setup, the Playbook downloads and installs 2.0.1.668 without issue.

    Sent from my BlackBerry 9900
    08-29-12 09:11 AM
  17. kbz1960's Avatar
    So we should be seeing an official 2.1 in sept? Last day?
    08-29-12 09:22 AM
  18. Stephen_TX's Avatar
    Now, the "magic" question.... After performing this downgrade from 2.1.0.840 to 2.0.1.668, what happens if a security wipe is performed? What version of OS is reloaded at setup, and is it complete?
    I'm not sure I want to find out! I'm just hoping that when the official 2.1 is released, it will neatly upgrade the 2.1 Beta. I'd hate to start over...
    08-29-12 03:13 PM
  19. Stephen_TX's Avatar
    Answered my own question. After downgrading from Beta .840 to .668, I performed a security wipe to see what would happen.

    I'm happy to announce that during the OS update portion of the Setup, the Playbook downloads and installs 2.0.1.668 without issue.

    Sent from my BlackBerry 9900
    I just saw this after answering your first comment. So you used Dingleberry to get back to .668, but once that was "locked in", when you officially updated, it "found" the full .668 and downloaded?
    08-29-12 03:16 PM
  20. DOCTOREVIL8's Avatar
    More or less. When I Dingleberried back to .668, I tried a security wipe just to see what would happen. (Owning 2 Playbooks gives me comfort if I seriously screw up.) On the initial setup it performed the usual update. The Playbook was sitting at 2.0.1.668 when all was said and done. I still cannot downgrade lower though.
    08-29-12 04:56 PM
  21. DC506's Avatar
    My problem was the wipe I did on 840. After doing so, I lost my android player. I am not looking to downgrade, I just want a fully functional 840 back. Even after re-registering, wiping again, and running DMs update again, (2.1.0.840) still doesn't fix it.

    The big question is "Why does a security wipe, mess up 2.1.0.840?"
    08-29-12 05:26 PM
  22. DOCTOREVIL8's Avatar
    I wish I could answer that question. The only thing I can think of is the 840 update is looking for previous versions of certain components to upgrade. After a wipe, those components don't exist so it doesn't perform an upgrade completely. That's my story and I'm sticking to it.

    If you want to run a 'good' .840, my recommendation is to downgrade to .668 (this will get everything working), re-register for the Beta and upgrade back to .840. That's how I recovered from the security wipe problem you are encountering.

    Sent from my BlackBerry 9900
    08-30-12 07:21 AM
LINK TO POST COPIED TO CLIPBOARD