08-12-15 11:53 PM
702 ... 1112131415 ...
tools
  1. BigBadWulf's Avatar
    Thank you to remind everyone of us about pride. From our side it is not about pride, it was because we do look at the reality that the affected devices includes one/some who never use SIC.
    I asked folks to tell us whether the blue LED was out of the box. Some said yes. It's entirely plausible something done in programming at the factory resulted in some of the devices having issues. It's also entirely plausible a corrupt download of SIC, or poor run on PC due to G_d knows what, caused some to have this issue. WE DON'T KNOW FOR SURE! Y'all are making a mess out of this thread, defending a program ffs. We all love BlackBerry. Is this thread an attack of BlackBerry, because it could easily be construed as that too.

    ENOUGH ALREADY!!!
    Mecca EL and jpvj like this.
    11-25-14 07:36 AM
  2. BigBadWulf's Avatar
    Stop, please stop. I have used SIC many times. All on the same PC, same cable, same port, same version. One of those times, it failed to remove the password, all five times. Every other time it worked perfectly. I'm attacking nothing. Simply using my own experience, and taking the logical leap that SIC should be something to look at as a cause. I believe it was also suggested an older cfp could have been the cause. The two are intertwined.

    Now we're going to have to go back and clean a mess on this thread, so we all can get back to focusing on a solution for those affected by this blue light issue.
    Last edited by zocster; 11-25-14 at 08:24 AM. Reason: quoted deleted post
    GPuba, Mecca EL, zephyr613 and 1 others like this.
    11-25-14 07:51 AM
  3. GPuba's Avatar
    Please, people! Let's not lose sight of the fact that there are some people that are having REAL problems w/their phones. If it were any of US (whose phones are NOT experiencing this), we would be MORE than willing to troubleshoot ANY and EVERYTHING.

    Let us try to look at it from the perspective of those that are currently affected, as opposed to having an personal feelings convention.

    Folk attacking the competence of others here is ridiculous, for if ANY OF US were TRULY "competent" on THIS issue, if we FULLY understood what could and/or could not be the cause of the problem, then there would no longer be an issue, for it would be SOLVED. This is why we TROUBLESHOOT. No need to troubleshoot if we have all the answers.

    Let us get back to CRITICAL THINKING instead of just being CRITICAL, so we can find the SOLUTION for this annoying blue light and related issue. Folk are far too sensitive these days. Logic and emotions cannot occupy the same quadrant, and critical thinking involves brainstorming AND logic. Let us learn to live, think, and act by PRINCIPLE and not emotion.

    Posted via CB10
    11-25-14 07:59 AM
  4. HarryDragon's Avatar
    That's right lets all work together to find solution for this poor lad.....
    As I mentioned before.... It's all about love not about bashing each other.....
    11-25-14 08:02 AM
  5. GPuba's Avatar
    Now... back to the purpose of this thread.

    Has anyone tried running Sachesi (non-destructively) from 10.2.1 to 10.3.1, and then immediately following it up w/an autoloader, or vice-versa?

    I know this seems extremely remedial and simplistic, but I have found in my many experiences that the solution is often more simple than we would think, thus while those with more knowledge suggest some good technical potential solutions, I will try to suggest some basic, but overlooked, potential ones. That is the correct way for a group to troubleshoot.

    Posted via CB10
    BigBadWulf likes this.
    11-25-14 08:06 AM
  6. xsacha's Avatar
    I would suggest trying:
    cfp resetqnxosregion
    If no one has yet.

    Otherwise, try the only method that has worked so far (what someone posted above), which is draining the power from device.

    As older versions of SIC did attempt to wipe arbitrary locations (even ones that were not valid), it was a concern. Although it doesn't seem to be the problem in this instance. Fairly sure cfp doesn't allow doing anything damaging on a secure device (luckily).
    Last edited by BigBadWulf; 11-25-14 at 10:22 AM. Reason: removed personal paragraph
    11-25-14 08:21 AM
  7. zocster's Avatar
    I really don't feel like getting out of bed at 3 a.m. just to clear out some junk peeps. Please keep it on topic, and chill, let's help OP determine the root cause of his/her problem.

    CHILL!
    BigBadWulf likes this.
    11-25-14 08:28 AM
  8. ofutur's Avatar
    The blue light is turned on for device "in production". I interpret this as devices which have already been released and are in use today, as opposed to dev, insecure, in pre-production, etc. The script queries the nvram and acts accordingly.
    The led turns to blue at run level 0 (low level hardware init) and the script disables some dev only features. It's then turned off at the end of the boot process.
    The fact that some people see it on for a while just indicates that the boot process never successfully completes and after a time-out, the device just reboots because something went wrong. And a booting sequence on a dev OS is different, so it's probably the reason those OS boot fine.

    I'm rooting for a partition corruption as highlighted earlier, which just makes the whole thing unstable.

    EDIT: A dev OS probably runs the device in developer mode (see my post below) and that's probably what's preventing the device from rebooting.
    Last edited by ofutur; 11-25-14 at 11:16 AM.
    toobs623, BigBadWulf and Mecca EL like this.
    11-25-14 09:10 AM
  9. ofutur's Avatar
    People with the automatic reset, could you try?
    Code:
    C:> cfp hos
    Our devices are in "user" mode which make them reset in case of a catastrophic failure. By switching to the "developer" mode, the device will not reset, but displays an error message instead.

    EDIT: Did not fix the reboots for me. No error messages shown on screen.
    Last edited by ofutur; 11-25-14 at 03:36 PM. Reason: Formatting
    clie610 and Mecca EL like this.
    11-25-14 10:26 AM
  10. clie610's Avatar
    People with the automatic reset, could you try?
    `$ cfp hos`

    Our devices are in "user" mode which make them reset in case of a catastrophic failure. By switching to the "developer" mode, the device will not reset, but display an error message instead.
    Always new things to learn everyday from this forum...thank you
    11-25-14 10:51 AM
  11. ofutur's Avatar
    Code:
    QNX Partition: type=0x03:80, blocks 33-95, total = 63, "nvram"
        QNX Partition: type=0x0F:80, blocks 96-543, total = 448, "cal_work"
        QNX Partition: type=0x11:80, blocks 544-1055, total = 512, "dmi"
        QNX Partition: type=0x12:00, blocks 544-544, total = 1, "dmi_mbr"
        QNX Partition: type=0x93:00, blocks 559-559, total = 1, "dmi_sig"
        QNX Partition: type=0x13:00, blocks 560-1055, total = 496, "dmi_fsys"
        QNX Partition: type=0x10:00, blocks 1056-2079, total = 1024, "cal_backup"
        QNX Partition: type=0x01:80, blocks 2080-10271, total = 8192, "os"
        QNX Partition: type=0x06:20, blocks 2080-2080, total = 1, "os_mbr"
        QNX Partition: type=0x07:40, blocks 2095-2095, total = 1, "os_sig"
        QNX Partition: type=0x89:40, blocks 2095-2095, total = 1, "os_sig"
    START OF FIRST SECURE
        QNX Partition: type=0x08:40, blocks 2096-2271, total = 176, "system"
        QNX Partition: type=0x09:40, blocks 2272-10271, total = 8000, "os_fsys"
        QNX Partition: type=0x01:80, blocks 10272-18463, total = 8192, "os"
        QNX Partition: type=0x06:20, blocks 10272-10272, total = 1, "os_mbr"
        QNX Partition: type=0x07:00, blocks 10287-10287, total = 1, "os_sig"
        QNX Partition: type=0x89:00, blocks 10287-10287, total = 1, "os_sig"
        QNX Partition: type=0x08:00, blocks 10288-10463, total = 176, "system"
        QNX Partition: type=0x09:00, blocks 10464-18463, total = 8000, "os_fsys"
    END OF FIRST SECURE
        QNX Partition: type=0x02:80, blocks 18464-20511, total = 2048, "radio"
        QNX Partition: type=0x0A:20, blocks 18464-18464, total = 1, "radio_mbr"
        QNX Partition: type=0x0B:40, blocks 18479-18479, total = 1, "radio_sig"
        QNX Partition: type=0x8C:40, blocks 18479-18479, total = 1, "radio_sig"
        QNX Partition: type=0x0C:40, blocks 18480-19487, total = 1008, "radio_fsys"
        QNX Partition: type=0x0A:20, blocks 19488-19488, total = 1, "radio_mbr"
        QNX Partition: type=0x0B:00, blocks 19503-19503, total = 1, "radio_sig"
        QNX Partition: type=0x8C:00, blocks 19503-19503, total = 1, "radio_sig"
        QNX Partition: type=0x0C:00, blocks 19504-20511, total = 1008, "radio_fsys"
    START OF SECOND SECURE
        QNX Partition: type=0x05:80, blocks 20512-524287, total = 503776, "user"
    END OF SECOND SECURE
    Interesting to see the differences with my broken Q10. The user partition is really small compared to yours... Your backup partition is also larger.
    Code:
        QNX Partition: type=0x03:80, blocks 33-95, total = 63, "nvram"
        QNX Partition: type=0x0F:80, blocks 96-671, total = 576, "cal_work"
        QNX Partition: type=0x10:00, blocks 672-1567, total = 896, "cal_backup"
        QNX Partition: type=0x11:80, blocks 1568-2079, total = 512, "dmi"
        QNX Partition: type=0x12:00, blocks 1568-1568, total = 1, "dmi_mbr"
        QNX Partition: type=0x93:00, blocks 1583-1583, total = 1, "dmi_sig"
        QNX Partition: type=0x13:00, blocks 1584-2079, total = 496, "dmi_fsys"
        QNX Partition: type=0x01:80, blocks 2080-10271, total = 8192, "os"
        QNX Partition: type=0x06:20, blocks 2080-2080, total = 1, "os_mbr"
        QNX Partition: type=0x07:40, blocks 2095-2095, total = 1, "os_sig"
        QNX Partition: type=0x89:40, blocks 2095-2095, total = 1, "os_sig"
        QNX Partition: type=0x08:40, blocks 2096-2271, total = 176, "system"
        QNX Partition: type=0x09:40, blocks 2272-10271, total = 8000, "os_fsys"
        QNX Partition: type=0x01:80, blocks 10272-18463, total = 8192, "os"
        QNX Partition: type=0x06:20, blocks 10272-10272, total = 1, "os_mbr"
        QNX Partition: type=0x07:00, blocks 10287-10287, total = 1, "os_sig"
        QNX Partition: type=0x89:00, blocks 10287-10287, total = 1, "os_sig"
        QNX Partition: type=0x08:00, blocks 10288-10463, total = 176, "system"
        QNX Partition: type=0x09:00, blocks 10464-18463, total = 8000, "os_fsys"
        QNX Partition: type=0x02:80, blocks 18464-22559, total = 4096, "radio"
        QNX Partition: type=0x0A:20, blocks 18464-18464, total = 1, "radio_mbr"
        QNX Partition: type=0x0B:40, blocks 18479-18479, total = 1, "radio_sig"
        QNX Partition: type=0x8C:40, blocks 18479-18479, total = 1, "radio_sig"
        QNX Partition: type=0x0C:40, blocks 18480-20511, total = 2032, "radio_fsys"
        QNX Partition: type=0x0A:20, blocks 20512-20512, total = 1, "radio_mbr"
        QNX Partition: type=0x0B:00, blocks 20527-20527, total = 1, "radio_sig"
        QNX Partition: type=0x8C:00, blocks 20527-20527, total = 1, "radio_sig"
        QNX Partition: type=0x0C:00, blocks 20528-22559, total = 2032, "radio_fsys"
        QNX Partition: type=0x05:80, blocks 22560-262143, total = 239584, "user"
    Mecca EL likes this.
    11-25-14 10:53 AM
  12. clie610's Avatar
    Interesting to see the differences with my broken Q10. The user partition is really small compared to yours... Your backup partition is also larger.
    [/CODE]
    normal one is with 128 multipliers
    11-25-14 11:02 AM
  13. ofutur's Avatar
    And something else, you should be able to get a comprehensive log of all the cfp commands that you've run for the past 2-3 months.

    Simply use this:
    Code:
    C:> cfp flashinfo > flashinfo.txt
    In mine I can see all the commands sent by SIC
    Code:
    --> Thu Oct 02 21:42:07 2014:3.10.0.57:DONE:EF:CFP -u erase 0x00005820-0x0003A3FF-ErrorCode:0-Success!
    --> Thu Oct 02 21:41:47 2014:3.10.0.57:EF:CFP -u erase 0x00005820-0x0003A3FF
    --> S:00010014
    --> Thu Oct 02 21:41:19 2014:3.10.0.57:DONE:EF:CFP -u nuke -a-ErrorCode:0-Success!
    --> Thu Oct 02 21:41:19 2014:3.10.0.57:EF:CFP -u nuke -a
    --> S:00010014
    Radio flashes have no OS number
    Code:
    --> Sat Nov 15 23:14:02 2014:3.11.0.11:DONE:QNXLOAD:0.0.0.0 DEV-ErrorCode:0-Success!
    --> Sat Nov 15 23:13:59 2014:3.11.0.11:QNXLOAD:0.0.0.0 DEV
    --> D:00010015
    A successful OS load
    Code:
    --> Thu Oct 30 23:46:09 2014:3.11.0.13:DONE:QNXLOAD:10.3.1.1016 DEV-ErrorCode:0-Success!
    --> Thu Oct 30 23:45:41 2014:3.11.0.13:QNXLOAD:10.3.1.1016 DEV
    --> D:00010015
    Unfortunately, it doesn't give any info about OTA loads, but there is an option to dump logs. The only problem is that they're encrypted, but I think that can be changed via Link.
    69goat likes this.
    11-25-14 11:06 AM
  14. clie610's Avatar
    And something else, you should be able to get a comprehensive log of all the cfp commands that you've run for the past 2-3 months.

    Simply use this:
    Code:
    C:> cfp flashinfo > flashinfo.txt
    In mine I can see all the commands sent by SIC
    Code:
    --> Thu Oct 02 21:42:07 2014:3.10.0.57:DONE:EF:CFP -u erase 0x00005820-0x0003A3FF-ErrorCode:0-Success!
    --> Thu Oct 02 21:41:47 2014:3.10.0.57:EF:CFP -u erase 0x00005820-0x0003A3FF
    --> S:00010014
    --> Thu Oct 02 21:41:19 2014:3.10.0.57:DONE:EF:CFP -u nuke -a-ErrorCode:0-Success!
    --> Thu Oct 02 21:41:19 2014:3.10.0.57:EF:CFP -u nuke -a
    --> S:00010014
    Radio flashes have no OS number
    Code:
    --> Sat Nov 15 23:14:02 2014:3.11.0.11:DONE:QNXLOAD:0.0.0.0 DEV-ErrorCode:0-Success!
    --> Sat Nov 15 23:13:59 2014:3.11.0.11:QNXLOAD:0.0.0.0 DEV
    --> D:00010015
    A successful OS load
    Code:
    --> Thu Oct 30 23:46:09 2014:3.11.0.13:DONE:QNXLOAD:10.3.1.1016 DEV-ErrorCode:0-Success!
    --> Thu Oct 30 23:45:41 2014:3.11.0.13:QNXLOAD:10.3.1.1016 DEV
    --> D:00010015
    Unfortunately, it doesn't give any info about OTA loads, but there is an option to dump logs. The only problem is that they're encrypted, but I think that can be changed via Link.
    yep, because we're not randomly put any range in it
    zocster and Sator like this.
    11-25-14 11:11 AM
  15. wu-wei's Avatar
    People with the automatic reset, could you try?
    Code:
    C:> cfp hos
    Our devices are in "user" mode which make them reset in case of a catastrophic failure. By switching to the "developer" mode, the device will not reset, but displays an error message instead.
    Always new things to learn everyday from this forum...thank you
    ...or by reading the help file already included in the utilities you've been using. But whatever.

    And we all already know you chose a random range. Sorry if I revealed the recipe for your useless secret sauce.
    11-25-14 11:53 AM
  16. gapostol's Avatar
    Did anyone try the new 1154 leak? Is this problem still there?

    Posted via CB10
    11-25-14 12:38 PM
  17. lawguyman's Avatar
    I read that SIC wipe is just a batch script that runs a BlackBerry utility. Is this true? What value does SIC add to the BlackBerry utility?

    Posted via CB10
    11-25-14 12:48 PM
  18. Rock Star1's Avatar
    1154 Same Problem
    11-25-14 12:58 PM
  19. zephyr613's Avatar
    1154 Same Problem
    Rockstar,

    Not to beat a dead horse here but could you please try the following :

    Load stable full 10.2.X (ensure reboot sticks settings and NO BLUE LED)

    Install 10.3.1.1154 using full auto loader. Do NOT wipe or SIc wipe for cfp nuke at all.

    See if that resolves anything while allowing phone to re boot itself after install.

    I'm just thinking that maybe we are all looking way too deep into this while trying to figure out. RCA

    Looking forward to your response and potential resolution.

    Z10STL100-4/10.3.1.1151
    11-25-14 01:18 PM
  20. dviles's Avatar
    My device doesn't "automatically" reboot. It never reboots, unless I do it. It boots with a blue led and no setup. Although, on 10.2.1.3442 the blue led is rare. Every other OS had the blue led, though.

    Posted via CB10
    11-25-14 01:43 PM
  21. zephyr613's Avatar
    My device doesn't "automatically" reboot. It never reboots, unless I do it. It boots with a blue led and no setup. Although, on 10.2.1.3442 the blue led is rare. Every other OS had the blue led, though.

    Posted via CB10
    Understood, what I was suggesting was to get a "base line" of 10.2.X and then run the auto loader with no sic wipe of cfp nuke in between Once the auto loader completes it should re boot your device automatically. Are you saying this does NOT hapen when you have used auto loader in the past?

    Z10STL100-4/10.3.1.1151
    Last edited by zephyr613; 11-25-14 at 02:40 PM.
    11-25-14 02:01 PM
  22. ofutur's Avatar
    Tried
    Code:
    cfp resetqnxosregion
    and saw no change. Partitions are the same and the device auto-reboots once like it always does.

    Tried
    Code:
    cfp.exe -u erase
    and got told off because I was trying to erase outside of the secure range.
    After investigation, I've found that the proper ranges are given lower in the logs
    Code:
    Memory Map:
      NAND Blocks:       238592 * 64 Kb
      RAM Base:          0x80000000
      IRAM Base:         0x2E000000
     OS Range:          2096 - 2266
    File System:
      Memory Map:
                         22560 - 238591
      Sectors:           216032
    So that would be
    Code:
    C;> cfp -u erase 0x00005820-0x0003A3FF
    and
    Code:
    C;> cfp -u erase 0x00000830-0x000008DA
    EDIT: After all this my password is still not wiped, so it's only doing some house cleaning.
    EDIT2: Device still reboots and non-destructive upgrades still fail by making the device non-nootable, so erasing those partitions does not seem to solve any issues.
    EDIT3: After the erase, the OS range changes to a different value, ready to load an even bigger OS.
    Code:
    OS Range:          2096 - 18463
    Last edited by ofutur; 11-25-14 at 03:25 PM.
    11-25-14 02:24 PM
  23. ofutur's Avatar
    Here is a log for a healthy device
    Code:
      Boot OS Count:     7,0,0 (Region0,Region1,Max)
                         3,0,0 (Version,Requested Region,Actual Region)
      OS Extra info:     2,0,0 (Version,Radio Max Boot Count,Error code)
    Now the same thing after a failed upgrade via Sachesi
    Code:
      Boot OS Count:     4,4,4 (Region0,Region1,Max)
                         3,1,0 (Version,Requested Region,Actual Region)
      OS Extra info:     2,0,7 (Version,Radio Max Boot Count,Error code)
      Boot Count Info:   QNX Sanity Check Failed
    Would be interesting if people who have issues could grab the same data.

    The OS gave up after having tried to reboot each region 4 times
    There is a discrepancy between the requested version and the actual region. Maybe Sachesi needs to tell the OS which one to update?
    I have no idea what error code 7 means... Let's see if more people get the same one.

    Flashing a radio via an autoloader always makes the device bootable again.
    Last edited by ofutur; 11-25-14 at 03:28 PM.
    11-25-14 03:09 PM
  24. dviles's Avatar
    I'm sorry Zypher613, but Ofutur seems to be working on a solution to the device resetting. My device doesn't randomly reset. Yes it does reset after an upgrade.

    Posted via CB10
    11-25-14 03:39 PM
  25. jpvj's Avatar
    It's really amazing to read the posts in this thread: It covers everything from "try battery pull", use SIC, try autoloader (shrinked), some "let's make fun of [CENSORED OUT]" to people showing some debugging skills.

    I'll place my 5 cents on a healthy device (from a HW point of view) but in a non-valid state. How they were brought into this state is still unknown.

    Let's keep thread on-track and our minds open.
    ppeters914 likes this.
    11-25-14 03:49 PM
702 ... 1112131415 ...

Similar Threads

  1. Snapchat since 10.3.1
    By AllenMQ in forum Ask a Question
    Replies: 19
    Last Post: 04-16-15, 06:34 PM
  2. Z30 10.3 Android Application Performance
    By bbking67 in forum BlackBerry Z30
    Replies: 6
    Last Post: 02-27-15, 07:31 AM
  3. Stickers issues after 10.3 official update anyone?
    By stethur in forum Ask a Question
    Replies: 2
    Last Post: 02-25-15, 09:13 PM
  4. Replies: 1
    Last Post: 02-25-15, 07:47 PM
  5. Having 'Blue LED' errors on your BlackBerry 10 device? Here's how to fix it!
    By CrackBerry News in forum CrackBerry.com News Discussion
    Replies: 0
    Last Post: 02-25-15, 07:12 PM
LINK TO POST COPIED TO CLIPBOARD