Well, probably something around a hundred worldwide

You seem to be underestimating things.

We're talking about CAS+ prototypes - not about ClickPad prototypes.

But this is mainly because we aren't putting much time in the device, because it's not that important (I mean, there are more important thing to do than spending hours on a prototype that almost nobody owns).

CAS+ aren't prototypes that allmost nobody owns.

And it's important to care about everyone.

Great! Did you dump it ?

No OS 2.01 yet?

I suppose you've allready installed OS 3.2, which has raised the minimal installable version to 3.1.0.392.
This is not cancelled when going back to OS 3.1 - so you cannot install the 3.1.0.1 dictionnaries anymore.

Just download the 3.1.0.392 dictionnaries which should install without any problem:
http://tiplanet.org/forum/archives_voir.php?id=6637 (CX-C CAS)
http://tiplanet.org/forum/archives_voir.php?id=6636 (non-CAS CX-C)

In a previous TI-Planet news, we figured out that there was a hardware difference between non-CAS TI-Nspire CX and TI-Nspire CX CAS.

Although both calculators are sharing the same screen board (which is the mainboard as it does include the ASIC and NAND chips but programmed differently), a FireBird_Color_MB_6422 we noticed that the keypad boards had different references:

• FireBird_Color_KB_EVT_4421 for the TI-Nspire CX CAS
  
• FireBird_Noncas_Color_KB_EVT_4421 for the non-CAS TI-Nspire CX

We were wondering what the interest of maintaining a separate production line for non-CAS TI-Nspire CX could be, since unlike previous models both keyboards are now the same on TI-Nspire CX.



To better understand what TI had in mind, let's just plug a TI-Nspire CX CAS screen board in a non-CAS TI-Nspire CX:
The TI-Nspire CX CAS OS doesn't want to start and shows you an "unrecognized keypad" error message, confirming that there is some hardware difference between the non-CAS CX and CX CAS keypad boards.



Let's also plug a non-CAS TI-Nspire CX screen board in a TI-Nspire CX CAS:
This time no error message, but the OS does not boot and the calculator enters a reboot loop.



All this is weird...

We could think to a protection against 'case switching' but it's not much harder to swith keypad boards after switching screen boards.

It might be intended to counter temporary or permanent non-CAS to CAs modifications through OSlauncher or hwMod, although they've never been runned successfully on TI-Nspire CX.

Or perhaps simply that this has been kept for strange compatibility reasons with non-CX Nspire models which had different keyboards.



Source:
http://tiplanet.org/forum/viewtopic.php?t=10390

We've been working a lot on TI-Nspire ClickPad prototypes, which revealed to be very interesting models.



On the one hand, a very small hardware difference made their NOR Flash chip writeable:

Thanks to this, we were able to reprogram the boot1 contained in this chip, turning prototypes into production models accepting the OS published by TI.



On the other hand, we noticed that the prototypes ASIC CAS/non-CAS flag wasn't set.

Thanks to this, we cound turn non-CAS TI-Nspire prototypes into TI-Nspire CAS.



It seemed obvious to us, that on production models, there was probably no way to reprogram the ASIC.



But, somebody (who apparently wants to remain anonymous) followed our work very seriously and decided to do the impossible: make NOR chips rewriteable on production TI-Nspire ClickPad!

Even if no flashing has been attempted yet to our knowledge, the NOR chip from this modified production TI-Nspire ClickPad now reports itself as writeable when asked for its properties through an Ndless program.



The Boot1 is the central piece in TI-Nspire models security.
It's the one to check Boot2 and diags checksums and RSA signatures before launching them or not.

Being able to reprogram the Boot1 means being able to run any original, modified or 3rd party diagnostic or boot2 image!

Those who think in the short term certainly have in mind installing a CAS OS on a non-CAS TI-Nspire, thanks to a modified or 3rd-party Boot2.

The others are probably allready thinking to installing Linux, thanks to the U-Boot launcher we dumped on some old TI-Nspire prototypes.



However, such mod if a comprehensive documentation is ever released for it, will only deal with TI-Nspire ClickPad models. TI-Nspire TouchPad have their NOR chip included in the ASIC: there is probably no way to open that chip without breaking everything.





Source:
http://tiplanet.org/forum/viewtopic.php?t=10389&lang=en

More information: (fragmented and incomplete so far)
http://tiplanet.org/forum/archives_voir.php?id=6835
http://www.cemetech.net/scripts/countdown.php?/text/production_clickpad_information.tar.gz&path=archives
http://ourl.ca/16358/305205 (point 3)
https://groups.google.com/forum/?fromgroups=#!topic/tinspire/GQJO45-kXyk (point 3)

I don't want to blame anyone here, but I updated the fxRemote package to build 26 (includes additional debug output) some time ago plus OS 2.01 and 2.02 backups for fx-9750GII calculators; and all of a sudden people find out there are OS 2.01.0700 ROMs around...

I was going to ask you if you had found out 2.01 backups for the fx-7400Gii.


The tutorial is not above the discovery/dumping of the 2.01 ROMs and I didn't pretend to have dumped them myself (I could have done it if I could find out the OS version before buying the calculator...). The tutorial is only about the update process.

But so, what do you want?
A public link to your package with the ROMs in the tutorial?
I'm not sure it's a good idea...

Such links should be kept private/secret as most as possible if we want them to remain valid to my advice.

Credits/thanks for the ROM dumping at the end of the tutorial?
No problem if I have your permission.
But I'm not sure it's a good idea either...


It's up to you anyway - I'll do as you wish