They might have heard of the downgrade protection being allready cracked...

They're going to release a much more closed 3.0 OS!

Great!

A warning message  in the TI-Nspire Computer Link would be nice...

TilP can't install 3.0!!!!

wtf...

I am really tempted to (safely) upgrade to see what the 3D graphs looks, but I don't want to risk anything going wrong...

Remove the boot2 3.0 from your TNC/TNO file using TNOC.
You won't have any poblem.

I've allready downgraded from 3.0 three times.

It's me again, for reporting my final tests.

This sucks about the anti-downgrade thing... I wonder if Nleash could be ported to 3.0...

The new anti-downgrade protection is different.
Nleash can't do anything against that.
The protection is related to the new 3.0 boot2.
So this boot2 will have to be removed anyway.
Unfortunately, up to now ExtendeD, Bsl and me couldn't come with a safe code to reflash the diagnostic software. So trying to reflash the boot2 won't work better...


So, I installed the full 3.0 OS (with 3.0 boot2).
Of course, I couldn't downgrade back to 2.1.

I removed the OS through the maintenance menu.
I couldn't install OS 2.1 either.

Here's the RS232 log by the way:
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

Then, I downgraded the boot2 to 1.4 through RS232.
And... I could  install OS 2.1.


My guess is that the 3.0 OS & 3.0 boot2 update codes are of course still checking the downgrade protection area, but also the boot2 version.
If a 3.0 boot2 is detected, any OS version below 3.0 is rejected.

This could have been a way of releasing the same OS file for both Nspire and Nspire CX calculators. This way, OSes older than 3.0 would have been forbidden on the CX because boot2 3.0 would have been preinstalled, but not on other Nspire which would have stayed with the older 1.4 boot2.
I really don't understand why they didn't change the minimal OS to 3.0 is the OS update files, not even for the Nspire CX.


So:

* If you have not updated yet:
- remove the 3.0 boot2 from the 3.0 OS with TNOC
- send the modified 3.0 OS
You can then downgrade whenever you want.

* If you have allready updated with the original 3.0 OS:
- remove the 3.0 OS through the maintenance menu (or it will reupdate the boot2 to 3.0 on the next successfull boot)
- downgrade the boot2 to 1.4 through RS232 (you can also send me the calculator )
You can now install the modified 3.0 OS, or 1.7-2.1 OSes.
To install older OSes, you'll have to use Nleash.
(yes, the other downgrade protection is still there... there are 2 downgrade protections with the 3.0 OS)


By the way as we can't use Goplat's emulator with the 3.0 boot2/OS yet, here's the complete 3.0 bootlog:

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

Quote from: critor on April 07, 2011, 06:33:48 pm

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.

Well, this solution is not perfect yet.
Because once the protection is installed, it cannot be undone easily up to now.

There will be many people who will trust their "update" dialog box before reading our news...

so am i stuck with a 3.0 calc forever with no hope for return?

Either you wait for Ndless 3.0 and a boot2 flashing program, which will probably take months/years...
Either you buy an RS232 interface (all informations in my posts about prototype Nspire calculators - it's not hard at all)
Either you send the bricked calculator to me.

I'm going to test if a boot2 downgrade does solve the problem.