It should also be noted that a new boot 2 version is present in these files. In addition, nspire_emu will not run the OS. :(it doesn't run the new boot ether...
As a closing note, it is probably best to hold off on upgrading the OS on an actual Nspire until further testing is done. As far as is known now, this OS very well might block downgrading/Ndless/countless other things.It is actually clearly stated at the download page that downgrading will not be possible...
Anybody analyzing the new downgrade protection?Of course.
It's not in the TNC/TNO header anymore...Not sure yet.
Hard-coded in the OS?
it does take up a 2 megs more which is ridiculous. but at least we can try to downgrade it
That's really too bad. Does System 3.0 add any more programming commands?
will Nleash work?
(just hoping)
will Nleash work?No. The downgrade protection has changed.
(just hoping)
yeah nope no document changes: the things that changes is you can complete the square (as if i needed that i couldve just made a function for it), 3d graphing so ti 89 users have nothing over the nspire anymore except programming, differential equations, stats and probs and finally you can do a lot more with series. which helps in calc bc.What nspire model are you using? CAS or basic, clickpad or touchpad?
Anybody analysing the new downgrade protection?
It's not in the TNC/TNO header anymore...
Hard-coded in the OS?
I think it does deserve a double-posting.
I just managed to upgrade and downgrade!!!
I've used:
- a TI-Nspire running boot2 1.4 (won't work with boot2 1.1)
- a modified 3.0 TNO file, with the new 3.0 boot2 removed
I upgraded to the 3.0 OS, which did boot correctly.
I then immediatly downgraded to the 2.1 OS which did boot correctly too.
Seems the new protection is related to the new boot2.
Just use TNOC to remove it before installing the OS.
Is it possible to downgrade boot2 on TI-Nspire calculators?
so critor is there a way to modify the boot2 so nspire 2.x or 1.x documents can work on the new os (3.0)?
no like to run os 2.x programs on os 3.0? like modify the boot2 to idk say run ndless on os 3.0? or is that not possible?
I think you should news, or edit the 1st post about the downgrade protection.
The TNOC way can only work if applied before the 3.0 upgrade.
Else, you'll have to buy an RS232 interface, or send the calculator to me.
critor, I've downloaded TNOC and mirrored it. :)
If you don't mind, I'll eventually also be mirroring all the OSes on TI-Bank as well. ;)
I think you should news, or edit the 1st post about the downgrade protection.
The TNOC way can only work if applied before the 3.0 upgrade.
Else, you'll have to buy an RS232 interface, or send the calculator to me.
I added it! Thank you for your tests, critor! :)
I guess TI didn't think we could beat our established record of about 2 weeks with Nleash. :P
so am i stuck with a 3.0 calc forever with no hope for return?
This sucks about the anti-downgrade thing... I wonder if Nleash could be ported to 3.0...
TI_OS_INSTALL_PRECHECK (5)
TI_OS_INSTALL_PRECHECK_OK (0)
TI_OS_INSTALL_PRECHECK (5)
TI_OS_INSTALL_VERIFYING_IMAGE (10)
IMAGE: verifying file "/tmp/TI-Nspire.tno"
TI_OS_INSTALL_VERIFYING_IMAGE incremental update (11)
TI_OS_INSTALL_VERIFYING_IMAGE incremental update (13)
TI_OS_INSTALL_INSTALLING_RESOURCES (15)
TI_OS_INSTALL_VERIFYING_IMAGE incremental update (17)
TI_OS_INSTALL_VERIFYING_IMAGE incremental update (19)
TI_OS_INSTALL_VERIFYING_IMAGE incremental update (21)
TI_OS_INSTALL_VERIFYING_IMAGE incremental update (23)
TI_OS_INSTALL_VERIFYING_IMAGE incremental update (25)
TI_OS_INSTALL_VERIFYING_IMAGE incremental update (27)
TI_OS_INSTALL_VERIFYING_IMAGE incremental update (29)
TI_OS_INSTALL_VERIFYING_IMAGE incremental update (31)
TI_OS_INSTALL_VERIFYING_IMAGE incremental update (33)
TI_OS_INSTALL_VERIFYING_IMAGE incremental update (35)
TI_OS_INSTALL_VERIFYING_IMAGE incremental update (37)
TI_OS_INSTALL_VERIFYING_IMAGE incremental update (39)
TI_OS_INSTALL_VERIFYING_IMAGE incremental update (41)
TI_OS_INSTALL_VERIFYING_IMAGE incremental update (43)
TI_OS_INSTALL_VERIFYING_IMAGE incremental update (45)
TI_OS_INSTALL_VERIFYING_IMAGE incremental update (47)
TI_OS_INSTALL_VERIFYING_IMAGE incremental update (49)
TI_OS_INSTALL_VERIFYING_IMAGE incremental update (51)
TI_OS_INSTALL_VERIFYING_IMAGE incremental update (53)
TI_OS_INSTALL_VERIFYING_IMAGE incremental update (55)
TI_OS_INSTALL_VERIFYING_IMAGE incremental update (55)
TI_OS_INSTALL_VERIFYING_IMAGE incremental update (59)
TI_OS_INSTALL_VERIFYING_IMAGE incremental update (61)
TI_OS_INSTALL_VERIFYING_IMAGE incremental update (63)
TI_OS_INSTALL_VERIFYING_IMAGE incremental update (65)
TI_OS_INSTALL_VERIFYING_IMAGE incremental update (67)
TI_OS_INSTALL_VERIFYING_IMAGE incremental update (69)
TI_OS_INSTALL_VERIFYING_IMAGE incremental update (71)
TI_OS_INSTALL_VERIFYING_IMAGE incremental update (73)
TI_OS_INSTALL_VERIFYING_IMAGE incremental update (75)
TI_OS_INSTALL_VERIFYING_IMAGE incremental update (77)
TI_OS_INSTALL_VERIFYING_IMAGE incremental update (79)
TI_OS_INSTALL_VERIFYING_IMAGE incremental update (81)
TI_OS_INSTALL_VERIFYING_IMAGE incremental update (83)
TI_OS_INSTALL_VERIFYING_IMAGE incremental update (85)
TI_OS_INSTALL_VERIFYING_IMAGE incremental update (87)
TI_OS_INSTALL_VERIFYING_IMAGE incremental update (89)
TI_OS_INSTALL_VERIFYING_IMAGE incremental update (91)
TI_OS_INSTALL_VERIFYING_IMAGE incremental update (93)
IMAGE: isImageBodyValid = false
TI_OS_INSTALL_VERIFYING_RESOURCE (95)
Deleting file [/tmp/TI-Nspire.tno]
TI_OS_INSTALL_FAILED
TI_OS_INSTALL_IMAGE_INVALID
Boot Loader Stage 1 (1.1.8916)
Build: 2007/4/23, 23:37:16
Copyright (c) 2006, 2007 Texas Instruments Incorporated
Using production keys
Last boot progress: 35
Clocks: CPU = 90MHz AHB = 45MHz APB = 22MHz
Available system memory: 37292
Checking for NAND: NAND Flash ID: ST Micro NAND256R3A
SDRAM memory test: Pass
Clearing SDRAM...Done.
Clearing SDRAM...Done.
Clearing SDRAM...Done.
Boot option: Normal
Loading BOOT2 software...
99%
BOOT1: loading complete (304 ticks), launching image.
Boot Loader Stage 2 (3.01.131)
Build: 2011/2/23, 11:34:31
Copyright (c) 2006-2010 Texas Instruments Incorporated
Using production keys
Clocks: CPU = 120MHz AHB = 60MHz APB = 30MHz
Checking for NAND: NAND Flash ID: ST Micro NAND256R3A
Initializing graphics subsystem.
Boot option: Normal
Initializing filesystem.
Datalight Reliance v2.10.1150
Copyright (c) 2003-2006 Datalight, Inc.
Datalight FlashFX Pro v3.00 Build 1358
Nucleus Edition for ARM9
Copyright (c) 1993-2006 Datalight, Inc.
Patents: US#5860082, US#6260156.
Filesystem ready.
Purging temporary files...
TI_OS_INSTALL_PRECHECK_OK (0)
Loading Operating System...
100%
BOOT2: loading complete (1521 ticks), launching image.
Beginning system initialization.
Clocks: CPU = 120 MHz AHB = 60 MHz APB = 30 MHz
Preparing file system. This takes a while...
POSIX layer initialized.
POSIX "NULL" device initialized.
POSIX "CONSOLE" device initialized.
Datalight Reliance v2.10.1150
Copyright (c) 2003-2006 Datalight, Inc.
Datalight FlashFX Pro v3.00 Build 1358
Nucleus Edition for ARM9
Copyright (c) 1993-2006 Datalight, Inc.
Patents: US#5860082, US#6260156.
POSIX file system initialized.
File system ready.
* P3 mode battery door detection
System build date: Mar 24 2011, 18:29:28
Available memory: 15024228 bytes
Purging temporary files...
Launching system...
Created Execution Context
NavNet Ready.
START TI_LOCALE_initializeDefaultLocale.....
DEFAULT LOCALE is en.....
Found a Match: en(MD) and en
END TI_LOCALE_initializeDefaultLocale.....
IME: non-ALPHA key pressed
IME: non-ALPHA key pressed
IME: non-ALPHA key pressed
IME: non-ALPHA key pressed
IME: non-ALPHA key pressed
Wireless Status:WCM_Info_GetStatus():SUCCESS
Network Status: SLED is Not Attached
Are the actual OS images for the CX any different?
Hey, they upped the clock speed!
I am really tempted to (safely) upgrade to see what the 3D graphs looks, but I don't want to risk anything going wrong...
FWIW, I did on my nspire. I haven't even figured out how to make a 3d graph.
It's probably under graph modes.
Shouldn't nDoom be the same?
If I had to guess, I would say open a graph page, press menu, and then go to graph type and choose 3D. This might not be right, though, as it is based on experience from older OSes.Thanks, when I didn't find it there I stopped looking.
Did anyone try to launch Nleash or the Ndless installer?
I hope you didnt get a "document not supported" message, which would mean TI has fixed things...
TilP can't install 3.0!!!! :(
hey you allI always wondered how you did that as well, even though I don't even own a Nspire.
@critor: can you plz create a topic explaining how to connect the nspire to pc through the rs232?
cheers
TilP can't install 3.0!!!! :(:(
They probably left the nleash-circumvented protection by virtue of not bothering to remove it.
Wouldn't that mean that the overflow is still there(and as such, a potiental way for ndless to be ported)?Well, no ;)
Spoiler For Spoiler:
Indeed, but that would be so un-TI of TI ;)It was un-TI of them to say that you could downgrade in the link before downloading too...
I removed boot2 and updated my TI-nspire CAS Touchpad to OS 3.0, but when I opened the status menu (5-4 on homescreen) it told me, it runs only on AAA Batteries.
This is in my calc:
http://education.ti.com/educationportal/sites/US/productDetail/us_nspire_battery.html (http://education.ti.com/educationportal/sites/US/productDetail/us_nspire_battery.html)
and it does not show up, as it did in OS 2.x, so I did a downgrade (for obvious reasons).
Is the rechargable-battery-detection in boot2?
TIA
TI-Nspire.tnc 3.1.1753 71252174 0
TI-Nspire.tnc 3.1.1753 7125217 0
Maybe they decided that it was too cruel to us. :P
No, they might have found a serious bug that they want to fix now.
Did anyone try to launch Nleash or the Ndless installer?
I hope you didnt get a "document not supported" message, which would mean TI has fixed things...
3.0 OSes are back.I checked both the .cer's and the whole .tnc whit an hexeditor, result: identical.
We should check if anything has been changed...
3.0 OSes are back.I checked both the .cer's and the whole .tnc whit an hexeditor, result: identical.
We should check if anything has been changed...
1.7 is still down too. :(
http://education.ti.com/calculators/downloads/US/Software/Find-OS
Yes... They removed the 1.7.2741 (Ndlessable) OS, and replaced it with the 1.7.1 OS which doesn't work with Ndless.Wow.. so they are providing an older OS 1.7 just to make sure ndless doesn't run on it...
I don't see why they couldn't include boot2 1.4 in 2.0, since it's not exactly hard to do so.
they are dlighted at how education and wonderful the nspire is :D
A permanent root exploit for Nucleus RTOS? That would rock.The only way you can call Nucleus functions is if you're already running code, so this doesn't make much sense.
Something odd: The OS version for three is 3.0.1.xxxx, but the header lists it as 3.1.xxxx
Ya know, this looks really funny from a non-calc dev viewpoint - how did 3.0 drop down to 1.7?
And where's 2.0? Yup, TI's looking like a fool with their pants on the ground. ;)
I wonder what the TI Nspire Google group's reactions are... :P
IMAGE: verifying file "/tmp/TI-Nspire.nosamples.tno"
IMAGE: header mismatch
TI_OS_INSTALL_VERIFYING_RESOURCE (95)
Deleting file [/tmp/TI-Nspire.nosamples.tno]
TI_OS_INSTALL_FAILED
TI_OS_INSTALL_IMAGE_INVALID
IMAGE: verifying file "/tmp/TI-Nspire.nosamples.tno"
IMAGE: BOOT2 upgrade required
They probably wish OS 2.71MP became a reality. O.O (well... without the bugs, that is)
3.0 TNC/TNO must be different than previous ones.Based on reverse engineering the two versions of boot2, here's the explanation of this:
- it's impossible to install them on OSes 1.1-1.3
- it's impossible to install them on an Os-less boot2 1.1
You get in both cases:Code: [Select]IMAGE: verifying file "/tmp/TI-Nspire.nosamples.tno"
IMAGE: header mismatch
TI_OS_INSTALL_VERIFYING_RESOURCE (95)
Deleting file [/tmp/TI-Nspire.nosamples.tno]
TI_OS_INSTALL_FAILED
TI_OS_INSTALL_IMAGE_INVALID
- it's impossible to install them on 1.4-2.1 oses running over a 1.1 boot2:Code: [Select]IMAGE: verifying file "/tmp/TI-Nspire.nosamples.tno"
IMAGE: BOOT2 upgrade required
So, it seems the work that hasn't been done with OS 2.1, has finally been done with OS 3.0. Instead of permanently freezing your calculator like OS 2.1, OS 3.0 just doesn't install. Note this major bug was reported by TI-Bank in july 2010. It took them 9 months, and many TI-Nspire calculators were bricked during that time...I wouldn't call that "bricking"; it was easily fixed using the maintenance menu and OS 1.7 or 2.0.
QuoteSo, it seems the work that hasn't been done with OS 2.1, has finally been done with OS 3.0. Instead of permanently freezing your calculator like OS 2.1, OS 3.0 just doesn't install. Note this major bug was reported by TI-Bank in july 2010. It took them 9 months, and many TI-Nspire calculators were bricked during that time...I wouldn't call that "bricking"; it was easily fixed using the maintenance menu and OS 1.7 or 2.0.
what does os 3.0 even offer thats majorly different? nothing really at all haha
Yes, they would.