0 Members and 3 Guests are viewing this topic.
Yes, the two are signed with different keys. :(
Quote from: apcalc on March 23, 2011, 09:01:12 pmYes, the two are signed with different keys. Darn.Please pardon my ignorance, it will be a week or two before I get my Nspire basic (v2 with touchpad and ti-84 emu [I wanted an Nspire CAS, but this was nearly new and $60. A CAS would have cost twice as much.]).Are boot1 and boot2 stored on the same NAND flash rom?If so, is there any chance of using Ndless to flash an OS with an invalid signature and a boot2 to load it?Or would I need to re-flash the NAND directly?
Yes, the two are signed with different keys.
So... boot1 might be changeable, boot2 is not. Flashing the NAND with Ndless is very unstable, and the reason has not yet been discovered. Do you think that the low success rate was due to some form of protection? Is it possible to see how the OS re-flashes the NAND, and possibly modify that routine if it checks the OS image signature?Thanks for all the info! I really enjoy learning about systems like this.
Quote from: mikehill2003 on March 23, 2011, 10:04:11 pmSo... boot1 might be changeable, boot2 is not. Flashing the NAND with Ndless is very unstable, and the reason has not yet been discovered. Do you think that the low success rate was due to some form of protection? Is it possible to see how the OS re-flashes the NAND, and possibly modify that routine if it checks the OS image signature?Thanks for all the info! I really enjoy learning about systems like this.The other way around. Although boot1 might be erasable, modifiable would be more difficult. And no, I don't think it's possible to see how the OS does it, or if it is, I don't think it's modifiable. It might be, though.
Quote from: apcalc on March 23, 2011, 09:01:12 pmYes, the two are signed with different keys. Actually, they are signed with the same key. The reason you cannot use a TI-Nspire CAS OS on the TI-Nspire or vice versa is because for an OS to validate:There must be an 8010 field present which matches the first two characters of the Product ID, which are stored in NAND flash (but don't bother trying to change it, because of the other protection described next)The 80E0 field must contain a byte matching a part of the value read from address 0x900A0028/0x900A002C (presumably, this is an 8 byte ROM inside the ASIC and cannot be changed)Changing these fields in the OS image will mean the signature isn't valid and the OS won't load.