1. kbz1960's Avatar
    Well maybe cfp or dingleberry will work if off?
    09-01-12 08:36 PM
  2. DC506's Avatar
    Have you considered Dingleberry? Just place the 668 file into the CUSTOM folder and tell Dingleberry to use a Custom install, Full OS. Easy. Worked for me. (need to be in development mode)
    Thanks for the heads up about using Dingleberry to roll back to 668. It worked perfectly (including the Android player). I'll stay at 668 for now.
    09-02-12 10:18 AM
  3. gheorghita.cristian's Avatar
    Hi guys

    So...I managed to wipe the PB with CFP wipe...i downloaded PB2.0.1.668, i double clicked it in order to install and i receive the error : Invalid image.Internal error.

    With Dingleberry had no chance because Dingleberry needs a working PB OS installed in order to set developer mode on, etc.

    Any ideas?
    09-02-12 12:00 PM
  4. DC506's Avatar
    Did you change the format of your 668 file from .bar to .zip?

    Read z3000w's post #21 below

    http://forums.crackberry.com/blackbe...61/index2.html
    Last edited by DC506; 09-02-12 at 12:29 PM.
    09-02-12 12:16 PM
  5. gheorghita.cristian's Avatar
    Did you change the format of your 668 file from .bar to .zip?

    Read z3000w's post #21 below

    http://forums.crackberry.com/blackbe...61/index2.html
    Thanks DC506 and kbz1960 ! I have 2.0.668 up and running !

    The post above did the job !
    09-02-12 03:29 PM
  6. roars1111's Avatar
    As I said in my post, the starting material ......... I tried to go back to 2.0.1.358 BlackBerry with both DM and both CFP which operate a device with a double flash of red.

    I have also tried to down grade with dingleberry 2.0.1.358 full operating system and when you restart the PB still the same operating system as I started.
    09-03-12 01:52 AM
  7. joannesbenedek's Avatar
    Guys, you can try this, though I havent tested it but it might work. Try command erase.
    I dont remember which address it was but it will delete OS completely.

    1. cfp erase 0x80000000 (dont worry about address, it will not erase it as pb is secured device and there is only two regions that can be erased)
    2. cfp will say which region is not secured and can be safely erased.
    3. use one of that address, it doesnt brick pb dont worry, I dont remember which one is for the os, but try both until you get from ''cfp info'' no os installed.
    4. cfp load 2.0.1.358.signed (Of course you can upload also 2.0.1.688 if you want...or anything up to 7111...anything below wont boot up)
    5. should boot up

    If someone has problem running cfp right away when connected to usb, I have a trick to get connected to bootrom always. Run BBDM and try to do debrick method until it ask about upgrade now or later. Have cfp ready and press enter, when you see on cfp that it says connecting to bootrom, pres on BBDM upgrade later. It will then connect to bootrom using cfp. Works nearly always for me.

    Also if you disconnect accidentaly cable before cfp is finished doing its job, dont worry, happend to me and I did it on purpose many times. Just run it again.

    PS: make sure when you extract the signed file rename it to smt short like 2.0.1.358.signed (dont leave that horrible long name unchanged) and put it in the same folder as cfp.
    Last edited by joannesbenedek; 09-03-12 at 11:03 AM.
    FF22 likes this.
    09-03-12 10:58 AM
  8. BB_Bmore's Avatar
    I used cfp to wipe and then load the previous 2.1 beta. I then whitelisted to the latest 2.1 beta ,upgraded and all is well. PlayBook is running great. portrait mode is back and Android apps launch again.
    09-03-12 11:12 AM
  9. Kaiser2000's Avatar
    Hey all,

    I upgraded to .840 beta and then security wiped it tonight to try and downgrade back to .358 - no joy.. comes back up with a "blank" .840 and downloads a 344MB update which at least puts the apps back on.

    But like everyone else in this thread, the Android apps won't run. I've re-registered with the beta, waited an hour and did another security wipe.. same thing as above.

    Any ideas? Can I just get the android runtime and install it manually or am I gonna have to wait until .840 goes final, or till .850 comes out?

    I'm new to the Blackberry side of things (am used to Android rooting etc though) so not sure of some of the stuff above (cfp etc?) Is there a step-by-step with the files needed and instructions?

    Cheers!
    Last edited by Kaiser2000; 09-08-12 at 03:35 PM.
    09-08-12 03:33 PM
  10. kbz1960's Avatar
    Have you wiped, shut it off not going thru the setup. Be signed up for the beta. Open dm plug pb in while off, choose update and or repair?
    09-08-12 03:44 PM
  11. Kaiser2000's Avatar
    Have you wiped, shut it off not going thru the setup. Be signed up for the beta. Open dm plug pb in while off, choose update and or repair?
    Gave that a shot now.. (twice)

    It gets as far as offering the 358 update, downloads it, extracts and fails with an "Unspecified error" ending in A2...

    The PB then fires up itself and starts offering the Setup again - but it's still on 840
    09-08-12 04:17 PM
  12. kbz1960's Avatar
    Yep I think the same happened to me. I used Dingle and the .668 image and is what I'm using now.
    09-08-12 04:20 PM
  13. Kaiser2000's Avatar
    Yep I think the same happened to me. I used Dingle and the .668 image and is what I'm using now.
    Well I re-registered again for the beta following this thread...

    Can't downgrade OS to 2.0.1.0.358 from beta 2.1.0... - BlackBerry Support Community Forums

    ... and as we speak its downloading a smaller (317MB) version of 840.

    Fingers crossed...
    09-08-12 04:36 PM
  14. Kaiser2000's Avatar
    Well I re-registered again for the beta following this thread...

    Can't downgrade OS to 2.0.1.0.358 from beta 2.1.0... - BlackBerry Support Community Forums

    ... and as we speak its downloading a smaller (317MB) version of 840.

    Fingers crossed...
    ... annd it worked! Thanks for the assist
    09-08-12 06:37 PM
  15. Yamcha's Avatar
    Sigh, I upgraded a while back as well but unable to restore back to OS 2.0.1.. I wish RIM would do something about the Desktop Software, in my opinion It's pretty bad.. Getting it to recognize my Playbook takes longer then it should..
    09-09-12 07:05 PM
65 123
LINK TO POST COPIED TO CLIPBOARD