Actually we might not be able to help much due to new forum policies (added after many complains from members of another TI forum and to avoid more inter site drama) but if you e-mail cfxm he might be able to help you. I think an issue is that you got a new generation 9750G with the SH4 processors, but cfxm apparently knows the answer

Might we know what kind of complaints would be related to the 9750Gii -> 9860Gii transformation?
This is not related to cheating to my advice.

Because I'm now wondering if I should stop newsing here on Linux and Boot1 flashing on the TI-Nspire for example. Many things have been attempted successfully this week... It would be sad not to tell you the end of the story.

And for some reason, they have every image once for each language

And there are similar wastes of space on the handhelds.
But fotunately, nCleaner does deal with that

@critor, can you see in what format the image is saved? Because this means some kind of format is natively supported, or am i wrong here?

It's just raw R5G6B6 top-down without a header.
That's simply the native format for the screen, which I'm using in mViewer.

Which image package?

TI-Nspire TouchPad, CX and CM come with a diagnostic software which can be launched by holding down before a reboot.

The EVT1 TI-Nspire Color prototype we discovered in a previous news is no exception:

This 3.0.0.102 version was compiled on 24th september 2010, and introduces itseld as a "NSC EVT1 Version3 Diag Menu".



Development Diags softwares are usually much more interesting than production Diags softwares, as they often include additionnal options.

Let's go to the "2. LCD" menu and launch the "LCD Pixel Test":

Nothing different from production Diags are you going to say?
On a production Diags, the test would end now, yes...

But on this prototype there's an additionnal screen:

Yes, there is an image hard coded in this prototype developement Diags, which was then removed on production Diags.

For information, it's a photo from the Aspen hot air balloon festival (Colorado) and here is it:

Strangely, the photo seems to be from september 2010 too, exactly like the Diags build date. Was one of the TI-Dallas Nspire CX developpers coming back from Colorado at that time?


The diagnostics has been dumped. If you flash it on your production TI-Nspire CX, your Boot1 won't accept to run it.

But you can run it without installation using my nsNandMgr tool!





Source:
http://tiplanet.org/forum/viewtopic.php?p=133920&lang=en

How? You transmitted it to the calc

Just try on a normal TI-Nspire CX and tell me if you manage to do this and how.

this may be a dumb question, but is the NspireColor a prototype for the CX, or for a future version of the nspire?

TI-Nspire Color is the name of the TI-Nspire CX prototypes.

I never knew about the Nspire color prototype.

Then you missed some news two months ago:
http://ourl.ca/17425

The right CAS+ option is /MP.
nspire_emu /1=your_casp_boot1 /PB=your_casp_boot2 /PO=your_casp_os /MP

For your first try, you should use Boot1/Boot2 1.0.526 and OS 1.0.529/1.0.554.
It works.

Older Boot2 are using a different format for OS images preloaded in memory or sent through RS232.
As it is not easy on the emulator side to guess which format is the right one, the /PO parameter uses the format suitable for the latest and more common CAS+ Boot2 (1.0.526).

For older Boot2 versions, you'll need to remove the /PO parameter, hexedit your OSes, add a specific header, and send the file using the Xmodem emulation.

For information:

boot2 EVT2 versions:
* preload format: 0x18 bytes, followed by contents of phoenix.img
+ 0x00: nul-terminated string "***PRELOAD_IMAGE***"
+ 0x14: phoenix.img size (big-endian)
* OS sent by XMODEM has no header (just phoenix.img)
* preload images in flash have no ECC

boot2 1.0.491:
* preload format: 0x1C bytes, followed by contents of manifest_img and
phoenix.img
+ 0x00: nul-terminated string "***PRELOAD_IMAGE***"
+ 0x14: manifest_img size (big-endian)
+ 0x18: phoenix.img size (big-endian)
* OS sent by XMODEM includes preload header
* preload images in flash have no ECC

boot2 1.0.526:
* preload format: 0x20 bytes, followed by contents of manifest_img and
phoenix.img
+ 0x00: nul-terminated string "***PRELOAD_IMAGE***"
+ 0x14: bytes 55 F0 01 55
+ 0x18: manifest_img size (big-endian)
+ 0x1C: phoenix.img size (big-endian)
* OS sent by XMODEM includes preload header
* preload images in flash have ECC in the "extra" part of each flash page

In the past, many NAND related Ndless tools were released for the TI-Nspire ...

• to reprogram the boot2:
  
  • Flash boot2 Prototype (for Ndless 1.1 and 1.2 prototypes)
  • FlashBoot2 (for Ndless 1.7 and 2.0)
  • FlashBoot2CX (for Ndless 3.1 on Nspire CX)
• to reprogram the Diagnostics software:
  
  • FlashDiags (for Ndless 1.7 and 2.0)
  • FlashDiagsCX (for Ndless 3.1 on Nspire CX)
• to remove the minimum installable OS version downgrade protection:
  
  • Nleash (for OS 1.7 and 2.1)
  • DowngradeFix (for Boot2 1.4)
  • DowngradeCX 3.1 (for Ndless 3.1 on Nspire CX)
• to launch Boot2 images without installing them:
  
  • Boot2Launcher (for Ndless 1.7 and 2.0)
• to launch Diagnostics software images without installing them:
  
  • DiagsLauncher (for Ndless 1.7 and 2.0)
