The other day I decided to experiment changing the TI-NSpire OS to something made by me. Of course I knew that I had to study the OSs made by Texas Instruments first, it's what I did.

I don't know ARM9 Assembly, so all I could do were some tiny experiments:


Experiment 1
I changed, in the code, 631 to 632. I was editing TI-Nspire-2.1.0.631.tno and in the code (hex to string) it said 'TI-NSpire.tno 2.10.631'. I changed the '631' to '632'. Tried putting it in my calculator and it said corrupted.

Experiment 2->30
I tried changing half-bytes, so 'DB' to 'DA' and stuff like that, also tried changing entire bytes, I made, in the overall, more than 30 different attempts to changing the OS (half-bytes!). All of them, Computer Link software said 'corrupted'.


Conclusion and Questions
Has any of you successfully changed anything in any of the OSs?
How come the Computer Link software be so good at detecting corruptions (Internet connection?)?.


My next experiment will be bit-changing, I'll open the binary of it, and change 1 bit in the code, then I'll see if Computer Link Software still states it as corrupted.

This looks like it may have some editable codes but there is something in the software protecting certain parts. I bet you could find one updated parrt that you could edit.(try knocking your internet connection out when you do it)

Not only a checksum, don't you also have to factor the 1024-bit signing keys?

The checksum makes sense, thanks.

"Not only a checksum, don't you also have to factor the 1024-bit signing keys?"

What is that?

Now to break the signing keys... This might take a while...

The other day I decided to experiment changing the TI-NSpire OS to something made by me. Of course I knew that I had to study the OSs made by Texas Instruments first, it's what I did.

I don't know ARM9 Assembly, so all I could do were some tiny experiments:


Experiment 1
I changed, in the code, 631 to 632. I was editing TI-Nspire-2.1.0.631.tno and in the code (hex to string) it said 'TI-NSpire.tno 2.10.631'. I changed the '631' to '632'. Tried putting it in my calculator and it said corrupted.

Experiment 2->30
I tried changing half-bytes, so 'DB' to 'DA' and stuff like that, also tried changing entire bytes, I made, in the overall, more than 30 different attempts to changing the OS (half-bytes!). All of them, Computer Link software said 'corrupted'.


Conclusion and Questions
Has any of you successfully changed anything in any of the OSs?
How come the Computer Link software be so good at detecting corruptions (Internet connection?)?.


My next experiment will be bit-changing, I'll open the binary of it, and change 1 bit in the code, then I'll see if Computer Link Software still states it as corrupted.

Is .tno the ti-nspire os?

The checksum makes sense, thanks.

"Not only a checksum, don't you also have to factor the 1024-bit signing keys?"

What is that?

The OS is signed with a 1024-bit key (that's what we've been complaining about since the Nspires first came out). You need to figure out the keys to successfully sign your own OS. An unsigned OS isn't accepted by the calc because the calc checks the signature.

@Stefen: Yup.

Ok, thanks.
(It isn't stefEn, it's stefan actually)

Edit: How can changing the 'name' of the os, change the os.