[yhamaie]

CORRECTION - Sachesi is designed to load device software (operating system, radio, and apps) to BlackBerry 10 smartphones always in a NON-DESTRUCTIVE manner. This is why Sachesi will install only the operating system part of a de-brick file . . . it will NOT install apps included in such de-brick file (as the user data partition contained in such de-brick file is destructive).

----------

I suppose that de-brick mode installation might be useful for those who often update software with Sachesi.exe on Microsoft Windows.

----------

STEP 1

Please create a folder (e.g. 10.2.1.2160) at your favorite location in Microsoft Windows.

STEP 2

Please download an appropriate RADIO file and a very large packaged .bar file (which contains the core OS and all application .bar files) from http://cdn.fs.sl.blackberry.com/fs/qnx/production/ and place them in the folder created in STEP 1.

Please double-check the extension of each file name. (.bar files may be erroneously saved as .zip files from time to time.)

Examples - OS Version: 10.2.1.2234 / Radio Version: 10.2.1.2235 / Software Release Version: 10.2.1.2160

Q5 and Q10 (all SQR100-x models and all SQN100-x models)

1,280,184,598 qc8960.factory_sfi.desktop-10.2.1.2234-nto+armle-v7+signed.bar
24,942,946 qc8960.wtr-10.2.1.2235-nto+armle-v7+signed.bar

Z10 (STL100-1)

1,266,774,145 winchester.factory_sfi.desktop-10.2.1.2234-nto+armle-v7+signed.bar
27,168,634 m5730-10.2.1.2235-nto+armle-v7+signed.bar

Z10 (STL100-2 and STL100-3)

1,280,184,598 qc8960.factory_sfi.desktop-10.2.1.2234-nto+armle-v7+signed.bar
23,367,554 qc8960-10.2.1.2235-nto+armle-v7+signed.bar

Z10 (STL100-4)

1,280,184,598 qc8960.factory_sfi.desktop-10.2.1.2234-nto+armle-v7+signed.bar
23,367,304 qc8960.omadm-10.2.1.2235-nto+armle-v7+signed.bar

Z30 (all STA100-x models)

1,280,184,598 qc8960.factory_sfi.desktop-10.2.1.2234-nto+armle-v7+signed.bar
28,484,571 qc8960.wtr5-10.2.1.2235-nto+armle-v7+signed.bar

STEP 3

Please connect your BlackBerry 10 device via USB cable to your PC and install the two .bar files downloaded in STEP 2.









Note:

The following .bar files (which contain the core OS only) are much smaller in size.

Q5, Q10, Z10 (excluding STL100-1), and Z30

308,122,039 qc8960.factory_sfi-10.2.1.2234-nto+armle-v7+signed.bar

Z10 (STL100-1)

295,158,963 winchester.factory_sfi-10.2.1.2234-nto+armle-v7+signed.bar

[jaydee5799]

Excellent! Thank you!

[yhamaie]

I suppose that de-brick mode installation might be useful for those who often update software with Sachesi.exe on Microsoft Windows.

P.S.

.bar files quoted in the above examples are located at the following URLs.


RADIO

Q5 and Q10 (all SQR100-x models and all SQN100-x models)

http://cdn.fs.sl.blackberry.com/fs/q...-v7+signed.bar

Z10 (STL100-1)

http://cdn.fs.sl.blackberry.com/fs/q...-v7+signed.bar

Z10 (STL100-2 and STL100-3)

http://cdn.fs.sl.blackberry.com/fs/q...-v7+signed.bar

Z10 (STL100-4)

http://cdn.fs.sl.blackberry.com/fs/q...-v7+signed.bar

Z30 (all STA100-x models)

http://cdn.fs.sl.blackberry.com/fs/q...-v7+signed.bar


Packaged File (containing the core OS and all application .bar files)

Q5, Q10, Z10 (excluding STL100-1), and Z30

http://cdn.fs.sl.blackberry.com/fs/q...-v7+signed.bar

Z10 (STL100-1)

http://cdn.fs.sl.blackberry.com/fs/q...-v7+signed.bar


OS (containing the core OS only)

Q5, Q10, Z10 (excluding STL100-1), and Z30

http://cdn.fs.sl.blackberry.com/fs/q...-v7+signed.bar

Z10 (STL100-1)

http://cdn.fs.sl.blackberry.com/fs/q...-v7+signed.bar


Note (quoted from BlackBerry Z10 - Hardware found in Wikipedia):
There are four SKUs for the Blackberry Z10, corresponding to the North American carrier band distribution and international versions.
The LTE version of the Z10 features the Qualcomm Snapdragon S4 Plus (SoC) which has a dual-core CPU running at 1.5 GHz, and an Adreno 225 GPU for LTE-capable units.
For markets where LTE is not supported, BlackBerry released the Z10 with the Texas Instruments OMAP 4470 (SoC) which has a dual-core CPU running at 1.5 GHz and a PowerVR SGX 544 GPU. It will use STE M5730 modem.