• to dump the boot2 and Diagnostics software:
  
  • Diagnostics software dumper (for Ndless 1.1)
  • Polydumper Prototypes (for prototypes Ndless 1.1 and 1.2)
  • Polydumper (for Ndless 1.1, 1.3, 1.4, 1.7, 2.0 and 3.1)
• to change the TI-Nspire type(CAS / non-CAS):
  
  • hwMod (for Ndess 3.1)

And this list is a problem in itself, because this wide range of NAND tools is very difficult to keep up to date.
Some tools have been updated to Ndless 3.1 for TI-Nspire CX, but not for TI-Nspire ClickPad / TouchPad for exemple. (FlashBoot2CX, FlashDiagsCX, DowngradeCX)
Other tools have never been updated to Ndless 3.1! (Boot2Launcher, DiagsLauncher)



I had already started to sort things by releasing my universal dumping tool, Polydumper, compatible with all TI-Nspire models and compiled for every released Ndless version from 1.1 to 3.1!



Today I'm at it again with nsNandMgr!

nsNandMgr is destined to become the Swiss Army knife of the NAND memory on the TI-Nspire. It includes all the functionalities of the tools mentioned above and even more!

It allows you to:

• change the type of your TI-Nspire (CAS or non-CAS) in the case where the used ASIC chip is generic (ClickPad prototypes from 2007)
• dump the Boot2
• flash a Boot2 image
• launch a Boot2 image without installation
• dump the Diagnostics software
• flash a Diagnostics software image
• launch a Diagnostics software image without installation
• remove the minimum installable OS version downgrade protection
• change the Boot2/Diags boot order
• delete the Boot Data area
• delete the Diags Data area

Published under a free license of course, the critic code is centralized with only a total of two NAND writing instructions in the whole program for all mentionned functionnalities!
It should be easy to maintain for future versions.

nsNandMgr has also been designed to check the Boot2 and Diags images before flashing or running them, in order to prevent some unintended accidents.



Let's try to understand the possibilities with examples. Here's a TI-Nspire CX CAS:

• As the ASIC is not generic (Nspire CAS), it is not possible to change the Nspire type.
• It comes with a compressed CX Boot2 3.1.0.16, and the file '/ndless/boot2.img' contains a compressed CX Boot2 3.0.1.131. It is therefore possible to run this image, or even flash it performing a Boot2 downgrade.
• It comes with an uncompressed CX Diags 3.1.0.20, but here the '/ndless/diags.img file contains an uncompressed CM Diags 3.1.0.21. As the Boot1 will refuse this TI-Nspire CM Diags, nsNandMgr won't let you flash it. But as hardware is similar, it will let you run it.
• The minimum installable OS version is 3.0.2.1785 and the boor order is Boot2 then Diags upon failure.

So just a few keystrokes and you perform a Boot2 downgrade from 3.1 to 3.0.1, the removal of the OS antidowngrade protection, and the launching of the TI-Nspire CM diagnostic software!



Now let's take a non-CAS TI-Nspire ClickPad:

• As the ASIC is not generic (Nspire non-CAS), it is not possible to change the Nspire type.
• It comes with a compressed Boot2 3.0.1.131, and the file '/ndless/boot2.img' contains a compressed Boot2 1.4.1571. It is therefore possible to run this image, or even flash it performing a Boot2 downgrade.
• It comes with an uncompressed Diags 1.1.9266, and the file '/ndless/diags.img contains an uncompressed development Diags 1.1.7383. Although the current nsNandMgr will let you flash this prototype Diags, Boot1 will refuse it. But you can still run it from nsNandMgr.
• The minimum installable OS version is 3.0.2.1785 and the boor order is Boot2 then Diags upon failure.

So just a few keystrokes and you perform a Boot2 downgrade from 3.1 to 1.4, the removal of the OS antidowngrade protection, and the launching of the TI-Nspire prototype diagnostic software!



Finally, let's take a non-CAS TI-Nspire ClickPad prototype:

• As the ASIC is generic, it is possible to change the Nspire type to CAS.
• It comes with a compressed Boot2 1.4.1571, and the file '/ndless/boot2.img' contains a compressed CX Boot2 3.0.1.131. As hardware is uncompatible,  nsNandMgr won't let you flash or run it.
• It comes with an uncompressed Diags 1.3.2406, and the file '/ndless/diags.img contains an uncompressed Lab Cradle Diags 3.0.1658. As the Boot1 will refuse this TI-Nspire Lab Cradle Diags, nsNandMgr won't let you flash it. But as hardware is similar, it will let you run it.
• The minimum installable OS version is 3.0.2.1785 and the boor order is Boot2 then Diags upon failure.

So just a few keystrokes and you perform a TI-Nspire to TI-Nspire CAS transformation and the removal of the OS antidowngrade protection.






Source & download:
http://tiplanet.org/forum/viewtopic.php?p=133849&lang=en

Seems you're directly connecting your TI-Nspire to you computer DB9/COM port.
That won't work.

The TI-Nspire uses the TTL protocol, which has different voltages level and polarity than the RS232 protocol.

You need some interface between the TI-Nspire and the computer to convert the voltages.

The easiest way is using a TTL/USB interface:


They're usually based on FTDI chips.