05-13-18 09:19 PM
3,558 ... 2728293031 ...
tools
  1. xsacha's Avatar
    It sounds like your OS is bugged on the radio install. Sachesi successfully sends the file (50% means complete sending) but the device would not install it.

    There is no need to do a destructive autoload. Create an autoloader in the 'Extract' tab with the .signed file from inside the radio.bar (extract it).
    Then run this autoloader. It will be non-destructive as it contains only a radio.
    09-05-13 09:56 AM
  2. Kamziron's Avatar
    One thing Ive noticed with Beta 24 is that for some carriers it's showing release 4181 even though something newer is available (for example, use MCC/MNC 310/120, model SQN100-4 to check for Sprint Q10 software which is release 4211, and it returns nothing found).
    09-05-13 09:58 AM
  3. tickerguy's Avatar
    I'm getting an error 99 this morning on the update server but the old Sachup (which I still have) is able to retrieve the files without error..... not sure what's going on with that...
    09-05-13 10:22 AM
  4. AnimalPak200's Avatar
    It sounds like your OS is bugged on the radio install. Sachesi successfully sends the file (50% means complete sending) but the device would not install it.

    There is no need to do a destructive autoload. Create an autoloader in the 'Extract' tab with the .signed file from inside the radio.bar (extract it).
    Then run this autoloader. It will be non-destructive as it contains only a radio.
    Actually, yesterday I tried making an autoloader from the .signed radio file I got from the "radio archive " thread... when I ran the autoloader it bricked my phone (flashing red light). Had to start from scratch with an old pre-Maintenance Release full autoloader I had (so that I could at least restore to a pre-MR backup).

    I'm starting to get a feeling that the current radio installed is interfering with any radio update (even though it used to work fine prior to the OS load)... yesterday was actually the third time I bricked my phone trying a radio-only autoloader (all different radios).

    Posted via CB10
    09-05-13 10:59 AM
  5. moosbb's Avatar
    I'm getting an error 99 this morning on the update server but the old Sachup (which I still have) is able to retrieve the files without error..... not sure what's going on with that...
    Which working revision have you please?
    All the ones I tried lastly will give me that error...

    Care to share?
    09-05-13 11:18 AM
  6. AnimalPak200's Avatar
    So still not working? Are you sure your phone is a STL 100-4? You can try using the STL 100-3 radio instead.
    Otherwise, try renaming the qc8960.omadm-.. to qc8960.wtr-... and try again?
    Good news! I renamed the file as you instructed: from "qc8960.omadm-..." to "qc8960.wtr-...", dragged over to the Install tab and it worked. After my phone rebooted I had the 4634 radio and I am finally able to make calls again! Perhaps beta 25 can include recognition for the other radio file names.

    Thanks for the help!
    09-05-13 12:11 PM
  7. tickerguy's Avatar
    Which working revision have you please?
    All the ones I tried lastly will give me that error...

    Care to share?
    B24 is the one that doesn't work. I have the old Sachup (I don't have a rev on the screen) and it is working.
    09-05-13 01:13 PM
  8. xsacha's Avatar
    I'm getting an error 99 this morning on the update server but the old Sachup (which I still have) is able to retrieve the files without error..... not sure what's going on with that...
    Error 99 usually means you are missing the DLLs that I packed it with. Are you running it from within the .zip or something? It needs to be extracted with the DLLs in the same directory.

    Perhaps beta 25 can include recognition for the other radio file names.
    Yes it will. I wasn't aware of the 'omadm' variation before. Usually STL 100-4 users install the STL 100-2 or STL 100-3 radios because they are newer (and the same).
    Thought you had tried renaming it before.

    Doesn't explain why autoloaders didn't work for you though :\
    09-05-13 07:50 PM
  9. cuek80's Avatar
    Frequently Asked

    Q. Where do I find the Country and Carrier codes?
    A. Country is MNC and Carrier is MCC. Full list is here: https://en.wikipedia.org/wiki/Mobile_country_code
    I think Country is MCC, Carrier is MNC.
    Thanks anyway, will try
    09-06-13 04:12 AM
  10. xsacha's Avatar
    I think Country is MCC, Carrier is MNC.
    Thanks anyway, will try
    Thanks for the find
    09-06-13 09:41 AM
  11. Gykesdollars's Avatar
    Can I side load a new os and radio nondestructively over an existing one without the need of doing a full os upgrade?? Possible??

    Posted from my Zee10 "the iPhone-killa"
    09-06-13 10:45 AM
  12. verymike's Avatar
    very layman question, I bought an UK unlocked Q10 f/ Unlocked-Mobiles.com which of course a SQN100-3, but using it in Sweden, so which MCC MNC should I choose?

    (the software release is still 10.1.0.273... checked update,..but... like never had an OTA, is that normal?)

    Thanks!
    09-06-13 01:58 PM
  13. xsacha's Avatar
    very layman question, I bought an UK unlocked Q10 f/ Unlocked-Mobiles.com which of course a SQN100-3, but using it in Sweden, so which MCC MNC should I choose?

    (the software release is still 10.1.0.273... checked update,..but... like never had an OTA, is that normal?)
    You can use any MCC/MNC. The idea is not to use your own. You can already use your own by doing 'Check for Updates' in Settings.

    The default MCC/MNC is a good choice because it represents the carrier with the latest known update.
    09-06-13 02:23 PM
  14. verymike's Avatar
    got that thx for such quick reply!
    09-06-13 02:30 PM
  15. hakdaddy1's Avatar
    hey,

    My docs to go native app has vanished off my playbook and need to get back on without wiping the device again. Someone suggested that I could do this with your software and extract the bar file from the latest PB 2.1 leak? Havent got a clue how to do this. Could you help please?
    09-06-13 04:15 PM
  16. hakdaddy1's Avatar
    You can use any MCC/MNC. The idea is not to use your own. You can already use your own by doing 'Check for Updates' in Settings.

    The default MCC/MNC is a good choice because it represents the carrier with the latest known update.
    hey,

    My docs to go native app has vanished off my playbook and need to get back on without wiping the device again. Someone suggested that I could do this with your software and extract the bar file from the latest PB 2.1 leak? Havent got a clue how to do this. Could you help please?
    09-06-13 04:16 PM
  17. aliallibhai's Avatar
    hey,

    My docs to go native app has vanished off my playbook and need to get back on without wiping the device again. Someone suggested that I could do this with your software and extract the bar file from the latest PB 2.1 leak? Havent got a clue how to do this. Could you help please?
    Download the leaked autoloader. Extract the file to get an exe file. Use the split tool on that exe file. You'll get an os signed file on which you use the extract BAR option. Find the file you want and install it on to your PB

    Posted via CB10
    09-06-13 06:20 PM
  18. Omnitech's Avatar
    Last time I tried making an autoloader from only a radio .signed file and running it, it bricked my Z10.
    Actually, yesterday I tried making an autoloader from the .signed radio file I got from the "radio archive " thread... when I ran the autoloader it bricked my phone (flashing red light). Had to start from scratch with an old pre-Maintenance Release full autoloader I had (so that I could at least restore to a pre-MR backup).

    I'm starting to get a feeling that the current radio installed is interfering with any radio update (even though it used to work fine prior to the OS load)... yesterday was actually the third time I bricked my phone trying a radio-only autoloader (all different radios).


    I had that problem a couple of times myself on my own Z10s.

    I have STL100-4s too, I wonder if there is something special about them not liking to have a separate radio file installed. Though I could swear I know people that have done exactly that.



    One thing Ive noticed with Beta 24 is that for some carriers it's showing release 4181 even though something newer is available (for example, use MCC/MNC 310/120, model SQN100-4 to check for Sprint Q10 software which is release 4211, and it returns nothing found).

    I see that B22 was able to find .4211/.4828 with those parameters, but B24 was not. So I guess I'm confirming your finding. In my test, it showed nothing available at all for that combo.


    Can I side load a new os and radio nondestructively over an existing one without the need of doing a full os upgrade?? Possible??

    Yes.
    09-06-13 06:34 PM
  19. hakdaddy1's Avatar
    Download the leaked autoloader. Extract the file to get an exe file. Use the split tool on that exe file. You'll get an os signed file on which you use the extract BAR option. Find the file you want and install it on to your PB

    Posted via CB10
    Havent got a clue how to do any of that stuff :-(
    09-06-13 07:09 PM
  20. cuek80's Avatar
    Hi. I tried upgrading Z10 to 10.1.0.4181 with problems.
    1. I downloaded the files, using MCC/MNC 510/11 (Indonesia/XL)
    2. z10 stuck at boot (100%) for more than an hour.

    I try OTA upgrade 3 times, and with sachesi 1 time. ALL stuck at 100% boot logo.
    Anyway, I reload the OS via BB Link, and It install the .4181. So, all good for now.
    I found out that the .4181 OS that was installed by BB Link is here: C:\Users\(user-name)\AppData\Local\Research In Motion\Application Loader\Cache\39ca4dda9b063c7a2a8e9eec7069a45477ab1 8d7
    I compare it to files that Sachesi had downloaded.

    Here's the differences: (name size)
    Code:
    -- Files that BB Link downloaded, but Sachesi didn't --
    qcfm.image.com.qnx.coreos.qcfm.os.factory_sfi.desktop.BB10_1_X.4633.556195.signed	1,593,311,792
    qcfm.image.com.qnx.qcfm.radio.m5730.BB10_1_X.4634.556195.signed	29,557,296
    winchester.factory_sfi.desktop-10.1.0.4633-nto+armle-v7+signed.bar	1,096,597,398
    
    -- Files that BB Link didn't download, Sachesi did --
    adobeReader-10.1.4.20-nto+armle-v7+signed.bar	5,240,422
    af_ZA-10.1.0.4-nto+armle-v7+signed.bar	2,127,568
    appworld-4.4.0.54-nto+armle-v7+signed.bar	2,348,745
    ar_SA-10.1.0.5-nto+armle-v7+signed.bar	1,953,140
    blackberry-10.1.4.6050-nto+armle-v7+signed.bar	6,295,731
    box-1.1.1.4-nto+armle-v7+signed.bar	712,973
    bridgeBBM-10.1.0.31-nto+armle-v7+signed.bar	1,183,397
    bugreport-1.0.2.37-nto+armle-v7+signed.bar	1,663,607
    carrier_data-10.1.0.1675-nto+armle-v7+signed.bar	346,704
    ca_ES-10.1.0.5-nto+armle-v7+signed.bar	1,221,865
    cs_CZ-10.1.0.4-nto+armle-v7+signed.bar	2,283,755
    da_DK-10.1.0.4-nto+armle-v7+signed.bar	2,057,872
    de_DE-10.1.0.4-nto+armle-v7+signed.bar	2,231,504
    el_GR-10.1.0.4-nto+armle-v7+signed.bar	1,853,790
    en_GB-10.1.0.5-nto+armle-v7+signed.bar	2,276,483
    en_US-10.1.0.9-nto+armle-v7+signed.bar	2,501,715
    es_ES-10.1.0.4-nto+armle-v7+signed.bar	2,269,244
    eu_ES-10.1.0.4-nto+armle-v7+signed.bar	1,181,949
    facebook-10.2.0.0-nto+armle-v7+signed.bar	5,623,805
    fi_FI-10.1.0.4-nto+armle-v7+signed.bar	2,356,850
    fr_FR-10.1.0.6-nto+armle-v7+signed.bar	2,138,334
    gl_ES-10.1.0.4-nto+armle-v7+signed.bar	2,378,787
    he_IL-10.1.0.4-nto+armle-v7+signed.bar	1,462,981
    howto-10.1.0.8-nto+armle-v7+signed.bar	23,325,751
    hr_HR-10.1.0.4-nto+armle-v7+signed.bar	2,170,560
    hu_HU-10.1.0.4-nto+armle-v7+signed.bar	2,324,541
    id_ID-10.1.0.4-nto+armle-v7+signed.bar	1,033,697
    it_IT-10.1.0.4-nto+armle-v7+signed.bar	2,006,724
    kk_KZ-10.1.0.4-nto+armle-v7+signed.bar	522,008
    ko_KR-10.1.0.4-nto+armle-v7+signed.bar	1,810,687
    linkedin-10.1.3.3-nto+armle-v7+signed.bar	3,434,919
    maps-10.1.0.804-nto+armle-v7+signed.bar	8,949,652
    nb_NO-10.1.0.4-nto+armle-v7+signed.bar	1,757,639
    newsstand-10.1.10.0-nto+armle-v7+signed.bar	6,969,012
    nl_NL-10.1.0.4-nto+armle-v7+signed.bar	2,368,244
    nuance_vocalizer-10.1.1.4-nto+armle-v7+signed.bar	34,693,204
    oobetutorials-10.1.0.8-nto+armle-v7+signed.bar	2,807,746
    pbcd-10.1.0.3-nto+armle-v7+signed.bar	94,592,528
    pl_PL-10.1.0.4-nto+armle-v7+signed.bar	2,291,150
    pt_BR-10.1.0.4-nto+armle-v7+signed.bar	2,064,641
    pt_PT-10.1.0.5-nto+armle-v7+signed.bar	2,138,456
    ro_RO-10.1.0.5-nto+armle-v7+signed.bar	2,276,068
    ru_RU-10.1.0.5-nto+armle-v7+signed.bar	2,146,056
    sv_SE-10.1.0.4-nto+armle-v7+signed.bar	2,277,991
    th_TH-10.1.0.5-nto+armle-v7+signed.bar	2,535,830
    tr_TR-10.1.0.4-nto+armle-v7+signed.bar	2,046,827
    twitter-10.1.3.8-nto+armle-v7+signed.bar	1,371,327
    vi_VN-10.1.0.4-nto+armle-v7+signed.bar	2,010,859
    wallpaper-10.1.0.3-nto+armle-v7+signed.bar	20,902,531
    zoneinfo-10.1.1.1-nto+armle-v7+signed.bar	373,267
    - Is this difference normal? BB Link Folder is 3+GB, Sachesi's folder is 1+GB
    - I can't find the option in Sachesi for clean install (not upgrade), is this not implemented yet? I use win version.
    - How many free space do we need for upgrading btw? I think the cause of failure is because not enough space on Z10, I have around 2GB of free space when I try to upgrade though.

    Thanks for the app. installing bar files is much easier now
    09-07-13 01:57 AM
  21. xsacha's Avatar
    The difference is you downloaded a Debrick from Link and an Upgrade from Sachesi.
    Choose 'Debrick' in Sachesi.
    09-07-13 05:22 AM
  22. Omnitech's Avatar
    Hi. I tried upgrading Z10 to 10.1.0.4181 with problems.
    1. I downloaded the files, using MCC/MNC 510/11 (Indonesia/XL)
    2. z10 stuck at boot (100%) for more than an hour.

    I try OTA upgrade 3 times, and with sachesi 1 time. ALL stuck at 100% boot logo.

    Some of the factors that seem to contribute to getting "stuck" at the 100% logo on 10.1 MR release upgrade attempts (either OTA or via Sachesi etc), are if the user has either a ton of messages (emails, texts) stored on the device, or in some cases, a large memory card installed. (I'm not sure if it's the card itself or the data on it that is the problem)
    09-07-13 01:11 PM
  23. tickerguy's Avatar
    Error 99 usually means you are missing the DLLs that I packed it with. Are you running it from within the .zip or something? It needs to be extracted with the DLLs in the same directory.
    No, I extracted it -- and it was working the previous day.

    It may be my machine going wonky -- it wouldn't be the first time.

    BTW the previous rev also made a unrestorable backup. Guess how I discovered that?
    09-07-13 05:04 PM
  24. Omnitech's Avatar
    BTW the previous rev also made a unrestorable backup. Guess how I discovered that?
    Ack. I originally used to make backups both with Link and Sachesi, for an important backup. Then I started getting lazy and sometimes didn't include the Link backup. (Because of the really really stupid UI that application has, among other things.)

    Looks like I'll go back to creating backups with both, for important stuff anyway. (ie my daily driver)
    09-07-13 05:48 PM
  25. xsacha's Avatar
    BTW the previous rev also made a unrestorable backup. Guess how I discovered that?
    Backup code hasn't changed since ~ rev 15 or so.

    It is likely an incompatibility with the new OS you installed instead?

    Either that or the backup process didn't start at all (due to error 99: missing SSL libraries).
    09-07-13 07:37 PM
3,558 ... 2728293031 ...

Similar Threads

  1. Replies: 41
    Last Post: 01-09-16, 11:03 AM
  2. Q10 shows "4G" and Z10 shows "4GLTE"
    By BGQ10 in forum BlackBerry Q10
    Replies: 22
    Last Post: 01-20-14, 10:31 AM
  3. BlackBerry needs to get BB10 in cars, and fast!
    By BlackBerry_Pwner in forum General BlackBerry Discussion
    Replies: 19
    Last Post: 09-17-13, 09:26 AM
  4. Suggestion: BBM Forum for x-platform BBM software and features
    By lorax1284 in forum Site Feedback & Help
    Replies: 2
    Last Post: 07-05-13, 06:01 PM
  5. July 9th Blackberry Webcast What do you expect and What do you want to hear?
    By Wilsonia Goldens in forum General BlackBerry Discussion
    Replies: 4
    Last Post: 07-04-13, 08:38 AM
LINK TO POST COPIED TO CLIPBOARD