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.
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.
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.
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.
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.
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?
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..