09-08-15 09:03 PM
609 ... 56789 ...
tools
  1. ofutur's Avatar
    Well done on the installer. I like the progress indicator. I guess regular checks is a good way of keeping the connection alive.

    One thing could be useful, if doable. An OS checker. autoload.exe notifies the user is the OS is not compatible with his device. This installer goes through the whole process and does nothing if the device is not compatible.
    04-30-13 03:55 AM
  2. xsacha's Avatar
    How do I know if it's compatible?
    You can load OS that are not intended for that device. Any qualcomm firmware works on any qualcomm device.
    04-30-13 05:57 AM
  3. ofutur's Avatar
    Is there a way to check the hardware ID family in the firmware against the one in the device before uploading it?

    I uploaded a Qualcomm firmware onto a TI device and there was no complaint, but it didn't work of course. And I'm guessing that if I uploaded a Q10 OS onto a Z10 I would get the same result.
    04-30-13 06:11 AM
  4. xsacha's Avatar
    Well you can load Q10 OS on to Z10 because they are same family. It should work.
    TI OMAP won't but I don't know how to check family other than manual (which I'd need to update all the time).
    04-30-13 07:21 AM
  5. ofutur's Avatar
    The Q10/Z10 radios are different and the device won't boot if you upload the wrong one. At least that's what happens with an autoloader.

    But you're right, it would be too much work to maintain hardware tables.
    04-30-13 07:47 AM
  6. lbfe's Avatar
    this is from stl100-2
    Code:
    Hardware ID:       0x8700240A RIM BlackBerry Device
    HW ID Override:    0x8700240A (OSTypes: 0x00000010)
    Hardware OS ID:    0x051D0001
    most important is hardware OS ID this is stored in OS.bar to radio dont have it that why can be loaded with autoloader cross stl100 and q10 models
    04-30-13 08:43 AM
  7. ofutur's Avatar
    Maybe the platform hardware ID would be a good first step, but it is indeed missing from the radio file...
    0x06001A06 for Dev Alpha A/B, Z10-1
    0x051D0001 for Z10/Q10
    04-30-13 09:06 AM
  8. wu-wei's Avatar
    Would love to see a way for sachup to retain settings between runs...so we're not always changing PIN, country and carrier codes, etc. Just a minor bother.
    faquick and Mecca EL like this.
    04-30-13 11:19 AM
  9. xsacha's Avatar
    You shouldn't need to change PIN. Don't think it will affect anything unless you use beta server.
    I figured the default settings are probably the best on every load.
    Sator likes this.
    04-30-13 12:43 PM
  10. Sith_Apprentice's Avatar
    Xsacha,
    does this work on internal beta servers as well?
    04-30-13 12:51 PM
  11. Morten's Avatar
    I see some here have a DevAlphaC device... so .. Does anyone know of the existence of an autoloader for the original 10.1.0.809 OS that came with the C devices?
    04-30-13 12:53 PM
  12. ofutur's Avatar
    I see some here have a DevAlphaC device... so .. Does anyone know of the existence of an autoloader for the original 10.1.0.809 OS that came with the C devices?
    I doubt you'll find it. Download the dev version (1485) from the dev site or the version used by the press (1483)
    04-30-13 05:04 PM
  13. ofutur's Avatar
    You shouldn't need to change PIN. Don't think it will affect anything unless you use beta server.
    I figured the default settings are probably the best on every load.
    But not all regions offer newer releases at the same time, so in order to try and find something new, we have to change country+carrier code a few times. With presets, we could save a few codes which often get the releases first and just quickly scan them.
    04-30-13 05:06 PM
  14. Boot191's Avatar
    Sachibar worked great!! I've already installed 10.0.10.99 onto my STL100-1 with no error at all.
    but the Software Release in about menu is still 10.0.10.82 though. OS is up to 10.0.10.738 which is right for this firmware. not sure what happened. :/
    05-01-13 10:47 AM
  15. xsacha's Avatar
    Software releases is a new thing for BB10. My guess is updates don't affect that number, only full installs (debricks).
    Boot191 likes this.
    05-01-13 08:20 PM
  16. missing.cn's Avatar
    i hava a dev A ,but couldnt find out anything.
    05-02-13 02:20 AM
  17. xsacha's Avatar
    They have stopped producing firmware for Dev A but STL 100-1 firmware should work on that as well.
    05-02-13 02:50 AM
  18. faquick's Avatar
    They have stopped producing firmware for Dev A but STL 100-1 firmware should work on that as well.
    Yes, until 10.0 builds. I tried 10.1.0.1609 a couple days ago but it keeps rebooting after ~30 seconds desktop time
    05-02-13 02:57 AM
  19. xsacha's Avatar
    Could that just be because you're using the wrong radio file?
    05-02-13 03:40 AM
  20. ofutur's Avatar
    From my experience, the device doesn't even boot and shows a messages about the wrong radio when you're using the wrong file.
    05-02-13 07:22 AM
  21. xsacha's Avatar
    Updated first post with new packs and a link to CAP.
    faquick likes this.
    05-04-13 12:35 AM
  22. ofutur's Avatar
    I like the new name.... SachUpiBar
    05-04-13 05:21 AM
  23. ofutur's Avatar
    For people who want to play with Country+carrier code to see if they can find something, I found this list useful
    Wikipedia | Mobile country code
    Sator and wu-wei like this.
    05-04-13 05:38 AM
  24. lawguyman's Avatar
    Is it possible to load a stl100-1 os on a Playbook? I see this was done with older dev os's.

    Posted via CB10
    05-04-13 08:49 AM
  25. dustmalik's Avatar
    Updated first post with new packs and a link to CAP.
    Great work man. Please Keep it up.

    Posted via CB10 using my Gorgeous Z10
    05-04-13 09:05 AM
609 ... 56789 ...
LINK TO POST COPIED TO CLIPBOARD