[san1234]

Ive have installed a leak version of 10.3.2 on my bb z10. nd m finding some problems with my phone. can i again go to the official version of os for my phone? if no can anyone plzz solve my phone's prob.

[KemKev]

Nope; there is no going back (as has been mentioned in several of the 10.3.2. threads).

I don't know which version of 10.3.2 you installed, but you can check out the Findings & Fixes threads below to see if you find solutions to whatever problems you are having.

http://forums.crackberry.com/bb10-le...fixes-1014364/

http://forums.crackberry.com/bb10-le...680-a-1018180/

[RLTurn77]

I thought that with 10.3.2 you could go back, but would have to go back to 10.1 or something crazy old then upgrade from there? I believe somebody has done this.

I haven't messed with any of the 10.3.2 leaks mostly because of this and because there is nothing groundbreaking in 10.3.2 whereas going from 10.2.1 to 10.3.1 was basically like getting all new devices. I'll wait until it's official, and even then, I'd have to see what new features there are as my Z10, Z30, and Passport are all perfect on 10.3.1 (and the going back issue).

Posted via CB10

[LostOnThePianoRoll]

From 10.3.2.500 you can return to 10.2.2.. but you can't upgrade to 10.3.1 because the block list is hard wired.

If you're on 10.3.2.640 you're stuck... you're only bet to get your phone working right again is to reload 10.3.2.640 with an autoloader.

Posted via CB10

[joeldf]

I thought that with 10.3.2 you could go back, but would have to go back to 10.1 or something crazy old then upgrade from there? I believe somebody has done this.

Posted via CB10

No. No one's been able to do that. As noted, with 500, you could only go back to 10.2.2, and one very early 10.3.1 developer build that somehow was missed in the block list. But you couldn't go beyond either of those. Only back to to 10.3.2.500 or newer.

Posted via CB10

[RLTurn77]

Thanks for the info. I stand corrected. Didn't realize you could only go back to 10.2.2 and not be able to update to 10.3.1.

That answers the original question. The OP could try to reload the OS (or another version of 10.3.2?) or go back to 10.2.2.

Posted via CB10