Forum TI-Planet.org

Whenever I try to install the CAS OS 3.6.0.546 on my TI Nspire CX using nLaunchy, I get the infamous clock of death:



I have tried the diagnostics mode trick, however that showed no error. I have also tried removing and replacing the battery. That also did not work. I have also tried running with and without Ndless, no change.

The installation of the OS itself goes smooth and everything works well, it's just that it does not ever get past that clock. How can I fix this and still have Ndless?

AFAIK, all other CAS OSes work fine, I have yet to test the non-CAS 3.6.0.546 OS with nLaunchy.

My calculator has datecode P-0811C and is running Boot2 3.10.16.

I am from America, and I do not understand French at all. If possible, can you please reply in English? Thanks!!
Je suis originaire de l'Amérique, et je ne comprends pas du tout le français. Si possible, pouvez-vous s'il vous plaît répondre en anglais? Merci !!

It's normal - 3.6 CAS does not work on non-CAS calculators, even with Nlaunch.

Chances are that it boils down to nullifying a single test followed by a branch, but nobody has published information about that.

Ah, but the README for v2.4 says so:

Code: Select all

**** CX installation (see above for Clickpad and Touchpad) *****
----------------------------------------------------------------
0) backup all your documents from your Nspire on your computer

1) install the 3.1.0.16 boot2, usually known as "3.1".
   If you currently have OS 3.1.0.392, 3.2.0.1212, 3.2.0.1219 or 3.2.3.1233 you
   probably already have it. If you have installed any newer version without
   TNOC-ing it, you probably will not be able to easily install the 3.1.0.16
   boot2.
   Otherwise, install OS 3.1.0.392:
   CX CAS: http://ti-pla.net/a3718
   CX    : http://ti-pla.net/a3717

2) get a compatible OS. See
   http://tiplanet.org/forum/archives_list.php?id=OS+Nspire
   - NOTE: Not all TI-OSes are compatible with nLaunchy (but many are).
     OSes 3.1.0.392, 3.2.0.1219, 3.2.0.1233 and 3.6.0.546 are.
     For a full list of compatible OSes, check src/patch.c


Also, the code in patch.c says it support 3.6.0.546:

Code: Select all

        case 0x10375620:    // TI-NspireCX-3.6.0.546/phoenix.raw
            patch_CXNCAS_3_6_0_546_extra();
            patch_CXNCAS_3_6_0_546_common();
        break;
        case 0x10376090:    // TI-NspireCXCAS-3.6.0.546/phoenix.raw
            patch_CXCAS_3_6_0_546_extra();
            patch_CXCAS_3_6_0_546_common();
        break;

I have posted a bug report, but this just seems to be weird. I know it's supported, the code's there.

I also downloaded the OS from here. Maybe a checksum/Boot2 failure?

Yes, 3.6 CX CAS will run on a CX CAS, and 3.6 CX will run on a CX.

3.6 are supported, or you wouldn't have been able to reach the above screen.

It's not a bug, TI did add a new hardware check in OS 3.6, which prevents the 3.6 OS from running on a different model.
And nobody took the time to take care of this new check up to now.

Awe. Is there no way to bypass this? I am pretty familiar with *nix, so I might be able to do something...

If not, is there any sort of Ndless patch (even beta) for CAS OS 3.2.3?

I need Ndless, but I also need conics. This is a problem for me...

There's no Ndless-able OS between 3.1 and 3.6.

If you need both CAS and 3.6 features, the only way for now is to install both OSes on your calculator, and to switch between them with Nlaunch.
Check this tutorial: viewtopic.php?f=57&t=11019

OK then. Thanks for your help. I'll just stay on 3.1 for now.

Maybe one day there will be Ndless for 3.2...

Until then, thanks for all the help!

Maybe one day there will be Ndless for 3.2...

I think we can safely say that this will never occur, unless you do it yourself or find someone interested in investing a significant amount of development time on a largely outdated OS, all the more Ndless is not available for OS 3.9, hampering both school and non-school uses of the Nspire platform

It would be far easier to use the publicly available OS decryption tooIs, reverse-engineer the OS binary to find the offending code in OS 3.6.0.546/550, and publish the result (which you'd better do anonymously ), than to develop Ndless for OS 3.2.

Isn't the model number stored in the NAND memory?

Why don't we just have a patch to change that to match the CAS version?