[AllenLoveBBRY]

I can't reload any os .used cfp or blackberrydesktop its said An error has occurred while updating your device software.Unspecified error encountered[A:0x000000A2] . cant install os 2.1 or os 10.0.9

[diegonei]

Welcome to the forums.

1st of all, try to keep calm. We're gonna try and salvage your PlayBook!

Did you try turning it off and pluging it to Desktop Manager/BB Link? That should prompt an update and force a OS reload.

[antiRIM]

pls help . i cant reload any os .used cfp or blackberrydesktop its said An error has occurred while updating your device software.Unspecified error encountered[A:0x000000A2] . cant install os 2.1 or os 10.0.9

Tell me exactly what you did and I will attempt to recreate it and find a solution.

[AllenLoveBBRY]

Welcome to the forums.

1st of all, try to keep calm. We're gonna try and salvage your PlayBook!

Did you try turning it off and pluging it to Desktop Manager/BB Link? That should prompt an update and force a OS reload.

Yes i do it but it said "An error has occurred while updating your device software.Unspecified error encountered[A:0x000000A2] " T.T
Thanks

[AllenLoveBBRY]

Tell me exactly what you did and I will attempt to recreate it and find a solution.

i do cfp wipe . and i try cfp to reload os . it done. but my playbook dont turn on . have only red LED T.T

[FF22]

Do you do anything before trying that restoration? What was happening that you used the cfp tool? Did you Playbook not boot? Did it freeze while in use? Did the battery run down?

How old is the unit - warranty?

Here's some specific debrick advice

Try the Debrick method....

Perform a backup of your pb if you can using Desktop Manager or, at least, manually coping any unique data, photos, voice recordings, documents, etc.

1) Turn your playbook OFF by holding down the power button
2) Let your playbook sit for about 10 minutes as earlier suggested.
3) After letting the PB sit (and still powered off) open up the Blackberry Desktop Software (the latest version)
4) Once the Blackberry Desktop Software is opened, use the USB Cable and hook the PB to the PC.. THEN power on the Playbook
5) A screen will show on your computer showing that the device cannot be found
6) Click on Update. It will take awhile

[AllenLoveBBRY]

Do you do anything before trying that restoration? What was happening that you used the cfp tool? Did you Playbook not boot? Did it freeze while in use? Did the battery run down?

How old is the unit - warranty?

Here's some specific debrick advice

Try the Debrick method....

Perform a backup of your pb if you can using Desktop Manager or, at least, manually coping any unique data, photos, voice recordings, documents, etc.

1) Turn your playbook OFF by holding down the power button
2) Let your playbook sit for about 10 minutes as earlier suggested.
3) After letting the PB sit (and still powered off) open up the Blackberry Desktop Software (the latest version)
4) Once the Blackberry Desktop Software is opened, use the USB Cable and hook the PB to the PC.. THEN power on the Playbook
5) A screen will show on your computer showing that the device cannot be found
6) Click on Update. It will take awhile

Before it happen I running on os 10.0.9 and I try to load os 10.1 . I think I got block by load os 10.1 .can't load os anymore

[antiRIM]

Before it happen I running on os 10.0.9 and I try to load os 10.1 . I think I got block by load os 10.1 .can't load os anymore

Yeah you can't run 10.1 on the PB. If you try to it will blacklist you and you won't be able to downgrade. The only thing I would try if I were you, is try loading a version of 10.0.6, it is an earlier build of BB10. See if that works, if not then you are probably in too deep of a mud hole to pull back out of unfortunately.

[FF22]

Maybe I will ask:

Is this a bb phone?

Or a playbook?

If the PB, you might want to ask in the Rooting Subforum.

If a PHONE, hit the forum for your model?

[AllenLoveBBRY]

Yeah you can't run 10.1 on the PB. If you try to it will blacklist you and you won't be able to downgrade. The only thing I would try if I were you, is try loading a version of 10.0.6, it is an earlier build of BB10. See if that works, if not then you are probably in too deep of a mud hole to pull back out of unfortunately.

i try 10.0.9.44 10.0.6.385 10.0.6.671 10.0.9.2320 but it still back to 10.1

