[kretch]

Playbook is all goobered up.......

I installed 2.1.0.840 and now I can't downgrade back to 2.0.1.358.

Using CFP .358 installs but PB never boots up, it has a black screen and a double red light blick. I guess this is what they call bricked.

With BB desktop it downloads file and when it tries to install .358 I get an error "Unspecified error encountered [A:0x000000A2]" and then the double red light blick.

Playbook will permit a downgrade using CFP to 2.0.1.668. I can also upgrade back to 2.1.0.840 and 2.1.0.560 but there are issues with a few apps not working or I would stay on them.

Anyone else have the same downgrade issue???

Whats up with this issue??

.

[FF22]

First, how recently did you register for and download/install the beta? It can take 24 hours or more before the server will give you back the standard OS.

If is is now working, try debrick again with Desktop Manager after at least 24 hours of beta.

[kretch]

I updated the day 2.1.0.840 came out, so thats 5 days now.

The server did give me back the standard 2.0.1.358 but it fails with an error. I even used a debrick file and CFP but it will not reboot. Just red double blink.

I even tried Dingleberry to down grade from 2.0.1.668 to 2.0.1.358 and when It restarted it was still 2.0.1.668.

Anyone else got any thoughts?


.

[HyTrojan]

Playbook is all goobered up.......

I installed 2.1.0.840 and now I can't downgrade back to 2.0.1.358.

Using CFP .358 installs but PB never boots up, it has a black screen and a double red light blick. I guess this is what they call bricked.
With BB desktop it downloads file and when it tries to install .358 I get an error "Unspecified error encountered [A:0x000000A2]" and then the double red light blick.

Playbook will permit a downgrade using CFP to 2.0.1.668. I can also upgrade back to 2.1.0.840 and 2.1.0.560 but there are issues with a few apps not working or I would stay on them.

Anyone else have the same downgrade issue???

Whats up with this issue??

.

I did the exact same thing and I got the same error code to the letter. Same two red led blinks is all I get.

[HyTrojan]

I had to get me a new 64 at office Depot yesterday. Price was 249.00 and I was okay with that. Guess I will keep my 16 as parts.

[kretch]

Is your PB now not usable because of this?
Mine was until I loaded 2.0.1.668 with cfp and now everything is fine.
You should try that.

[HyTrojan]

I will be on the lookout for a copy of 2.0.1.668 and try loading it.
Thanks

[xocox]

kretch is right, it appears that upgradin to last betas only allows to back to closer previous ones

[Sith_Apprentice]

What method are you using to downgrade? Are you using DM or are you using the debrick method (reboot the Playbook while it is connected to DM).

CFP is usually something that shouldnt be messed with, as doing things incorrectly can result in a dead device.

[kretch]

As I said in my starting post......... I have tried to revert back to 2.0.1.358 using both BlackBerry DM and CFP with both resulting in an inoperable device with a double blinking red LED.

I have also tried to down grade to 2.0.1.358 using dingleberry full OS and when the PB reboots it is still has the same OS that I started with.

.

[Sith_Apprentice]

kretch, I am talking about the DM normal downgrade, or DM debrick method.

[kretch]

Used the Debrick method.


.

[Sith_Apprentice]

Do you have other OS's on your machine, or just the latest one? Its stored in a data directory when it is unzipped etc from DM.

[kretch]

I remove them from the research in motion folder that DM gets its data from to a storage drive. I have a copy of all of the past OS files as well on my storage drive.

.

[ubik17]

I have had the same problem.

With BB desktop it downloads file and when it tries to install .358 I get an error "Unspecified error encountered [A:0x000000A2]" and then the double red light blick.

I have used the DM normal downgrade
I have registered my playbook in beta zone again and I have repeated the installation of playbook OS 2.1.0.840. Instalation was successful. Sorry for my English.

[CanadianBB]

I have had the same problem.

With BB desktop it downloads file and when it tries to install .358 I get an error "Unspecified error encountered [A:0x000000A2]" and then the double red light blick.


I now have an unusable 64 GB Playbook.

Brian

[kbz1960]

I have had the same problem.

With BB desktop it downloads file and when it tries to install .358 I get an error "Unspecified error encountered [A:0x000000A2]" and then the double red light blick.


I now have an unusable 64 GB Playbook.

Brian

If you register again for the beta wouldn't it install it with no trouble? At least you would have a working pb.

[Graheem]

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.

[715dixon]

If you register again for the beta wouldn't it install it with no trouble? At least you would have a working pb.

Yes, reinstalling Beta ver. 2.1.0.840 has given me back a working tablet with 2.1.0.840on it and the beta version hasn't been giving me any problems. But like one of the other earlier authors I took advantage of the Staples sale on the 64GB model intending to put my 16 GB Playbook up on Ebay and then discovered the A:0x000000A2 error trying to downgrade to 2.0.1.358 when the 16 GB tablet had been on 668 before installing the beta version. So my question is what happens when there is a new "official" version of the OS either 2.01 or 2.1 either the OTA update process or the debrick process likely to let my tablet move to the next "official" version?

[DC506]

I was running 2.1.0.840 and did a wipe. Big mistake, because now none of the Android apps will open. When updating (debricking) with DM, I get the same error as everyone else. I did re-register for the beta, then wiped again, installed the update (2.1.0.840). And have a working PB again, but still no working android player.

This whole CFP thing seems a little daunting, I might just have to wait for a new update.

[DOCTOREVIL8]

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)

[kbz1960]

RIM f'd this one up again. Will it be another year?

[FF22]

RIM f'd this one up again. Will it be another year?

Just around the corner. A year, two years, three or more!

[DC506]

I have to do some reading on Dingleberry I guess.

[twdawson]

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.