02-09-18 12:39 AM
3,553 ... 2627282930 ...
tools
  1. xsacha's Avatar
    Thanks again for your great work. Concerning the removal of the boot and exploit options in Windows. Including the necessary drivers when you release sachesi is not an option???
    The issue isn't just that you need to make your own winusb driver. You also need to 'unload' the Link driver which conflicts with boot settings.
    I plan to make a special plugin for Windows that interfaces with the Link driver directly. It's not a priority as Windows already has cfp/cap.

    A few quick questions, going forward is it possible for me to upgrade to a newer version (non destructively)using your utility ?? I last upgraded to OS 10.2.0.1443 using the autoloader method !!
    Only if you have the .bar for the OS.

    Lastly, has OS 1558 been released yet and available ??
    No OS 1558. Latest one is 1581.
    1558 would be a radio if it were a successful build.
    09-02-13 10:32 AM
  2. Norg's Avatar
    The issue isn't just that you need to make your own winusb driver. You also need to 'unload' the Link driver which conflicts with boot settings.
    I plan to make a special plugin for Windows that interfaces with the Link driver directly. It's not a priority as Windows already has cfp/cap.

    Only if you have the .bar for the OS.

    No OS 1558. Latest one is 1581.
    1558 would be a radio if it were a successful build.
    Many thanks again XSacha and many thanks for your patience as you educate me, truly appreciated....

    So, if we use OS 1447 as an example, is the bar file for it available ?? And if yes, therefore could I have upgraded to 1447 without the autoloader using your utility as an alternate to the autoloader method ??

    Posted via CB10 using my handy dandy STL100-3 ~ 10.2.0.1443 ~ AT&T
    09-02-13 10:54 AM
  3. xsacha's Avatar
    Beta 24 up.

    So, if we use OS 1447 as an example, is the bar file for it available ?? And if yes, therefore could I have upgraded to 1447 without the autoloader using your utility as an alternate to the autoloader method ??
    For a .bar to be available, it'd need to appear as an OTA for someone.
    Latest ones we have are 1047 and 1323 I think. May be hard to find them though.
    09-02-13 11:51 AM
  4. Norg's Avatar
    Beta 24 up.

    For a .bar to be available, it'd need to appear as an OTA for someone.
    Latest ones we have are 1047 and 1323 I think. May be hard to find them though.
    Clear now and understood sir, again thanks for the info and help !!
    09-02-13 12:48 PM
  5. fabianr's Avatar
    The issue isn't just that you need to make your own winusb driver. You also need to 'unload' the Link driver which conflicts with boot settings.
    I plan to make a special plugin for Windows that interfaces with the Link driver directly. It's not a priority as Windows already has cfp/cap.
    Okey dokey!
    09-03-13 08:25 AM
  6. D.Vader's Avatar
    Oh yes, this is a device firmware issue. Cannot be fixed on my end.
    Basically when you uninstall apps, the data is left behind.
    Really? So it is definitely caused by un-installing applications? I would think there would be a means to remove that data though.

    Have any newer BB10 OS updates addressed this?
    09-03-13 03:56 PM
  7. ddddafadf's Avatar
    Really? So it is definitely caused by un-installing applications? I would think there would be a means to remove that data though.

    Have any newer BB10 OS updates addressed this?
    I think BlackBerry leaves the data behind on purpose.
    09-03-13 08:37 PM
  8. ralfyguy's Avatar
    I find this stupid to leave data behind. So question is: Is it uninstalled or not? Or does "uninstalling" mean just wiping the app name off the phone?
    There needs to be an app at least to clean up the garbage.
    09-03-13 09:53 PM
  9. xsacha's Avatar
    There needs to be an app at least to clean up the garbage.
    It's not possible. Apps are in protected sandboxes and only the system and the app itself can access its data.
    If the system doesn't clean it up (I think it's a bug), then it will remain until wiped.

    The only workaround is to use debug tokens for your installed apps. This way, you have full access to the data.
    09-03-13 11:07 PM
  10. Norg's Avatar
    xsacha, I've been trying to figure out how to install the 1444 radio signed file using sachesi b24. ...Can you explain the key steps in order to accomplish this please ??
    09-03-13 11:45 PM
  11. ralfyguy's Avatar
    It's not possible. Apps are in protected sandboxes and only the system and the app itself can access its data.
    If the system doesn't clean it up (I think it's a bug), then it will remain until wiped.

    The only workaround is to use debug tokens for your installed apps. This way, you have full access to the data.
    So if you wipe for example and then restore from a backup, all the garbage is restored as well?

    Posted via CB10
    09-03-13 11:53 PM
  12. saotome's Avatar
    sorry for dumb question, is this possible to backup application from appworld not developer/sideload?

    many thanks advanced sachesi
    09-04-13 04:36 AM
  13. xsacha's Avatar
    sorry for dumb question, is this possible to backup application from appworld not developer/sideload?
    No, sorry.
    Only with the 'Backup' tab which is the same as Link. There is no actual access to the apps.
    09-04-13 06:36 AM
  14. AnimalPak200's Avatar
    If I forgot to add the radio file to the 'bar' folder (Apps, OS, Radio) ... what's the best way to load the correct radio. Last time I tried making an autoloader from only a radio .signed file and running it, it bricked my Z10.
    09-04-13 08:08 PM
  15. xsacha's Avatar
    You can just sideload the radio.bar in the Install tab.
    09-04-13 09:39 PM
  16. AnimalPak200's Avatar
    I tried that, but it kept giving me an error. Even after hitting the 'refresh' button, I could see the old radio file (incompatible with new OS) was still there. I tried to delete it (selecting check box and clicking the trash can icon), but it would keep showing up.
    09-04-13 10:02 PM
  17. AnimalPak200's Avatar
    Actually, I just realized that my original folder did have the radio file in it. For some reason, when I 'installed' the folder, the apps and the OS went, but the radio file remained unchanged. Any ideas as to what I did wrong?
    09-04-13 10:34 PM
  18. nuntym's Avatar
    I am using Sachesi on Win7. I downgraded my Z10 from 10.2 to 10.1; before downgrading, i used both Sachesi and BB Link to back up. Now that my Z10 is running on 10.1, I tried to restore my data using Sachesi, but the dialogue box "Error: Could not open backup file" keeps on popping up for both the BB Link and Sachesi backups. Help please?
    09-04-13 11:09 PM
  19. xsacha's Avatar
    Actually, I just realized that my original folder did have the radio file in it. For some reason, when I 'installed' the folder, the apps and the OS went, but the radio file remained unchanged. Any ideas as to what I did wrong?
    What is the name of the radio bar file?
    Currently I determine if it's a radio solely based off its name.
    You can try ensuring that the filename begins with "wtr-".

    I am using Sachesi on Win7. I downgraded my Z10 from 10.2 to 10.1; before downgrading, i used both Sachesi and BB Link to back up. Now that my Z10 is running on 10.1, I tried to restore my data using Sachesi, but the dialogue box "Error: Could not open backup file" keeps on popping up for both the BB Link and Sachesi backups. Help please?
    This means that the operating system did not allow me to open that file. Where is the file located? Does the app have permission to access it?
    09-05-13 12:21 AM
  20. nuntym's Avatar
    This means that the operating system did not allow me to open that file. Where is the file located? Does the app have permission to access it?
    As far as I know, the program should have access to both files. The BB Link backup is in the default backup location in "My Documents\Blackberry\Backup", and the Sachesi backup is in the same folder as where I extracted Sachesi. Both are not read-only files.
    09-05-13 12:37 AM
  21. AnimalPak200's Avatar
    What is the name of the radio bar file?
    Currently I determine if it's a radio solely based off its name.
    You can try ensuring that the filename begins with "wtr-".
    Hmmm... I don't see any files that start with "wtr-" so I'm doing something wrong.

    I'm trying to get the 10.1.0.4634 radio onto an STL100-4. Your "search" tab gave me a 22MB file that is named "qc8960.omadm-10.1.0.4634...bar" as part of an entire 10.1.0.4633 OS download, and I basically just dragged the entire folder into the instal tab.
    09-05-13 12:51 AM
  22. thurask's Avatar
    Hmmm... I don't see any files that start with "wtr-" so I'm doing something wrong.

    I'm trying to get the 10.1.0.4634 radio onto an STL100-4. Your "search" tab gave me a 22MB file that is named "qc8960.omadm-10.1.0.4634...bar" as part of an entire 10.1.0.4633 OS download, and I basically just dragged the entire folder into the instal tab.
    Radio filenames are determined like so:

    qc8960.wtr-{version}-nto+armle-v7+signed.bar - Q10/Q5
    m5730-{version}-nto+armle-v7+signed.bar - Z10 STL100-1
    qc8960.-{version}-nto+armle-v7+signed.bar - Z10 STL100-2/3
    qc8960.omadm-{version}-nto+armle-v7+signed.bar - Z10 STL100-4
    09-05-13 01:04 AM
  23. AnimalPak200's Avatar
    Radio filenames are determined like so:

    qc8960.wtr-{version}-nto+armle-v7+signed.bar - Q10/Q5
    m5730-{version}-nto+armle-v7+signed.bar - Z10 STL100-1
    qc8960.-{version}-nto+armle-v7+signed.bar - Z10 STL100-2/3
    qc8960.omadm-{version}-nto+armle-v7+signed.bar - Z10 STL100-4
    That sounds about right then... For some reason it didn't replace an older radio I had previously installed... And Phone calls stopped working,
    09-05-13 01:16 AM
  24. xsacha's Avatar
    That sounds about right then... For some reason it didn't replace an older radio I had previously installed... And Phone calls stopped working,
    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?
    09-05-13 03:49 AM
  25. 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?
    Yeah, still isn't working. And I'm pretty sure it's the STL 100-4... I'm on Verizon.

    It starts to send the file, then eventually hangs at 50% and then Sachesi returns an "Error 500". Nothing changes on the device. I've tried several USB ports (although the entire OS loaded successfully via the first one anyway).

    If renaming doesn't work, I might try to do a back up at this version, then do a destructive full autoloader (they've always worked for me) and (hopefully) restore... although it sure seems unnecessary given how easy ppl seem to swap radios.

    Appreciate the continued help.

    Posted via CB10
    09-05-13 09:38 AM
3,553 ... 2627282930 ...

Similar Threads

  1. Replies: 41
    Last Post: 01-09-16, 12:03 PM
  2. Q10 shows "4G" and Z10 shows "4GLTE"
    By BGQ10 in forum BlackBerry Q10
    Replies: 22
    Last Post: 01-20-14, 11: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, 10: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, 07: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, 09:38 AM
LINK TO POST COPIED TO CLIPBOARD