[jeroen_13]

With all these problems i am just staying on .358, cant understand how RIM keeps on messing up again and again.
No wonder people dont buy these things.

Is there a tutorial somewhere on here that describes installing the os with offline files (.358).

Thanks.

RIM pulled out the .668 update already for about 3weeks now

[twdawson]

RIM pulled out the .668 update already for about 3weeks now

I was on about .358 not .668

[DOCTOREVIL8]

I would like to blame RIM for this issue but really only developers have the right to complain. The Beta release was never intended for regular users. USE AT YOUR OWN RISK is the warning we've all been given and ignored by most. There is a workaround available to get back to .668 but because of the Beta risk that is as low as you can go for now.

[twdawson]

So if you put the beta on then you cant go back to .358, is that right?

[DOCTOREVIL8]

So if you put the beta on then you cant go back to .358, is that right?

I would say that is an accurate statement. I haven't found information to prove otherwise. .668 is lowest I have been able to downgrade to since the .840 Beta.

Sent from my BlackBerry 9900

[twdawson]

Then that makes me even more determined to stay away from beta software and i will wait for a couple of weeks before doing anymore os updates.
I am on .358 and staying there.

[DOCTOREVIL8]

I would say that's a wise and safe choice. For me, I didn't appear to have issues with .668, so I am happy to have that as an option. .840 was fun to play with and to see where 2.1 is headed, but I myself would prefer to stick with "released" software. Here's hoping another release comes sooner then later.

Note: This is my 100th post. I'm an "abuser" now! Yeehaw!

[twdawson]

I didn't have problems with .668 as well but i could not take any chances, so thats why i went back to .358.

[HookerOne]

I was stuck with the 'Unspecified error encountered [A:0x000000A2]' trying to 'debrick' and couldn't get anywhere. @b1g1an came to the rescue with this suggestion:

"You can only roll back to 668 and as that's been removed and .358 is the latest, I guess that's why the debrick doesn't work. Just download cfp and a copy of 668 and do it manually, nuke, wipe and reinstall. Did it myself this afternoon and worked perfectly."

It worked perfectly for me too. I gather there were a lot of props with .668 and that's why RIM pulled it and only .358 shows, and won't work trying to roll back from 2.1.0.840.

After process you will have to reinstall Appworld downloads, and Android sideloads, but if it worked before bricking, it will work after this process. Plus, in my case, it also fixed my missing Appworld icon and preloaded wallpapers.

Shout outs to @b1g1an for solving my (multiple) issues with this.

New to all this so is there any chance of some instructions on how to make this happen

[DOCTOREVIL8]

http://forums.crackberry.com/blackbe...61/index2.html

Check out post #21 from the above link.

[pblakeney]

I've not had any problems with 688 on my 16g but now have a 64g I want to transfer all over to. However don't have 688 to put on the 64g to make all compatible and can't downgrade to 358 on the 16g. Would be nice if this was resolved soon like now as we all are stating here.

[HookerOne]

I have followed these instructions but the following happens.

Keep all file in c:\PB
Open cmd type
1, "CD C:\PB"
2, "CFP -U NUKE -A"
3, "CFP -U WIPE"
4, extract the sined file from PB OS keep in same dir
and use commend "CFP LOAD OSNAME"

When I try to carry out step 4 I get the following message

'Error: Can't open file/File not found

The entry I have made is

cfp load qcfm.os.com.qnx.coreos.qcfm.os.factory_sfi.7971.14 8170.signed

Has anyone got any advice that might be able to help me solve this problem as I currently have a bricked PB

[Willard814]

I would like to blame RIM for this issue but really only developers have the right to complain. The Beta release was never intended for regular users. USE AT YOUR OWN RISK is the warning we've all been given and ignored by most. There is a workaround available to get back to .668 but because of the Beta risk that is as low as you can go for now.

Any way to get to .358 from .668 my broweser functionality is almost zero?

[kbz1960]

Yes get the image and use Dingle to install it.

[DOCTOREVIL8]

I tried the 358 image with Dingleberry but no success for me.

[BB_Bmore]

I had a 2.1.0.840 -installed but no android or portrait working. I had to use cfp to go back to.2.1.0.358 and then I whitelisted to 2.1.0.840 and all is well now.

[Willard814]

I didn't have problems with .668 as well but i could not take any chances, so thats why i went back to .358.

What process did you use to downgrade back to .358?

[Graheem]

Here's what worked for me:

Playbook OS changing with cpf/pload (same app I believe, just two names)

Download cfp.exe and PB2.0.1.668.exe (google them I can't remember exactly where I got them)

Then nuke, wipe and reinstall:

Put all files in in a new folder (call it, for example 'pb') on your 'c' drive
Open cmd and type:
1, "CD C:\PB"
2, "CFP -U NUKE -A"
3, "CFP -U WIPE"

Then run (double click) PB2.0.1.668.exe

That's it. You are back to 2.01.668 (if you were up to 2.1.0.840 you can't go back to 2.0.1.358).

Then put on developer mode, and do software update. You will then be back to 2.1.0.840).

The whole process took me about 3 hours I think.

I am totally enjoying my PB with 2.1.0.840, running lots of great PB native apps, and Android sideloads.

Good luck, be patient.

[gheorghita.cristian]

Man I need help

I wanted to go back from 2.1 beta to 2.0.1.6687 and used cpf for that . After "CFP -U NUKE -A" ,which took about 10 minutes to complete, i tried "CFP -U WIPE" but accidentally (forgot) i unplugged the usb cable
Now the red LED is blinking and when trying nuke or wipe i get the line : Connecting to Bootrom: and nothing happens no matter how much time i wait.

Did i just "killed" my PB?

Please help me cause i am desperate!

Thanks

[gheorghita.cristian]

Man I need help

I wanted to go back from 2.1 beta to 2.0.1.6687 and used cpf for that . After "CFP -U NUKE -A" ,which took about 10 minutes to complete, i tried "CFP -U WIPE" but accidentally (forgot) i unplugged the usb cable
Now the red LED is blinking and when trying nuke or wipe i get the line : Connecting to Bootrom: and nothing happens no matter how much time i wait.

Did i just "killed" my PB?

Please help me cause i am desperate!

Thanks

Also BB DM doenst recognise the PB when connected to USB ....

[kbz1960]

Have you made sure it is off? Taken in a dark area? Then try with off plugging in with dm open.

[gheorghita.cristian]

I tried to shut it down but holding the power button did not close the LED ... it is still blinkind 2 short blinks and 1 lon blink..then it repeats..

[gheorghita.cristian]

Wait...i think i did manage tio shut it down eventually ...my finger is alost bleeding...

So..now it is downloading the x.0.358 .... hope it works...last time (before i tried cfp) i ended up in error ...

[kbz1960]

Good luck!

[gheorghita.cristian]

and after 5 minutes of downloading its back to where i started in the beginning :

An error has occurred while updating your device's software.

Unspecified error encountered [A:0x000000A2]