[AllenLoveBBRY]

Maybe I will ask:

Is this a bb phone?

Or a playbook?

If the PB, you might want to ask in the Rooting Subforum.

If a PHONE, hit the forum for your model?

Playbook

[antiRIM]

i try 10.0.9.44 10.0.6.385 10.0.6.671 10.0.9.2320 but it still back to 10.1

Run this in cfp and copy the log on here (erase your S/N and PIN#):

CFP info
----------------------------------------------------------------
I am doing this because it will show us what OS your PB says you are running and it will help us determine what is going on.

[AllenLoveBBRY]

Run this in cfp and copy the log on here (erase your S/N and PIN#):

CFP info
----------------------------------------------------------------
I am doing this because it will show us what OS your PB says you are running and it will help us determine what is going on.

10.2 =_=
when i try to load 1.0.6.385

[antiRIM]

Ok here is what you should get on 2.1.0.1526:
RIM Wireless Device Command-Line Programmer Version 3.9.4.0
Copyright 2012 Blackberry-FIF Support By drcom

Connecting to Bootrom: Connected

[ Uploading RAM Image 0x801279A4 ] [############## 100 ##############]

Device Info:
PIN:

Bootrom Version: 5.27.0.20
Hardware ID: RIM BlackBerry Device
HW ID Override: None
Metrics Version: 6.24
Build Date: Mar 24 2011
Build Time: 15:31:02
Build User: ec_agent
Security: Enabled
Supported Options: 0x00000009
Drivers: 0x00000010
Processor: 0x00000020
FlashID: 0x00000000
LDR Blocks: 0x80014674
Bootrom Size: 0x00020000
External MCT/HWV: Enabled
Boot Mode: Product

Boot OS Count: 0,21,0 (Region0,Region1,Max)

HWV:
Board Revision 0001 - 0x01
CPU Version 0002 - 0x74
SW Compatibility 0003 - 0x01
POP Revision 0004 - 0x03
Power Mgt Hardware 0007 - 0x3E
POP Security 000B - 0x02
RAMImage Compat 000E - 0x01


Mem Config Table (ver 1.24):
Flash Chip: blocks 0-262143, Chip 0, Sub 0
Boot0 MMC: blocks 0-0, total = 1, flags = 0x0001
Boot1 MMC: blocks 1-4, total = 4, flags = 0x0001
User MMC: blocks 5-262143, total = 262139, flags = 0x0001
MCT: block 0
MFG Data: blocks 1-4, total = 4
Bootrom: blocks 5-12
MBR: blocks 2053-2068
OS Fixed: blocks 2069-18436
OS NV: blocks 18437-18500, total 64
Branding: blocks 18501-18692
FS Fixed: blocks 18693-262143, total = 243451
MMC Enhanced: blocks 5-2052, total 2048
QNX region 0: blocks 2069-10244, total = 8176
QNX region 1: blocks 10261-18436, total = 8176
RAM Chip: 0x80000000-9FFFFFFF, Bank Size 67108864
RAM Chip: 0xA0000000-BFFFFFFF, Bank Size 67108864
NAND Config: type 0, data 0x00001000 0x00010000
NAND Config: type 1, data 0x15160003 0x00000000
CRC: 0x429312CC

Flash:
Number of chips: 1
Flash ID: NAND blocks 0-240964
Device ID: 16
Vendor ID: 69
Manufacturer ID: 0x45
OEM/Application ID: 0x100
Product Name: SEM16G
Product Revision: 0x90
Product Serial Number:
Manufacturing Date: Year 2011, Month 2
MMC Partition Info:
Boot0: 1024 KB (enhanced)
Boot1: 1024 KB (enhanced)
User: 131072 KB (enhanced)
User: 15290368 KB
Total Size: 15060 MB

Memory Map:
NAND Blocks: 240965 * 64 Kb
RAM Base: 0x80000000
IRAM Base: 0x40304000
OS Range: 2069 - 2118

File System:
Memory Map:
18693 - 240964
Sectors: 222272

Branding:
VendorID: 504

OS Version: 2.8.0.1526
Hardware ID: RIM BlackBerry Device
Metrics Version: 3.18
FS Code Version: 0.0.0.0
Package Version: "↕"
Build Date: Jan 30 2013
Build Time: 17:43:47
Build User: ec_agent
OS Address: 0x800FF800-0x80415343
App Start: * No Application Linked *

Companion Binary: 0.0.0.0

RAM usage: 0x00000000-0x00000000
IRAM End: 0x00000000
DSP ROM2 Address: *not present*
OS Extended Addr: 0x00000000
LDR Blocks: 0x00000000

API Checksum: 0x00000000
JumpTable (<3): 0x00000000
JumpTable (>2): 0x00000000

Radio Code: No radio code linked
OS API Version: 0.0
STP Protocol Ver: 0.0.4 (release OS)

Version Table:



Done.

[AllenLoveBBRY]

when i try 2.1.0.1526
RIM Wireless Device Command-Line Programmer Version 3.9.0.249
Copyright 2012 Research In Motion Limited

Connecting to Bootrom: Connected

[ Uploading RAM Image 0x8012CE1C ] [############## 100 ##############]

Device Info:
PIN:

Bootrom Version: 5.27.0.20
Hardware ID: 0x06001A06 RIM BlackBerry Device
HW ID Override: None
OS ID: None
Metrics Version: 6.24
Build Date: Mar 24 2011
Build Time: 15:31:02
Build User: ec_agent
Security: Enabled
Supported Options: 0x00000009
Drivers: 0x00000010
Processor: 0x00000020
FlashID: 0x00000000
LDR Blocks: 0x80014674
Bootrom Size: 0x00020000
External MCT/HWV: Enabled
Boot Mode: Product

Boot OS Count: 0,0,0 (Region0,Region1,Max)

HWV:
Board Revision 0001 - 0x01
CPU Version 0002 - 0x74
SW Compatibility 0003 - 0x01
POP Revision 0004 - 0x03
Power Mgt Hardware 0007 - 0x3E
POP Security 000B - 0x02
RAMImage Compat 000E - 0x01


Mem Config Table (ver 1.24):
Flash Chip: blocks 0-262143, Chip 0, Sub 0
Boot0 MMC: blocks 0-0, total = 1, flags = 0x0001
Boot1 MMC: blocks 1-4, total = 4, flags = 0x0001
User MMC: blocks 5-262143, total = 262139, flags = 0x0001
MCT: block 0
MFG Data: blocks 1-4, total = 4
Bootrom: blocks 5-12
MBR: blocks 2053-2068
OS Fixed: blocks 2069-18436
OS NV: blocks 18437-18500, total 64
Branding: blocks 18501-18692
FS Fixed: blocks 18693-262143, total = 243451
MMC Enhanced: blocks 5-2052, total 2048
QNX region 0: blocks 2069-10244, total = 8176
QNX region 1: blocks 10261-18436, total = 8176
RAM Chip: 0x80000000-9FFFFFFF, Bank Size 67108864
RAM Chip: 0xA0000000-BFFFFFFF, Bank Size 67108864
NAND Config: type 0, data 0x00001000 0x00010000
NAND Config: type 1, data 0x15190003 0x00000000
CRC: 0xB3C5A019

Flash:
Number of chips: 1
Flash ID: NAND blocks 0-240964
Device ID: 0x10
Vendor ID: 0x45
Manufacturer Name: SanDisk (4.41)
OEM/Application ID: 0x100
Product Name: SEM16G
Product Revision: 0x90
Product Serial Number:
Manufacturing Date: Year 2011, Month 3
MMC Partition Info:
Boot0: 1024 KB (enhanced)
Boot1: 1024 KB (enhanced)
User: 131072 KB (enhanced)
User: 15290368 KB
Total Size: 15060 MB

Memory Map:
NAND Blocks: 240965 * 64 Kb
RAM Base: 0x80000000
IRAM Base: 0x40304000
OS Range: 2069 - 2118

File System:
Memory Map:
18693 - 240964
Sectors: 222272

Branding:
VendorID: 504

OS Version: 2.8.0.1526
Hardware ID: 0x06001A06 RIM BlackBerry Device
Metrics Version: 3.18
FS Code Version: 0.0.0.0
Package Version: ""
Build Date: Jan 30 2013
Build Time: 17:43:47
Build User: ec_agent
OS Address: 0x800FF800-0x80415343
App Start: * No Application Linked *

Companion Binary: 0.0.0.0

RAM usage: 0x00000000-0x00000000
IRAM End: 0x00000000
DSP ROM2 Address: *not present*
OS Extended Addr: 0x00000000
LDR Blocks: 0x00000000

API Checksum: 0x00000000
JumpTable (<3): 0x00000000
JumpTable (>2): 0x00000000

Radio Code: No radio code linked
OS API Version: 0.0
STP Protocol Ver: 0.0.4 (release OS)

Version Table:



Done.

[antiRIM]

when i try 2.1.0.1526
RIM Wireless Device Command-Line Programmer Version 3.9.0.249
Copyright 2012 Research In Motion Limited

Connecting to Bootrom: Connected

[ Uploading RAM Image 0x8012CE1C ] [############## 100 ##############]

Device Info:
PIN:

Bootrom Version: 5.27.0.20
Hardware ID: 0x06001A06 RIM BlackBerry Device
HW ID Override: None
OS ID: None
Metrics Version: 6.24
Build Date: Mar 24 2011
Build Time: 15:31:02
Build User: ec_agent
Security: Enabled
Supported Options: 0x00000009
Drivers: 0x00000010
Processor: 0x00000020
FlashID: 0x00000000
LDR Blocks: 0x80014674
Bootrom Size: 0x00020000
External MCT/HWV: Enabled
Boot Mode: Product

Boot OS Count: 0,0,0 (Region0,Region1,Max)

HWV:
Board Revision 0001 - 0x01
CPU Version 0002 - 0x74
SW Compatibility 0003 - 0x01
POP Revision 0004 - 0x03
Power Mgt Hardware 0007 - 0x3E
POP Security 000B - 0x02
RAMImage Compat 000E - 0x01


Mem Config Table (ver 1.24):
Flash Chip: blocks 0-262143, Chip 0, Sub 0
Boot0 MMC: blocks 0-0, total = 1, flags = 0x0001
Boot1 MMC: blocks 1-4, total = 4, flags = 0x0001
User MMC: blocks 5-262143, total = 262139, flags = 0x0001
MCT: block 0
MFG Data: blocks 1-4, total = 4
Bootrom: blocks 5-12
MBR: blocks 2053-2068
OS Fixed: blocks 2069-18436
OS NV: blocks 18437-18500, total 64
Branding: blocks 18501-18692
FS Fixed: blocks 18693-262143, total = 243451
MMC Enhanced: blocks 5-2052, total 2048
QNX region 0: blocks 2069-10244, total = 8176
QNX region 1: blocks 10261-18436, total = 8176
RAM Chip: 0x80000000-9FFFFFFF, Bank Size 67108864
RAM Chip: 0xA0000000-BFFFFFFF, Bank Size 67108864
NAND Config: type 0, data 0x00001000 0x00010000
NAND Config: type 1, data 0x15190003 0x00000000
CRC: 0xB3C5A019

Flash:
Number of chips: 1
Flash ID: NAND blocks 0-240964
Device ID: 0x10
Vendor ID: 0x45
Manufacturer Name: SanDisk (4.41)
OEM/Application ID: 0x100
Product Name: SEM16G
Product Revision: 0x90
Product Serial Number:
Manufacturing Date: Year 2011, Month 3
MMC Partition Info:
Boot0: 1024 KB (enhanced)
Boot1: 1024 KB (enhanced)
User: 131072 KB (enhanced)
User: 15290368 KB
Total Size: 15060 MB

Memory Map:
NAND Blocks: 240965 * 64 Kb
RAM Base: 0x80000000
IRAM Base: 0x40304000
OS Range: 2069 - 2118

File System:
Memory Map:
18693 - 240964
Sectors: 222272

Branding:
VendorID: 504

OS Version: 2.8.0.1526
Hardware ID: 0x06001A06 RIM BlackBerry Device
Metrics Version: 3.18
FS Code Version: 0.0.0.0
Package Version: ""
Build Date: Jan 30 2013
Build Time: 17:43:47
Build User: ec_agent
OS Address: 0x800FF800-0x80415343
App Start: * No Application Linked *

Companion Binary: 0.0.0.0

RAM usage: 0x00000000-0x00000000
IRAM End: 0x00000000
DSP ROM2 Address: *not present*
OS Extended Addr: 0x00000000
LDR Blocks: 0x00000000

API Checksum: 0x00000000
JumpTable (<3): 0x00000000
JumpTable (>2): 0x00000000

Radio Code: No radio code linked
OS API Version: 0.0
STP Protocol Ver: 0.0.4 (release OS)

Version Table:



Done.

Ok, load 2.1 over that one more time and then do this when that is finished:

cfp resetqnxosregion
--------------------------------------------------
That is all I can think to try. Let me know how it goes.

[xsacha]

Argh, you flashed 10.2.
No chance of going back now. Sorry :\

The reason why RIM blacklisted 10.0.9 (and earlier) is because a root exploit was discovered in that version.
It's also the last version that works on Playbook.

[AllenLoveBBRY]

Ok, load 2.1 over that one more time and then do this when that is finished:

cfp resetqnxosregion
--------------------------------------------------
That is all I can think to try. Let me know how it goes.

Microsoft Windows [Version 6.2.9200]
(c) 2012 Microsoft Corporation. All rights reserved.

RIM Wireless Device Command-Line Programmer Version 3.9.4.0
Copyright 2012 Blackberry-FIF Support By drcom

Connecting to Bootrom: Connected

[ Uploading RAM Image 0x801279A4 ] [############## 100 ##############]
QNX OSREGION NVRAM record cleared.

Done.
Still 2.8

[AllenLoveBBRY]

Argh, you flashed 10.2.
No chance of going back now. Sorry :\

The reason why RIM blacklisted 10.0.9 (and earlier) is because a root exploit was discovered in that version.
It's also the last version that works on Playbook.

[antiRIM]

Microsoft Windows [Version 6.2.9200]
(c) 2012 Microsoft Corporation. All rights reserved.

RIM Wireless Device Command-Line Programmer Version 3.9.4.0
Copyright 2012 Blackberry-FIF Support By drcom

Connecting to Bootrom: Connected

[ Uploading RAM Image 0x801279A4 ] [############## 100 ##############]
QNX OSREGION NVRAM record cleared.

Done.
Still 2.8

Sorry man.

[AllenLoveBBRY]

Sorry man.

Np and thanks for help . : D

[quackquack147]

Np and thanks for help . : D

hey allen!
wait! there is hope. jtag! we are close. are you willing to jtag? if yes contact me. or the rooting forum.
xsacha is right. you cant fix it with those tools. you need jtag.
but before that one question. Do you have enough patience and a towel, to wipe your sweat. this will be a long and challanging task!
we are very close to jtag. i will post in info ASAP i am sanguine it does what its supposed to do, or i intend to do.
thanks!
-paul
http://forums.crackberry.com/playbook-rooting-f256/

[quackquack147]

I can't reload any os .used cfp or blackberrydesktop its said An error has occurred while updating your device software.Unspecified error encountered[A:0x000000A2] . cant install os 2.1 or os 10.0.9

now i know how to brick the devices. :-D without opening and passing voltage. thanks you! ;-)
one mans meat is others poison. so your poison is crackberry's meat.
thanks!
-paul

[AllenLoveBBRY]

now i know how to brick the devices. :-D without opening and passing voltage. thanks you! ;-)
one mans meat is others poison. so your poison is crackberry's meat.
thanks!
-paul

Yayyyyyyyyyy!!! Yayyyyy!! Yayy! :P

[quackquack147]

Yayyyyyyyyyy!!! Yayyyyy!! Yayy! :P

:-P looks like other than mmap and pmap there is no way you can recover it w/o jtag. i am working on jtag also. i am not an expert. i am new too. i joined on 10 th june 2013. and none of the developer expert know of other method. well time to gamble again. this time with memory.
thanks!
-paul