[DarcyTallGuy]

Just remember that updating using the debrick bar file does NOT actually update the apps even though the apps are in the debrick bar. Whether you use the debrick or non-debrick OS bar file, only the OS itself is updated. You must do the apps seperately.

[dviles]

So, when I updated to 1925 with an autoloader, or 2141 with Sachesi (nondestructive), or 2228 via Tmobile over the air, I didn't upgrade the apps? Can you elaborate?

Posted via CB10

[abramadhi]

Just remember that updating using the debrick bar file does NOT actually update the apps even though the apps are in the debrick bar. Whether you use the debrick or non-debrick OS bar file, only the OS itself is updated. You must do the apps seperately.

Darcy's right. Compare the apps and take note apps that are upgraded and than extract those apps and sideload.

The easiest way is to download the production bars which is a debrick file but in parts of each apps and then sideload.

Posted via CB10

[yhamaie]

Just remember that updating using the debrick bar file does NOT actually update the apps even though the apps are in the debrick bar. Whether you use the debrick or non-debrick OS bar file, only the OS itself is updated. You must do the apps seperately.

Noted with a lot of thanks . . . it is true that, unlike Blackberry Link desktop software which stores a debrick OS .bar file and an appropriate RADIO .bar file in \\Users\ [account name] \AppData\Local\Research In Motion\Application Loader\Cache\ [the last part of base URL] when we choose to Reload Device Software (to reset a BlackBerry 10 device to factory setting), Sachesi.exe does not install application .bar files which are contained in such debrick OS .bar file.

It would be nice if the author of Sachesi.exe kindly adds to this marvelous program a "Reset Your Device" ("Reload Device Software") functionality (by making use of debrick OS .bar files of our choice) as alternative to autoloaders.

[yhamaie]

So, when I updated to 1925 with an autoloader, or 2141 with Sachesi (nondestructive), or 2228 via Tmobile over the air, I didn't upgrade the apps? Can you elaborate?

Please do not worry . . . when you updated your BlackBerry 10 device to 1925 with an autoloader, 2141 with Sachesi (in non-destructive UPGRADE mode), or 2228 via Tmobile over the air, all application files contained in such autoloader, fetched by Sachesi, or downloaded over the air were properly installed in your BlackBerry 10 device.

Sachesi DOES NOT automatically extract application .bar files from very large OS .bar files (as large as autoloaders) fetched in DEBRICK mode so that application .bar files are NOT installed (although all application .bar files are contained in such very large OS . bar files fetched in DEBRICK mode).

[dviles]

OK. Thank you. Had heard of application bars not installing with debrick bars. Just wasn't sure how it worked in other instances.

Posted via CB10

[DarcyTallGuy]

Noted with a lot of thanks . . . it is true that, unlike Blackberry Link desktop software which stores a debrick OS .bar file and an appropriate RADIO .bar file in \\Users\ [account name] \AppData\Local\Research In Motion\Application Loader\Cache\ [the last part of base URL] when we choose to Reload Device Software (to reset a BlackBerry 10 device to factory setting), Sachesi.exe does not install application .bar files which are contained in such debrick OS .bar file.

It would be nice if the author of Sachesi.exe kindly adds to this marvelous program a "Reset Your Device" ("Reload Device Software") functionality (by making use of debrick OS .bar files of our choice) as alternative to autoloaders.

Link doesn't load them as bar files like Sachesi does, link loads them like an autoloader - destructively. Sachesi allows you to do this by creating the autoloaders out of the signed files. It's just the way Blackberry designed the phones to work (and there are technical reasons for it which I won't get into again), and there's code in place to deal with these exact scenarios. The only way to update the apps is either through individual bar files, or using the debrick files autoloader style and wipe your phone.

[bmoney1229]

Will this work on a z10 that won't even connect to pc usually?

Posted via CB10

[rashidJkhan69]

Thanks

Posted via CB10

[tickerguy]

Be very, very careful doing this if you jump revisions.

If the application BAR files are incompatible with the core OS and radio you load you're screwed and will be forced to do a destructive install.

What I do is to put the Core, radio and ALL app BAR files for the desired target into a directory, then load THAT with Sachesi. This loads them all as one operation and avoids this risk.

What's described above works fine within a minor release (e.g. 10.2.0.x -> 10.2.0.y) in general but I assure you that if you try to jump major releases (e.g. 10.2 -> 10.3) or sometimes even within them (e.g. 10.2.0 to 10.2.1) you're begging for trouble and, if you find it, Sachesi won't reconnect after the core and radio are loaded to be able to replace the BAR files.

Your only option at that point is a destructive load with an autoloader.